From: Christopher Obbard <chris.obbard@collabora.com>
To: Heiko Stuebner <heiko@sntech.de>, linux-rockchip@lists.infradead.org
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
Christopher Obbard <chris.obbard@collabora.com>
Subject: [PATCH v1 0/3] Update eMMC alias for Radxa ROCK 5 Model A and Model B DTS
Date: Tue, 10 Jan 2023 15:52:49 +0000 [thread overview]
Message-ID: <20230110155252.189300-1-chris.obbard@collabora.com> (raw)
The MMC aliases for the Radxa ROCK 5 Model A and Model B do not match the other
Rockchip devices: mmc0 is usually the eMMC. In the initial devicetree series,
I incorrectly set the alias for the eMMC to mmc1 to match the vendor kernel.
Update the alias for the eMMC to mmc0 to better match other Rockchip devices.
While we are here, remove an empty line to keep good style across the tree.
Christopher Obbard (3):
arm64: dts: rockchip: Update sdhci alias for rock-5a
arm64: dts: rockchip: Remove empty line from rock-5a
arm64: dts: rockchip: Update sdhci alias for rock-5b
arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-10 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 15:52 Christopher Obbard [this message]
2023-01-10 15:52 ` [PATCH v1 1/3] arm64: dts: rockchip: Update sdhci alias for rock-5a Christopher Obbard
2023-01-10 19:21 ` Krzysztof Kozlowski
2023-01-10 19:55 ` Christopher Obbard
2023-01-10 15:52 ` [PATCH v1 2/3] arm64: dts: rockchip: Remove empty line from rock-5a Christopher Obbard
2023-01-10 15:52 ` [PATCH v1 3/3] arm64: dts: rockchip: Update sdhci alias for rock-5b Christopher Obbard
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=20230110155252.189300-1-chris.obbard@collabora.com \
--to=chris.obbard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.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=michael.riesch@wolfvision.net \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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).