From: Wolfram Sang <wsa@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
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: Re: [PATCH 1/3] dt-bindings: i2c: mv64xxx: Document DMA properties
Date: Wed, 7 Sep 2022 22:02:28 +0200 [thread overview]
Message-ID: <Yxj41IrD/WzMSeac@shikoro> (raw)
In-Reply-To: <20220830020824.62288-2-samuel@sholland.org>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
On Mon, Aug 29, 2022 at 09:08:22PM -0500, Samuel Holland wrote:
> Allwinner's I2C offload engine includes bidirectional DMA support. Add
> the properties for describing this in the devicetree. "dmas" is optional
> because not all instances of the controller have their DRQs hooked up.
> For example, R_I2C0 and R_I2C1 on V536 have no DRQ number assigned.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-07 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 2:08 [PATCH 0/3] DMA binding for Allwinner V536/newer I2C Samuel Holland
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 [this message]
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=Yxj41IrD/WzMSeac@shikoro \
--to=wsa@kernel.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=samuel@sholland.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).