From: Vignesh Raghavendra <vigneshr@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@gmail.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v2 0/4] dt-bindings: dma: ti: k3*: Update optional reg regions
Date: Wed, 22 Nov 2023 21:12:34 +0530 [thread overview]
Message-ID: <20231122154238.815781-1-vigneshr@ti.com> (raw)
DMAs on TI K3 SoCs have channel configuration registers region which are
usually hidden from Linux and configured via Device Manager Firmware
APIs. But certain early SWs like bootloader which run before Device
Manager is fully up would need to directly configure these registers and
thus require to be in DT description.
This add bindings for such configuration regions. Backward
compatibility is maintained to existing DT by only mandating existing
regions to be present and this new region as optional.
This update is mainly to aid SPL/U-Boot to reuse kernel DT as is. And is
applicable to entire K3 family of SoCs.
v2:
Fix issues pointed out by Conor and Peter
* Add new patch 1/4 to describe existing register regions
* Rename cfg region as ring
* Add bchan register space for bcdma
* Include descriptions for new registers
v1: https://lore.kernel.org/all/20230810174356.3322583-1-vigneshr@ti.com/
Vignesh Raghavendra (4):
dt-bindings: dma: ti: k3-*: Add descriptions for register regions
dt-bindings: dma: ti: k3-bcdma: Describe cfg register regions
dt-bindings: dma: ti: k3-pktdma: Describe cfg register regions
dt-bindings: dma: ti: k3-udma: Describe cfg register regions
.../devicetree/bindings/dma/ti/k3-bcdma.yaml | 43 +++++++++++++------
.../devicetree/bindings/dma/ti/k3-pktdma.yaml | 26 +++++++++--
.../devicetree/bindings/dma/ti/k3-udma.yaml | 20 +++++++--
3 files changed, 71 insertions(+), 18 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-22 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 15:42 Vignesh Raghavendra [this message]
2023-11-22 15:42 ` [PATCH v2 1/4] dt-bindings: dma: ti: k3-*: Add descriptions for register regions Vignesh Raghavendra
2023-11-22 16:19 ` Krzysztof Kozlowski
2023-11-22 17:04 ` Vignesh Raghavendra
2023-11-22 15:42 ` [PATCH v2 2/4] dt-bindings: dma: ti: k3-bcdma: Describe cfg " Vignesh Raghavendra
2023-11-22 15:42 ` [PATCH v2 3/4] dt-bindings: dma: ti: k3-pktdma: " Vignesh Raghavendra
2023-11-22 15:42 ` [PATCH v2 4/4] dt-bindings: dma: ti: k3-udma: " Vignesh Raghavendra
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=20231122154238.815781-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh+dt@kernel.org \
--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).