From: Yang Xiwen <forbidden405@outlook.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Igor Opaniuk <igor.opaniuk@linaro.org>,
tianshuliang <tianshuliang@hisilicon.com>,
David Yang <mmyangfl@gmail.com>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org,
Yang Xiwen <forbidden405@outlook.com>
Subject: [PATCH v3 0/4] mmc: add hi3798mv200 specific extensions of DWMMC
Date: Sat, 17 Feb 2024 05:02:28 +0800 [thread overview]
Message-ID: <20240217-b4-mmc-hi3798mv200-v3-0-f15464176947@outlook.com> (raw)
it's modified from hi3798cv200 driver, but quite a lot of code gets
rewritten because of the hardware differences. Actually cv200 DWMMC core
is called HIMCIV200 while mv200 DWMMC core is called HIMCIV300 in
downstream.
Pending on:
[PATCH] mmc: host: replace 1st argument to struct device * for mmc_of_parse_clk_phase():
https://lore.kernel.org/all/20240215-mmc_phase-v1-1-f27644ee13e4@outlook.com/
Signed-off-by: Yang Xiwen <forbidden405@outlook.com>
---
Changes in v3:
- dw_mmc-hi3798: fix bot error (Rob Herring)
- Link to v2: https://lore.kernel.org/r/20240216-b4-mmc-hi3798mv200-v2-0-010d63e6a1d5@outlook.com
Changes in v2:
- dw_mmc-hi3798mv200: use dev_err_probe() helper - Suggested by Krzysztof Kozlowski.
- dw_mmc-hi3798mv200: add missing err=0;
- dw_mmc-hi3798c(m)v200: remove unused MODULE_ALIAS() - Suggested by Krzysztof Kozlowski.
- binding: rename the binding, a lot of tweaks suggested by Krzysztof Kozlowski.
- Link to v1: https://lore.kernel.org/r/20240216-b4-mmc-hi3798mv200-v1-0-7d46db845ae6@outlook.com
---
Yang Xiwen (4):
mmc: dw_mmc-hi3798cv200: remove MODULE_ALIAS()
mmc: dw_mmc: add support for hi3798mv200
dt-bindings: mmc: dw-mshc-hi3798cv200: convert to YAML
dt-bindings: mmc: hisilicon,hi3798cv200-dw-mshc: rename to hisilicon,hi3798-dw-mshc
.../bindings/mmc/hi3798cv200-dw-mshc.txt | 40 ----
.../bindings/mmc/hisilicon,hi3798-dw-mshc.yaml | 94 +++++++++
drivers/mmc/host/Kconfig | 9 +
drivers/mmc/host/Makefile | 1 +
drivers/mmc/host/dw_mmc-hi3798cv200.c | 1 -
drivers/mmc/host/dw_mmc-hi3798mv200.c | 235 +++++++++++++++++++++
6 files changed, 339 insertions(+), 41 deletions(-)
---
base-commit: 8d3dea210042f54b952b481838c1e7dfc4ec751d
change-id: 20240121-b4-mmc-hi3798mv200-a5730edf122c
Best regards,
--
Yang Xiwen <forbidden405@outlook.com>
next reply other threads:[~2024-02-16 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 21:02 Yang Xiwen [this message]
2024-02-16 21:02 ` [PATCH v3 1/4] mmc: dw_mmc-hi3798cv200: remove MODULE_ALIAS() Yang Xiwen
2024-02-16 21:02 ` [PATCH v3 2/4] mmc: dw_mmc: add support for hi3798mv200 Yang Xiwen
2024-02-16 21:02 ` [PATCH v3 3/4] dt-bindings: mmc: dw-mshc-hi3798cv200: convert to YAML Yang Xiwen
2024-02-16 21:02 ` [PATCH v3 4/4] dt-bindings: mmc: hisilicon,hi3798cv200-dw-mshc: rename to hisilicon,hi3798-dw-mshc Yang Xiwen
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=20240217-b4-mmc-hi3798mv200-v3-0-f15464176947@outlook.com \
--to=forbidden405@outlook.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.opaniuk@linaro.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=mmyangfl@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tianshuliang@hisilicon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).