From: Samuel Holland <samuel@sholland.org>
To: Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
linux-sunxi@lists.linux.dev
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Samuel Holland <samuel@sholland.org>
Subject: [PATCH 0/4] dmaengine: sun6i: Allwinner D1 support
Date: Thu, 18 Nov 2021 23:26:57 -0600 [thread overview]
Message-ID: <20211119052702.14392-1-samuel@sholland.org> (raw)
D1 is a new RISC-V SoC that uses mostly the same peripherals as
existing ARM-based sunxi SoCs. This series adds dmaengine support for
D1, after fixing an issue where the driver depended on architecture-
specific behavior (patch 2) and resolving a TODO item (patch 3).
Samuel Holland (4):
dt-bindings: dma: sun50i-a64: Add compatible for D1
dmaengine: sun6i: Do not use virt_to_phys
dmaengine: sun6i: Add support for 34-bit physical addresses
dmaengine: sun6i: Add support for the D1 variant
.../dma/allwinner,sun50i-a64-dma.yaml | 9 ++-
drivers/dma/Kconfig | 2 +-
drivers/dma/sun6i-dma.c | 78 +++++++++++++------
3 files changed, 61 insertions(+), 28 deletions(-)
--
2.32.0
next reply other threads:[~2021-11-19 5:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 5:26 Samuel Holland [this message]
2021-11-19 5:26 ` [PATCH 1/4] dt-bindings: dma: sun50i-a64: Add compatible for D1 Samuel Holland
2021-11-29 23:13 ` Rob Herring
2021-11-19 5:26 ` [PATCH 2/4] dmaengine: sun6i: Do not use virt_to_phys Samuel Holland
2021-11-19 5:27 ` [PATCH 3/4] dmaengine: sun6i: Add support for 34-bit physical addresses Samuel Holland
2021-11-22 8:45 ` Maxime Ripard
2021-11-19 5:27 ` [PATCH 4/4] dmaengine: sun6i: Add support for the D1 variant Samuel Holland
2021-11-22 8:45 ` [PATCH 0/4] dmaengine: sun6i: Allwinner D1 support Maxime Ripard
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=20211119052702.14392-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=wens@csie.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).