From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] rockchip: dts: rk3328: add aliases for mmc controller
Date: Tue, 23 May 2017 23:27:26 +0200 [thread overview]
Message-ID: <1969746.8ixlS7VFTt@phil> (raw)
In-Reply-To: <20170523211419.GQ23727@bill-the-cat>
Hi,
Am Dienstag, 23. Mai 2017, 17:14:19 CEST schrieb Tom Rini:
> On Tue, May 23, 2017 at 11:03:23PM +0200, Mark Kettenis wrote:
> > > From: Heiko Stuebner <heiko@sntech.de>
> > > Date: Tue, 23 May 2017 22:29:33 +0200
> > >
> > > Hi Kever, Tom,
> > >
> > > Am Dienstag, 23. Mai 2017, 14:32:44 CEST schrieb Kever Yang:
> > > > This is not from kernel, seems the kernel mmc driver does not
> > > > support aliases now,
> > > >
> > > > thought I hope they both support the aliases for ordering.
> > >
> > > there was a lengthy discussion about the pros and cons of ordering
> > > mmc devices last year [0].
> > >
> > > With the outcome that explicit ordering via aliases is not desired
> > > and the argument being that mmc devices are not so different from
> > > usb storage or scsi/sata devices whose ordering is random all the time.
> >
> > Aren't you intepreting the outcome of that discussion a bit too
> > broadly tough? That discussion seems to reject an explicit ordering
> > of mmc device names in the Linux kernel, mainly because better
> > mechanisms exist to refer to a particular device than its device
> > name/number. But that doesn't preclude having a meaningful set of
> > aliases for certain boards if there is some sort of canonical boot
> > order or if devices are actually numbered on a board?
> >
> > In OpenFirmware the primary purpose of these aliases is to specify
> > which device to boot from.
readding the lkml-link for the above:
[0] https://lkml.org/lkml/2016/4/29/621
As for that being to broad, wasn't that why Tom suggested moving that
to a -u-boot.dtsi file, because while generally not desired, it may
benefit uboot to get some sane boot order / type marks (emmc, sd-card),
but doesn't influence the core devicetree files that should ideally be
synced from the kernel or wherever?
Heiko
next prev parent reply other threads:[~2017-05-23 21:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 8:05 [U-Boot] [PATCH] rockchip: dts: rk3328: add aliases for mmc controller Kever Yang
2017-05-22 20:26 ` Simon Glass
2017-06-09 0:48 ` Kever Yang
2017-06-09 12:27 ` Simon Glass
2017-06-15 19:21 ` sjg at google.com
2017-05-22 21:18 ` Tom Rini
2017-05-23 6:32 ` Kever Yang
2017-05-23 11:47 ` Tom Rini
2017-05-23 20:29 ` Heiko Stuebner
2017-05-23 20:32 ` Tom Rini
2017-05-23 21:03 ` Mark Kettenis
2017-05-23 21:14 ` Tom Rini
2017-05-23 21:27 ` Heiko Stuebner [this message]
2017-05-23 22:18 ` Andreas Färber
2017-05-24 0:44 ` Simon Glass
2017-05-24 8:18 ` Heiko Stuebner
2017-05-24 12:56 ` Tom Rini
2017-06-01 3:11 ` Simon Glass
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=1969746.8ixlS7VFTt@phil \
--to=heiko@sntech.de \
--cc=u-boot@lists.denx.de \
/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