From: Andrew Lunn <andrew@lunn.ch>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: "Clément Léger" <clement.leger@bootlin.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Magnus Damm" <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Biju Das" <biju.das.jz@bp.renesas.com>,
"Fabrizio Castro" <fabrizio.castro.jz@renesas.com>,
"Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH net-next 2/2] net: pcs: rzn1-miic: Add support for PHY link active-level configuration
Date: Wed, 12 Nov 2025 22:00:50 +0100 [thread overview]
Message-ID: <686d84c6-c2ea-4055-897a-6377eec1fca0@lunn.ch> (raw)
In-Reply-To: <20251112201937.1336854-3-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Wed, Nov 12, 2025 at 08:19:37PM +0000, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Add support to configure the PHY link signal active level per converter
> using the DT property "renesas,miic-phylink-active-low".
>
> Introduce the MIIC_PHYLINK register definition and extend the MIIC driver
> with a new `phylink`
You probably want to avoid the name phylink. It is well know that is
all about PHYs , SPFs, PCS, etc.
Andrew
next prev parent reply other threads:[~2025-11-12 21:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 20:19 [PATCH net-next 0/2] Add support for PHY link active-level configuration in RZN1 MIIC driver Prabhakar
2025-11-12 20:19 ` [PATCH net-next 1/2] dt-bindings: net: pcs: renesas,rzn1-miic: Add renesas,miic-phylink-active-low property Prabhakar
2025-11-12 20:40 ` Wolfram Sang
2025-11-13 14:45 ` Lad, Prabhakar
2025-11-13 15:58 ` Russell King (Oracle)
2025-11-13 19:05 ` Lad, Prabhakar
2025-11-13 19:10 ` Lad, Prabhakar
2025-11-12 20:57 ` Andrew Lunn
2025-11-13 18:53 ` Lad, Prabhakar
2025-11-13 21:58 ` Andrew Lunn
2025-11-26 20:55 ` Lad, Prabhakar
2025-11-26 21:28 ` Andrew Lunn
2026-01-09 9:18 ` Lad, Prabhakar
2025-11-12 20:19 ` [PATCH net-next 2/2] net: pcs: rzn1-miic: Add support for PHY link active-level configuration Prabhakar
2025-11-12 21:00 ` Andrew Lunn [this message]
2025-11-12 22:11 ` Russell King (Oracle)
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=686d84c6-c2ea-4055-897a-6377eec1fca0@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=biju.das.jz@bp.renesas.com \
--cc=clement.leger@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@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
all inboxes | Powered by JetHome®