From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Chris Brandt <chris.brandt@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: pinctrl: renesas,rza2-pinctrl: Fix pin controller node name
Date: Sun, 23 Aug 2020 12:00:01 +0300 [thread overview]
Message-ID: <b270e095-441c-bef3-f841-4bb24d31c646@gmail.com> (raw)
In-Reply-To: <CAMuHMdVr1FBD+Gto8zf-tAp4_YTP1zs_qKu=yBeS3n2yjVqX0g@mail.gmail.com>
On 21.08.2020 20:41, Geert Uytterhoeven wrote:
>> On 8/21/20 2:11 PM, Geert Uytterhoeven wrote:
>>> According to Devicetree Specification v0.2 and later, Section "Generic
>>> Names Recommendation", the node name for a pin controller device node
>>> should be "pinctrl".
>>
>> Ugh, what a lame name! :-(
>> And they say DT should be OS agnostic...
>>
>>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>>
>> I think more DTs have "pin-controler".
>
> I was surprised to discover the opposite, too:
>
> $ git grep "\<pinctrl@" v5.9-rc1 | wc -l
> 335
> $ git grep "\<pin-controller@" v5.9-rc1 | wc -l
> 102
Sorry, I was probably thinking that I was replying to a DT patch, not the
bindings patch, hence this comment (it only meant Renesas DTs). It doesn't
really surprise me that more DTs overall have "pinctrl", sigh...
> Gr{oetje,eeting}s,
>
> Geert
MBR, Sergei
next prev parent reply other threads:[~2020-08-23 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 11:11 [PATCH] dt-bindings: pinctrl: renesas,rza2-pinctrl: Fix pin controller node name Geert Uytterhoeven
2020-08-21 15:27 ` Sergei Shtylyov
2020-08-21 17:41 ` Geert Uytterhoeven
2020-08-23 9:00 ` Sergei Shtylyov [this message]
2020-08-28 9:37 ` Linus Walleij
2020-09-08 20:52 ` Rob Herring
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=b270e095-441c-bef3-f841-4bb24d31c646@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).