All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Radhey Shyam Pandey <radheys@xilinx.com>,
	Andy Chiu <andy.chiu@sifive.com>,
	"robert.hancock@calian.com" <robert.hancock@calian.com>,
	Michal Simek <michals@xilinx.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Greentime Hu <greentime.hu@sifive.com>,
	Harini Katakam <harinik@xilinx.com>
Subject: Re: [PATCH v4 3/4] dt-bindings: net: xilinx_axienet: add pcs-handle attribute
Date: Tue, 22 Mar 2022 11:51:39 -0500	[thread overview]
Message-ID: <Yjn+m6OwkxPAc8/A@robh.at.kernel.org> (raw)
In-Reply-To: <YjkWca40JbosV7Hq@lunn.ch>

On Tue, Mar 22, 2022 at 01:21:05AM +0100, Andrew Lunn wrote:
> > > The use case is generic i.e. require separate handle to internal SGMII
> > > and external Phy so would prefer this new DT convention is 
> > > standardized or we discuss possible approaches on how to handle
> > > both phys and not add it as vendor specific property in the first 
> > > place.
> > 
> > IMO, you should use 'phys' for the internal PCS phy. That's aligned with 
> > other uses like PCIe, SATA, etc. (there is phy h/w that will do PCS, 
> > PCIe, SATA). 'phy-handle' is for the ethernet PHY.
> 
> We need to be careful here, because the PCS can have a well defined
> set of registers accessible over MDIO. Generic PHY has no
> infrastructure for that, it is all inside phylink which implements the
> pcs registers which are part of 802.3.

Using the phy binding doesn't mean you have to use the kernel's 'generic 
PHY' subsytem.

But if there's a need to do something different then propose something 
that handles the complex cases.

> 
> I also wonder if a PCS might actually have a generic PHY embedded in
> it to provide its lower interface?

That's just looking at a single PCS/PHY block the other way around. 
PCS is part of the PHY or the PHY is part of PCS? I don't think that 
matters too much. I think the 2 cases would be it's all 1 block or 2 
blocks.

Rob

  reply	other threads:[~2022-03-22 16:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 15:25 [PATCH v4 1/4] net: axienet: setup mdio unconditionally Andy Chiu
2022-03-21 15:25 ` [PATCH v4 2/4] net: axienet: factor out phy_node in struct axienet_local Andy Chiu
2022-03-21 18:09   ` Robert Hancock
2022-03-21 15:25 ` [PATCH v4 3/4] dt-bindings: net: xilinx_axienet: add pcs-handle attribute Andy Chiu
2022-03-21 15:42   ` Radhey Shyam Pandey
2022-03-21 18:11     ` Robert Hancock
2022-03-21 23:44     ` Rob Herring
2022-03-21 23:56       ` Robert Hancock
2022-03-22  0:21       ` Andrew Lunn
2022-03-22 16:51         ` Rob Herring [this message]
2022-03-21 15:25 ` [PATCH v4 4/4] net: axiemac: use a phandle to reference pcs_phy Andy Chiu
2022-03-21 18:12   ` Robert Hancock
2022-03-21 18:08 ` [PATCH v4 1/4] net: axienet: setup mdio unconditionally Robert Hancock
2022-03-21 18:20 ` Andrew Lunn
2022-03-22  4:34   ` Andy Chiu

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=Yjn+m6OwkxPAc8/A@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=andy.chiu@sifive.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=greentime.hu@sifive.com \
    --cc=harinik@xilinx.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michals@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radheys@xilinx.com \
    --cc=robert.hancock@calian.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 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.