From: Biju Das <biju.das.jz@bp.renesas.com>
To: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Chris Brandt <chris.brandt@renesas.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH v4 0/4] Add RZ/G2L DMAC support
Date: Mon, 19 Jul 2021 10:25:31 +0100 [thread overview]
Message-ID: <20210719092535.4474-1-biju.das.jz@bp.renesas.com> (raw)
This patch series aims to add DMAC support on RZ/G2L SoC's.
It is based on the work done by Chris Brandt for RZ/A DMA driver.
v3->v4:
* Added Rob's Rb tag for binding patch.
* Incorporated Vinod and Geert's review comments.
v2->v3:
* Described clocks and resets in binding file as per Rob's feedback.
v1->v2
* Started using virtual DMAC
* Added Geert's Rb tag for binding patch.
Biju Das (4):
dt-bindings: dma: Document RZ/G2L bindings
drivers: dma: sh: Add DMAC driver for RZ/G2L SoC
arm64: dts: renesas: r9a07g044: Add DMAC support
arm64: defconfig: Enable DMA controller for RZ/G2L SoC's
.../bindings/dma/renesas,rz-dmac.yaml | 124 +++
arch/arm64/boot/dts/renesas/r9a07g044.dtsi | 36 +
arch/arm64/configs/defconfig | 1 +
drivers/dma/sh/Kconfig | 9 +
drivers/dma/sh/Makefile | 1 +
drivers/dma/sh/rz-dmac.c | 929 ++++++++++++++++++
6 files changed, 1100 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/renesas,rz-dmac.yaml
create mode 100644 drivers/dma/sh/rz-dmac.c
--
2.17.1
next reply other threads:[~2021-07-19 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 9:25 Biju Das [this message]
2021-07-19 9:25 ` [PATCH v4 2/4] drivers: dma: sh: Add DMAC driver for RZ/G2L SoC Biju Das
2021-07-27 7:56 ` Biju Das
2021-07-27 12:40 ` Vinod Koul
2021-07-27 13:45 ` Biju Das
2021-07-28 6:20 ` Vinod Koul
2021-07-28 7:00 ` Biju Das
2021-07-28 11:05 ` Vinod Koul
2021-07-28 11:58 ` Biju Das
2021-07-28 12:34 ` Geert Uytterhoeven
2021-07-28 12:42 ` Biju Das
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=20210719092535.4474-1-biju.das.jz@bp.renesas.com \
--to=biju.das.jz@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@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).