From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: sheetal <sheetal@nvidia.com>, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Move HDA into the correct bus
Date: Tue, 4 Nov 2025 13:34:38 +0000 [thread overview]
Message-ID: <bb48fea6-de95-46d4-890c-acaabb1d588c@nvidia.com> (raw)
In-Reply-To: <20251104132345.1689397-1-thierry.reding@gmail.com>
On 04/11/2025 13:23, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> HDA is part of the DISP_USB bus, so move it into that and drop the
> address prefix accordingly.
>
Is there a fixes-tag we need for this?
Otherwise ...
Acked-by: Jon Hunter <jonathanh@nvidia.com>
Jon
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../arm64/boot/dts/nvidia/tegra264-p3971.dtsi | 4 ++-
> arch/arm64/boot/dts/nvidia/tegra264.dtsi | 32 +++++++++----------
> 2 files changed, 19 insertions(+), 17 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra264-p3971.dtsi b/arch/arm64/boot/dts/nvidia/tegra264-p3971.dtsi
> index 1fcfac2066ae..b1bd4ee7aee3 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra264-p3971.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra264-p3971.dtsi
> @@ -29,8 +29,10 @@ interrupt-controller@9960000 {
> status = "okay";
> };
> };
> + };
>
> - hda@88090b0000 {
> + bus@8800000000 {
> + hda@90b0000 {
> nvidia,model = "NVIDIA Jetson Thor AGX HDA";
> status = "okay";
> };
> diff --git a/arch/arm64/boot/dts/nvidia/tegra264.dtsi b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> index c66ea12ef5a3..f137565da804 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> @@ -3347,22 +3347,6 @@ pmc: pmc@c800000 {
> #interrupt-cells = <2>;
> interrupt-controller;
> };
> -
> - hda@88090b0000 {
> - compatible = "nvidia,tegra264-hda";
> - reg = <0x88 0x90b0000 0x0 0x10000>;
> - interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&bpmp TEGRA264_CLK_AZA_2XBIT>;
> - clock-names = "hda";
> - resets = <&bpmp TEGRA264_RESET_HDA>,
> - <&bpmp TEGRA264_RESET_HDACODEC>;
> - reset-names = "hda", "hda2codec_2x";
> - interconnects = <&mc TEGRA264_MEMORY_CLIENT_HDAR &emc>,
> - <&mc TEGRA264_MEMORY_CLIENT_HDAW &emc>;
> - interconnect-names = "dma-mem", "write";
> - iommus = <&smmu3 TEGRA264_SID_HDA>;
> - status = "disabled";
> - };
> };
>
> /* TOP_MMIO */
> @@ -3716,6 +3700,22 @@ smmu3: iommu@6000000 {
> #iommu-cells = <1>;
> dma-coherent;
> };
> +
> + hda@90b0000 {
> + compatible = "nvidia,tegra264-hda";
> + reg = <0x0 0x90b0000 0x0 0x10000>;
> + interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&bpmp TEGRA264_CLK_AZA_2XBIT>;
> + clock-names = "hda";
> + resets = <&bpmp TEGRA264_RESET_HDA>,
> + <&bpmp TEGRA264_RESET_HDACODEC>;
> + reset-names = "hda", "hda2codec_2x";
> + interconnects = <&mc TEGRA264_MEMORY_CLIENT_HDAR &emc>,
> + <&mc TEGRA264_MEMORY_CLIENT_HDAW &emc>;
> + interconnect-names = "dma-mem", "write";
> + iommus = <&smmu3 TEGRA264_SID_HDA>;
> + status = "disabled";
> + };
> };
>
> /* UPHY MMIO */
--
nvpublic
next prev parent reply other threads:[~2025-11-04 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 13:23 [PATCH] arm64: tegra: Move HDA into the correct bus Thierry Reding
2025-11-04 13:34 ` Jon Hunter [this message]
2025-11-04 13:44 ` 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=bb48fea6-de95-46d4-890c-acaabb1d588c@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=sheetal@nvidia.com \
--cc=thierry.reding@gmail.com \
/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