devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tianling Shen <cnsztl@gmail.com>
To: Dragan Simic <dsimic@manjaro.org>,
	Diederik de Haas <didi.debian@cknow.org>
Cc: 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 21:52:51 +0800	[thread overview]
Message-ID: <ad4a7dda-8f6f-4d2a-84d9-838611f2285f@gmail.com> (raw)
In-Reply-To: <d0a3d5d4480eac12ba5e2b15bcbc578f@manjaro.org>

Hi Dragan,

On 2025/9/27 21:47, Dragan Simic wrote:
> 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.

The schematic for NanoPi R76S is available at 
https://wiki.friendlyelec.com/wiki/images/6/60/NanoPi_R76S_LP4X_2411_SCH.pdf

For more information please move to 
https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R76S.

Thanks,
Tianling.

  reply	other threads:[~2025-09-27 13:52 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
2025-09-27 13:52           ` Tianling Shen [this message]
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=ad4a7dda-8f6f-4d2a-84d9-838611f2285f@gmail.com \
    --to=cnsztl@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=didi.debian@cknow.org \
    --cc=dsimic@manjaro.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).