From: Pavel Machek <pavel@ucw.cz>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: linux-leds@vger.kernel.org, rpurdie@rpsys.net,
jacek.anaszewski@gmail.com, robh+dt@kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, joel@jms.id.au,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH v2 1/2] dt-bindings: leds: gpio: Add optional retain-state-shutdown property
Date: Mon, 28 Aug 2017 12:19:52 +0200 [thread overview]
Message-ID: <20170828101952.GE18012@amd> (raw)
In-Reply-To: <20170828001711.19662-2-andrew@aj.id.au>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
On Mon 2017-08-28 09:47:10, Andrew Jeffery wrote:
> On Baseboard Management Controller (BMC) systems it's sometimes
> necessary for a LED to retain its state across a BMC reset (which is
> independent of the host system state). Add a devicetree property to
> describe this behaviour. The property would typically be used in
> conjunction with 'default-state = "keep"'.
>
> Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Acked-by: Pavel Machek <pavel@ucw.cz>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-08-28 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 0:17 [PATCH v2 0/2] leds: gpio: Allow retaining state on shutdown Andrew Jeffery
2017-08-28 0:17 ` [PATCH v2 1/2] dt-bindings: leds: gpio: Add optional retain-state-shutdown property Andrew Jeffery
2017-08-28 10:19 ` Pavel Machek [this message]
2017-08-28 21:13 ` Brandon Wyman
2017-08-29 19:13 ` Jacek Anaszewski
2017-08-31 21:28 ` Rob Herring
2017-08-31 23:02 ` Andrew Jeffery
2017-09-05 19:10 ` Jacek Anaszewski
2017-08-28 0:17 ` [PATCH v2 2/2] leds: gpio: Allow LED to retain state at shutdown Andrew Jeffery
2017-08-28 20:22 ` [PATCH v2 0/2] leds: gpio: Allow retaining state on shutdown 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=20170828101952.GE18012@amd \
--to=pavel@ucw.cz \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
/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).