From: Florian Fainelli <f.fainelli@gmail.com>
To: Detlev Casanova <detlev.casanova@collabora.com>,
linux-kernel@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] net: phy: realtek: Disable clock on suspend
Date: Fri, 2 Jun 2023 12:11:17 -0700 [thread overview]
Message-ID: <3597b0be-2dc9-5dbd-a773-6dd5704ef4a9@gmail.com> (raw)
In-Reply-To: <20230602182659.307876-4-detlev.casanova@collabora.com>
On 6/2/23 11:26, Detlev Casanova wrote:
> For PHYs that call rtl821x_probe() where an external clock can be
> configured, make sure that the clock is disabled
> when ->suspend() is called and enabled on resume.
>
> The PHY_ALWAYS_CALL_SUSPEND is added to ensure that the suspend function
> is actually always called.
>
> Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
prev parent reply other threads:[~2023-06-02 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 18:26 net: phy: realtek: Support external PHY clock Detlev Casanova
2023-06-02 18:26 ` [PATCH v2 1/3] net: phy: realtek: Add optional " Detlev Casanova
2023-06-02 18:43 ` Andrew Lunn
2023-06-02 19:10 ` Florian Fainelli
2023-06-02 18:26 ` [PATCH v2 2/3] dt-bindings: net: phy: Document support for external PHY clk Detlev Casanova
2023-06-02 18:42 ` Andrew Lunn
2023-06-02 19:26 ` Detlev Casanova
2023-06-02 19:43 ` Andrew Lunn
2023-06-03 10:27 ` Krzysztof Kozlowski
2023-06-02 18:26 ` [PATCH v2 3/3] net: phy: realtek: Disable clock on suspend Detlev Casanova
2023-06-02 19:11 ` Florian Fainelli [this message]
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=3597b0be-2dc9-5dbd-a773-6dd5704ef4a9@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=robh+dt@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.