devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andy Yan" <andyshrk@163.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: dsimic@manjaro.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	krzk+dt@kernel.org, "Andy Yan" <andy.yan@rock-chips.com>
Subject: Re:Re:Re: [PATCH] arm64: dts: rockchip: aliase sdhci as mmc0 for rk3566 box demo
Date: Thu, 20 Mar 2025 20:56:04 +0800 (CST)	[thread overview]
Message-ID: <2ae3fb1a.ad30.195b3a0087e.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <19b62068.1082.193ed25f901.Coremail.andyshrk@163.com>

Hi Heiko,

At 2024-12-22 14:55:09, "Andy Yan" <andyshrk@163.com> wrote:
>
>Hi Heiko,
>At 2024-12-21 20:55:02, "Heiko Stübner" <heiko@sntech.de> wrote:
>>Hi Andy,
>>
>>Am Samstag, 21. Dezember 2024, 11:49:07 CET schrieb Andy Yan:
>>> From: Andy Yan <andy.yan@rock-chips.com>
>>> 
>>> Follow most others rk356x based boards, and u-boot only use mmc0/1
>>> as mmc boot targets, so aliase sdhci as mmc0.
>>> 
>>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>>> ---
>>> 
>>>  arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts | 6 +++---
>>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>> 
>>> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts b/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts
>>> index 41b4cd5a4220..7d0eedf1bd0d 100644
>>> --- a/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts
>>> +++ b/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts
>>> @@ -19,9 +19,9 @@ / {
>>>  
>>>  	aliases {
>>>  		ethernet0 = &gmac1;
>>> -		mmc0 = &sdmmc0;
>>> -		mmc1 = &sdmmc1;
>>> -		mmc2 = &sdhci;
>>> +		mmc0 = &sdhci;
>>> +		mmc1 = &sdmmc0;
>>> +		mmc2 = &sdmmc1;
>>
>>sorry, but that won't be possible :-( .
>>
>>The original aliases for the mmc order were added over 2 years ago
>>(november 2022) and became part of the ABI then.
>
>Yes,  the patch for this board was submitted by me.
>This is a tv box  evaluation demo board that we use internally,and it is not sold to the public.
>I submitted it to the mainline because it is small, compact and streamlined, it easy for me
>to use it  test the mainline vop2 driver. 
>I think i am currently the only user who will use this board run the mainline kernel.
>I'm not sure if we can let it go.


So far, no one has come forward to claim that they are using this board.
Actually, as I mentioned before, currently, it is only me who is using this
board to do some DRM-related tests. Could you consider merging it? 
If later on someone really comes forward and claims that this modification
has affected it, we can still revert this patch.

>
>
>>
>>Imagine someone using that board with a rootfs=/dev/mmcblk2p1 part
>>in the commandline to mount the old sdhci-part1 as rootfs, but now
>>you reorder the controllers, so so that commandline would try to access
>>sdmmc1, so their system won't boot anymore after just a simple kernel
>>update.
>>
>>Breaking people's setup is one of those big no-go-s in the kernel, so
>>sadly you'll need to live with the existing order.
>>
>>
>>Heiko
>>
>>

  reply	other threads:[~2025-03-20 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21 10:49 [PATCH] arm64: dts: rockchip: aliase sdhci as mmc0 for rk3566 box demo Andy Yan
2024-12-21 12:55 ` Heiko Stübner
2024-12-22  6:55   ` Andy Yan
2025-03-20 12:56     ` Andy Yan [this message]
2025-04-07  7:17 ` 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=2ae3fb1a.ad30.195b3a0087e.Coremail.andyshrk@163.com \
    --to=andyshrk@163.com \
    --cc=andy.yan@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.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).