From: Herve Codina <herve.codina@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [RFC PATCH] ARM: dts: renesas: r9a06g032-rzn1d400-db: use interrupt for Micrel PHYs
Date: Mon, 20 Oct 2025 10:35:29 +0200 [thread overview]
Message-ID: <20251020103529.0f948c67@bootlin.com> (raw)
In-Reply-To: <20251001104312.40771-2-wsa+renesas@sang-engineering.com>
Hi Wolfram,
On Wed, 1 Oct 2025 12:38:06 +0200
Wolfram Sang <wsa+renesas@sang-engineering.com> wrote:
> Make use of the interrupts wired to the Micrel PHYs via the GPIO IRQ
> mux.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> Works nicely and kinda out-of-the-box for the Micrel PHYs, couldn't get
> it to work (reliably?) with the Marvell PHYs on the EB. Leaving this for
> later (if ever), no more bandwidth currently. But at least we have an
> upstream user for the gpioirqmux now.
>
> RFC because Hervé's patches are still in-flight.
Yes and v5 has been sent:
https://lore.kernel.org/lkml/20251020080648.13452-1-herve.codina@bootlin.com/
This v5 iteration should impact modification done in this RFC.
>
> .../dts/renesas/r9a06g032-rzn1d400-db.dts | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
Reviewed-by: Herve Codina <herve.codina@bootlin.com>
Best regards,
Hervé
next prev parent reply other threads:[~2025-10-20 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 10:38 [RFC PATCH] ARM: dts: renesas: r9a06g032-rzn1d400-db: use interrupt for Micrel PHYs Wolfram Sang
2025-10-20 8:35 ` Herve Codina [this message]
2025-10-28 9:08 ` Wolfram Sang
2025-10-28 11:41 ` Herve Codina
2025-10-28 11:43 ` Wolfram Sang
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=20251020103529.0f948c67@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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 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).