[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=WjfHC_yR=1QrTWz+K5zv02c4sixngfsy8sX5zhDd0ppw@mail.gmail.com>
Date: Wed, 6 Aug 2014 12:43:10 -0700
From: Doug Anderson <dianders@...omium.org>
To: stefan@...er.ch, Chris Ball <chris@...ntf.net>,
Ulf Hansson <ulf.hansson@...aro.org>
Cc: "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
Russell King <linux@....linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Heiko Stübner <heiko@...ech.de>,
Addy Ke <addy.ke@...k-chips.com>,
Andrew Bresticker <abrestic@...omium.org>,
Olof Johansson <olof@...om.net>
Subject: Re: [RFC 1/2] mmc: read mmc alias from device tree
Stefan,
On Tue, Apr 1, 2014 at 1:35 PM, <stefan@...er.ch> wrote:
> From: Stefan Agner <stefan@...er.ch>
>
> To get the SD/MMC host device ID, read the alias from the device
> tree.
>
> This is useful in case a SoC has multipe SD/MMC host controllers while
> the second controller should logically be the first device (e.g. if
> the second controller is connected to an internal eMMC). Combined
> with block device numbering using MMC/SD host device ID, this
> results in predictable name assignment of the internal eMMC block
> device.
>
> Signed-off-by: Stefan Agner <stefan@...er.ch>
Yes, please. It is very handy to have mmc devices be enumerated in a
predictable way.
Reviewed-by: Doug Anderson <dianders@...omium.org>
Tested-by: Doug Anderson <dianders@...omium.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists