RE: [PATCH v2 1/3] target/nios2: Move IIC code into CPU object proper

2020-11-30 Thread Wu, Wentong
On Monday, November 30, 2020 5:54 PM, Peter Maydell wrote: > On Mon, 30 Nov 2020 at 05:41, Wu, Wentong wrote: > > Reviewed and tested. > > Thanks! Can I put that in as Reviewed-by/Tested-by lines? Sure and my pleasure, thanks Peter! > > -- PMM

Re: [PATCH v2 1/3] target/nios2: Move IIC code into CPU object proper

2020-11-30 Thread Philippe Mathieu-Daudé
On 11/29/20 6:40 PM, Peter Maydell wrote: > The Nios2 architecture supports two different interrupt controller > options: > > * The IIC (Internal Interrupt Controller) is part of the CPU itself; >it has 32 IRQ input lines and no NMI support. Interrupt status is >queried and controlled vi

Re: [PATCH v2 1/3] target/nios2: Move IIC code into CPU object proper

2020-11-30 Thread Peter Maydell
On Mon, 30 Nov 2020 at 05:41, Wu, Wentong wrote: > Reviewed and tested. Thanks! Can I put that in as Reviewed-by/Tested-by lines? -- PMM

RE: [PATCH v2 1/3] target/nios2: Move IIC code into CPU object proper

2020-11-29 Thread Wu, Wentong
On Monday, November 30, 2020 1:40 AM, Peter Maydell wrote: > The Nios2 architecture supports two different interrupt controller > options: > > * The IIC (Internal Interrupt Controller) is part of the CPU itself; >it has 32 IRQ input lines and no NMI support. Interrupt status is >queried

[PATCH v2 1/3] target/nios2: Move IIC code into CPU object proper

2020-11-29 Thread Peter Maydell
The Nios2 architecture supports two different interrupt controller options: * The IIC (Internal Interrupt Controller) is part of the CPU itself; it has 32 IRQ input lines and no NMI support. Interrupt status is queried and controlled via the CPU's ipending and istatus registers. * The