From: Henrik Grimler <henrik@grimler.se>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
alim.akhtar@samsung.com, m.szyprowski@samsung.com,
virag.david003@gmail.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Cc: Henrik Grimler <henrik@grimler.se>
Subject: [PATCH v2 0/2] arm64: dts: add mmc aliases for Exynos devices
Date: Wed, 15 Mar 2023 22:28:12 +0100 [thread overview]
Message-ID: <20230315212814.15908-1-henrik@grimler.se> (raw)
It is convenient to have fixed mmcblk numbering of the eMMC and sdcard
so that assigned numbers will not change from boot-to-boot or
depending on if storage devices are actually attached or not.
Also drop mshc aliases while we are at it and instead add mmc
capabilities to the individual device trees (right now they are added
depending on alias index).
---
Changes since v1:
* Set mmc-ddr-1_8v in device trees so that MMC_CAP_1_8V_DDR is set
also after removal of mshc0 alias. Issue was pointed out by
Krzysztof and David.
Henrik Grimler (2):
arm64: dts: exynos: drop mshc aliases
arm64: dts: exynos: add mmc aliases
arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi | 5 +++--
arch/arm64/boot/dts/exynos/exynos7-espresso.dts | 5 +++--
arch/arm64/boot/dts/exynos/exynos7885-jackpotlte.dts | 1 +
3 files changed, 7 insertions(+), 4 deletions(-)
base-commit: 35ade1eb465438cfd16fdc3a4905dd82f658fdce
--
2.30.2
next reply other threads:[~2023-03-15 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 21:28 Henrik Grimler [this message]
2023-03-15 21:28 ` [PATCH v2 1/2] arm64: dts: exynos: drop mshc aliases Henrik Grimler
2023-03-16 10:32 ` Marek Szyprowski
2023-03-15 21:28 ` [PATCH v2 2/2] arm64: dts: exynos: add mmc aliases Henrik Grimler
2023-03-16 10:32 ` Marek Szyprowski
2023-03-17 12:45 ` [PATCH v2 0/2] arm64: dts: add mmc aliases for Exynos devices Krzysztof Kozlowski
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=20230315212814.15908-1-henrik@grimler.se \
--to=henrik@grimler.se \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=virag.david003@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).