From: Samuel Holland <samuel@sholland.org>
To: Chen-Yu Tsai <wens@csie.org>, Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: Samuel Holland <samuel@sholland.org>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@lists.linux.dev
Subject: [PATCH 0/3] DMA binding for Allwinner V536/newer I2C
Date: Mon, 29 Aug 2022 21:08:21 -0500 [thread overview]
Message-ID: <20220830020824.62288-1-samuel@sholland.org> (raw)
This series documents the DMA capability of the I2C offload engine in
Allwinner V536 and newer SoCs. This includes the following SoCs which
have some support in mainline Linux:
- A100 (updated by this series)
- H616 (missing DMA controller binding/support)
- D1 (initial DT submission is on the ML; this series resolves some
dtbs_check warnings with that DT)
Samuel Holland (2):
dt-bindings: i2c: mv64xxx: Document DMA properties
arm64: dts: allwinner: a100: Add I2C DMA requests
Yangtao Li (1):
arm64: dts: allwinner: a100: Add device node for DMA controller
.../bindings/i2c/marvell,mv64xxx-i2c.yaml | 13 ++++++++++
.../arm64/boot/dts/allwinner/sun50i-a100.dtsi | 24 +++++++++++++++++++
2 files changed, 37 insertions(+)
--
2.35.1
next reply other threads:[~2022-08-30 2:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 2:08 Samuel Holland [this message]
2022-08-30 2:08 ` [PATCH 1/3] dt-bindings: i2c: mv64xxx: Document DMA properties Samuel Holland
2022-08-30 9:36 ` Krzysztof Kozlowski
2022-08-30 13:10 ` Samuel Holland
2022-08-30 13:23 ` Krzysztof Kozlowski
2022-09-07 20:02 ` Wolfram Sang
2022-08-30 2:08 ` [PATCH 2/3] arm64: dts: allwinner: a100: Add device node for DMA controller Samuel Holland
2022-09-06 21:09 ` Jernej Škrabec
2022-09-08 20:01 ` Jernej Škrabec
2022-08-30 2:08 ` [PATCH 3/3] arm64: dts: allwinner: a100: Add I2C DMA requests Samuel Holland
2022-09-06 21:11 ` Jernej Škrabec
2022-09-08 20:01 ` Jernej Škrabec
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=20220830020824.62288-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh+dt@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).