From: Marek Vasut <marex@denx.de>
To: Pavel Machek <pavel@ucw.cz>, lee.jones@linaro.org
Cc: linux-leds@vger.kernel.org,
Christoph Niedermaier <cniedermaier@dh-electronics.com>
Subject: Re: [PATCH] leds: gpio: Configure per-LED pin control
Date: Mon, 8 May 2023 01:11:30 +0200 [thread overview]
Message-ID: <1e22f00a-490a-503d-463c-d7d4df1da64e@denx.de> (raw)
In-Reply-To: <5156c474-9f44-6cda-6090-c3e58f7459f0@denx.de>
On 4/2/23 23:58, Marek Vasut wrote:
> On 3/27/23 13:58, Pavel Machek wrote:
>> Hi!
>>
>>> Each gpio-leds DT node DT subnode can have a pinctrl property assigned
>>> to it, parse the DT subnode pinctrl properties and configure each pin
>>> accordingly.
>>
>> Do we need update to
>> Documentation/devicetree/bindings/leds/leds-gpio.yaml ?
>
> As far as I can tell, no. The pinctrl properties are generic and outside
> of the leds-gpio yaml schema.
Are there any further concerns or can this patch be applied now ?
Thanks!
prev parent reply other threads:[~2023-05-07 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 0:31 [PATCH] leds: gpio: Configure per-LED pin control Marek Vasut
2022-11-07 9:15 ` Christoph Niedermaier
2023-02-28 22:01 ` Marek Vasut
2023-03-27 11:58 ` Pavel Machek
2023-04-02 21:58 ` Marek Vasut
2023-05-07 23:11 ` Marek Vasut [this message]
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=1e22f00a-490a-503d-463c-d7d4df1da64e@denx.de \
--to=marex@denx.de \
--cc=cniedermaier@dh-electronics.com \
--cc=lee.jones@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).