From: Drew Fustini <pdp7pdp7@gmail.com>
To: Jisheng Zhang <jszhang@kernel.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
linux-mmc@vger.kernel.org
Subject: Designware MSHC: dw_mmc versus sdhci-of-dwcmshc?
Date: Sat, 27 Aug 2022 13:07:16 -0700 [thread overview]
Message-ID: <Ywp5dA3iQLZu/+2d@x1> (raw)
Hello, I am bringing up Linux on an SoC which has Synopsys "DesignWare
Cores Mobile Storage Host Controller (Cryptographic)" IP configured to
support an eMMC 5.0 device (IS21ES08G) on the bring-up board. I am
trying to figure out why there are two seemingly similar drivers,
dw_mmc and sdhci-of-dwmshc, in drivers/mmc/host for Synopsys
DesignWare host controller IP. I am hoping someone might be able to
give me some insight into the history of these drivers.
I have found the following:
- dw_mmc.c is a "DW Multimedia Card Interface driver"
- created back in 2011 with f95f3850f7a9 ("mmc: dw_mmc: Add Synopsys
DesignWare mmc host driver.")
- CONFIG_MMC_DW refers to it as "Synopsys DesignWare Memory Card
Interface" with description of "Synopsys DesignWare Mobile Storage IP
block, this provides host support for SD and MMC interfaces, in both
PIO, internal DMA mode and external DMA mode"
- "snps,dw-mshc" compatible supported in dw_mmc-pltfm.c and
synopsys-dw-mshc.yaml binding refers to it as "Synopsys Designware
Mobile Storage Host Controller"
- sdhci-of-dwcmshc.c is a "SDHCI platform driver for Synopsys DWC MSHC"
- created more recently in 2018 with e438cf49b305 ("mmc:
sdhci-of-dwcmshc: add SDHCI OF Synopsys DWC MSHC driver")
- CONFIG_MMC_SDHCI_OF_DWCMSHC refers to it as "SDHCI OF support for
the Synopsys DWC MSHC" with description of "Synopsys DesignWare Cores
Mobile Storage Controller support."
- the driver supports "snps,dwcmshc-sdhci" compatible and the
snps,dwcmshc-sdhci.yaml binding describes it as "Synopsys Designware
Mobile Storage Host Controller"
I would greatly appreciate any advice anyone may have on which driver
might be the best fit.
Thank you,
Drew
next reply other threads:[~2022-08-27 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 20:07 Drew Fustini [this message]
2022-08-29 14:14 ` Designware MSHC: dw_mmc versus sdhci-of-dwcmshc? Jisheng Zhang
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=Ywp5dA3iQLZu/+2d@x1 \
--to=pdp7pdp7@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=jszhang@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox