From: shravan chippa <shravan.chippa@microchip.com>
To: <green.wan@sifive.com>, <vkoul@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <palmer@dabbelt.com>,
<paul.walmsley@sifive.com>, <conor+dt@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<nagasuresh.relli@microchip.com>, <praveen.kumar@microchip.com>,
<shravan.chippa@microchip.com>
Subject: [PATCH v5 0/4] dma: sf-pdma: various sf-pdma updates for the mpfs platform
Date: Fri, 8 Dec 2023 16:08:52 +0530 [thread overview]
Message-ID: <20231208103856.3732998-1-shravan.chippa@microchip.com> (raw)
From: Shravan Chippa <shravan.chippa@microchip.com>
Changes from V4 -> V5:
Modified commit msg
Replaced the sf_pdma_of_xlate() function with
of_dma_xlate_by_chan_id()
Changes from V3 -> V4:
Removed unnecessary parentheses and extra space Added review tags
Changes from V2 -> V3:
Removed whitespace
Change naming convention of the macros (modified code as per new macros)
updated with new API device_get_match_data()
modified dt-bindings as per the commmets from v2
modified compatible name string for mpfs platform
Changes from V1 -> V2:
Removed internal review tags
Commit massages modified.
Added devicetree patch with new compatible name for mpfs platform
Added of_dma_controller_free() clenup call in sf_pdma_remove() function
V1:
This series does the following
1. Adds a PolarFire SoC specific compatible and code to support for
out-of-order dma transfers
2. Adds generic device tree bindings support by using
of_dma_controller_register()
Shravan Chippa (4):
dmaengine: sf-pdma: Support of_dma_controller_register()
dt-bindings: dma: sf-pdma: add new compatible name
dmaengine: sf-pdma: add mpfs-pdma compatible name
riscv: dts: microchip: add specific compatible for mpfs pdma
.../bindings/dma/sifive,fu540-c000-pdma.yaml | 1 +
arch/riscv/boot/dts/microchip/mpfs.dtsi | 2 +-
drivers/dma/sf-pdma/sf-pdma.c | 44 +++++++++++++++++--
drivers/dma/sf-pdma/sf-pdma.h | 8 +++-
4 files changed, 50 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-08 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 10:38 shravan chippa [this message]
2023-12-08 10:38 ` [PATCH v5 1/4] dmaengine: sf-pdma: Support of_dma_controller_register() shravan chippa
2023-12-08 10:38 ` [PATCH v5 2/4] dt-bindings: dma: sf-pdma: add new compatible name shravan chippa
2023-12-08 10:38 ` [PATCH v5 3/4] dmaengine: sf-pdma: add mpfs-pdma " shravan chippa
2023-12-08 10:38 ` [PATCH v5 4/4] riscv: dts: microchip: add specific compatible for mpfs pdma shravan chippa
2023-12-11 15:04 ` (subset) [PATCH v5 0/4] dma: sf-pdma: various sf-pdma updates for the mpfs platform Vinod Koul
2024-02-06 19:39 ` Conor Dooley
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=20231208103856.3732998-1-shravan.chippa@microchip.com \
--to=shravan.chippa@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=green.wan@sifive.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nagasuresh.relli@microchip.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=praveen.kumar@microchip.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 read-only IMAP folder(s) and NNTP newsgroup(s).