netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: Holger Brunck <holger.brunck@hitachienergy.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [v3 2/2] dsa: mv88e6xxx: make serdes SGMII/Fiber output amplitude configurable
Date: Wed, 15 Dec 2021 21:53:50 +0100	[thread overview]
Message-ID: <20211215215350.7a8b353a@thinkpad> (raw)
In-Reply-To: <AM0PR0602MB366630C33E7F36499BCD1C40F7769@AM0PR0602MB3666.eurprd06.prod.outlook.com>

On Wed, 15 Dec 2021 10:27:02 +0000
Holger Brunck <holger.brunck@hitachienergy.com> wrote:

> Hi Marek,
> 
> > > This gets interesting when PCIe and USB needs to use this property,
> > > what names are used, and if it is possible to combine two different
> > > lists?  
> >
> > I don't think it is possible, I tried that once and couldn't get it to work.
> >
> > I am going to try write the proposal. But unfortunately PHY binding is not
> > converted to YAML yet :(
> >  
> 
> I saw you recent patches to convert this. Thanks!
> 
> This make my serdes.yaml obsolete then, correct? Should I then only re-post
> my driver code, once your patches are accepted?

Yes, please let's do it this way. It may take some time for Rob to
review this, though, and he may require some changes.

Also I was thinking whether it wouldn't be better to put the property
into a separate SerDes PHY node, i.e.

  switch {
    compatible = "marvell,mv88e6085";
    ...

    ports {
      port@6 {
        reg = <0x6>;
        phy-handle = <&switch_serdes_phy>;
      };

      ...
    };

    mdio {
      switch_serdes_phy: ethernet-phy@f {
        reg = <0xf>;
        tx-amplitude-microvolt = <1234567>;
      };

      ...
    };
  };

  reply	other threads:[~2021-12-15 20:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:07 [v3 1/2] Docs/devicetree: add serdes.yaml Holger Brunck
2021-12-07 19:07 ` [v3 2/2] dsa: mv88e6xxx: make serdes SGMII/Fiber output amplitude configurable Holger Brunck
2021-12-07 19:27   ` Marek Behún
2021-12-08 12:29     ` Holger Brunck
2021-12-08 15:28       ` Marek Behún
2021-12-08 15:49         ` Holger Brunck
2021-12-08 16:17           ` Marek Behún
2021-12-08 16:21             ` Marek Behún
2021-12-08 16:41               ` Vladimir Oltean
2021-12-08 16:49                 ` Vladimir Oltean
2021-12-08 17:00                   ` Marek Behún
2021-12-08 17:19                     ` Vladimir Oltean
2021-12-08 17:36                       ` Marek Behún
2021-12-08 17:55                         ` Andrew Lunn
2021-12-08 18:15                           ` Marek Behún
2021-12-08 16:51                 ` Marek Behún
2021-12-08 16:59                   ` Vladimir Oltean
2021-12-08 17:10                     ` Marek Behún
2021-12-08 17:12                       ` Marek Behún
2021-12-08 17:20                       ` Vladimir Oltean
2021-12-08 17:00             ` Andrew Lunn
2021-12-08 17:16               ` Marek Behún
2021-12-15 10:27                 ` Holger Brunck
2021-12-15 20:53                   ` Marek Behún [this message]
2022-01-20  7:52                     ` Holger Brunck
2022-01-20 17:57                       ` Marek Behún

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=20211215215350.7a8b353a@thinkpad \
    --to=kabel@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=holger.brunck@hitachienergy.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.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).