From: Andrew Lunn <andrew@lunn.ch>
To: Asmaa Mnebhi <asmaa@nvidia.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Thompson <davthompson@nvidia.com>
Subject: Re: [PATCH net v1] mlxbf-gige: Support workaround for MDIO GPIO degradation bug
Date: Wed, 2 Jul 2025 23:26:42 +0200 [thread overview]
Message-ID: <c6f5da79-df83-4fad-9bfc-6fd45940d10f@lunn.ch> (raw)
In-Reply-To: <CH3PR12MB7738E1776CD326A2566254D5D740A@CH3PR12MB7738.namprd12.prod.outlook.com>
> > You need to put the MDIO bus device into its own pm_domain. Try
> > calling dev_pm_domain_set() to separate the MDIO bus from the MAC
> > driver in terms of power domains. ethtool will then power on/off the
> > MAC but leave the MDIO bus alone.
> >
> Using dev_pm_domain_set() has the same effect as SET_RUNTIME_PM_OPS. The dev struct is shared so ethtool is still calling the suspend/resume.
>
> int mlxbf_gige_mdio_probe(struct platform_device *pdev, struct mlxbf_gige *priv)
> {
> struct device *dev = &pdev->dev;
> @@ -390,14 +418,27 @@ int mlxbf_gige_mdio_probe(struct platform_device *pdev, struct mlxbf_gige *priv)
> snprintf(priv->mdiobus->id, MII_BUS_ID_SIZE, "%s",
> dev_name(dev));
>
> + pm_runtime_set_autosuspend_delay(priv->mdiobus->parent, 100);
> + pm_runtime_use_autosuspend(priv->mdiobus->parent);
Why parent?
Andrew
next prev parent reply other threads:[~2025-07-02 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 22:48 Asmaa Mnebhi
2024-11-26 17:32 ` Andrew Lunn
2025-05-08 14:18 ` Asmaa Mnebhi
2025-05-08 14:44 ` Andrew Lunn
2025-05-08 14:53 ` Asmaa Mnebhi
2025-06-27 19:00 ` Asmaa Mnebhi
2025-06-28 8:40 ` Andrew Lunn
2025-07-02 20:56 ` Asmaa Mnebhi
2025-07-02 21:26 ` Andrew Lunn [this message]
2025-07-03 18:51 ` Asmaa Mnebhi
2025-07-03 20:49 ` 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=c6f5da79-df83-4fad-9bfc-6fd45940d10f@lunn.ch \
--to=andrew@lunn.ch \
--cc=asmaa@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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®