Configure interrupt on ARM when mapped

[zbb]

Summary

Do interrupt configuration as soon as is being mapped.

Submitted by: Wojciech Macek <[e-mail]>
Obtained from: Semihalf

[imp]

This is likely to cause bumps / races that aren't in the code. Thankfully, most of these aren't that large and are easy to manage.

sys/arm/arm/intr.c

122

extra braces

[• ian]

I think this is completely wrong and the interrupt needs to be configured when it is activated, not when it is parsed/decoded. Consider for example a gpio pin interrupt... we wouldn't want to mess with the pin state while the fdt data is being parsed because that data could refer to a possible configuration which is never going to be activated, and the actual use of the pin in the configuration that is active could be something else (not even related to interrupts).

[mmel]

From intrng: Each interrupt controller gets FDT(property) data in his decode fdt() routine.
And it is entirely his responsibility, if he stores and uses it, immediately or later.
Note: In theory, FDT data may contain more information than just polarity and triggering

[zbb]

I'm closing this. Corresponding issue will be resolved in the platform code.