From: Alex Soo <yuklin.soo@starfivetech.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Yangtao Li <frank.li@vivo.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>
Cc: <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alex Soo <yuklin.soo@starfivetech.com>
Subject: [PATCH 0/3] Add driver for Cadence SD6HC SD/eMMC controller
Date: Thu, 28 Dec 2023 14:53:19 +0800 [thread overview]
Message-ID: <20231228065322.1176351-1-yuklin.soo@starfivetech.com> (raw)
Starfive JH8100 SoC consists of a Cadence SD/eMMC host controller
(Version 6) with Combo PHY which provides DFI interface to SD/eMMC
removable or embedded devices. This patch adds initial SD/eMMC support
for JH8100 SoC by providing device drivers for Cadence SD/eMMC Version 6
host controller and Combo PHY. This patch series is depending on the
JH8100 base patch series in [1], [2], and [3].
The relevant dt-bindings documentation has been updated accordingly.
[1] https://lore.kernel.org/lkml/20231201121410.95298-1-jeeheng.sia@starfivetech.com/
[2] https://lore.kernel.org/lkml/20231206115000.295825-1-jeeheng.sia@starfivetech.com/
[3] https://lore.kernel.org/lkml/20231221083622.3445726-1-yuklin.soo@starfivetech.com/
Alex Soo (3):
dt-bindings: mmc: sdhci-cadence6: add DT bindings documentation
mmc: sdhci-cadence6: add Cadence SD6HC support
riscv: dts: starfive: jh8100: Add SD/eMMC device tree nodes
.../devicetree/bindings/mmc/cdns,sd6hci.yaml | 65 +++
MAINTAINERS | 6 +
arch/riscv/boot/dts/starfive/jh8100.dtsi | 34 ++
drivers/mmc/host/Kconfig | 11 +
drivers/mmc/host/Makefile | 2 +
drivers/mmc/host/sdhci-cadence6-phy.c | 384 +++++++++++++
drivers/mmc/host/sdhci-cadence6.c | 531 ++++++++++++++++++
drivers/mmc/host/sdhci-cadence6.h | 148 +++++
8 files changed, 1181 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/cdns,sd6hci.yaml
create mode 100644 drivers/mmc/host/sdhci-cadence6-phy.c
create mode 100644 drivers/mmc/host/sdhci-cadence6.c
create mode 100644 drivers/mmc/host/sdhci-cadence6.h
--
2.25.1
next reply other threads:[~2023-12-28 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 6:53 Alex Soo [this message]
2023-12-28 6:53 ` [PATCH 1/3] dt-bindings: mmc: sdhci-cadence6: add DT bindings documentation Alex Soo
2024-01-04 9:28 ` Krzysztof Kozlowski
2023-12-28 6:53 ` [PATCH 2/3] mmc: sdhci-cadence6: add Cadence SD6HC support Alex Soo
2024-01-04 9:29 ` Krzysztof Kozlowski
2023-12-28 6:53 ` [PATCH 3/3] riscv: dts: starfive: jh8100: Add SD/eMMC device tree nodes Alex Soo
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=20231228065322.1176351-1-yuklin.soo@starfivetech.com \
--to=yuklin.soo@starfivetech.com \
--cc=adrian.hunter@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@vivo.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).