From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
netdev@vger.kernel.org, davem@davemloft.net,
vladimir.oltean@nxp.com, claudiu.manoil@nxp.com,
alexandru.marginean@nxp.com, michael@walle.cc,
f.fainelli@gmail.com
Subject: Re: [PATCH net-next 4/5] net: phy: add Lynx PCS MDIO module
Date: Thu, 18 Jun 2020 23:27:27 +0100 [thread overview]
Message-ID: <20200618222727.GM1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200618221352.GB279339@lunn.ch>
On Fri, Jun 19, 2020 at 12:13:52AM +0200, Andrew Lunn wrote:
> > MAINTAINERS | 7 +
> > drivers/net/phy/Kconfig | 6 +
> > drivers/net/phy/Makefile | 1 +
> > drivers/net/phy/mdio-lynx-pcs.c | 358 ++++++++++++++++++++++++++++++++
> > include/linux/mdio-lynx-pcs.h | 43 ++++
> > 5 files changed, 415 insertions(+)
> > create mode 100644 drivers/net/phy/mdio-lynx-pcs.c
> > create mode 100644 include/linux/mdio-lynx-pcs.h
>
> Hi Ioana
>
> We should think about naming convention here.
>
> All MDIO bus driver, MDIO multiplexors etc use mdio- as a prefix.
>
> This is not a bus driver, so i don't think it should use the mdio-
> prefix. How about pcs-lynx.c?
>
> In terms of Kconfig, MDIO_ prefix is used for MDIO bus drivers etc. I
> don't think it is appropriate here. How about PCS_LYNX? I don't think
> any other subsystem is using PCS_ as a prefix.
>
> > --- a/drivers/net/phy/Kconfig
> > +++ b/drivers/net/phy/Kconfig
> > @@ -235,6 +235,12 @@ config MDIO_XPCS
> > This module provides helper functions for Synopsys DesignWare XPCS
> > controllers.
> >
> > +config MDIO_LYNX_PCS
> > + bool
> > + help
> > + This module provides helper functions for Lynx PCS enablement
> > + representing the PCS as an MDIO device.
> > +
> > endif
> > endif
>
> Maybe add this at the end, and add a
>
> comment "PCS device drivers"
>
> before it? I'm assuming with time we will have more of these drivers.
It think we will.
The other thing is, drivers/net/phy is becoming a little cluttered -
we have approaching 100 files there.
Should we be thinking about drivers/net/phy/mdio/ (for mdio*),
drivers/net/phy/lib/ for the core phylib code or leaving it where
it is, and, hmm, drivers/net/phy/media/ maybe for the PHY and PCS
drivers? Or something like that?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-06-18 22:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 12:08 [PATCH net-next 0/5] net: phy: add Lynx PCS MDIO module Ioana Ciornei
2020-06-18 12:08 ` [PATCH net-next 1/5] net: phylink: add interface to configure clause 22 PCS PHY Ioana Ciornei
2020-06-18 12:08 ` [PATCH net-next 2/5] net: phylink: consider QSGMII interface mode in phylink_mii_c22_pcs_get_state Ioana Ciornei
2020-06-18 12:08 ` [PATCH net-next 3/5] net: mdiobus: add clause 45 mdiobus write accessor Ioana Ciornei
2020-06-18 12:08 ` [PATCH net-next 4/5] net: phy: add Lynx PCS MDIO module Ioana Ciornei
2020-06-18 14:06 ` Russell King - ARM Linux admin
2020-06-18 16:17 ` Ioana Ciornei
2020-06-18 16:55 ` Russell King - ARM Linux admin
2020-06-18 17:34 ` Ioana Ciornei
2020-06-18 22:01 ` Russell King - ARM Linux admin
2020-06-18 22:03 ` Andrew Lunn
2020-06-18 22:21 ` Russell King - ARM Linux admin
2020-06-18 22:56 ` Ioana Ciornei
2020-06-18 15:47 ` Jakub Kicinski
2020-06-18 22:13 ` Andrew Lunn
2020-06-18 22:25 ` Vladimir Oltean
2020-06-18 22:27 ` Russell King - ARM Linux admin [this message]
2020-06-18 22:37 ` Andrew Lunn
2020-06-18 22:49 ` Russell King - ARM Linux admin
2020-06-18 12:08 ` [PATCH net-next 5/5] net: dsa: felix: use the Lynx PCS helpers Ioana Ciornei
2020-06-18 15:48 ` Jakub Kicinski
2020-06-19 7:43 ` Ioana Ciornei
2020-06-20 15:46 ` kernel test robot
2020-06-20 15:46 ` kernel test robot
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=20200618222727.GM1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandru.marginean@nxp.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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.