From: Ulf Hansson <ulf.hansson@linaro.org>
To: William Qiu <william.qiu@starfivetech.com>
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-mmc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] StarFive's SDIO/eMMC driver support
Date: Wed, 15 Feb 2023 13:37:40 +0100 [thread overview]
Message-ID: <CAPDyKFqJxrLh+pgQ-u_Lwxv4_TsH--rga049GBTqKAa_M14_yw@mail.gmail.com> (raw)
In-Reply-To: <20230215113249.47727-1-william.qiu@starfivetech.com>
On Wed, 15 Feb 2023 at 12:32, William Qiu <william.qiu@starfivetech.com> wrote:
>
> 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/20221220011247.35560-1-hal.feng@starfivetech.com/
>
> Changes v3->v4:
> - Added documentation to describe StarFive System Controller Registers.
> - Added aon_syscon and stg_syscon node.
> - Fixed some checkpatch errors/warnings.
>
> Changes v2->v3:
> - Wraped commit message according to Linux coding style.
> - Rephrased the description of the patches.
> - Changed the description of syscon regsiter.
> - Dropped redundant properties.
>
> Changes v1->v2:
> - 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.
>
> William Qiu (4):
> dt-bindings: mmc: Add StarFive MMC module
> mmc: starfive: Add sdio/emmc driver support
> riscv: dts: starfive: Add mmc node
> dt-bindings: syscon: Add StarFive syscon doc
>
> .../bindings/mmc/starfive,jh7110-mmc.yaml | 77 ++++++++
> .../bindings/soc/starfive/jh7110-syscon.yaml | 51 +++++
> MAINTAINERS | 11 ++
> .../jh7110-starfive-visionfive-2.dtsi | 23 +++
> arch/riscv/boot/dts/starfive/jh7110.dtsi | 47 +++++
> drivers/mmc/host/Kconfig | 10 +
> drivers/mmc/host/Makefile | 1 +
> drivers/mmc/host/dw_mmc-starfive.c | 186 ++++++++++++++++++
> 8 files changed, 406 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mmc/starfive,jh7110-mmc.yaml
> create mode 100644 Documentation/devicetree/bindings/soc/starfive/jh7110-syscon.yaml
> create mode 100644 drivers/mmc/host/dw_mmc-starfive.c
>
I have dropped the v3 patches and applied patch1 and patch2 from the
v4 series instead, for my next branch, thanks!
Kind regards
Uffe
next prev parent reply other threads:[~2023-02-15 12:38 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 11:32 [PATCH v4 0/4] StarFive's SDIO/eMMC driver support William Qiu
2023-02-15 11:32 ` [PATCH v4 1/4] dt-bindings: mmc: Add StarFive MMC module William Qiu
2023-02-15 11:59 ` Shengyu Qu
2023-02-15 12:08 ` William Qiu
2023-02-15 16:49 ` Shengyu Qu
[not found] ` <202302160545.31G5jiuf087662@SH1-CSMTP-DB111.sundns.com>
2023-02-16 5:51 ` William Qiu
2023-02-16 10:21 ` Krzysztof Kozlowski
2023-02-16 10:31 ` Conor Dooley
2023-02-16 10:39 ` Shengyu Qu
[not found] ` <a7b51602-3ba4-d822-4da0-f6e51e7dddea@outlook.com>
2023-02-15 12:03 ` Shengyu Qu
2023-02-15 11:32 ` [PATCH v4 2/4] mmc: starfive: Add sdio/emmc driver support William Qiu
2023-03-27 16:01 ` Shengyu Qu
2023-03-28 16:08 ` Shengyu Qu
2023-03-31 9:33 ` William Qiu
2023-04-10 18:04 ` Shengyu Qu
2023-04-11 2:54 ` William Qiu
2023-02-15 11:32 ` [PATCH v4 3/4] riscv: dts: starfive: Add mmc node William Qiu
2023-02-15 12:12 ` Emil Renner Berthing
2023-02-15 12:22 ` Emil Renner Berthing
2023-02-15 12:26 ` William Qiu
2023-08-05 13:14 ` Emil Renner Berthing
2023-08-07 1:51 ` William Qiu
2023-02-15 12:26 ` William Qiu
2023-02-15 11:32 ` [PATCH v4 4/4] dt-bindings: syscon: Add StarFive syscon doc William Qiu
2023-02-16 10:23 ` Krzysztof Kozlowski
2023-02-16 10:29 ` Conor Dooley
2023-02-16 10:31 ` Krzysztof Kozlowski
2023-03-06 14:04 ` Conor Dooley
2023-03-07 1:43 ` William Qiu
2023-02-16 10:30 ` William Qiu
2023-02-16 10:32 ` Krzysztof Kozlowski
2023-02-20 23:43 ` Rob Herring
2023-02-21 2:44 ` William Qiu
2023-02-27 22:29 ` Rob Herring
2023-02-28 9:05 ` William Qiu
2023-02-28 10:37 ` Krzysztof Kozlowski
2023-02-28 11:02 ` Emil Renner Berthing
2023-02-28 11:28 ` Krzysztof Kozlowski
2023-02-28 14:59 ` Emil Renner Berthing
2023-02-28 16:59 ` Krzysztof Kozlowski
2023-02-28 17:31 ` Emil Renner Berthing
2023-02-28 18:06 ` Conor Dooley
2023-02-28 11:08 ` Conor Dooley
2023-02-15 12:37 ` Ulf Hansson [this message]
2023-02-27 7:47 ` [PATCH v4 0/4] StarFive's SDIO/eMMC driver support William Qiu
2023-02-27 14:53 ` Ulf Hansson
2023-02-28 5:56 ` 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=CAPDyKFqJxrLh+pgQ-u_Lwxv4_TsH--rga049GBTqKAa_M14_yw@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--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=william.qiu@starfivetech.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).