From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
"Andrew Lunn" <andrew@lunn.ch>,
"Jakub Kicinski" <kuba@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Herve Codina" <herve.codina@bootlin.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
"Marek Behún" <kabel@kernel.org>,
"Piergiorgio Beruto" <piergiorgio.beruto@gmail.com>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Nicolò Veronese" <nicveronese@gmail.com>,
"Simon Horman" <horms@kernel.org>,
mwojtas@chromium.org, "Nathan Chancellor" <nathan@kernel.org>,
"Antoine Tenart" <atenart@kernel.org>
Subject: Re: [PATCH net-next] net: phy: Don't conditionally compile the phy_link_topology creation
Date: Tue, 30 Apr 2024 15:36:55 +0200 [thread overview]
Message-ID: <20240430153655.2df7a54c@device-28.home> (raw)
In-Reply-To: <20240430135734.503f51a2@device-28.home>
On Tue, 30 Apr 2024 13:57:34 +0200
Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:
> Hello Heiner,
>
> On Tue, 30 Apr 2024 10:17:31 +0200
> Heiner Kallweit <hkallweit1@gmail.com> wrote:
>
> > On 29.04.2024 15:10, Maxime Chevallier wrote:
> > > The core of the phy_link_topology isn't directly tied to phylib, and at
> > > the moment it's initialized, phylib might not be loaded yet. Move the
> > > initialization of the topology to the phy_link_topology_core header,
> > > which contains the bare minimum so that we can initialize it at netdev
> > > creation.
> > >
> >
> > The change fixes the issue for me, but according to my personal taste
> > the code isn't intuitive and still error-prone. Also there's no good
> > reason to inline a function like phy_link_topo_create() and make it
> > publicly available. Do you expect it to be ever used outside net core?
> > In general it may make sense to add a config symbol for the topology
> > extension, there seem to be very few, specialized use cases for it.
>
> I think I'm missing the point here then. Do you mean adding a Kconfig
> option to explicitely turn phy_link_topology on ? or build it as a
> dedicated kernel module ?
>
> Or do you see something such as "if phylib is M or Y, then build the
> topology stuff and make sure it's allocated when a netdev gets created
> ?"
I've prototyped something that's cleaner and should fit what you
described, which is to have a Kconfig option for phy_topology and
have it autoselected by CONFIG_SFP (for now, the only case where we can
have multiple PHYs on the link). When phy mux support is added (I'll
followup with that once the topology is settled), we can also make is
select the phy_topology config option. I'll send that patch when I'll
have properly tested it, especially with all the different bits
(phylib, sfp, drivers) being tested as modules or builtin.
Thanks for the tips,
Maxime
>
> Thanks,
>
> Maxime
>
> >
> > > Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> > > Closes: https://lore.kernel.org/netdev/2e11b89d-100f-49e7-9c9a-834cc0b82f97@gmail.com/
> > > Closes: https://lore.kernel.org/netdev/20240409201553.GA4124869@dev-arch.thelio-3990X/
> > > ---
> > > drivers/net/phy/phy_link_topology.c | 23 --------------------
> > > include/linux/phy_link_topology.h | 5 -----
> > > include/linux/phy_link_topology_core.h | 30 +++++++++++++++++---------
> > > 3 files changed, 20 insertions(+), 38 deletions(-)
> > >
> > > diff --git a/drivers/net/phy/phy_link_topology.c b/drivers/net/phy/phy_link_topology.c
> > > index 985941c5c558..960aedd73308 100644
> > > --- a/drivers/net/phy/phy_link_topology.c
> > > +++ b/drivers/net/phy/phy_link_topology.c
> > > @@ -12,29 +12,6 @@
> > > #include <linux/rtnetlink.h>
> > > #include <linux/xarray.h>
> > >
> > > -struct phy_link_topology *phy_link_topo_create(struct net_device *dev)
> > > -{
> > > - struct phy_link_topology *topo;
> > > -
> > > - topo = kzalloc(sizeof(*topo), GFP_KERNEL);
> > > - if (!topo)
> > > - return ERR_PTR(-ENOMEM);
> > > -
> > > - xa_init_flags(&topo->phys, XA_FLAGS_ALLOC1);
> > > - topo->next_phy_index = 1;
> > > -
> > > - return topo;
> > > -}
> > > -
> > > -void phy_link_topo_destroy(struct phy_link_topology *topo)
> > > -{
> > > - if (!topo)
> > > - return;
> > > -
> > > - xa_destroy(&topo->phys);
> > > - kfree(topo);
> > > -}
> > > -
> > > int phy_link_topo_add_phy(struct phy_link_topology *topo,
> > > struct phy_device *phy,
> > > enum phy_upstream upt, void *upstream)
> > > diff --git a/include/linux/phy_link_topology.h b/include/linux/phy_link_topology.h
> > > index 6b79feb607e7..ad72d7881257 100644
> > > --- a/include/linux/phy_link_topology.h
> > > +++ b/include/linux/phy_link_topology.h
> > > @@ -32,11 +32,6 @@ struct phy_device_node {
> > > struct phy_device *phy;
> > > };
> > >
> > > -struct phy_link_topology {
> > > - struct xarray phys;
> > > - u32 next_phy_index;
> > > -};
> > > -
> > > static inline struct phy_device *
> > > phy_link_topo_get_phy(struct phy_link_topology *topo, u32 phyindex)
> > > {
> > > diff --git a/include/linux/phy_link_topology_core.h b/include/linux/phy_link_topology_core.h
> > > index 0a6479055745..0116ec49cd1b 100644
> > > --- a/include/linux/phy_link_topology_core.h
> > > +++ b/include/linux/phy_link_topology_core.h
> > > @@ -2,24 +2,34 @@
> > > #ifndef __PHY_LINK_TOPOLOGY_CORE_H
> > > #define __PHY_LINK_TOPOLOGY_CORE_H
> > >
> > > -struct phy_link_topology;
> > > +#include <linux/xarray.h>
> > >
> > > -#if IS_REACHABLE(CONFIG_PHYLIB)
> > > -
> > > -struct phy_link_topology *phy_link_topo_create(struct net_device *dev);
> > > -void phy_link_topo_destroy(struct phy_link_topology *topo);
> > > -
> > > -#else
> > > +struct phy_link_topology {
> > > + struct xarray phys;
> > > + u32 next_phy_index;
> > > +};
> > >
> > > static inline struct phy_link_topology *phy_link_topo_create(struct net_device *dev)
> > > {
> > > - return NULL;
> > > + struct phy_link_topology *topo;
> > > +
> > > + topo = kzalloc(sizeof(*topo), GFP_KERNEL);
> > > + if (!topo)
> > > + return ERR_PTR(-ENOMEM);
> > > +
> > > + xa_init_flags(&topo->phys, XA_FLAGS_ALLOC1);
> > > + topo->next_phy_index = 1;
> > > +
> > > + return topo;
> > > }
> > >
> > > static inline void phy_link_topo_destroy(struct phy_link_topology *topo)
> > > {
> > > -}
> > > + if (!topo)
> > > + return;
> > >
> > > -#endif
> > > + xa_destroy(&topo->phys);
> > > + kfree(topo);
> > > +}
> > >
> > > #endif /* __PHY_LINK_TOPOLOGY_CORE_H */
> >
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-30 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 13:10 [PATCH net-next] net: phy: Don't conditionally compile the phy_link_topology creation Maxime Chevallier
2024-04-30 8:17 ` Heiner Kallweit
2024-04-30 11:57 ` Maxime Chevallier
2024-04-30 13:36 ` Maxime Chevallier [this message]
2024-04-30 21:29 ` Heiner Kallweit
2024-05-02 7:05 ` Maxime Chevallier
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=20240430153655.2df7a54c@device-28.home \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mwojtas@chromium.org \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piergiorgio.beruto@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox