From: William Qiu <william.qiu@starfivetech.com>
To: <linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-mmc@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
William Qiu <william.qiu@starfivetech.com>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/3] StarFive's SDIO/eMMC driver support
Date: Tue, 27 Dec 2022 20:22:24 +0800 [thread overview]
Message-ID: <20221227122227.460921-1-william.qiu@starfivetech.com> (raw)
Hi,
This patchset adds initial rudimentary support for the StarFive
designware mobile storage host controller driver. And this driver will
be used in StarFive's VisionFive 2 board. The main purpose of adding
this driver is to accommodate the ultra-high speed mode of eMMC.
The last patch should be applied after the patchset [1]:
[1] https://lore.kernel.org/all/20221118011714.70877-1-hal.feng@starfivetech.com/
Changes since v1:
- Renamed the dt-binding 'starfive,jh7110-sdio.yaml' to 'starfive,jh7110-mmc.yaml'.
- Changed the type of 'starfive,syscon' and modify its description.
- Deleted unused head files like '#include <linux/gpio.h>'.
- Added comment for the 'rise_point' and 'fall_point'.
- Changed the API 'num_caps' to 'common_caps'.
- Changed the node name 'sys_syscon' to 'syscon'.
- Changed the node name 'sdio' to 'mmc'.
The patch series is based on v6.1-rc5.
William Qiu (3):
dt-bindings: mmc: Add bindings for StarFive
mmc: starfive: Add sdio/emmc driver support
riscv: dts: starfive: Add mmc node
.../bindings/mmc/starfive,jh7110-mmc.yaml | 72 +++++++
MAINTAINERS | 6 +
.../jh7110-starfive-visionfive-v2.dts | 25 +++
arch/riscv/boot/dts/starfive/jh7110.dtsi | 38 ++++
drivers/mmc/host/Kconfig | 10 +
drivers/mmc/host/Makefile | 1 +
drivers/mmc/host/dw_mmc-starfive.c | 185 ++++++++++++++++++
7 files changed, 337 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/starfive,jh7110-mmc.yaml
create mode 100644 drivers/mmc/host/dw_mmc-starfive.c
--
2.34.1
next reply other threads:[~2022-12-27 12:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 12:22 William Qiu [this message]
2022-12-27 12:22 ` [PATCH v2 1/3] dt-bindings: mmc: Add bindings for StarFive William Qiu
2022-12-27 13:05 ` Krzysztof Kozlowski
2022-12-28 10:40 ` William Qiu
2022-12-27 12:22 ` [PATCH v2 2/3] mmc: starfive: Add sdio/emmc driver support William Qiu
2023-01-19 22:17 ` Conor Dooley
2022-12-27 12:22 ` [PATCH v2 3/3] riscv: dts: starfive: Add mmc node William Qiu
2023-01-02 14:03 ` Ulf Hansson
2023-01-04 6:08 ` William Qiu
2023-01-04 16:05 ` Ulf Hansson
2023-01-06 8:41 ` William Qiu
2023-01-19 18:43 ` Conor Dooley
2023-01-31 8:02 ` William Qiu
2023-01-06 8:44 ` [PATCH v2 0/3] StarFive's SDIO/eMMC driver support William Qiu
-- strict thread matches above, loose matches on Subject: below --
2022-12-27 11:58 William Qiu
2022-12-27 13:07 ` Krzysztof Kozlowski
2022-12-28 10:46 ` William Qiu
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=20221227122227.460921-1-william.qiu@starfivetech.com \
--to=william.qiu@starfivetech.com \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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).