From: Pavel Machek <pavel@ucw.cz>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>,
linux-leds@vger.kernel.org, linux-media@vger.kernel.org,
kyungmin.park@samsung.com, cooloney@gmail.com, rpurdie@rpsys.net,
s.nawrocki@samsung.com,
Sakari Ailus <sakari.ailus@linux.intel.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 01/12] DT: leds: Improve description of flash LEDs related properties
Date: Wed, 8 Apr 2015 11:17:24 +0200 [thread overview]
Message-ID: <20150408091724.GD5646@amd> (raw)
In-Reply-To: <20150408091129.GT20756@valkosipuli.retiisi.org.uk>
Hi!
> > I think that a board designed so that it can be damaged because of
> > software bugs should be considered not eligible for commercial
> > use.
Hello? It is 2015. Yes, that was nice rule... in 1995 or so :-).
> > As I mentioned in the previous message in this subject, the max-microamp
> > property refers also to non-flash LEDs. Since existing LED class devices
> > does not require them, then it should be left optional and default to
> > max. It would however be inconsistent with flash LEDs related
> > properties.
For non-flash LEDs and backward compatibility, I guess you are
right. Inconsistency is fine in this case...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-04-08 9:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427809965-25540-1-git-send-email-j.anaszewski@samsung.com>
2015-03-31 13:52 ` [PATCH v4 01/12] DT: leds: Improve description of flash LEDs related properties Jacek Anaszewski
2015-04-02 14:41 ` Pavel Machek
2015-04-03 12:09 ` Sakari Ailus
2015-04-03 12:56 ` Jacek Anaszewski
2015-04-03 20:37 ` Pavel Machek
2015-04-08 1:20 ` Bryan Wu
[not found] ` <CAK5ve-KR81cNrJnPj_XUkNvctsEYLDGb58qTVaOOAYJnoZTGXg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-08 7:48 ` Sakari Ailus
2015-04-08 9:13 ` Pavel Machek
2015-04-08 8:54 ` Jacek Anaszewski
2015-04-08 9:11 ` Sakari Ailus
2015-04-08 9:17 ` Pavel Machek [this message]
2015-04-08 10:23 ` Jacek Anaszewski
[not found] ` <5525019B.8050104-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-04-08 10:44 ` Sakari Ailus
2015-04-08 10:03 ` Sylwester Nawrocki
2015-04-08 10:36 ` Pavel Machek
2015-04-08 11:58 ` Jacek Anaszewski
2015-04-08 14:45 ` Sylwester Nawrocki
2015-03-31 13:52 ` [PATCH v4 04/12] DT: Add documentation for the mfd Maxim max77693 Jacek Anaszewski
[not found] ` <1427809965-25540-5-git-send-email-j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-03-31 14:34 ` Jacek Anaszewski
2015-03-31 13:52 ` [PATCH v4 06/12] of: Add Skyworks Solutions, Inc. vendor prefix Jacek Anaszewski
2015-04-08 11:59 ` Sakari Ailus
2015-03-31 13:52 ` [PATCH v4 07/12] DT: Add documentation for the Skyworks AAT1290 Jacek Anaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150408091724.GD5646@amd \
--to=pavel@ucw.cz \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).