Hi Bryan, Bryan Wu wrote: > On Fri, Apr 3, 2015 at 1:37 PM, Pavel Machek <pa...@ucw.cz> wrote: >> Hi! >> >>>>> +- flash-timeout-us : Timeout in microseconds after which the flash >>>>> + LED is turned off. If omitted this will default to >>>>> the >>>>> + maximum timeout allowed by the device. >>>>> >>>>> >>>>> Examples: >>>> >>>> Pavel pointed out that the brightness between maximum current and the >>>> maximum *allowed* another current might not be noticeable,leading a >>>> potential spelling error to cause the LED being run at too high current. >>> >>> Where did he point this out? Do you think about the current version >>> of the leds/common.txt documentation or there was some other message, >>> that I don't see? >> >> Date: Thu, 2 Apr 2015 22:30:44 +0200 >> From: Pavel Machek <pa...@ucw.cz> >> To: Sakari Ailus <sakari.ai...@iki.fi> >> Subject: Re: [PATCHv3] media: i2c/adp1653: devicetree support for adp1653 >> >>> Besides, I can't understand your point. Could you express it in other >>> words, please? >> >> Typo in device tree would cause hardware damage. But idea. Make the >> properties mandatory. >> Pavel > > I don't quite follow there. I think Pavel acked this patch right? So > what's left to hold here?
LED flash controllers are capable of providing more current than the LEDs attached to them can withstand without hardware damage. This is the reason the maximum current limits lower than the LED controller maximums are there. Pavel, quite rightly so in my opinion, is suggesting these properties are made mandatory. A typo in the DT source could cause the controller maximum current used instead of LED maximum which is often lower. That kind of a problem would easily go unnoticed since there isn't necessarily any perceivable change in the functionality of the board. You'd only notice later on, when the LEDs stop working. -- Regards, Sakari Ailus sakari.ai...@linux.intel.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
