From: Markus Reichl <m.reichl@fivetechno.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: exynos: Assign a fixed index to mmc devices on ODROID XU3/4 boards
Date: Wed, 4 Nov 2020 13:42:17 +0100 [thread overview]
Message-ID: <28660119-ffe3-cd01-0daa-8c0994e29571@fivetechno.de> (raw)
In-Reply-To: <4ac01b71-e806-18c8-13ce-6acdcc1a3b41@samsung.com>
Hi Marek,
Am 04.11.20 um 13:24 schrieb Marek Szyprowski:
> Hi Markus,
>
> On 04.11.2020 11:08, Markus Reichl wrote:
>> Recently introduced async probe on mmc devices can shuffle block IDs.
>> Pin them to fixed values to ease booting in evironments where UUIDs
>> are not practical. Use newly introduced aliases for mmcblk devices from [1].
>>
>> [1]
>> https://patchwork.kernel.org/patch/11747669/
>
> Wow, this is a long standing issue, called by others 'a feature'. Good
> that this has been finally solved.
>
>> Signed-off-by: Markus Reichl <m.reichl@fivetechno.de>
>> ---
>> arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
>> index e35af40a55cb..91d2840ac8ca 100644
>> --- a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
>> +++ b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
>> @@ -13,6 +13,11 @@
>> #include "exynos5422-odroid-core.dtsi"
>>
>> / {
>> + aliases {
>> + mmc0 = &mmc_2;
>> + mmc1 = &mmc_0;
>
> Frankly, I would keep the MMC numbers the same as in u-boot and
> datasheets. 0 for the build-in eMMC and 2 for the SD-card. This would be
> much more natural. On the other hand, I would agree to do it differently
> only on Odroid HC1/HD2/MC1, which don't have build-in eMMC - just use 0
> there for the SD-card.
This would break present and long standing boot ordering in mainline, which is
mmcblk0 = SD-card and
mmcblk1 = eMMC
Still desired?
>
>> + };
>> +
>> gpio-keys {
>> compatible = "gpio-keys";
>> pinctrl-names = "default";
>
> Best regards
>
Gruß,
--
Markus Reichl
next prev parent reply other threads:[~2020-11-04 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201104105152eucas1p28eb6ca629a685f24a2463c72898fdbc5@eucas1p2.samsung.com>
2020-11-04 10:08 ` Markus Reichl
2020-11-04 12:24 ` Marek Szyprowski
2020-11-04 12:42 ` Markus Reichl [this message]
2020-11-04 12:56 ` Marek Szyprowski
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=28660119-ffe3-cd01-0daa-8c0994e29571@fivetechno.de \
--to=m.reichl@fivetechno.de \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.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=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
all inboxes | Powered by JetHome®