All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prasanna Vengateshan <prasanna.vengateshan@microchip.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <netdev@vger.kernel.org>, <olteanv@gmail.com>,
	<robh+dt@kernel.org>, <UNGLinuxDriver@microchip.com>,
	<woojung.huh@microchip.com>, <hkallweit1@gmail.com>,
	<linux@armlinux.org.uk>, <davem@davemloft.net>, <kuba@kernel.org>,
	<linux-kernel@vger.kernel.org>, <vivien.didelot@gmail.com>,
	<f.fainelli@gmail.com>, <devicetree@vger.kernel.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v9 net-next 03/11] dt-bindings: net: dsa: dt bindings for microchip lan937x
Date: Tue, 22 Mar 2022 01:49:29 +0530	[thread overview]
Message-ID: <b7d6a721c1a5dd7de39483a9f70c40912bb5265b.camel@microchip.com> (raw)
In-Reply-To: <YjZ6GIrGCMzBaftB@lunn.ch>

On Sun, 2022-03-20 at 01:49 +0100, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
> 
> > +examples:
> 
> > +          port@6 {
> > +            reg = <6>;
> > +            label = "lan5";
> > +            phy-mode = "internal";
> > +            phy-handle = <&t1phy4>;
> > +          };
> > +          port@7 {
> > +            reg = <7>;
> > +            label = "lan3";
> > +            phy-mode = "internal";
> > +            phy-handle = <&t1phy5>;
> > +          };
> > +        };
> > +
> > +        mdio {
> 
> ..
> 
> > +          t1phy4: ethernet-phy@6{
> > +            reg = <0x6>;
> > +          };
> > +          t1phy5: ethernet-phy@7{
> > +            reg = <0x7>;
> > +          };
> 
> I know it is only an example, but the numbering is a little odd here.
> 
> Port 6, which is named lan5 using t1phy4 at address 6?
> 
> I would be more likely to use t1phy6 instead of t1phy4. And t1phy7
> instead of t1phy5.

> 
>         Andrew

Sure, will change it in the next rev as above, Labels are just named to
understand front panel naming.

Prasanna V


  reply	other threads:[~2022-03-21 20:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  8:55 [PATCH v9 net-next 00/11] net: dsa: microchip: DSA driver support for LAN937x switch Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 01/11] dt-bindings: net: make internal-delay-ps based on phy-mode Prasanna Vengateshan
2022-03-20  0:41   ` Andrew Lunn
2022-03-20  2:13   ` Rob Herring
2022-03-18  8:55 ` [PATCH v9 net-next 02/11] dt-bindings: net: add mdio property Prasanna Vengateshan
2022-03-20  0:41   ` Andrew Lunn
2022-03-21 23:27   ` Rob Herring
2022-03-22 14:46     ` Prasanna Vengateshan
2022-03-22 14:56       ` Rob Herring
2022-03-18  8:55 ` [PATCH v9 net-next 03/11] dt-bindings: net: dsa: dt bindings for microchip lan937x Prasanna Vengateshan
2022-03-20  0:49   ` Andrew Lunn
2022-03-21 20:19     ` Prasanna Vengateshan [this message]
2022-03-18  8:55 ` [PATCH v9 net-next 04/11] net: dsa: move mib->cnt_ptr reset code to ksz_common.c Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 05/11] net: dsa: tag_ksz: add tag handling for Microchip LAN937x Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 06/11] net: dsa: microchip: add DSA support for microchip lan937x Prasanna Vengateshan
2022-03-20  1:17   ` Andrew Lunn
2022-03-21 20:09     ` Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 07/11] net: dsa: microchip: add support for phylink management Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 08/11] net: dsa: microchip: add support for ethtool port counters Prasanna Vengateshan
2022-03-20  1:26   ` Andrew Lunn
2022-03-21 19:33     ` Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 09/11] net: dsa: microchip: add support for port mirror operations Prasanna Vengateshan
2022-03-18 11:00   ` Vladimir Oltean
2022-03-21 20:22     ` Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 10/11] net: dsa: microchip: add support for fdb and mdb management Prasanna Vengateshan
2022-03-18  8:55 ` [PATCH v9 net-next 11/11] net: dsa: microchip: add support for vlan operations Prasanna Vengateshan

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=b7d6a721c1a5dd7de39483a9f70c40912bb5265b.camel@microchip.com \
    --to=prasanna.vengateshan@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=vivien.didelot@gmail.com \
    --cc=woojung.huh@microchip.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.