From: Vinod Koul <vkoul@kernel.org>
To: "Kishon Vijay Abraham I" <kishon@kernel.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Peter Griffin" <peter.griffin@linaro.org>
Cc: linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, kernel-team@android.com,
William Mcvicker <willmcvicker@google.com>,
Manivannan Sadhasivam <mani@kernel.org>,
neil.armstrong@linaro.org
Subject: Re: [PATCH v5 0/2] Add new phy_notify_state() api
Date: Tue, 18 Nov 2025 22:48:21 +0530 [thread overview]
Message-ID: <176348630114.62598.12188488023476027485.b4-ty@kernel.org> (raw)
In-Reply-To: <20251112-phy-notify-pmstate-v5-0-39df622d8fcb@linaro.org>
On Wed, 12 Nov 2025 16:27:05 +0000, Peter Griffin wrote:
> This series adds a new phy_notify_state() API to the phy subsystem. It is
> designed to be used when some specific runtime configuration parameters
> need to be changed when transitioning to the desired state which can't be
> handled by phy_calibrate()or phy_power_{on|off}().
>
> The first user of the new API is phy-samsung-ufs and phy-gs101-ufs which
> need to issue some register writes when entering and exiting the hibern8
> link state.
>
> [...]
Applied, thanks!
[1/2] phy: add new phy_notify_state() api
commit: 4edf654be5471659e3260be0a557eaa2ece668ab
[2/2] phy: samsung: gs101-ufs: Add .notify_phystate() & hibern8 enter/exit values
commit: a1af5d2be169ecec92cb4d85c811450d68164aec
Best regards,
--
~Vinod
prev parent reply other threads:[~2025-11-18 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 16:27 Peter Griffin
2025-11-12 16:27 ` [PATCH v5 1/2] phy: add " Peter Griffin
2025-11-18 9:13 ` neil.armstrong
2025-11-12 16:27 ` [PATCH v5 2/2] phy: samsung: gs101-ufs: Add .notify_phystate() & hibern8 enter/exit values Peter Griffin
2025-11-18 9:14 ` neil.armstrong
2025-11-18 17:18 ` Vinod Koul [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=176348630114.62598.12188488023476027485.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=kernel-team@android.com \
--cc=kishon@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=peter.griffin@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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®