diff options
| author | Stijn Tintel <stijn@linux-ipv6.be> | 2018-06-22 14:42:20 +0300 |
|---|---|---|
| committer | Mathias Kresin <dev@kresin.me> | 2018-06-25 22:00:05 +0200 |
| commit | 34e22653ac18b6ac7fd368ca47625f665808067f (patch) | |
| tree | e9ed4fac3645bdaf7aea836a79e18cb7bd1c9ce4 /tools/firmware-utils/src/mkporayfw.c | |
| parent | 60deb3cdef4ac50a7d0fe9964a0f4a55aca1567e (diff) | |
| download | upstream-34e22653ac18b6ac7fd368ca47625f665808067f.tar.gz upstream-34e22653ac18b6ac7fd368ca47625f665808067f.tar.bz2 upstream-34e22653ac18b6ac7fd368ca47625f665808067f.zip | |
mac80211: enable ath10k LED support by default
Commit 61d57a2f88b90ba951012e66c7c6fae9234c97b4 adds ath10k LED
support, but doesn't add an option to actually enable it.
After enabling this option, a LED named ath10k-phy0 appears in sysfs,
and a trigger can be assigned to it. Since 60deb3cdef4a the default set
trigger is the tpt one.
Enable it by default, as most devices using ath10k chips shouldn't be
severely space-constrained. There are likely many devices that can
benefit from having it enabled, like my testing device.
Before:
text data bss dec hex filename
245311 8899 16 254226 3e112 ath10k_core.ko
After:
text data bss dec hex filename
245979 8899 16 254894 3e3ae ath10k_core.ko
Tested on a D-Link DAP-2695-A1 (ar71xx).
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Diffstat (limited to 'tools/firmware-utils/src/mkporayfw.c')
0 files changed, 0 insertions, 0 deletions