Re: [PATCH v2] leds: implement OpenFirmare GPIO LED driver
From: Anton Vorontsov <hidden>
Date: 2008-07-15 14:24:17
Also in:
lkml
On Tue, Jul 15, 2008 at 02:31:27PM +0100, Richard Purdie wrote:
On Tue, 2008-07-15 at 17:24 +0400, Anton Vorontsov wrote:quoted
On Tue, Jul 15, 2008 at 01:54:30PM +0100, Richard Purdie wrote:quoted
I don't have any issue with the driver itself, just the name which is going to confuse people no end. Can we come up with a better name for this driver please?[...]quoted
quoted
"openfirmware-led"?And this would be wrong, since this driver is for GPIO LEDs only, not for all LEDs that OF can describe. In future there could be OF PWM LEDs or something like this.Ok, will these be a separate driver or combined into the gpio driver?
I believe this must be a separate driver. The two drivers would have nothing in common except prologue registration stuff.
quoted
quoted
I'm mainly concerned with the more user visible bits like the name of the .c file, the wording of the Kconfig option and the module description. We need to play down the GPIO bit and play up the openfirmware bindings bit.Hm... file name is leds-of-gpio.c, how could I play up the "of" bit more than this? ;-)Spell out openfirmware :). I initially had no idea "of == openfirmware" and I suspect others won't either...
This would be unusually long name, that is $ find . -iname '*openfirmware*' | wc -l 0 And in contrast: drivers/video/offb.c drivers/video/nvidia/nv_of.c drivers/usb/host/ohci-ppc-of.c drivers/usb/host/ehci-ppc-of.c drivers/serial/of_serial.c drivers/mtd/maps/physmap_of.c ... So, I think we should stick with the "of" for consistency, while confused users may consult with Kconfig for disambiguation. But if you really want the expanded name.. just repeat it, and I'll change the name. Thanks, -- Anton Vorontsov email: cbouatmailru@gmail.com irc://irc.freenode.net/bd2