From: Alex Courbot <acourbot@nvidia.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: Use of the pwm-names DT property
Date: Wed, 4 Jul 2012 16:48:31 +0900 [thread overview]
Message-ID: <4FF3F54F.1060809@nvidia.com> (raw)
In-Reply-To: <20120704073942.GC25386@avionic-0098.mockup.avionic-design.de>
On Wed 04 Jul 2012 04:39:42 PM JST, Thierry Reding wrote:
> In fact the *-names properties are rather common. They are used for the
> reg and interrupts properties. The pinctrl subsystem and the upcoming
> clock bindings also use the *-names properties. So one could just as
> well argue that the regulator and gpio bindings should have been using
> regulator-names and gpio-names respectively instead.
I was not aware of that, thanks for the explanation. Too bad the DT is
already split in two different ways for naming things.
Alex.
prev parent reply other threads:[~2012-07-04 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 6:53 Use of the pwm-names DT property Alex Courbot
2012-07-04 7:39 ` Thierry Reding
2012-07-04 7:48 ` Alex Courbot [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=4FF3F54F.1060809@nvidia.com \
--to=acourbot@nvidia.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@avionic-design.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 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).