From: Vignesh Raghavendra <vigneshr@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] arm64: dts: ti: k3: Add additioal regs for DMA components
Date: Tue, 12 Dec 2023 16:46:31 +0530 [thread overview]
Message-ID: <20231212111634.3515175-1-vigneshr@ti.com> (raw)
This adds additional reg ranges which are not directly used by Linux but
by other components like U-Boot
Binding is accepted via dmaengine tree and is in linux-next[0]
[0] https://lore.kernel.org/dmaengine/170083278148.771517.1841889156174413563.b4-ty@kernel.org/
Manorit Chawdhry (2):
arm64: dts: ti: k3-am65: Add additional regs for DMA components
arm64: dts: ti: k3-j7*: Add additional regs for DMA components
Vignesh Raghavendra (1):
arm64: dts: ti: k3-am6*: Add additional regs for DMA components
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 18 ++++++++++++++----
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 18 ++++++++++++++----
arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 18 ++++++++++++++----
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 18 ++++++++++++++----
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 8 ++++++--
arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 8 ++++++--
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 8 ++++++--
.../arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 8 ++++++--
arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 8 ++++++--
.../arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 8 ++++++--
arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 8 ++++++--
.../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 8 ++++++--
arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 8 ++++++--
.../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 8 ++++++--
14 files changed, 116 insertions(+), 36 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-12 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 11:16 Vignesh Raghavendra [this message]
2023-12-12 11:16 ` [PATCH 1/3] arm64: dts: ti: k3-am65: Add additional " Vignesh Raghavendra
2023-12-13 9:46 ` Jai Luthra
2023-12-12 11:16 ` [PATCH 2/3] arm64: dts: ti: k3-j7*: " Vignesh Raghavendra
2023-12-13 9:55 ` Jai Luthra
2023-12-12 11:16 ` [PATCH 3/3] arm64: dts: ti: k3-am6*: " Vignesh Raghavendra
2023-12-13 9:39 ` Jai Luthra
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=20231212111634.3515175-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®