From: Jon Hunter <jonathanh@nvidia.com>
To: Charan Pedumuru <charan.pedumuru@gmail.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 1/2] arm: dts: nvidia: tegra20,30: Rename the apbdma nodename to match with common dma-controller binding
Date: Thu, 8 May 2025 11:45:10 +0100 [thread overview]
Message-ID: <7a8cc7d9-30b9-404e-8456-8ad362440561@nvidia.com> (raw)
In-Reply-To: <20250507-nvidea-dma-v4-1-6161a8de376f@gmail.com>
On 07/05/2025 05:57, Charan Pedumuru wrote:
> Rename the apbdma nodename from "dma@" to "dma-controller@" to align with
> linux common dma-controller binding.
>
> Signed-off-by: Charan Pedumuru <charan.pedumuru@gmail.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> arch/arm/boot/dts/nvidia/tegra20.dtsi | 2 +-
> arch/arm/boot/dts/nvidia/tegra30.dtsi | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/nvidia/tegra20.dtsi b/arch/arm/boot/dts/nvidia/tegra20.dtsi
> index 8da75ccc44025bf2978141082332b78bf94c38a9..882adb7f2f26392db2be386b0a936453fc839049 100644
> --- a/arch/arm/boot/dts/nvidia/tegra20.dtsi
> +++ b/arch/arm/boot/dts/nvidia/tegra20.dtsi
> @@ -284,7 +284,7 @@ flow-controller@60007000 {
> reg = <0x60007000 0x1000>;
> };
>
> - apbdma: dma@6000a000 {
> + apbdma: dma-controller@6000a000 {
> compatible = "nvidia,tegra20-apbdma";
> reg = <0x6000a000 0x1200>;
> interrupts = <GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH>,
> diff --git a/arch/arm/boot/dts/nvidia/tegra30.dtsi b/arch/arm/boot/dts/nvidia/tegra30.dtsi
> index f866fa7b55a509a0f66d3e49456565df0d74a678..2a4d93db81347e3e1dd942e6c10a1ff5683402e7 100644
> --- a/arch/arm/boot/dts/nvidia/tegra30.dtsi
> +++ b/arch/arm/boot/dts/nvidia/tegra30.dtsi
> @@ -431,7 +431,7 @@ flow-controller@60007000 {
> reg = <0x60007000 0x1000>;
> };
>
> - apbdma: dma@6000a000 {
> + apbdma: dma-controller@6000a000 {
> compatible = "nvidia,tegra30-apbdma", "nvidia,tegra20-apbdma";
> reg = <0x6000a000 0x1400>;
> interrupts = <GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH>,
>
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2025-05-08 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 4:57 [PATCH v4 0/2] dt-bindings: dma: nvidia,tegra20-apbdma: Add json schema for text binding Charan Pedumuru
2025-05-07 4:57 ` [PATCH v4 1/2] arm: dts: nvidia: tegra20,30: Rename the apbdma nodename to match with common dma-controller binding Charan Pedumuru
2025-05-08 10:45 ` Jon Hunter [this message]
2025-05-08 20:19 ` Thierry Reding
2025-05-07 4:57 ` [PATCH v4 2/2] dt-bindings: dma: nvidia,tegra20-apbdma: convert text based binding to json schema Charan Pedumuru
2025-05-07 5:32 ` Krzysztof Kozlowski
2025-05-08 10:50 ` Jon Hunter
2025-05-08 20:20 ` Thierry Reding
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=7a8cc7d9-30b9-404e-8456-8ad362440561@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=charan.pedumuru@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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