diff options
| author | Mathias Kresin <dev@kresin.me> | 2018-12-07 09:42:09 +0100 |
|---|---|---|
| committer | Mathias Kresin <dev@kresin.me> | 2019-02-10 17:59:18 +0100 |
| commit | d997712c71eb281b9aab3c73b39b8deae2b7d946 (patch) | |
| tree | 2d742cb0fd98c994d84f0a90c2e082cc29088930 /package/kernel/brcm2708-gpu-fw | |
| parent | 9b14c7d3d1fb7666a9d75373b87fb8c8179ef21c (diff) | |
| download | upstream-d997712c71eb281b9aab3c73b39b8deae2b7d946.tar.gz upstream-d997712c71eb281b9aab3c73b39b8deae2b7d946.tar.bz2 upstream-d997712c71eb281b9aab3c73b39b8deae2b7d946.zip | |
ath9k: register GPIO chip for OF targets
This partitialy reverts commit f506de2cdaf9.
Registering the GPIO chip without a parent device completely breaks the
ath9k GPIOs for device tree targets.
As long as boards using the devicetree don't have the gpio-controller
property set for the ath9k node, the unloading of the driver works as
expected.
Register the GPIO chip with the ath9k device as parent only for OF
targets to find a trade-off between the needs of driver developers and
the broken LEDs and buttons seen by users.
Fixes: FS#2098
Signed-off-by: Mathias Kresin <dev@kresin.me>
(cherry picked from commit d35f2a5565fc51fb277f72a8565c871ce1785588)
Diffstat (limited to 'package/kernel/brcm2708-gpu-fw')
0 files changed, 0 insertions, 0 deletions