[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+V-a8tDwa3ZYAwZi=-cDH1f5cuJJ0EHP3Z9W1o0adKHsxLEnw@mail.gmail.com>
Date: Tue, 29 Oct 2024 14:45:41 +0000
From: "Lad, Prabhakar" <prabhakar.csengg@...il.com>
To: Claudiu Beznea <claudiu.beznea@...on.dev>
Cc: Geert Uytterhoeven <geert+renesas@...der.be>, Magnus Damm <magnus.damm@...il.com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>, linux-renesas-soc@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, Biju Das <biju.das.jz@...renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH v2 0/6] pinctrl: rzg2l: Fix releasing of IRQ and status
reported in pinmux-pins
Hi Claudiu,
On Tue, Oct 29, 2024 at 12:37 PM Claudiu Beznea
<claudiu.beznea@...on.dev> wrote:
>
> Hi, Prabhakar,
>
> On 25.10.2024 14:49, Prabhakar wrote:
> > From: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
> >
> > Hi All,
> >
> > This patch series aims to fix the reporting of pin status in the
> > `pinmux-pins` file and properly free up the IRQ line when using a GPIO
> > pin as an interrupt via the `interrupts`/`interrupts-extended` property.
>
> With this series, the Ethernet PHYs IRQs switch to poll mode after a
> suspend to RAM cycle. I've added the logs here:
> https://p.fr33tux.org/3e8193
>
Thank you for testing it on RZ/G3S, I'll investigate it further.
Cheers,
Prabhakar
Powered by blists - more mailing lists