Hi! > >>>>> +Optional child properties: > >>>>> + - runtime-ramp-up-msec: Current ramping from one brightness level to > >>>>> + the a higher brightness level. > >>>>> + Range from 2048 us - 117.44 s > This is this problem with the Device Tree's scope of responsibility. > It is defined as a means for "describing the hardware", but often > this rule is abused by the properties that fall into "configuration" > category. E.g. default-state, retain-state-suspended from leds-gpio.txt > or linux-default-trigger from common LED bindings. I always assumed that ramp-up time is there because hardware (power supply?) can not handle "too fast" switching. Missing capacitors or something. If so, this needs to be in device tree. If not, it indeed does not belong to device tree. > In some cases this is justified. The question is whether it is something > that necessarily needs to be configured on driver probing? If not, then > I'd go for sysfs interface. While this would be useful for hardware accelerated patterns, I doubt we want to make it configurable without that support. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
