From: Maksim Kiselev <bigunclemax@gmail.com>
Cc: Maksim Kiselev <bigunclemax@gmail.com>,
Tom Rini <trini@konsulko.com>, Peng Fan <peng.fan@nxp.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Paul Barker <paul.barker.ct@bp.renesas.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Kever Yang <kever.yang@rock-chips.com>,
Oleksandr Suvorov <oleksandr.suvorov@foundries.io>,
Stefan Roese <sr@denx.de>, Peter Geis <pgwipeout@gmail.com>,
u-boot@lists.denx.de
Subject: [RFC PATCH v1 0/1] Add TH1520 eMMC/SD controller support
Date: Sat, 30 Mar 2024 20:59:45 +0300 [thread overview]
Message-ID: <20240330175948.80931-1-bigunclemax@gmail.com> (raw)
Hi list,
I want to introduce support for DesignWare SDHCI host controller
on Alibaba TH1520 SoC. The driver based on mainline Linux and Revyos
U-boot drivers. Work with eMMC and SD was tested on a LicheePi 4A board.
I would like to point out that the TH1520's SDHCI controller is very
similar to Rockchip's IPs those already have U-boot driver -
rockchip_sdhci.c
Also on Linux, T-head and Rockchip SDHCI controllers use a common driver -
sdhci-of-dwcmshc.c
At my glance we have two options:
- leave TH1520 in a separate driver
- stretch this driver on rockchip_sdhc
I chose the first option for now. And would be glad to hear your thoughts.
Best regards,
Maksim
Maksim Kiselev (1):
mmc: snps_sdhci: Add sdhci driver support for TH1520 SoC
drivers/mmc/Kconfig | 12 +
drivers/mmc/Makefile | 1 +
drivers/mmc/snps_sdhci.c | 464 +++++++++++++++++++++++++++++++++++++++
3 files changed, 477 insertions(+)
create mode 100644 drivers/mmc/snps_sdhci.c
--
2.40.1
next reply other threads:[~2024-03-30 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 17:59 Maksim Kiselev [this message]
2024-03-30 17:59 ` [RFC PATCH v1 1/1] mmc: snps_sdhci: Add sdhci driver support for TH1520 SoC Maksim Kiselev
2024-04-02 14:47 ` Heinrich Schuchardt
2024-04-02 17:19 ` Maxim Kiselev
2024-04-02 19:08 ` Heinrich Schuchardt
2024-04-02 15:39 ` Sean Anderson
2024-04-02 18:56 ` Maxim Kiselev
2024-04-17 10:50 ` Jaehoon Chung
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=20240330175948.80931-1-bigunclemax@gmail.com \
--to=bigunclemax@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=kever.yang@rock-chips.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=oleksandr.suvorov@foundries.io \
--cc=paul.barker.ct@bp.renesas.com \
--cc=peng.fan@nxp.com \
--cc=pgwipeout@gmail.com \
--cc=sr@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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