From: David Lechner <david@lechnology.com>
To: Pavel Machek <pavel@ucw.cz>, Marcel Holtmann <marcel@holtmann.org>
Cc: linux-leds@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Joel Becker <jlbec@evilplan.org>
Subject: Re: [RFC] User-defined leds
Date: Fri, 5 Aug 2016 14:54:33 -0500 [thread overview]
Message-ID: <8db4e308-ae2f-ee8a-d570-cd751c4f0269@lechnology.com> (raw)
In-Reply-To: <20160805195130.GA26694@amd>
On 08/05/2016 02:51 PM, Pavel Machek wrote:
>
> Could the device tree be used to bind LED driver to otherwise unused
> gpio?
>
> Pavel
>
There is already a leds-gpio driver that does this.
https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/leds-gpio.txt
WARNING: multiple messages have this Message-ID (diff)
From: david@lechnology.com (David Lechner)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] User-defined leds
Date: Fri, 5 Aug 2016 14:54:33 -0500 [thread overview]
Message-ID: <8db4e308-ae2f-ee8a-d570-cd751c4f0269@lechnology.com> (raw)
In-Reply-To: <20160805195130.GA26694@amd>
On 08/05/2016 02:51 PM, Pavel Machek wrote:
>
> Could the device tree be used to bind LED driver to otherwise unused
> gpio?
>
> Pavel
>
There is already a leds-gpio driver that does this.
https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/leds-gpio.txt
next prev parent reply other threads:[~2016-08-05 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 18:36 [RFC] User-defined leds David Lechner
2016-07-25 18:36 ` David Lechner
2016-07-25 18:45 ` Marcel Holtmann
2016-07-25 18:45 ` Marcel Holtmann
2016-07-26 7:38 ` Jacek Anaszewski
2016-07-26 7:38 ` Jacek Anaszewski
2016-08-05 19:51 ` Pavel Machek
2016-08-05 19:51 ` Pavel Machek
2016-08-05 19:54 ` David Lechner [this message]
2016-08-05 19:54 ` David Lechner
2016-08-05 19:58 ` Pavel Machek
2016-08-05 19:58 ` Pavel Machek
2016-07-26 7:38 ` Jacek Anaszewski
2016-07-26 7:38 ` 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=8db4e308-ae2f-ee8a-d570-cd751c4f0269@lechnology.com \
--to=david@lechnology.com \
--cc=j.anaszewski@samsung.com \
--cc=jlbec@evilplan.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@ucw.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.