From: Paolo Abeni <pabeni@redhat.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: micrel: Add callback for restoring context
Date: Thu, 10 Jul 2025 15:38:11 +0200 [thread overview]
Message-ID: <60e77fb5-ef9f-4c89-899d-398cd9eb8f85@redhat.com> (raw)
In-Reply-To: <20250707142957.118966-1-biju.das.jz@bp.renesas.com>
On 7/7/25 4:29 PM, Biju Das wrote:
> @@ -374,6 +376,7 @@ static struct kszphy_hw_stat kszphy_hw_stats[] = {
> };
>
> struct kszphy_type {
> + void (*resume)(struct phy_device *phydev);
> u32 led_mode_reg;
> u16 interrupt_level_mask;
> u16 cable_diag_reg;
Why adding another callback? I think you could avoid it using a
ksz9131-specific phy_driver->resume.
> @@ -444,6 +447,7 @@ struct kszphy_priv {
> bool rmii_ref_clk_sel;
> bool rmii_ref_clk_sel_val;
> bool clk_enable;
> + bool is_suspended;
> u64 stats[ARRAY_SIZE(kszphy_hw_stats)];
> struct kszphy_phy_stats phy_stats;
> };
> @@ -491,6 +495,7 @@ static const struct kszphy_type ksz9021_type = {
> };
>
> static const struct kszphy_type ksz9131_type = {
> + .resume = ksz9131_restore_rgmii_delay,
> .interrupt_level_mask = BIT(14),
> .disable_dll_tx_bit = BIT(12),
> .disable_dll_rx_bit = BIT(12),
> @@ -1387,6 +1392,12 @@ static int ksz9131_config_rgmii_delay(struct phy_device *phydev)
> txcdll_val);
> }
>
> +static void ksz9131_restore_rgmii_delay(struct phy_device *phydev)
> +{
> + if (phy_interface_is_rgmii(phydev))
> + ksz9131_config_rgmii_delay(phydev);
> +}
> +
> /* Silicon Errata DS80000693B
> *
> * When LEDs are configured in Individual Mode, LED1 is ON in a no-link
> @@ -2345,6 +2356,11 @@ static int kszphy_generic_suspend(struct phy_device *phydev)
>
> static int kszphy_suspend(struct phy_device *phydev)
> {
> + struct kszphy_priv *priv = phydev->priv;
> +
> + if (priv)
> + priv->is_suspended = true;
Under which circumstances `priv` could be NULL? AFAICS it should always
not NULL after probe.
> +
> /* Disable PHY Interrupts */
> if (phy_interrupt_is_valid(phydev)) {
> phydev->interrupts = PHY_INTERRUPT_DISABLED;
> @@ -2381,8 +2397,17 @@ static void kszphy_parse_led_mode(struct phy_device *phydev)
>
> static int kszphy_resume(struct phy_device *phydev)
> {
> + struct kszphy_priv *priv = phydev->priv;
> int ret;
>
> + if (priv && priv->is_suspended) {
I think you can use phydev->suspended instead of adding another flag.
Also, can resume be invoked without the phydev being suspended?
/P
next prev parent reply other threads:[~2025-07-10 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 14:29 Biju Das
2025-07-10 13:38 ` Paolo Abeni [this message]
2025-07-10 17:43 ` Biju Das
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=60e77fb5-ef9f-4c89-899d-398cd9eb8f85@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew@lunn.ch \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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®