At present interrupt routing is set up from arch_misc_init(). We can do it
a little later instead, in interrupt_init().
This removes the manual pirq_init() call. Where the platform does not have
an interrupt router defined in its device tree, no error is generated. Some
platforms do not have this.
On Mon, Dec 14, 2015 at 2:05 PM, Bin Meng wrote:
> On Tue, Dec 1, 2015 at 12:47 PM, Simon Glass wrote:
>> At present interrupt routing is set up from arch_misc_init(). We can do it
>> a little later instead, in interrupt_init().
>>
>> This removes the manual pirq_init() call. Where the platform d
On Tue, Dec 1, 2015 at 12:47 PM, Simon Glass wrote:
> At present interrupt routing is set up from arch_misc_init(). We can do it
> a little later instead, in interrupt_init().
>
> This removes the manual pirq_init() call. Where the platform does not have
> an interrupt router defined in its device
At present interrupt routing is set up from arch_misc_init(). We can do it
a little later instead, in interrupt_init().
This removes the manual pirq_init() call. Where the platform does not have
an interrupt router defined in its device tree, no error is generated. Some
platforms do not have this.
4 matches
Mail list logo
