linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: "Johnson CH Chen (陳昭勳)" <JohnsonCH.Chen@moxa.com>
Cc: "lkundrak@v3.sk" <lkundrak@v3.sk>,
	"dianders@chromium.org" <dianders@chromium.org>,
	"Victor Yu (游勝義)" <victor.yu@moxa.com>,
	linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: Please review the patch "mmc: core: try to use an id from the devicetree " again
Date: Thu, 19 Dec 2019 15:46:23 +0100	[thread overview]
Message-ID: <CAPDyKFq=Jg8Gs-QOS6OD1EJt=y_O4fieTvDhHTpeBYWCZ-r_ZA@mail.gmail.com> (raw)
In-Reply-To: <HK0PR01MB3521E416A9562724AC4A14EDFA520@HK0PR01MB3521.apcprd01.prod.exchangelabs.com>

On Thu, 19 Dec 2019 at 11:57, Johnson CH Chen (陳昭勳)
<JohnsonCH.Chen@moxa.com> wrote:
>
> Dear Ulf,
>
> We have a requirement to set a specific mmc's disk slot for a root path when booting. I think a specific "slot" is different from a specific "device". For example, When a platform has four mmc/sd slots, and we have ten mmc/sd cards. We need to test some cards for booting in one slot, and other slots can be filled with one card each for another use. Actually the order of these four slots is not constant because it depends on the order of registering mmc/sd drivers, and different platforms may have different situations. Slot id can be related with block id, so it can be related with mmc id for current linux kernel, too. We need to set a specific slot id to satisfy our requirement.
>
> I find the following patch: https://lkml.org/lkml/2019/6/20/638
> This is Lubomir provides has a function we need. Actually I have a patch with similar function without mmc alias and just set "mmc-id" in device tree, but I think Lubomir's is better than myself.
>
> Someone think why not use "LABEL" or "UUID" for initramfs, or use "PARTLABEL" or "PARTUUID" for u-boot? I think they assign a specific numbers/characters for mmc/sd cards, not for mmc/sd slots. Besides, if I set the same "LABEL" or "PARTLABEL" in some mmc/sd card, I think kernel will be confused how to find a desired mmc/sd card.
>
> So kindly review the patch "mmc: core: try to use an id from the devicetree " if you are free, thanks!

There have been several attempts to fix this and me personally don't
have a problem with using aliases/labels in DT. I said that before as
well.

However, what is missing today, is that someone collects the proper
arguments for *why* this is needed (and especially why UUID/LABEL
doesn't work). I think all that information is available in the
discussion here: https://lore.kernel.org/patchwork/cover/674381/

When I see a new patch posted, that contains these arguments in the
commit message of the patch, I am ready to review it again.

Kind regards
Uffe

      reply	other threads:[~2019-12-19 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 10:57 Please review the patch "mmc: core: try to use an id from the devicetree " again Johnson CH Chen (陳昭勳)
2019-12-19 14:46 ` Ulf Hansson [this message]

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='CAPDyKFq=Jg8Gs-QOS6OD1EJt=y_O4fieTvDhHTpeBYWCZ-r_ZA@mail.gmail.com' \
    --to=ulf.hansson@linaro.org \
    --cc=JohnsonCH.Chen@moxa.com \
    --cc=dianders@chromium.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=victor.yu@moxa.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).