taken a look at the specific code, and from my point of view the code
that sets up the LED (including callback) is so trivial that it's simply
not worth dealing with adding the leds-gpio driver to the mix.
It adds extra complexity and an extra dependency for no reason at all.
There's no extra functionality to be gained by using it.
Stupid question: If the LED driver isn't using the GPIO subsystem
(when enabled), what happens if the user uses the GPIO subsystem to
fiddle with the pin the LED is connected to?
in our case here it can coexist and will not have a negative effect
since the led will still run. (except if you reconfigure the gpio to input)
for sure it makes no sense.
but however i can block the gpio for beeing reused if the led driver
took it. this has been made in ath9k for instance.
in ath10k i did not do it, since there is no technical requirement for it.
but that might not be the case for all gpio controllers, so there is no
generic answer. for ath10k. harmless
Sebastian
Thanks,
--
Mit freundlichen Grüssen / Regards
Sebastian Gottschall / CTO
NewMedia-NET GmbH - DD-WRT
Firmensitz: Stubenwaldallee 21a, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottsch...@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565
