diff options
| author | Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl> | 2019-08-02 17:12:34 +0200 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2019-08-30 23:20:31 +0200 |
| commit | 7ac60446327ac4e3fa11f11d0bfe884119bf1ae4 (patch) | |
| tree | f7713906bb53323844c5ebaf6699111162a86563 /package/libs/libusb-compat | |
| parent | 9d1cd9d098946c31d584bb487cd79b365f269182 (diff) | |
| download | upstream-7ac60446327ac4e3fa11f11d0bfe884119bf1ae4.tar.gz upstream-7ac60446327ac4e3fa11f11d0bfe884119bf1ae4.tar.bz2 upstream-7ac60446327ac4e3fa11f11d0bfe884119bf1ae4.zip | |
ar71xx: WNR2200: remove redundant GPIO for WLAN LED
Without this patch, an extra entry appears for AR9287 GPIO
that duplicates WLAN LED but in fact drives nothing:
gpiochip1: GPIOs 502-511, ath9k-phy0:
gpio-502 ( |netgear:blue:wlan ) out hi
gpio-503 ( |netgear:amber:test ) out hi
gpio-504 ( |netgear:green:power ) out lo
gpio-505 ( |rfkill ) in hi
gpio-507 ( |wps ) in hi
gpio-508 ( |reset ) in hi
gpio-510 ( |ath9k-phy0 ) out hi <===!
The pin pointed above is default LED GPIO (8) for AR9287.
For WNR2200 it is not connected anywhere - pin 0 drives blue WLAN
LED instead - but initialization code is missing that information.
This fix calls ap9x_pci_setup_wmac_led_pin() function at device
setup, forcing WLAN LED pin to be 0 and removing redundant entry.
Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
Diffstat (limited to 'package/libs/libusb-compat')
0 files changed, 0 insertions, 0 deletions