From: Jon Hunter <jonathanh@nvidia.com>
To: Brad Griffis <bgriffis@nvidia.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Fix Tegra234 PCIe interrupt-map
Date: Fri, 13 Dec 2024 09:51:30 +0000 [thread overview]
Message-ID: <e3a566cb-fe72-478b-b0a0-b866be7d4e93@nvidia.com> (raw)
In-Reply-To: <20241212211114.330245-1-bgriffis@nvidia.com>
On 12/12/2024 21:11, Brad Griffis wrote:
> For interrupt-map entries, the DTS specification requires
> that #address-cells is defined for both the child node and the
> interrupt parent. For the PCIe interrupt-map entries, the parent
> node ("gic") has not specified #address-cells. The existing layout
> of the PCIe interrupt-map entries indicates that it assumes
> that #address-cells is zero for this node.
>
> Explicitly set #address-cells to zero for "gic" so that it complies
> with the device tree specification.
>
> Signed-off-by: Brad Griffis <bgriffis@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> index 984c85eab41a..e1c07c99e9bd 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> @@ -4010,6 +4010,7 @@ ccplex@e000000 {
>
> gic: interrupt-controller@f400000 {
> compatible = "arm,gic-v3";
> + #address-cells = <0>;
> reg = <0x0 0x0f400000 0x0 0x010000>, /* GICD */
> <0x0 0x0f440000 0x0 0x200000>; /* GICR */
> interrupt-parent = <&gic>;
Can you add the fixes tag for this?
BTW, I had a quick look and this appears to be a common problem across
all Tegra devices, Tegra210, Tegra186 and Tegra194. Should we fix up all
while we are at it?
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2024-12-13 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 21:11 [PATCH] arm64: tegra: Fix Tegra234 PCIe interrupt-map Brad Griffis
2024-12-13 9:51 ` Jon Hunter [this message]
2024-12-13 10:21 ` Thierry Reding
2024-12-13 11:11 ` Krzysztof Kozlowski
2024-12-13 11:37 ` Jon Hunter
2024-12-13 13:26 ` Krzysztof Kozlowski
2024-12-14 0:35 ` Brad Griffis
2024-12-14 10:27 ` Krzysztof Kozlowski
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=e3a566cb-fe72-478b-b0a0-b866be7d4e93@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=bgriffis@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.