From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chen-Yu Tsai <wenst@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Sasha Levin <sashal@kernel.org>, Rob Herring <robh@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Saravana Kannan <saravanak@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [GIT PULL] Devicetree updates for v6.13
Date: Mon, 25 Nov 2024 12:33:48 +0100 [thread overview]
Message-ID: <e77669ea-9edd-4321-8d17-4da40161b59d@linaro.org> (raw)
In-Reply-To: <19ba4910-f909-41b4-ba62-c904bc37d41d@linaro.org>
On 25/11/2024 12:00, Krzysztof Kozlowski wrote:
> On 25/11/2024 11:34, Chen-Yu Tsai wrote:
>> On Mon, Nov 25, 2024 at 5:48 PM AngeloGioacchino Del Regno
>> <angelogioacchino.delregno@collabora.com> wrote:
>>>
>>> Il 24/11/24 17:59, Sasha Levin ha scritto:
>>>> On Sun, Nov 24, 2024 at 05:47:33PM +0100, Krzysztof Kozlowski wrote:
>>>>> On 24/11/2024 17:29, Sasha Levin wrote:
>>>>>> Hi Rob,
>>>>>>
>>>>>> On Mon, Nov 18, 2024 at 03:07:30PM -0600, Rob Herring wrote:
>>>>>>> of: WARN on deprecated #address-cells/#size-cells handling
>>>>>>
>>>>>> With the commit above, I've started seeing boot warnings on a few
>>>>>
>>>>> And same boards do not report problems on the next?
>>>>
>>>> Looks like they do. I haven't checked it previously, but I see that we
>>>> have similar warnings on a few boards that KernelCI is testing -next on.
>>>>
>>>
>>> That's... horrendous.
>>>
>>> I hope that we can get a proper fix with a bootloader update on these (now very
>>> old) devices... Adding a Google engineer to the loop so that he can follow up
>>> internally.
>>
>> AFAIK that's unlikely going to happen given the resources needed from
>> the ODMs for a firmware re-qualification. Or we would have fixed the GIC
>> bug in ATF and had pseudo-NMI.
>>
>> Some of the firmware code involved is 10 years old, so even the RK3399
>> Chromebooks, which no longer have support, could suffer from this as
>> well.
>>
>>> The alternative would be to hack-in a firmware node to mt8183-kukui.dtsi, but....
>>> ...ugh. That'd be indeed a hack for the sole purpose of fixing a bootloader that
>>> is acting in a broken way, and I don't like that at all (...and I'm sure I'm not
>>> alone!).
>>
>
> Then we should add it to the exception list. Let me take a look at this.
https://lore.kernel.org/linux-devicetree/20241125113151.107812-1-krzysztof.kozlowski@linaro.org/T/#u
I sent a fix for this platform only. You did not paste links to other
failing platforms (and sorry but kernelci web interface was absolutely
unmanageable and unusable, so I am not going to even try to look for
them) so not sure who should be added to list of exceptions.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-25 11:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 21:07 Rob Herring
2024-11-20 22:56 ` pr-tracker-bot
2024-11-24 16:29 ` Sasha Levin
2024-11-24 16:47 ` Krzysztof Kozlowski
2024-11-24 16:59 ` Sasha Levin
2024-11-25 9:48 ` AngeloGioacchino Del Regno
2024-11-25 10:34 ` Chen-Yu Tsai
2024-11-25 11:00 ` Krzysztof Kozlowski
2024-11-25 11:33 ` Krzysztof Kozlowski [this message]
2024-11-25 12:11 ` AngeloGioacchino Del Regno
2024-11-25 13:24 ` Sasha Levin
2024-11-25 15:15 ` Rob Herring
2024-12-09 9:28 ` Chen-Yu Tsai
2026-04-17 21:25 ` [regression] of: mis-parsing Depthcharge's /firmware Brian Norris
2026-04-20 12:57 ` Rob Herring
2026-04-20 20:57 ` Brian Norris
2026-04-20 22:19 ` Rob Herring
2026-04-20 22:54 ` Brian Norris
2026-04-21 19:30 ` Rob Herring
2026-04-28 20:21 ` Brian Norris
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=e77669ea-9edd-4321-8d17-4da40161b59d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=sashal@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wenst@chromium.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®