On Mon 2019-07-15 16:57:28, Enrico Weigelt, metux IT consult wrote: > From: Enrico Weigelt <i...@metux.net> > > This driver only supports gpio-attached LEDs on apu1/2/3 boards, > but neither gpio's themselves, nor other gpio-attached devices > (eg. front button). > > For apu2+ a newer, more complete driver exists, based on a generic > driver for the AMD SOCs gpio-controller, supporting LEDs as well > other devices. Therefore these boards don't need legacy support > from this driver anymore. > > Both drivers claim the same device, so only one driver may exist > in a system, putting distros in the position to decide between > either apu2+ keys or apu1 led support. > > Therefore drop the apu2+ led support from the old driver, solve > the conflict and reduce unnecessary code. > > Signed-off-by: Enrico Weigelt <i...@metux.net> > --- > drivers/leds/Kconfig | 5 +- > drivers/leds/leds-apu.c | 124 > +++--------------------------------------------- > 2 files changed, 10 insertions(+), 119 deletions(-) > > diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig > index b0fdeef..f7a3dd7 100644 > --- a/drivers/leds/Kconfig > +++ b/drivers/leds/Kconfig > @@ -74,9 +74,12 @@ config LEDS_APU > depends on LEDS_CLASS > depends on X86 && DMI > help > - This driver makes the PC Engines APU/APU2/APU3 front panel LEDs > + This driver makes the PC Engines APU1 front panel LEDs > accessible from userspace programs through the LED subsystem. > > + If you're looking for APU2/3, use the pcengines-apu2 driver. > + (symbol CONFIG_PCENGINES_APU2) > + > To compile this driver as a module, choose M here: the > module will be called leds-apu. >
Ok, so I understand the reasons, but people updating from old kernels
(make oldconfig) will see nothing and their LEDs will stop working.
Can we do something to help them?
Rest is ok.
Acked-by: Pavel Machek <pa...@ucw.cz>
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
signature.asc
Description: Digital signature
