[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+V-a8t2w14bJVCiiHQq8bwgetw5za1-t_OSfyr6Cwo4eZOt2Q@mail.gmail.com>
Date: Sat, 11 Jun 2022 09:01:09 +0100
From: "Lad, Prabhakar" <prabhakar.csengg@...il.com>
To: Yongqin Liu <yongqin.liu@...aro.org>
Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Rob Herring <robh+dt@...nel.org>,
Marc Zyngier <maz@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Biju Das <biju.das.jz@...renesas.com>
Subject: Re: [RFC PATCH] of/platform: Drop static setup of IRQ resource from
DT core
Hi Yongqin,
On Sat, Jun 11, 2022 at 6:28 AM Yongqin Liu <yongqin.liu@...aro.org> wrote:
>
> Hi, Lad
>
> # sorry for the confusion if you have received it before with the
> non-plain-text mode
>
> In this change you said "all the DT drivers have switched to
> platform_get_irq()",
> could you please help share with me one example about the above change
> as reference?
The change is we just switch to using platform_get_irq() [0] for
fetching IRQ numbers.
> We have one hikey960 android build with some out of tree changes,
> which could not boot
> successfully with some errors on surfaceflinger(I am not sure it's a
> problem with the gpu or display),
> but could boot if I have this change reverted.
>
> I guess it needs some changes on the gpu/display dts or driver side to
> have it work
Just the changes to the driver is needed.
> with this change, not sure if you could give some suggestions on the fix.
>
> And here are two out of tree changes might be related listed here just
> for reference in case:
> https://android-review.linaro.org/c/kernel/common/+/21680
> https://android-review.linaro.org/c/kernel/common/+/21682
>
[0] https://lore.kernel.org/lkml/20211221213547.1553-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
Cheers,
Prabhakar
Powered by blists - more mailing lists