summaryrefslogtreecommitdiff
path: root/lib/lz4
diff options
context:
space:
mode:
authorLinus Walleij <linus.walleij@linaro.org>2015-02-18 17:12:18 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-03-25 15:04:32 +0100
commit7085a7401ba54e92bbb5aa24d6f428071e18e509 (patch)
tree5945f68e6efa24d2bec09c1f7f53f29e5c8a9fde /lib/lz4
parent13fcffbbdec4e4863a9a9c7792b821cd6d363a8f (diff)
drivers: platform: parse IRQ flags from resources
This fixes a regression from the net subsystem: After commit d52fdbb735c36a209f36a628d40ca9185b349ba7 "smc91x: retrieve IRQ and trigger flags in a modern way" a regression would appear on some legacy platforms such as the ARM PXA Zylonite that specify IRQ resources like this: static struct resource r = { .start = X, .end = X, .flags = IORESOURCE_IRQ | IORESOURCE_IRQ_HIGHEDGE, }; The previous code would retrieve the resource and parse the high edge setting in the SMC91x driver, a use pattern that means every driver specifying an IRQ flag from a static resource need to parse resource flags and apply them at runtime. As we switched the code to use IRQ descriptors to retrieve the the trigger type like this: irqd_get_trigger_type(irq_get_irq_data(...)); the code would work for new platforms using e.g. device tree as the backing irq descriptor would have its flags properly set, whereas this kind of oldstyle static resources at no point assign the trigger flags to the corresponding IRQ descriptor. To make the behaviour identical on modern device tree and legacy static platform data platforms, modify platform_get_irq() to assign the trigger flags to the irq descriptor when a client looks up an IRQ from static resources. Fixes: d52fdbb735c3 ("smc91x: retrieve IRQ and trigger flags in a modern way") Tested-by: Robert Jarzmik <robert.jarzmik@free.fr> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/lz4')
0 files changed, 0 insertions, 0 deletions