All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: Joe Hershberger <joe.hershberger@ni.com>,
	Ramon Fried <rfried.dev@gmail.com>, Nishanth Menon <nm@ti.com>,
	Robert Nelson <robertcnelson@gmail.com>,
	Wadim Egorov <w.egorov@phytec.de>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Simon Glass <sjg@chromium.org>,
	srk@ti.com, s-vadapalli@ti.com, vigneshr@ti.com,
	r-gunasekaran@ti.com, danishanwar@ti.com, u-boot@lists.denx.de
Subject: Re: [PATCH 0/5] net: mdio-uclass: probe generic Ethernet PHY driver & Fix Beagleplay Ethernet
Date: Mon, 25 Mar 2024 22:00:38 -0400	[thread overview]
Message-ID: <20240326020038.GF3442575@bill-the-cat> (raw)
In-Reply-To: <a91f3573-0e2c-49ff-bbe0-933eff7eedc7@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

On Mon, Mar 25, 2024 at 02:16:53PM +0200, Roger Quadros wrote:
> Hi Tom / Joe,
> 
> On 05/03/2024 15:24, Roger Quadros wrote:
> > Currently, the GPIO Reset Device Tree properties of the
> > PHY node are ignored when the PHY is probed via mdio-uclass driver [1].
> > 
> > To resolve this, for each child of the MDIO bus node, bind and probe
> > the generic Ethernet PHY driver if CONFIG_DM_ETH_PHY is enabled.
> > 
> > This should now show the generic_phy_driver in "dm tree"
> > and also apply the GPIO reset before the MDIO bus driver scans the bus
> > for the PHYs.
> > 
> >  ethernet      0  [ + ]   am65_cpsw_nuss_port       |   |-- ethernet@8000000port@1
> >  bootdev       3  [   ]   eth_bootdev               |   |   `-- port@1.bootdev
> >  mdio          0  [ + ]   cpsw_mdio                 |   `-- mdio@f00
> >  eth_phy_ge    0  [ + ]   eth_phy_generic_drv       |       |-- ethernet-phy@0
> >  eth_phy_ge    1  [ + ]   eth_phy_generic_drv       |       `-- ethernet-phy@1
> > 
> > To test this on Beagleplay, the following series is required
> > 
> > [1] Switch am65-cpsw to DM MDIO
> >  https://lore.kernel.org/all/20240228-for-2024-07-am65-cpsw-mdio-v2-0-f74f972eafeb@kernel.org/
> > 
> > The last 3 patches are marked [not-for-merge]. They are to show how the
> > whole solution can work to fix Ethernet on Beagleplay, which has been broken
> > so far. Those DT patches will be sent once the device tree changes are merged
> > into Linux tree.
> > 
> > Signed-off-by: Roger Quadros <rogerq@kernel.org>
> > ---
> > Roger Quadros (5):
> >       net: mdio-uclass: Bind and probe generic Ethernet PHY driver
> >       configs/am62x_beagleplay_a53_defconfig: enable DM_ETH_PHY
> 
> Any comments to the first 2 patches in this series?

Oh, so the CI failure, unfortunately, was because sometimes those tests
hit some resource-related race condition I believe. And I took your
comment at the time to mean you would v2 them. Yes, these patches seem
fine as is and I'll pick up assorted changes for -next soon. Thanks for
your patience.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2024-03-26  2:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 13:24 [PATCH 0/5] net: mdio-uclass: probe generic Ethernet PHY driver & Fix Beagleplay Ethernet Roger Quadros
2024-03-05 13:24 ` [PATCH 1/5] net: mdio-uclass: Bind and probe generic Ethernet PHY driver Roger Quadros
2024-03-28 15:09   ` Tom Rini
2024-03-05 13:24 ` [PATCH 2/5] configs/am62x_beagleplay_a53_defconfig: enable DM_ETH_PHY Roger Quadros
2024-03-28 15:09   ` Tom Rini
2024-03-05 13:24 ` [PATCH not-for-merge 3/5] arm: dts: k3-am62*: sync with linux-next-20240229 Roger Quadros
2024-03-05 13:24 ` [PATCH not-for-merge 4/5] k3-am625-beagleplay-u-boot: get CPSW Ethernet to work Roger Quadros
2024-03-05 13:24 ` [PATCH not-for-merge 5/5] arm: dts: k3-am625-beagleplay: Fix Ethernet PHY reset GPIO Roger Quadros
2024-03-08  8:22 ` [PATCH 0/5] net: mdio-uclass: probe generic Ethernet PHY driver & Fix Beagleplay Ethernet Roger Quadros
2024-03-08  8:26   ` Roger Quadros
2024-03-25 12:16 ` Roger Quadros
2024-03-26  2:00   ` Tom Rini [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=20240326020038.GF3442575@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=danishanwar@ti.com \
    --cc=joe.hershberger@ni.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=nm@ti.com \
    --cc=r-gunasekaran@ti.com \
    --cc=rfried.dev@gmail.com \
    --cc=robertcnelson@gmail.com \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=sjg@chromium.org \
    --cc=srk@ti.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    --cc=w.egorov@phytec.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.