From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, Tim Harvey <tharvey@gateworks.com>
Cc: Martin Schiller <ms@dev.tdt.de>,
Hauke Mehrtens <hauke@hauke-m.de>,
martin.blumenstingl@googlemail.com, hkallweit1@gmail.com,
Russell King - ARM Linux <linux@armlinux.org.uk>,
David Miller <davem@davemloft.net>,
kuba@kernel.org, netdev <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v3] net: phy: intel-xway: enable integrated led functions
Date: Wed, 2 Feb 2022 19:12:34 -0800 [thread overview]
Message-ID: <c732e1ce-8c9c-b947-8d4b-78903920a5b2@gmail.com> (raw)
In-Reply-To: <YfspazpWoKuHEwPU@lunn.ch>
On 2/2/2022 5:01 PM, Andrew Lunn wrote:
>> As a person responsible for boot firmware through kernel for a set of
>> boards I continue to do the following to keep Linux from mucking with
>> various PHY configurations:
>> - remove PHY reset pins from Linux DT's to keep Linux from hard resetting PHY's
>> - disabling PHY drivers
>>
>> What are your thoughts about this?
>
> Hi Tim
>
> I don't like the idea that the bootloader is controlling the hardware,
> not linux.
This is really trying to take advantage of the boot loader setting
things up in a way that Linux can play dumb by using the Generic PHY
driver and being done with it. This works... until it stops, which
happens very very quickly in general. The perfect counter argument to
using the Generic PHY driver is when your system implements a low power
mode where the PHY loses its power/settings, comes up from suspend and
the strap configuration is insufficient and the boot loader is not part
of the resume path *prior* to Linux. In that case Linux needs to restore
the settings, but it needs a PHY driver for that.
If your concern Tim is with minimizing the amount of time the link gets
dropped and re-established, then there is not really much that can be
done that is compatible with Linux setting things up, short of
minimizing the amount of register writes that do need the "commit phase"
via BMCR.RESET.
I do agree that blindly imposing LED settings that are different than
those you want is not great, and should be remedied. Maybe you can
comment this part out in your downstream tree for a while until the LED
binding shows up (we have never been so close I am told).
--
Florian
next prev parent reply other threads:[~2022-02-03 3:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 5:50 Martin Schiller
2021-04-21 18:10 ` patchwork-bot+netdevbpf
2021-04-21 21:25 ` Martin Blumenstingl
2022-02-01 20:54 ` Tim Harvey
2022-02-03 1:01 ` Andrew Lunn
2022-02-03 3:12 ` Florian Fainelli [this message]
2022-02-03 16:02 ` Tim Harvey
2022-02-04 17:06 ` Florian Fainelli
2022-02-03 15:57 ` Tim Harvey
2022-02-03 16:37 ` Andrew Lunn
2022-02-03 17:52 ` Tim Harvey
2022-02-04 0:04 ` Andrew Lunn
2022-02-04 22:35 ` Tim Harvey
2022-02-04 22:54 ` Andrew Lunn
2022-02-09 16:31 ` Tim Harvey
2022-02-10 0:04 ` Andrew Lunn
2022-02-10 15:52 ` Tim Harvey
2022-02-11 19:17 ` Andrew Lunn
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=c732e1ce-8c9c-b947-8d4b-78903920a5b2@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hauke@hauke-m.de \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin.blumenstingl@googlemail.com \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=tharvey@gateworks.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
all inboxes | Powered by JetHome®