From: Rob Herring <robh+dt@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Ulf Hansson <ulf.hansson@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Stefan Agner <stefan@agner.ch>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Brian Norris <computersforpeace@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Heiko Stuebner <heiko@sntech.de>,
Jisheng Zhang <jszhang@marvell.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"devicetree-spec@vger.kernel.org"
<devicetree-spec@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Venu Byravarasu <vbyravarasu@nvidia.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Jon Hunter <jonathanh@nvidia.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Grant Grundler <grundler@chromium.org>,
Kumar Gala <galak@codeaurora.org>,
"Luca Porzio (lporzio)" <lporzio@micron.com>,
Chaotian Jing <chaotian.jing@mediatek.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Sudeep Holla <sudeep.holla@arm.com>,
zhonghui.fu@linux.intel.com, kirill.shutemov@linux.intel.com
Subject: Re: [PATCH v2 0/4] Patches to allow consistent mmc / mmcblk numbering w/ device tree
Date: Sat, 30 Apr 2016 08:23:17 -0500 [thread overview]
Message-ID: <CAL_JsqKOwshLWyXr3moMXo8GeDwHgoNRU6gWm3D9WBivoqskEg@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=U5jnJJ3v=nFGFecoKB5KGv1ufC+aKbHx2iCqBTWpDTww@mail.gmail.com>
On Fri, Apr 29, 2016 at 6:01 PM, Doug Anderson <dianders@chromium.org> wrote:
> Hi,
>
> On Fri, Apr 29, 2016 at 3:44 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> My reply would be... why should MMC have special handling that no
>> other subsystem has?
>
> No other subsystem?
>
> * i2c allows numbering devices by alias
> * rtc allows numbering devices by alias.
> * serial allows numbering devices by alias.
> * spi allows numbering devices by alias.
> * watchdog allows numbering devices by alias.
>
> ...at least that's my impression doing a grep for of_alias_get_id(),
> which I suggested earlier in this thread but apparently wasn't done.
IMO, we should remove most or all of these not add more. We shoud move
to identifying devices by other OS independent means. Peter already
pointed out why serial is a problem.
Rob
next prev parent reply other threads:[~2016-04-30 13:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 17:32 [PATCH v2 0/4] Patches to allow consistent mmc / mmcblk numbering w/ device tree Douglas Anderson
2016-04-29 17:32 ` [PATCH v2 1/4] Documentation: mmc: Document mmc aliases Douglas Anderson
2016-04-29 17:32 ` [PATCH v2 2/4] mmc: read mmc alias from device tree Douglas Anderson
2016-04-29 17:32 ` [PATCH v2 3/4] mmc: use SD/MMC host ID for block device name ID Douglas Anderson
2016-04-29 17:32 ` [PATCH v2 4/4] ARM: dts: rockchip: Add mmc aliases for rk3288 platform Douglas Anderson
2016-04-29 18:12 ` [PATCH v2 0/4] Patches to allow consistent mmc / mmcblk numbering w/ device tree Rob Herring
2016-04-29 19:31 ` Doug Anderson
2016-04-29 19:50 ` Russell King - ARM Linux
2016-04-29 20:02 ` Doug Anderson
2016-04-29 18:12 ` Russell King - ARM Linux
2016-04-29 19:43 ` Doug Anderson
2016-04-29 19:57 ` Russell King - ARM Linux
2016-04-29 20:04 ` Doug Anderson
2016-04-29 21:13 ` Russell King - ARM Linux
2016-04-29 21:17 ` Doug Anderson
2016-04-29 21:29 ` Russell King - ARM Linux
2016-04-29 21:39 ` Doug Anderson
2016-04-29 21:50 ` Russell King - ARM Linux
2016-04-29 21:56 ` Doug Anderson
2016-04-29 22:16 ` Russell King - ARM Linux
2016-04-29 22:22 ` Doug Anderson
2016-04-29 22:44 ` Russell King - ARM Linux
2016-04-29 23:01 ` Doug Anderson
2016-04-29 23:58 ` Peter Hurley
[not found] ` <CAD=FV=V_YyfBOSs7BLkyhv=_5HBmf3djUWACbL6d-bwnrueDjA@mail.gmail.com>
2016-04-30 0:31 ` Peter Hurley
2016-04-30 2:29 ` Doug Anderson
2016-04-30 8:38 ` Russell King - ARM Linux
2016-04-30 13:23 ` Rob Herring [this message]
2016-04-29 22:42 ` Javier Martinez Canillas
2016-04-30 10:48 ` Russell King - ARM Linux
2016-05-03 19:17 ` Trent Piepho
2016-05-04 7:18 ` Pavel Machek
2016-05-04 12:25 ` Rob Herring
2016-05-04 12:46 ` Pavel Machek
2019-03-05 12:39 ` Måns Rullgård
2019-03-15 21:52 ` Tim Harvey
2019-03-15 23:00 ` Marek Vasut
2019-03-15 23:13 ` Tim Harvey
2019-03-15 23:23 ` Doug Anderson
[not found] ` <yw1xftrn2em9.fsf@mansr.com>
2019-03-16 12:33 ` Marek Vasut
2019-03-16 15:39 ` Russell King - ARM Linux admin
2019-03-17 15:05 ` Stefan Agner
2019-03-17 15:43 ` Russell King - ARM Linux admin
2019-03-17 15:50 ` Marek Vasut
2019-03-17 16:48 ` Måns Rullgård
2019-03-17 16:59 ` Russell King - ARM Linux admin
2019-03-27 17:37 ` Tim Harvey
2019-03-27 20:54 ` Russell King - ARM Linux admin
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=CAL_JsqKOwshLWyXr3moMXo8GeDwHgoNRU6gWm3D9WBivoqskEg@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=chaotian.jing@mediatek.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=grundler@chromium.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=jonathanh@nvidia.com \
--cc=jszhang@marvell.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=lporzio@micron.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=shawn.lin@rock-chips.com \
--cc=stefan@agner.ch \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=vbyravarasu@nvidia.com \
--cc=zhonghui.fu@linux.intel.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).