From: "Rob Herring (Arm)" <robh@kernel.org>
To: Vaishnav Achath <vaishnav.a@ti.com>
Cc: dmaengine@vger.kernel.org, peter.ujfalusi@gmail.com,
linux-kernel@vger.kernel.org, u-kumar1@ti.com,
j-choudhary@ti.com, vkoul@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, vigneshr@ti.com
Subject: Re: [PATCH v3 1/2] dt-bindings: dma: ti: k3-bcdma: Add J722S CSI BCDMA
Date: Wed, 27 Nov 2024 09:10:07 -0600 [thread overview]
Message-ID: <173272020652.3515198.4029351537372259051.robh@kernel.org> (raw)
In-Reply-To: <20241127101627.617537-2-vaishnav.a@ti.com>
On Wed, 27 Nov 2024 15:46:26 +0530, Vaishnav Achath wrote:
> J722S CSI BCDMA is similar to J721S2 CSI BCDMA and supports both RX and TX
> channels but has a different PSIL thread base ID which is currently
> handled in k3-udma driver. Add an entry for J722S CSIRX BCDMA.
>
> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
> ---
>
> V2->V3:
> * Added missing compatible entry missed in v2.
> * Address Krzysztof's review comments to not wrap commit
> message too early.
>
> V1->V2:
> * Address review from Conor to add new J722S compatible
> * J722S BCDMA is more similar to J721S2 in terms of RX/TX support,
> add an entry alongside J721S2 instead of modifying AM62A.
>
> Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-11-27 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 10:16 [PATCH v3 0/2] Add support for J722S CSI BCDMA Vaishnav Achath
2024-11-27 10:16 ` [PATCH v3 1/2] dt-bindings: dma: ti: k3-bcdma: Add " Vaishnav Achath
2024-11-27 15:10 ` Rob Herring (Arm) [this message]
2024-11-27 10:16 ` [PATCH v3 2/2] dmaengine: ti: k3-udma: Add support for " Vaishnav Achath
2024-12-04 12:30 ` Vinod Koul
2024-12-09 4:29 ` Vaishnav Achath
2024-12-18 22:09 ` Péter Ujfalusi
2024-12-24 10:42 ` [PATCH v3 0/2] " Vinod Koul
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=173272020652.3515198.4029351537372259051.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.com \
--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