devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>,
	devicetree@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [RFC 0/2] Set mmc(blk)X with DT alias
Date: Fri, 26 Jul 2013 10:09:53 +0200	[thread overview]
Message-ID: <20130726080953.GA2118@pengutronix.de> (raw)
In-Reply-To: <51F16046.3020809@wwwdotorg.org>

On Thu, Jul 25, 2013 at 10:28:38AM -0700, Stephen Warren wrote:
> On 07/24/2013 02:09 AM, Steffen Trumtrar wrote:
> > Hi!
> > 
> > Embedded devices often use multiple SD/MMC devices as boot/rootfs disks.
> > Some of them are removable, some not. If the removable cards are not
> > present, but are probed before the non-removable ones, the indexing
> > scheme changes. This makes it harder to hard-code the rootfs in the
> > cmdline.
> >
> > First solution I came up with was the alias-node in DT.
> > I guess my implementation is pretty hacky and ugly, but you can get lost
> > pretty fast in the whole mmc stack.
> > For example, the second patch should use "card->host->index" instead of parsing
> > the alias again, I guess. I'm not sure why it currently doesn't though.
> 
> This has been discussed a few times before and rejected IIRC. One issue
> is that block device ID is actually decoupled from host controller ID
> anyway, e.g. if a removable device is mounted, removed, and then
> re-plugged the new device can get a different ID, so this approach
> doesn't really work in all cases anyway.
> 

Hm, okay. I actually wasn't aware of the older discussions.

> > So, if there is a better place or solution to specify a reliable ordering
> > of mmc devices, please let me hear it.
> 
> root=UUID=xxx or root=PARTUUID=xxx are the best solution. With recent
> U-Boot, you can enable and use the "part" command to find the partition
> UUID automatically, and hence not need to hard-code anything. Something
> similar could presumably be implemented for other bootloaders.

I am actually okay with that. I know barebox can do that, but didn't knew that
U-Boot is also capabable of that.
So, I'm okay with dropping the patch.

Thanks,
Steffen

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      reply	other threads:[~2013-07-26  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  9:09 [RFC 0/2] Set mmc(blk)X with DT alias Steffen Trumtrar
2013-07-24  9:09 ` [RFC 1/2] mmc: block: allow setting name_idx via devicetree Steffen Trumtrar
2013-07-24  9:09 ` [RFC 2/2] mmc: host: allow setting index " Steffen Trumtrar
2013-07-25 17:28 ` [RFC 0/2] Set mmc(blk)X with DT alias Stephen Warren
2013-07-26  8:09   ` Steffen Trumtrar [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=20130726080953.GA2118@pengutronix.de \
    --to=s.trumtrar@pengutronix.de \
    --cc=cjb@laptop.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=swarren@wwwdotorg.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).