From: Chen-Yu Tsai <wens@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh+dt@kernel.org>
Cc: linux-rockchip@lists.infradead.org, Chen-Yu Tsai <wens@csie.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] arm64: dts: rockchip: misc. cleanups
Date: Fri, 27 Mar 2020 11:04:08 +0800 [thread overview]
Message-ID: <20200327030414.5903-1-wens@kernel.org> (raw)
From: Chen-Yu Tsai <wens@csie.org>
Hi,
Here are a bunch of cleanups for rk3399 and rk3328.
- Some dtc warnings were silenced, however a few still remain.
Found those while making device tree overlays
- Replaced some hardware specific device node names, such as dwc3
and rk808, with generic names
- Fixed MMC numbering for roc-rk3399-pc with mezzanine
The series is based on linux-next 2020-03-24. For some reason 2020-03-26
doesn't boot.
Please have a look.
Regards
ChenYu
Chen-Yu Tsai (6):
arm64: dts: rockchip: rk3399-roc-pc: Fix MMC numbering for LED
triggers
arm64: dts: rockchip: rk3328: Replace RK805 PMIC node name with "pmic"
arm64: dts: rockchip: rk3328: drop non-existent gmac2phy pinmux
options
arm64: dts: rockchip: rk3328: drop #address-cells, #size-cells from
grf node
arm64: dts: rockchip: rk3399: drop #address-cells, #size-cells from
pmugrf node
arm64: dts: rockchip: rk3399: Rename dwc3 device nodes to make dtc
happy
arch/arm64/boot/dts/rockchip/rk3328-evb.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 18 ------------------
.../dts/rockchip/rk3399-roc-pc-mezzanine.dts | 8 ++++++++
.../arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi | 4 ++--
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 6 ++----
6 files changed, 14 insertions(+), 26 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-03-27 3:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 3:04 Chen-Yu Tsai [this message]
2020-03-27 3:04 ` [PATCH 1/6] arm64: dts: rockchip: rk3399-roc-pc: Fix MMC numbering for LED triggers Chen-Yu Tsai
2020-03-27 9:58 ` Johan Jonker
2020-03-29 16:36 ` Chen-Yu Tsai
2020-03-31 11:07 ` Robin Murphy
2020-04-01 20:05 ` Jacek Anaszewski
2020-04-06 9:13 ` Pavel Machek
2020-04-13 5:33 ` Chen-Yu Tsai
2020-03-27 3:04 ` [PATCH 2/6] arm64: dts: rockchip: rk3328: Replace RK805 PMIC node name with "pmic" Chen-Yu Tsai
2020-03-27 12:12 ` Johan Jonker
2020-03-27 12:15 ` Chen-Yu Tsai
2020-03-27 3:04 ` [PATCH 3/6] arm64: dts: rockchip: rk3328: drop non-existent gmac2phy pinmux options Chen-Yu Tsai
2020-03-27 3:04 ` [PATCH 4/6] arm64: dts: rockchip: rk3328: drop #address-cells, #size-cells from grf node Chen-Yu Tsai
2020-03-27 3:04 ` [PATCH 5/6] arm64: dts: rockchip: rk3399: drop #address-cells, #size-cells from pmugrf node Chen-Yu Tsai
2020-03-27 3:04 ` [PATCH 6/6] arm64: dts: rockchip: rk3399: Rename dwc3 device nodes to make dtc happy Chen-Yu Tsai
2020-04-19 11:36 ` [PATCH 0/6] arm64: dts: rockchip: misc. cleanups Heiko Stuebner
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=20200327030414.5903-1-wens@kernel.org \
--to=wens@kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).