From: Vaishnav Achath <vaishnav.a@ti.com>
To: <peter.ujfalusi@gmail.com>, <vigneshr@ti.com>, <vkoul@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>
Cc: <devicetree@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>,
<j-choudhary@ti.com>, <vaishnav.a@ti.com>
Subject: [PATCH v3 0/2] Add support for J721S2 CSI BCDMA
Date: Fri, 5 May 2023 20:09:27 +0530 [thread overview]
Message-ID: <20230505143929.28131-1-vaishnav.a@ti.com> (raw)
This series adds support for J721S2 BCDMA instance for Camera Serial
Interface (CSI).
V1 : https://lore.kernel.org/all/20230503065303.16674-1-vaishnav.a@ti.com/
V2 : https://lore.kernel.org/all/20230505082602.31783-1-vaishnav.a@ti.com/
V2->V3:
* Avoid using if:else:if, instead move ti,am64-dmss-bcdma
to new if:, also keep entries in alphabetical order.
V1->V2:
Address Krzysztof's feedback:
* Move J721S2 BCDMA entry to else condition to avoid failure
with AM62A BCDMA in binding.
dtbs_check :
https://gist.github.com/vaishnavachath/221155d02575e0c5803a62f2ee22e70e
Vaishnav Achath (2):
dt-bindings: dma: ti: Add J721S2 BCDMA
dmaengine: ti: k3-udma: Add support for J721S2 CSI BCDMA instance
.../devicetree/bindings/dma/ti/k3-bcdma.yaml | 30 ++++++++++++++++++-
drivers/dma/ti/k3-udma.c | 25 ++++++++++++++++
2 files changed, 54 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2023-05-05 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 14:39 Vaishnav Achath [this message]
2023-05-05 14:39 ` [PATCH v3 1/2] dt-bindings: dma: ti: Add J721S2 BCDMA Vaishnav Achath
2023-05-05 17:53 ` Krzysztof Kozlowski
2023-05-05 14:39 ` [PATCH v3 2/2] dmaengine: ti: k3-udma: Add support for J721S2 CSI BCDMA instance Vaishnav Achath
2023-05-16 17:56 ` [PATCH v3 0/2] Add support for J721S2 CSI BCDMA 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=20230505143929.28131-1-vaishnav.a@ti.com \
--to=vaishnav.a@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@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;
as well as URLs for NNTP newsgroup(s).