From: Alex Bee <knaerzche@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Alex Bee <knaerzche@gmail.com>
Subject: [PATCH 0/3] Move core bus and gpio aliases to SoC dtsi for RK3128
Date: Sat, 2 Dec 2023 14:05:04 +0100 [thread overview]
Message-ID: <20231202130506.66738-2-knaerzche@gmail.com> (raw)
Following up the recent discussion [0] about where aliases can be/should be
placed this series moves gpio, i2c and uart aliases to SoC dtsi for RK3128.
Note: This patches are based on maintainter's repo.
[0] https://lore.kernel.org/all/b0c637f5-5abf-420b-8b02-839eba68799e@linaro.org/T/#m94aebb23a29b015d94b250a70b675febdaa902ea
Alex Bee (3):
ARM: dts: rockchip: Move gpio aliases to SoC dtsi for RK3128
ARM: dts: rockchip: Move i2c aliases to SoC dtsi for RK3128
ARM: dts: rockchip: Move uart aliases to SoC dtsi for RK3128
arch/arm/boot/dts/rockchip/rk3128-evb.dts | 5 -----
arch/arm/boot/dts/rockchip/rk3128-xpi-3128.dts | 7 +------
arch/arm/boot/dts/rockchip/rk3128.dtsi | 14 ++++++++++++++
3 files changed, 15 insertions(+), 11 deletions(-)
base-commit: fd610e604837936440ef7c64ab6998b004631647
--
2.43.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2023-12-02 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 13:05 Alex Bee [this message]
2023-12-02 13:05 ` [PATCH 1/3] ARM: dts: rockchip: Move gpio aliases to SoC dtsi for RK3128 Alex Bee
2023-12-02 13:05 ` [PATCH 2/3] ARM: dts: rockchip: Move i2c " Alex Bee
2023-12-02 13:05 ` [PATCH] ARM: dts: rockchip: Move uart " Alex Bee
2023-12-05 0:05 ` [PATCH 0/3] Move core bus and gpio " Heiko Stuebner
2023-12-05 13:33 ` Alex Bee
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=20231202130506.66738-2-knaerzche@gmail.com \
--to=knaerzche@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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