From: Tony Lindgren <tony@atomide.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Sebastian Reichel <sre@kernel.org>, Pavel Machel <pavel@ucw.cz>,
Timo Kokkonen <timo.t.kokkonen@iki.fi>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: OMAP2+: n900 needs MMC slot names for legacy user space
Date: Wed, 27 Apr 2016 07:17:03 -0700 [thread overview]
Message-ID: <20160427141703.GW5995@atomide.com> (raw)
In-Reply-To: <CAPDyKFokkpF_-yxE+G2_nvC2q3uHkMCxZJHYU7y4KRRDWfvPTQ@mail.gmail.com>
* Ulf Hansson <ulf.hansson@linaro.org> [160427 01:50]:
> On 27 April 2016 at 01:46, Tony Lindgren <tony@atomide.com> wrote:
> > Let's pass the slot names in pdata like the legacy code does.
> > Once we have a generic DT binding for the slot names we can
> > switch to that.
>
> I am not sure we ever will get a DT binding accepted for the slot
> name. It seem far from being a HW description. :-)
Hmm it does describe where on the the device the MMC is
located though as in "external" or "internal".
> Instead, the long term and proper solution, is to enable userspace to
> be able to use UUID/PARTID instead.
OK.
> Until that happens, I guess this will have to do.
Yeah especially as that has been working with the legacy booting
for years.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP2+: n900 needs MMC slot names for legacy user space
Date: Wed, 27 Apr 2016 07:17:03 -0700 [thread overview]
Message-ID: <20160427141703.GW5995@atomide.com> (raw)
In-Reply-To: <CAPDyKFokkpF_-yxE+G2_nvC2q3uHkMCxZJHYU7y4KRRDWfvPTQ@mail.gmail.com>
* Ulf Hansson <ulf.hansson@linaro.org> [160427 01:50]:
> On 27 April 2016 at 01:46, Tony Lindgren <tony@atomide.com> wrote:
> > Let's pass the slot names in pdata like the legacy code does.
> > Once we have a generic DT binding for the slot names we can
> > switch to that.
>
> I am not sure we ever will get a DT binding accepted for the slot
> name. It seem far from being a HW description. :-)
Hmm it does describe where on the the device the MMC is
located though as in "external" or "internal".
> Instead, the long term and proper solution, is to enable userspace to
> be able to use UUID/PARTID instead.
OK.
> Until that happens, I guess this will have to do.
Yeah especially as that has been working with the legacy booting
for years.
Regards,
Tony
next prev parent reply other threads:[~2016-04-27 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:46 [PATCH 0/2] Pass n900 MMC slot names in pdata for legacy user space Tony Lindgren
2016-04-26 23:46 ` Tony Lindgren
2016-04-26 23:46 ` [PATCH 1/2] ARM: OMAP2+: n900 needs MMC slot names " Tony Lindgren
2016-04-26 23:46 ` Tony Lindgren
2016-04-27 8:48 ` Ulf Hansson
2016-04-27 8:48 ` Ulf Hansson
2016-04-27 14:17 ` Tony Lindgren [this message]
2016-04-27 14:17 ` Tony Lindgren
2016-05-02 7:05 ` Pavel Machek
2016-05-02 7:05 ` Pavel Machek
2016-04-26 23:46 ` [PATCH 2/2] mmc: omap_hsmmc: Check if MMC slot name is passed in pdata Tony Lindgren
2016-04-26 23:46 ` Tony Lindgren
2016-04-27 8:52 ` Ulf Hansson
2016-04-27 8:52 ` Ulf Hansson
2016-04-27 14:17 ` Tony Lindgren
2016-04-27 14:17 ` Tony Lindgren
2016-04-28 20:33 ` [PATCH 0/2] Pass n900 MMC slot names in pdata for legacy user space Ivaylo Dimitrov
2016-04-28 20:33 ` Ivaylo Dimitrov
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=20160427141703.GW5995@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=timo.t.kokkonen@iki.fi \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.