[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190207145517.08bb8975@bootlin.com>
Date: Thu, 7 Feb 2019 14:55:17 +0100
From: Maxime Chevallier <maxime.chevallier@...tlin.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org,
Antoine Tenart <antoine.tenart@...tlin.com>,
thomas.petazzoni@...tlin.com, gregory.clement@...tlin.com,
miquel.raynal@...tlin.com, nadavh@...vell.com, stefanc@...vell.com,
mw@...ihalf.com
Subject: Re: [PATCH net-next v2 01/10] net: phy: Update PHY linkmodes after
config_init
Hello Andrew,
On Thu, 7 Feb 2019 14:48:07 +0100
Andrew Lunn <andrew@...n.ch> wrote:
>On Thu, Feb 07, 2019 at 10:49:30AM +0100, Maxime Chevallier wrote:
>> We want to be able to update a PHY's supported list in the config_init
>> callback, so move the Pause parameters settings from phydrv->features
>> after calling config_init to make sure these parameters aren't
>> overwritten.
>
>Hi Maxime
>
>I have a patch which makes some core changes to support PHY doing
>runtime feature detection. I would prefer to use them, than this.
>
>Either I or Heiner will post them soon.
Sure, no problem, thanks for doing this. I'll be happy to review and
test that on my side.
As I said, I lack the big picture view on that part so my approach was
pretty naive, I'm glad you can take care of this :)
Thanks,
Maxime
Powered by blists - more mailing lists