Thread (7 messages) 7 messages, 3 authors, 2013-01-22

Re: [PATCH v2] HID: add ThingM blink(1) USB RGB LED support

From: Jiri Kosina <hidden>
Date: 2013-01-22 13:45:13
Also in: lkml

On Tue, 22 Jan 2013, Vivien Didelot wrote:
quoted
quoted
quoted
Shouldn't the name presented in the sys/class/leds directories
change
appropriately too?
The directory name for the device under /sys/class/leds is
"blink(1)::<serial>",
where <serial> is the last 4 digits of the device serial number
(the first 4
digits are always the same: "1A00"). For instance,
"blink(1)::1234".
Let me know if I misunderstood your question.
I believe that Simon's (valid) observation is that the sysfs path
should
reflect the name change, i.e. something along the lines of
/sys/class/leds/thingm-blink:<serial>   ... ?
The vendor's name is "ThingM" and the product's name is "blink(1)", not "blink".
Given that, would you prefer to keep "blink(1)::1234", or would it rather be
"thingm-blink1::1234" (avoiding parenthesis)?

I ask the same question for the driver name, which is actually "blink(1)".
Actually, for HID bus drivers, we are mostly following the convention of 
having just the vendor name in the driver, see hid-microsoft, 
hid-logitech, etc.

So it'd make most sense to me to name the driver hid-thingm, and in case 
it is driving blink(1) device (no other devices will be driven by it 
currently), let it create /sys/class/leds/blink1... 

-- 
Jiri Kosina
SUSE Labs
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help