From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jakub Kicinski <kuba@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] net: phy: Support master-slave config via device tree
Date: Mon, 16 Sep 2024 07:30:12 +0200 [thread overview]
Message-ID: <ZufCZAfXB_KFIKmI@pengutronix.de> (raw)
In-Reply-To: <5befa01e-f52d-44de-b356-bc7e1946777a@lunn.ch>
On Sun, Sep 15, 2024 at 08:41:42PM +0200, Andrew Lunn wrote:
> On Sun, Sep 15, 2024 at 06:06:30PM +0200, Jakub Kicinski wrote:
> > On Fri, 13 Sep 2024 10:40:20 +0200 Oleksij Rempel wrote:
> > > This patch series adds support for configuring the master/slave role of
> > > PHYs via the device tree. A new `master-slave` property is introduced in
> > > the device tree bindings, allowing PHYs to be forced into either master
> > > or slave mode. This is particularly necessary for Single Pair Ethernet
> > > (SPE) PHYs (1000/100/10Base-T1), where hardware strap pins may not be
> > > available or correctly configured, but it is applicable to all PHY
> > > types.
> >
> > I was hoping we'd see some acks here in time, but now Linus cut the 6.11
> > final so the 6.12 game is over now:
>
> The device tree binding is not decided on yet. So deferred is correct.
No problem. See you on LPC, my flight starting right now.
Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-09-16 5:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 8:40 [PATCH net-next v3 0/2] net: phy: Support master-slave config via device tree Oleksij Rempel
2024-09-13 8:40 ` [PATCH net-next v3 1/2] dt-bindings: net: ethernet-phy: Add timing-role role property for ethernet PHYs Oleksij Rempel
2024-09-16 17:57 ` Rob Herring (Arm)
2024-09-17 9:11 ` Russell King (Oracle)
2024-09-17 9:28 ` Oleksij Rempel
2024-09-13 8:40 ` [PATCH net-next v3 2/2] net: phy: Add support for PHY timing-role configuration via device tree Oleksij Rempel
2024-09-17 9:17 ` Russell King (Oracle)
2024-09-15 16:06 ` [PATCH net-next v3 0/2] net: phy: Support master-slave config " Jakub Kicinski
2024-09-15 18:41 ` Andrew Lunn
2024-09-16 5:30 ` Oleksij Rempel [this message]
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=ZufCZAfXB_KFIKmI@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).