From: Douglas Anderson <dianders@chromium.org>
To: ulf.hansson@linaro.org, jh80.chung@samsung.com
Cc: shawn.lin@rock-chips.com, adrian.hunter@intel.com,
stefan@agner.ch, linux-mmc@vger.kernel.org,
computersforpeace@gmail.com, dmitry.torokhov@gmail.com,
Douglas Anderson <dianders@chromium.org>,
mark.rutland@arm.com, vbyravarasu@nvidia.com,
justin.wang@spreadtrum.com, ksumrall@android.com,
lars@metafoo.de, dtor@chromium.org, jonathanh@nvidia.com,
huangtao@rock-chips.com, devicetree@vger.kernel.org,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, lporzio@micron.com, robh+dt@kernel.org,
chuanxiao.dong@intel.com, chaotian.jing@mediatek.com,
sergei.shtylyov@cogentembedded.com, linux-kernel@vger.kernel.org,
sudeep.holla@arm.com
Subject: [PATCH 0/3] Patches to allow consistent mmc / mmcblk numbering
Date: Thu, 28 Apr 2016 16:06:42 -0700 [thread overview]
Message-ID: <1461884805-29466-1-git-send-email-dianders@chromium.org> (raw)
This series picks patches from various different places to produce what
I consider the best solution to getting consistent mmc and mmcblk
ordering.
Why consistent ordering and why not just use UUIDs? IMHO consistent
ordering solves a few different problems:
1. For poor, feeble-minded humans like me, have sane numbering for
devices helps a lot. When grepping through dmesg it's terribly handy
if a given SDMMC device has a consistent number. I know that I can
do "dmesg | grep mmc0" or "dmesg | grep mmcblk0" to find info about
the eMMC. I know that I can do "dmesg | grep mmc1" to find info
about the SD card slot. I don't want it to matter which one probed
first, I don't want it to matter if I'm working on a variant of the
hardware that has the SD card slot disabled, and I don't want to care
what my boot device was. Worrying about what device number I got
increases my cognitive load.
2. There are cases where it's not trivially easy during development to
use the UUID. Specifically I work a lot with coreboot / depthcharge
as a BIOS. When configured properly, that BIOS has a nice feature to
allow you to fetch the kernel and kernel command line from TFTP by
pressing Ctrl-N. In this particular case the BIOS doesn't actually
know which disk I'd like for my root filesystem, so it's not so easy
for it to put the right UUID into the command line. For this
purpose, knowing that "mmcblk0" will always refer to eMMC is handy.
Jaehoon Chung (1):
Documentation: mmc: Document mmc aliases
Stefan Agner (2):
mmc: read mmc alias from device tree
mmc: use SD/MMC host ID for block device name ID
Documentation/devicetree/bindings/mmc/mmc.txt | 11 +++++++++++
drivers/mmc/card/block.c | 3 ++-
drivers/mmc/core/host.c | 25 ++++++++++++++++++++-----
3 files changed, 33 insertions(+), 6 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-04-28 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 23:06 Douglas Anderson [this message]
2016-04-28 23:06 ` [PATCH 1/3] Documentation: mmc: Document mmc aliases Douglas Anderson
2016-04-28 23:06 ` [PATCH 2/3] mmc: read mmc alias from device tree Douglas Anderson
2016-04-28 23:06 ` [PATCH 3/3] mmc: use SD/MMC host ID for block device name ID Douglas Anderson
2016-04-29 2:18 ` [PATCH 0/3] Patches to allow consistent mmc / mmcblk numbering Jisheng Zhang
2016-04-29 7:21 ` Ulf Hansson
2016-04-29 17:32 ` Doug Anderson
2016-04-29 17:39 ` Arnd Bergmann
2016-05-10 11:09 ` Ulf Hansson
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=1461884805-29466-1-git-send-email-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=adrian.hunter@intel.com \
--cc=chaotian.jing@mediatek.com \
--cc=chuanxiao.dong@intel.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@chromium.org \
--cc=galak@codeaurora.org \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=jonathanh@nvidia.com \
--cc=justin.wang@spreadtrum.com \
--cc=ksumrall@android.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lporzio@micron.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--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 \
/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).