From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: [PATCH 0/6] v3u: add SDHI/MMC support
Date: Sun, 27 Dec 2020 18:41:54 +0100 [thread overview]
Message-ID: <20201227174202.40834-1-wsa+renesas@sang-engineering.com> (raw)
So, this series adds SDHI/MMC support to the Renesas R-Car V3U SoC.
While SDHI is usually complicated, adding basic support to V3U was
refreshingly uncomplicated :) The crux was this time in the CPG driver.
In order to avoid code duplication, a CPG library was introduced, so we
can share the SD clock handling between generic Gen3, V3U, and hopefully
Gen4 later. The library turned out to be a quite nice solution for SDHI.
I am quite happy with it. I think we could have a similar benefit for
RPC, but we still need to see if this is enabled on V3U after all.
So much for now, looking forward to comments. The branch is here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/v3u/sdhi
Happy hacking,
Wolfram
Takeshi Saito (2):
arm64: dts: renesas: r8a779a0: Add MMC node
arm64: dts: renesas: falcon: Enable MMC
Wolfram Sang (4):
dt-bindings: mmc: renesas,sdhi: Add r8a779a0 support
clk: renesas: rcar-gen3: remove cpg_quirks access when registering SD
clock
clk: renesas: rcar-gen3: factor out CPG library
clk: renesas: r8a779a0: add SDHI support
.../devicetree/bindings/mmc/renesas,sdhi.yaml | 1 +
.../boot/dts/renesas/r8a779a0-falcon.dts | 41 +++
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 12 +
drivers/clk/renesas/Kconfig | 5 +
drivers/clk/renesas/Makefile | 1 +
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 17 +-
drivers/clk/renesas/rcar-cpg-lib.c | 270 ++++++++++++++++++
drivers/clk/renesas/rcar-cpg-lib.h | 33 +++
drivers/clk/renesas/rcar-gen3-cpg.c | 267 +----------------
9 files changed, 387 insertions(+), 260 deletions(-)
create mode 100644 drivers/clk/renesas/rcar-cpg-lib.c
create mode 100644 drivers/clk/renesas/rcar-cpg-lib.h
--
2.28.0
next reply other threads:[~2020-12-27 17:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 17:41 Wolfram Sang [this message]
2020-12-27 17:41 ` [PATCH 1/6] dt-bindings: mmc: renesas,sdhi: Add r8a779a0 support Wolfram Sang
2021-01-08 3:36 ` Rob Herring
2021-01-08 12:23 ` Geert Uytterhoeven
2021-01-13 11:25 ` Ulf Hansson
2020-12-27 17:41 ` [PATCH 2/6] clk: renesas: rcar-gen3: remove cpg_quirks access when registering SD clock Wolfram Sang
2021-01-08 12:59 ` Geert Uytterhoeven
2020-12-27 17:41 ` [PATCH 3/6] clk: renesas: rcar-gen3: factor out CPG library Wolfram Sang
2021-01-08 12:59 ` Geert Uytterhoeven
2020-12-27 17:41 ` [PATCH 4/6] clk: renesas: r8a779a0: add SDHI support Wolfram Sang
2021-01-08 12:59 ` Geert Uytterhoeven
2020-12-27 17:41 ` [PATCH 5/6] arm64: dts: renesas: r8a779a0: Add MMC node Wolfram Sang
2020-12-27 17:45 ` Wolfram Sang
2021-01-08 12:47 ` Geert Uytterhoeven
2020-12-27 17:42 ` [PATCH 6/6] arm64: dts: renesas: falcon: Enable MMC Wolfram Sang
2021-01-08 12:59 ` Geert Uytterhoeven
2021-01-19 12:46 ` Wolfram Sang
2021-01-12 11:47 ` Geert Uytterhoeven
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=20201227174202.40834-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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).