From: Dragan Simic <dsimic@manjaro.org>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: Tianling Shen <cnsztl@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Jonas Karlman <jonas@kwiboo.se>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add devicetree for the FriendlyElec NanoPi R76S
Date: Sat, 27 Sep 2025 15:47:35 +0200 [thread overview]
Message-ID: <d0a3d5d4480eac12ba5e2b15bcbc578f@manjaro.org> (raw)
In-Reply-To: <DD3EST9Y5UHF.12FJMDJUSZNYL@cknow.org>
Hello Diederik and Tianling,
On 2025-09-27 09:37, Diederik de Haas wrote:
> On Sat Sep 27, 2025 at 3:19 AM CEST, Tianling Shen wrote:
>> On 2025/9/27 0:07, Diederik de Haas wrote:
>>> It is recommended to use the labels in the schematics to define the
>>> pinctl nodes (and thus their references). In quite a lot of cases
>>> that's
>>> indeed the case, but not for gpio-keys (USER_BUT) or these gpio-leds
>>> pinctls.
>>
>> I cannot find any specific naming rules from the gpio-keys[1] and
>> gpio-leds[2] bindings, did I miss any update?
>>
>> I think this naming matches the current practice at least in
>> rockchip's
>> dt tree.
>
> There is an unofficial rule/aim:
> https://lore.kernel.org/linux-rockchip/5360173.ktpJ11cQ8Q@diego/
> But granted, there is 'some' inconsistency.
>
> And used in f.e.
> https://lore.kernel.org/linux-rockchip/20250727144409.327740-4-jonas@kwiboo.se/
>
> Where you can just copy the pinctrl labels from the dts[i] and paste
> that in the schematic document and you're instantly at the right place.
> Which is the exact purpose of that rule/aim.
Is the schematic actually publicly available? I tried searching for
it, but found nothing, unfortunately.
next prev parent reply other threads:[~2025-09-27 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 9:15 [PATCH 1/2] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi R76S Tianling Shen
2025-09-22 9:15 ` [PATCH 2/2] arm64: dts: rockchip: Add devicetree for the " Tianling Shen
2025-09-26 16:07 ` Diederik de Haas
2025-09-27 1:19 ` Tianling Shen
2025-09-27 7:37 ` Diederik de Haas
2025-09-27 9:06 ` Tianling Shen
2025-09-27 13:47 ` Dragan Simic [this message]
2025-09-27 13:52 ` Tianling Shen
2025-09-27 14:13 ` Dragan Simic
2025-09-22 20:56 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add " Rob Herring (Arm)
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=d0a3d5d4480eac12ba5e2b15bcbc578f@manjaro.org \
--to=dsimic@manjaro.org \
--cc=cnsztl@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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).