From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
philippe.schenker@toradex.com, andrew@lunn.ch,
qiangqing.zhang@nxp.com, davem@davemloft.net, festevam@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: perform a PHY reset on resume
Date: Tue, 14 Dec 2021 12:58:57 +0100 [thread overview]
Message-ID: <20211214115857.GA13490@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <YbSymkxlslW2DqLW@shell.armlinux.org.uk>
On Sat, Dec 11, 2021 at 02:15:54PM +0000, Russell King (Oracle) wrote:
> I don't particularly like this - this impacts everyone who is using
> phylib at this point, whereas no reset was happening if the reset was
> already deasserted here.
Let's drop this patch, Philippe will send a new patch adding a
phy_reset_after_power_on() function similar to
phy_reset_after_clk_enable().
Francesco
next prev parent reply other threads:[~2021-12-14 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 10:13 [RFC PATCH 0/2] Reset PHY in fec_resume if it got powered down Philippe Schenker
2021-12-06 10:13 ` [RFC PATCH 1/2] net: fec: make fec_reset_phy not only usable once Philippe Schenker
2021-12-06 13:13 ` Andrew Lunn
2021-12-06 10:13 ` [RFC PATCH 2/2] net: fec: reset phy in resume if it was powered down Philippe Schenker
2021-12-07 1:58 ` [RFC PATCH 0/2] Reset PHY in fec_resume if it got " Joakim Zhang
2021-12-10 13:51 ` Philippe Schenker
2021-12-11 13:01 ` [PATCH net-next] net: phy: perform a PHY reset on resume Francesco Dolcini
2021-12-11 14:15 ` Russell King (Oracle)
2021-12-11 14:57 ` Francesco Dolcini
2021-12-14 11:58 ` Francesco Dolcini [this message]
2021-12-13 4:40 ` Joakim Zhang
2021-12-13 10:57 ` Philippe Schenker
2021-12-13 4:39 ` [RFC PATCH 0/2] Reset PHY in fec_resume if it got powered down Joakim Zhang
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=20211214115857.GA13490@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=festevam@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=philippe.schenker@toradex.com \
--cc=qiangqing.zhang@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
all inboxes | Powered by JetHome®