From: Stefan Agner <stefan@xxxxxxxx>
Nowadays SoCs usually have multiple SD/MMC host adapters. Often
the first is connected to an internal eMMC, however sometimes it
is the second controller that is connected to the eMMC.
If the second controller is connected to the eMMC, the number
assigned to the eMMC block device varies depending on whether the
external SD-Card is present or not.
The boot device could be specified using partition UUIDs, but
those can change when recreating the partition table. Especially
for embedded devices it would be preferable to have a reliable
assigned block device number.
The first patch aims to give a way to specify the logical SD/MMC
host order. This is achieved by extending the device tree using
aliases:
aliases {
mmc0 = "/sdhci@78000600";
mmc1 = "/sdhci@78000200";
};
The second patch then uses the SD/MMC host index as preferred id
for the block device.
In theory, one SD/MMC host could control multiple cards. For this
case, this patch is somewhat ugly. It would only assign the first
host/card combination with a predictable block number. However,
for the case at hand this would be sufficient.
Stefan Agner (2):
mmc: read mmc alias from device tree
mmc: use SD/MMC host ID for block device name ID
drivers/mmc/card/block.c | 3 ++-
drivers/mmc/core/host.c | 24 +++++++++++++++++++-----
2 files changed, 21 insertions(+), 6 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
