On 06/23/2014 08:48 AM, Rob Herring wrote:
On Tue, Jun 17, 2014 at 5:51 PM, Guenter Roeck <[email protected]> wrote:
Commits 9ec36ca (of/irq: do irq resolution in platform_get_irq)
and ad69674 (of/irq: do irq resolution in platform_get_irq_byname)
change the semantics of platform_get_irq and platform_get_irq_byname
to always rely on devicetree information if devicetree is enabled
and if a devicetree node is attached to the device. The functions
now return an error if the devicetree data does not include interrupt
information, even if the information is available as platform resource
data.
This causes mfd client drivers to fail if the interrupt number is
passed via platform resources. Therefore, if of_irq_get fails, try
platform_get_resource as method of last resort. This restores the
original functionality for drivers depending on platform resources
to get irq information.
Cc: Russell King <[email protected]>
Cc: Rob Herring <[email protected]>
Cc: Tony Lindgren <[email protected]>
Cc: Grant Likely <[email protected]>
Cc: Grygorii Strashko <[email protected]>
Signed-off-by: Guenter Roeck <[email protected]>
Acked-by: Rob Herring <[email protected]>
Greg should take this for 3.16.
Wound be great. In the meantime, I asked for the da9055 code to be re-tested,
since I suspect that it may be affected. There may be others, but I don't have
the time to track it all down.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
