All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Behun <marek.behun@nic.cz>
To: u-boot@lists.denx.de
Subject: [EXT] Re: [PATCH v1 2/5] net: phy: marvell: extend 88E2110 to use both 2.5GHz modes
Date: Thu, 8 Apr 2021 21:35:36 +0200	[thread overview]
Message-ID: <20210408213536.56a4ae41@thinkpad> (raw)
In-Reply-To: <CO6PR18MB3873CC0C6CED884EE8C21969B0749@CO6PR18MB3873.namprd18.prod.outlook.com>

On Thu, 8 Apr 2021 19:18:09 +0000
Stefan Chulski <stefanc@marvell.com> wrote:

> > 
> > Stefan, you suggest to drop this define from PHY_INTERFACE enum which we
> > can't easily do with other drivers (like NXP) also referencing this macro.
> > 
> > How to continue then?
> > 
> > Thanks,
> > Stefan  
> 
> Probably we should drop SGMII_2500 from this series, introduce "manage" devicetree property(that would indicate if inband supported or not).
> For example this is armada-8040-mcbin.dtsi In kernel, when in-band supported:
> &cp1_eth2 {
> 	/* CPS Lane 5 */
> 	status = "okay";
> 	/* Network PHY */
> 	phy-mode = "2500base-x";
> 	managed = "in-band-status";
> 	/* Generic PHY, providing serdes lanes */
> 	phys = <&cp1_comphy5 2>;
> 	sfp = <&sfp_eth3>;
> }; 
> 
> If in-band not supported(for example PPv2 MAC connected to 88E2110 in 2.5G speed) we would use default managed = "auto" and fixed link property.

Such DTS properties should first be proposed to device-tree ML
and documented in devicetree bindings documentation.

Marek

  reply	other threads:[~2021-04-08 19:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  9:20 [PATCH v1 0/5] net: phy: marvell: Sync Marvell ethernet PHY code with Marvell version Stefan Roese
2021-03-24  9:20 ` [PATCH v1 1/5] net: phy: marvell: add support for 88E2110 phy Stefan Roese
2021-03-24  9:20 ` [PATCH v1 2/5] net: phy: marvell: extend 88E2110 to use both 2.5GHz modes Stefan Roese
2021-03-24 10:44   ` Marek Behun
2021-03-24  9:55     ` [EXT] " Kostya Porotchkin
2021-03-24  9:59       ` Stefan Chulski
2021-03-24 11:47       ` Marek Behun
2021-03-24 11:12         ` Kostya Porotchkin
2021-03-24 12:06           ` Stefan Chulski
2021-03-24 13:09             ` Stefan Chulski
2021-03-24 14:52               ` Marek Behun
2021-03-24 16:36                 ` Stefan Chulski
2021-03-24 22:45                   ` Marek Behun
2021-03-25 12:59                     ` Stefan Chulski
2021-04-08  8:24                       ` Stefan Roese
2021-04-08 18:35                         ` Marek Behun
2021-04-08 19:18                         ` Stefan Chulski
2021-04-08 19:35                           ` Marek Behun [this message]
2021-04-08 19:43                             ` Stefan Chulski
2021-03-24  9:20 ` [PATCH v1 3/5] net: phy: marvell: remove hardcoded PHY 2210 lane swap Stefan Roese
2021-03-24  9:20 ` [PATCH v1 4/5] net: phy: marvell: Fix PHY 221 2.5G speed detection Stefan Roese
2021-03-24  9:20 ` [PATCH v1 5/5] net: phy: marvell: Fix 2210 link and speed detection resolution Stefan Roese

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=20210408213536.56a4ae41@thinkpad \
    --to=marek.behun@nic.cz \
    --cc=u-boot@lists.denx.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.