On 19/03/2011 16:51, [email protected] wrote: > From: Ed Wildgoose <[email protected]> > > This new driver replaces the old PCEngines Alix 2/3 LED driver with > a new driver that controls the LEDs through the leds-gpio driver. > The old driver accessed GPIOs directly, which created a conflict > and prevented also loading the cs5535-gpio driver to read other > GPIOs on the Alix board. With this new driver, we hook into leds-gpio > which in turn uses GPIO to control the LEDs and therefore it's > possible to control both the LEDs and access onboard GPIOs > > Driver is moved to platform/geode and any other geode > initialisation modules should move here also. > > This driver is inspired by leds-net5501.c > by: Alessandro Zummo <[email protected]> > Ideally, leds-net5501.c should also be moved to platform/geode. > Additionally the driver relies on parts of the patch: 7f131cf3ed > by: Daniel Mack <[email protected]> to perform detection of the Alix board > Signed-off-by: Ed Wildgoose <[email protected]>
Hi Grant I *think* this patch should now be satisfactory and I believe to be implemented as we discussed: - I have made the driver look like a straightforward platform initialisation routine and so further platform setup could be added here if required. My only thought is that it's quite tucked away and hard to find here, given that at present it only enables LEDs on this platform (and seems reasonably unlikely to grow beyond that). Would it be acceptable/sensible to put the Kconfig entry under LEDs for the time being (but the code under /platform/)? Obviously if it starts to do more initialisation/setup then the KConfig can be moved back to /arch/x86/ ? However, grateful if you could please now review this for inclusion? I will submit a second patch momentarily which adds the extra dependency of -gpio on -mfd as we discussed in the previous email Many thanks Ed W _______________________________________________ Linux-geode mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-geode
