From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Robert Richter <rric@kernel.org>, SoC Team <soc@kernel.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: cavium: Fix GICv3 ITS nodes
Date: Fri, 17 Mar 2023 13:40:48 +0100 [thread overview]
Message-ID: <cce4f28e-075d-137d-3f64-6bfd4074be72@linaro.org> (raw)
In-Reply-To: <CAL_JsqLz9mtsOr1sTB+eAxGOsZFthrLV-LbFBW7o7RdwgLCBZQ@mail.gmail.com>
On 16/03/2023 20:51, Rob Herring wrote:
> On Wed, Feb 8, 2023 at 12:55 PM Rob Herring <robh@kernel.org> wrote:
>>
>> The GICv3 ITS is an MSI controller, therefore its node name should be
>> 'msi-controller'. The ITS node is also expected to have '#msi-cells'.
>> Add it on Thunder as there are no users. Thunder2 uses 'msi-parent', but
>> Robin says that should be 'msi-map' instead and I'm not sure what's
>> correct for it.
>>
>> The unit-addresses of both the ITS and main GIC node on thunder2 are also
>> wrong, so fix them while we're here.
>>
>> Cc: Robin Murphy <robin.murphy@arm.com>
>> Signed-off-by: Rob Herring <robh@kernel.org>
>> ---
>> arch/arm64/boot/dts/cavium/thunder-88xx.dtsi | 3 ++-
>> arch/arm64/boot/dts/cavium/thunder2-99xx.dtsi | 4 ++--
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> Ping!
>
> Should we remove these platforms instead if they aren't maintained?
5 weeks should be enough... Applied with my other cleanups.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-03-17 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 18:55 [PATCH] arm64: dts: cavium: Fix GICv3 ITS nodes Rob Herring
2023-03-17 12:40 ` Krzysztof Kozlowski
[not found] ` <CAL_JsqLz9mtsOr1sTB+eAxGOsZFthrLV-LbFBW7o7RdwgLCBZQ@mail.gmail.com>
2023-03-17 12:40 ` Krzysztof Kozlowski [this message]
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=cce4f28e-075d-137d-3f64-6bfd4074be72@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rric@kernel.org \
--cc=soc@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).