[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16f6912c-84a9-f1ab-6688-6a55ebf34270@gmail.com>
Date: Mon, 17 Feb 2020 13:54:19 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Russell King <rmk+kernel@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>,
Jonathan Corbet <corbet@....net>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Ioana Radulescu <ruxandra.radulescu@....com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Felix Fietkau <nbd@...nwrt.org>,
John Crispin <john@...ozen.org>,
Sean Wang <sean.wang@...iatek.com>,
Mark Lee <Mark-MC.Lee@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre Torgue <alexandre.torgue@...com>,
Jose Abreu <joabreu@...opsys.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Radhey Shyam Pandey <radhey.shyam.pandey@...inx.com>,
Michal Simek <michal.simek@...inx.com>,
Vivien Didelot <vivien.didelot@...il.com>,
linux-doc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
linux-stm32@...md-mailman.stormreply.com
Subject: Re: [CFT 1/8] net: phylink: propagate resolved link config via
mac_link_up()
On 2/17/2020 9:23 AM, Russell King wrote:
> Propagate the resolved link parameters via the mac_link_up() call for
> MACs that do not automatically track their PCS state.
>
> Signed-off-by: Russell King <rmk+kernel@...linux.org.uk>
> ---
[snip]
> -static void macb_mac_link_up(struct phylink_config *config, unsigned int mode,
> - phy_interface_t interface, struct phy_device *phy)
> +static void macb_mac_link_up(struct phylink_config *config,
> + struct phy_device *phy,
> + unsigned int mode, phy_interface_t interface,
> + int speed, int duplex,
> + bool tx_pause, bool rx_pause)
I have not been able to find an answer so I will ask this question, why
not pass a const struct phylink_link_state reference here instead of
splitting those link settings as individual function parameters? Or
maybe introduce a phylink_link_settings comprised of all of those 4
settings and embed it within phylink_link_state as well?
You would obviously need to squash patch #1 and #2 past this submission
stage to avoid bisection build failures.
--
Florian
Powered by blists - more mailing lists