diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2019-10-17 08:08:20 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-10-17 08:08:20 -0700 |
| commit | 7801158f83fc90cbe2d5cceac6ef58a4a6cf2d33 (patch) | |
| tree | 0e33e6998dd6e13824d64b0a74869fe180d548fa /drivers/leds | |
| parent | bc88f85c6c09306bd21917e1ae28205e9cd775a7 (diff) | |
| parent | 75e99bf5ed8fa74bc80d693d8e0a24eeaa38202b (diff) | |
| download | linux-7801158f83fc90cbe2d5cceac6ef58a4a6cf2d33.tar.bz2 | |
Merge tag 'gpio-v5.4-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio
Pull GPIO fixes from Linus Walleij:
"The fixes pertain to a problem with initializing the Intel GPIO
irqchips when adding gpiochips.
Andy fixed it up elegantly by adding a hardware initialization
callback to the struct gpio_irq_chip so let's use this. Tested and
verified on the target hardware"
* tag 'gpio-v5.4-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio:
gpio: lynxpoint: set default handler to be handle_bad_irq()
gpio: merrifield: Move hardware initialization to callback
gpio: lynxpoint: Move hardware initialization to callback
gpio: intel-mid: Move hardware initialization to callback
gpiolib: Initialize the hardware with a callback
gpio: merrifield: Restore use of irq_base
Diffstat (limited to 'drivers/leds')
0 files changed, 0 insertions, 0 deletions