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 v7 0/3] Add RZ/G2L DMAC support
Date: Fri, 6 Aug 2021 10:53:19 +0100 [thread overview]
Message-ID: <20210806095322.2326-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.
v6->v7:
* As per the DMA documention vc.lock must be held by caller for
vchan_cookie_complete. So added vc.lock for this function.
* Added lock for the lists used in rz_dmac_terminate_all.
v5->v6:
* Added Rb tag from Rob for binding patch
* Fixed dma_addr_t and size_t format specifier issue reported by
kernel test robot
* Started using ARRAY_SIZE macro instead of magic number in
rz_dmac_ds_to_val_mapping function.
v4->v5:
* Passing legacy slave channel configuration parameters using dmaengine_slave_config is prohibited.
So started passing this parameters in DT instead, by encoding MID/RID values with channel parameters
in the #dma-cells.
* Removed Rb tag's of Geert and Rob since there is a modification in binding patch
* Added 128 byte slave bus width support
* Removed SoC dtsi and Defconfig patch from this series. Will send as separate patch.
Ref:-
https://lore.kernel.org/linux-renesas-soc/20210719092535.4474-1-biju.das.jz@bp.renesas.com/T/#ma0b261df6d4400882204aaaaa014ddb59c479db4
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 (3):
dt-bindings: dma: Document RZ/G2L bindings
dmaengine: Extend the dma_slave_width for 128 bytes
drivers: dma: sh: Add DMAC driver for RZ/G2L SoC
.../bindings/dma/renesas,rz-dmac.yaml | 130 +++
drivers/dma/sh/Kconfig | 9 +
drivers/dma/sh/Makefile | 1 +
drivers/dma/sh/rz-dmac.c | 971 ++++++++++++++++++
include/linux/dmaengine.h | 3 +-
5 files changed, 1113 insertions(+), 1 deletion(-)
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-08-06 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 9:53 Biju Das [this message]
2021-08-06 9:53 ` [PATCH v7 1/3] dt-bindings: dma: Document RZ/G2L bindings Biju Das
2021-08-06 9:53 ` [PATCH v7 2/3] dmaengine: Extend the dma_slave_width for 128 bytes Biju Das
2021-08-06 9:53 ` [PATCH v7 3/3] drivers: dma: sh: Add DMAC driver for RZ/G2L SoC Biju Das
2021-08-16 7:52 ` [PATCH v7 0/3] Add RZ/G2L DMAC support Biju Das
2021-08-25 14:32 ` Vinod Koul
2021-08-25 14:38 ` 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=20210806095322.2326-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.