From: Alexander Dahl <ada@thorsis.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: linux-leds@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Dan Murphy <dmurphy@ti.com>,
linux-kernel@vger.kernel.org, Alexander Dahl <post@lespocky.de>
Subject: Re: [PATCH] leds: pwm: Allow automatic labels for DT based devices
Date: Mon, 31 Aug 2020 11:20:09 +0200 [thread overview]
Message-ID: <1837645.vzTIdMnA0P@ada> (raw)
In-Reply-To: <eff509d5-a5f7-0d5d-b39c-aac364e53aca@gmail.com>
Hello Jacek,
Am Freitag, 28. August 2020, 22:43:02 CEST schrieb Jacek Anaszewski:
> On 8/28/20 9:00 AM, Alexander Dahl wrote:
> > Am Donnerstag, 27. August 2020, 23:28:45 CEST schrieb Jacek Anaszewski:
> >> This part looks good, but corresponding update of
> >> Documentation/devicetree/bindings/leds/leds-pwm.txt is needed as well.
> >
> > I'm not sure, what needs updating. The properties 'function' and 'color'
> > are already documented in
> > Documentation/devicetree/bindings/leds/common.yaml … the only thing I can
> > think of here is updating the examples? That would be nice, as would be
> > updating to yaml, but I don't see the strong relation, yet.
> It is necessary to tell the user that given driver is capable of
> utilizing a property. I thought of something like in commit [0].
>
> >> It would be good to switch to yaml by this occassion.
> >
> > Is there some guidance on that in general?
>
> I am not aware of, but surely sooner or later all bindings will
> need to be unified. Touching the file is always a good opportunity
> to address that. It's up to you, though.
This update from txt to yaml is a manual task and after reading [1] and some
other examples, I tried to come up with something. I pushed the WIP to my
GitHub tree and will run the checks recommended by [1] later in the evening.
If that goes well, I'll send a v2 series.
> [0]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/Do
> cumentation/devicetree/bindings/leds/leds-lm3692x.txt?id=4dcbc8f8c59f4b618d6
> 51f5ba884ee5bf562c8de
Well okay, that was for the old format, but I see what you mean.
Greets
Alex
[1] https://www.kernel.org/doc/html/latest/devicetree/writing-schema.html
prev parent reply other threads:[~2020-08-31 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 9:37 [PATCH] leds: pwm: Allow automatic labels for DT based devices Alexander Dahl
2020-08-27 21:28 ` Jacek Anaszewski
2020-08-28 7:00 ` Alexander Dahl
2020-08-28 20:43 ` Jacek Anaszewski
2020-08-31 9:20 ` Alexander Dahl [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=1837645.vzTIdMnA0P@ada \
--to=ada@thorsis.com \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=post@lespocky.de \
/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.