public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Wei Fang <wei.fang@nxp.com>,
	andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, florian.fainelli@broadcom.com,
	heiko.stuebner@cherry.de, frank.li@nxp.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	imx@lists.linux.dev
Subject: Re: [PATCH v5 net] net: phy: micrel: Dynamically control external clock of KSZ PHY
Date: Thu, 19 Dec 2024 09:02:29 -0800	[thread overview]
Message-ID: <629802cd-ddb1-4e3d-9050-612739d8f3fc@gmail.com> (raw)
In-Reply-To: <20241217063500.1424011-1-wei.fang@nxp.com>

On 12/16/24 22:35, Wei Fang wrote:
> On the i.MX6ULL-14x14-EVK board, enet1_ref and enet2_ref are used as the
> clock sources for two external KSZ PHYs. However, after closing the two
> FEC ports, the clk_enable_count of the enet1_ref and enet2_ref clocks is
> not 0. The root cause is that since the commit 985329462723 ("net: phy:
> micrel: use devm_clk_get_optional_enabled for the rmii-ref clock"), the
> external clock of KSZ PHY has been enabled when the PHY driver probes,
> and it can only be disabled when the PHY driver is removed. This causes
> the clock to continue working when the system is suspended or the network
> port is down.
> 
> Although Heiko explained in the commit message that the patch was because
> some clock suppliers need to enable the clock to get the valid clock rate
> , it seems that the simple fix is to disable the clock after getting the
> clock rate to solve the current problem. This is indeed true, but we need
> to admit that Heiko's patch has been applied for more than a year, and we
> cannot guarantee whether there are platforms that only enable rmii-ref in
> the KSZ PHY driver during this period. If this is the case, disabling
> rmii-ref will cause RMII on these platforms to not work.
> 
> Secondly, commit 99ac4cbcc2a5 ("net: phy: micrel: allow usage of generic
> ethernet-phy clock") just simply enables the generic clock permanently,
> which seems like the generic clock may only be enabled in the PHY driver.
> If we simply disable the generic clock, RMII may not work. If we keep it
> as it is, the platform using the generic clock will have the same problem
> as the i.MX6ULL platform.
> 
> To solve this problem, the clock is enabled when phy_driver::resume() is
> called, and the clock is disabled when phy_driver::suspend() is called.
> Since phy_driver::resume() and phy_driver::suspend() are not called in
> pairs, an additional clk_enable flag is added. When phy_driver::suspend()
> is called, the clock is disabled only if clk_enable is true. Conversely,
> when phy_driver::resume() is called, the clock is enabled if clk_enable
> is false.
> 
> The changes that introduced the problem were only a few lines, while the
> current fix is about a hundred lines, which seems out of proportion, but
> it is necessary because kszphy_probe() is used by multiple KSZ PHYs and
> we need to fix all of them.
> 
> Fixes: 985329462723 ("net: phy: micrel: use devm_clk_get_optional_enabled for the rmii-ref clock")
> Fixes: 99ac4cbcc2a5 ("net: phy: micrel: allow usage of generic ethernet-phy clock")
> Signed-off-by: Wei Fang <wei.fang@nxp.com>

Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
-- 
Florian

  parent reply	other threads:[~2024-12-19 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  6:35 [PATCH v5 net] net: phy: micrel: Dynamically control external clock of KSZ PHY Wei Fang
2024-12-19 16:21 ` Andrew Lunn
2024-12-19 17:02 ` Florian Fainelli [this message]
2024-12-20  2:10 ` patchwork-bot+netdevbpf

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=629802cd-ddb1-4e3d-9050-612739d8f3fc@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=frank.li@nxp.com \
    --cc=heiko.stuebner@cherry.de \
    --cc=hkallweit1@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wei.fang@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