From: Heiko Stuebner <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
robh+dt@kernel.org, jay.xu@rock-chips.com,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
conor+dt@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v1 1/2] ARM: dts: rockchip: add gpio alias for gpio dt nodes
Date: Thu, 7 Dec 2023 21:57:30 +0100 [thread overview]
Message-ID: <170198261663.24767.3042454537755741300.b4-ty@sntech.de> (raw)
In-Reply-To: <89f2a229-9f14-d43f-c53d-5d4688e70456@gmail.com>
On Sat, 2 Dec 2023 19:22:01 +0100, Johan Jonker wrote:
> Rockchip SoC TRM, SoC datasheet and board schematics always refer to
> the same gpio numbers - even if not all are used for a specific board.
> In order to not have to re-define them for every board add the
> aliases to SoC dtsi files.
>
>
Applied, thanks!
[1/2] ARM: dts: rockchip: add gpio alias for gpio dt nodes
commit: 04c521c3bec1fa0ccb97a1fbf74f0faeda3f4a53
[2/2] arm64: dts: rockchip: add gpio alias for gpio dt nodes
commit: cfb0264f3654e357bcdfe27c2f7240241c2ac6c5
Added the Co-developed-by for Jianqun before applying.
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2023-12-07 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 18:22 [PATCH v1 1/2] ARM: dts: rockchip: add gpio alias for gpio dt nodes Johan Jonker
2023-12-02 18:22 ` [PATCH v1 2/2] arm64: " Johan Jonker
2023-12-04 20:10 ` Dragan Simic
2023-12-04 19:35 ` [PATCH v1 1/2] ARM: " Heiko Stübner
2023-12-04 19:50 ` Johan Jonker
2023-12-04 20:10 ` Dragan Simic
2023-12-07 20:57 ` Heiko Stuebner [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=170198261663.24767.3042454537755741300.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jay.xu@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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