Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-17 Thread Damien Hedde
On 8/17/21 10:25 AM, Luc Michel wrote: > On 10:33 Thu 12 Aug , Peter Maydell wrote: >> Currently we implement the RAS register block within the NVIC device. >> It isn't really very tightly coupled with the NVIC proper, so instead >> move it out into a sysbus device of its own and have the to

Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-17 Thread Luc Michel
On 10:33 Thu 12 Aug , Peter Maydell wrote: > Currently we implement the RAS register block within the NVIC device. > It isn't really very tightly coupled with the NVIC proper, so instead > move it out into a sysbus device of its own and have the top level > ARMv7M container create it and map it

Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-16 Thread Peter Maydell
On Sun, 15 Aug 2021 at 18:30, Philippe Mathieu-Daudé wrote: > > +Peter/David > > On 8/12/21 11:33 AM, Peter Maydell wrote: > > Currently we implement the RAS register block within the NVIC device. > > It isn't really very tightly coupled with the NVIC proper, so instead > > move it out into a sysb

Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-16 Thread David Hildenbrand
On 15.08.21 19:30, Philippe Mathieu-Daudé wrote: +Peter/David On 8/12/21 11:33 AM, Peter Maydell wrote: Currently we implement the RAS register block within the NVIC device. It isn't really very tightly coupled with the NVIC proper, so instead move it out into a sysbus device of its own and hav

Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-15 Thread Philippe Mathieu-Daudé
+Peter/David On 8/12/21 11:33 AM, Peter Maydell wrote: > Currently we implement the RAS register block within the NVIC device. > It isn't really very tightly coupled with the NVIC proper, so instead > move it out into a sysbus device of its own and have the top level > ARMv7M container create it a

Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-12 Thread Alistair Francis
On Thu, Aug 12, 2021 at 7:34 PM Peter Maydell wrote: > > Currently we implement the RAS register block within the NVIC device. > It isn't really very tightly coupled with the NVIC proper, so instead > move it out into a sysbus device of its own and have the top level > ARMv7M container create it a

Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-12 Thread Peter Maydell
On Thu, 12 Aug 2021 at 12:08, Alexandre IOOSS wrote: > > > > On 8/12/21 11:33 AM, Peter Maydell wrote: > > Currently we implement the RAS register block within the NVIC device. > > It isn't really very tightly coupled with the NVIC proper, so instead > > move it out into a sysbus device of its own

Re: [PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-12 Thread Alexandre IOOSS
On 8/12/21 11:33 AM, Peter Maydell wrote: Currently we implement the RAS register block within the NVIC device. It isn't really very tightly coupled with the NVIC proper, so instead move it out into a sysbus device of its own and have the top level ARMv7M container create it and map it into mem

[PATCH for-6.2 01/25] arm: Move M-profile RAS register block into its own device

2021-08-12 Thread Peter Maydell
Currently we implement the RAS register block within the NVIC device. It isn't really very tightly coupled with the NVIC proper, so instead move it out into a sysbus device of its own and have the top level ARMv7M container create it and map it into memory at the right address. Signed-off-by: Pete