mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	gbcm-kernel-feedback-list@broadcom.com,
	gkrzysztof.kozlowski+dt@linaro.org, gnsaenz@kernel.org,
	grobh+dt@kernel.org, nsaenz@kernel.org, stefan.wahren@i2se.com
Subject: Re: [PATCH] ARM: dts: bcm2711-rpi-4-b: Use aliases to set custom MMC device index
Date: Mon, 13 Jun 2022 09:46:58 -0300	[thread overview]
Message-ID: <f83690bb-5513-db87-2d97-7cbd981aa0f7@collabora.com> (raw)
In-Reply-To: <CALeDE9PR80qS63wwAKB-hENWbEj1xNHj+k81tyWkPPfZ0TS8Pw@mail.gmail.com>

Hi Peter,

On 6/12/22 17:38, Peter Robinson wrote:
> On Wed, Jun 8, 2022 at 1:35 PM Ariel D'Alessandro
> <ariel.dalessandro@collabora.com> wrote:
>>
>> Add MMC aliases to ensure that the /dev/mmcblk ID for SD card won't
>> change depending on the probe order of the MMC drivers.
> 
> Is  the bcm2711-rpi.dtsi a better place for it given there's other
> aliases there and it will be consistent across variations?

Yes, indeed, it makes sense moving it to bcm2711-rpi.dtsi

The other board what will be affected by this alias is the Raspberry Pi
Compute Module 4 IO Board, on which emmc2 is the eMMC. However, the
alias makes sense, to have that as the first mmc device.

Maybe we can add the alias as follows?

    mmc0 = &emmc2;  /* mmcblk0 for eMMC/SD */

Regards,
Ariel

> 
>> Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
>> ---
>>  arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
>> index 4432412044de..780812542bad 100644
>> --- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
>> +++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
>> @@ -14,6 +14,10 @@ chosen {
>>                 stdout-path = "serial1:115200n8";
>>         };
>>
>> +       aliases {
>> +               mmc0 = &emmc2;  /* mmcblk0 for SD */
>> +       };
>> +
>>         leds {
>>                 led-act {
>>                         gpios = <&gpio 42 GPIO_ACTIVE_HIGH>;
>> --
>> 2.34.1
>>
>>
>> _______________________________________________
>> linux-rpi-kernel mailing list
>> linux-rpi-kernel@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-rpi-kernel

  reply	other threads:[~2022-06-13 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 12:32 Ariel D'Alessandro
2022-06-12 20:38 ` Peter Robinson
2022-06-13 12:46   ` Ariel D'Alessandro [this message]
2022-06-13 23:34     ` Florian Fainelli
2022-06-14  6:34       ` Stefan Wahren

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=f83690bb-5513-db87-2d97-7cbd981aa0f7@collabora.com \
    --to=ariel.dalessandro@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gbcm-kernel-feedback-list@broadcom.com \
    --cc=gkrzysztof.kozlowski+dt@linaro.org \
    --cc=gnsaenz@kernel.org \
    --cc=grobh+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=nsaenz@kernel.org \
    --cc=pbrobinson@gmail.com \
    --cc=stefan.wahren@i2se.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

all inboxes | Powered by JetHome®