From: sashiko-bot@kernel.org
To: "Louis-Alexis Eyraud" <louisalexis.eyraud@collabora.com>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-scsi@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v14 08/23] scsi: ufs: mediatek: Add dual 0.9V supply support
Date: Fri, 16 Oct 2026 12:43:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-174329@kernel.org> (raw)
In-Reply-To: <20261016-mt8196-ufs-v14-8-e8d565e0cd45@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] scsi: ufs: mediatek: bypass of allow_pwr_on leaves regulator enabled on error
--
commit 169f13062deb73e7db2227752ba9ee6ad0ec3257
Author: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
scsi: ufs: mediatek: Add dual 0.9V supply support
This commit adds support for an additional 0.9V supply pin on the MT8196
SoC compared to the MT8183 SoC. It introduces management for a second
optional 0.9V regulator named "avdd09-1".
> diff --git a/drivers/ufs/host/ufs-mediatek.c b/drivers/ufs/host/ufs-mediatek.c
> index bcb7f350984c0..c8c5f85507af6 100644
> --- a/drivers/ufs/host/ufs-mediatek.c
> +++ b/drivers/ufs/host/ufs-mediatek.c
[ ... ]
> @@ -513,20 +514,43 @@ static int ufs_mtk_wait_link_state(struct ufs_hba *hba, u32 state,
> static int ufs_mtk_09v_off(struct ufs_mtk_host *host, bool allow_pwr_on)
> {
> struct arm_smccc_res res;
> - int ret;
> + int ret, ret2;
>
> - if (!host->reg_avdd09)
> + if (!host->reg_avdd09 && !host->reg_avdd09_1)
> return 0;
>
> ufs_mtk_va09_pwr_ctrl(res, 0);
> - ret = regulator_disable(host->reg_avdd09);
> - if (ret) {
> - dev_err(host->hba->dev, "Failed to disable avdd09-supply: %pe\n",
> - ERR_PTR(ret));
> - if (allow_pwr_on)
> - ufs_mtk_va09_pwr_ctrl(res, 1);
>
> - return ret;
> + if (host->reg_avdd09) {
> + ret = regulator_disable(host->reg_avdd09);
> + if (ret) {
> + dev_err(host->hba->dev, "Failed to disable avdd09-supply: %pe\n",
> + ERR_PTR(ret));
> + if (allow_pwr_on)
> + ufs_mtk_va09_pwr_ctrl(res, 1);
> +
> + return ret;
> + }
> + }
> +
> + if (host->reg_avdd09_1) {
> + ret = regulator_disable(host->reg_avdd09_1);
> + if (ret) {
> + dev_err(host->hba->dev, "Failed to disable avdd09-1-supply: %pe\n",
> + ERR_PTR(ret));
> +
> + if (host->reg_avdd09) {
> + ret2 = regulator_enable(host->reg_avdd09);
[Severity: Medium]
When regulator_disable() fails for reg_avdd09_1, does this unintentionally
re-enable the avdd09 regulator even if allow_pwr_on is false?
For example, ufs_mtk_mphy_power_on() calls ufs_mtk_09v_off(host, false) on
its error path to force regulators off.
If the allow_pwr_on parameter is false to prevent rolling back to a powered-on
state, unconditionally calling regulator_enable() here seems to defeat the
purpose of the flag. This could leave the regulator actively powered on after
a forced shutdown.
Should this regulator_enable() be conditioned on allow_pwr_on as well?
> + if (ret2)
> + dev_err(host->hba->dev,
> + "Failed to re-enable avdd09-supply: %pe\n",
> + ERR_PTR(ret2));
> + }
> + if (allow_pwr_on)
> + ufs_mtk_va09_pwr_ctrl(res, 1);
> +
> + return ret;
> + }
> }
>
> return 0;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261016-mt8196-ufs-v14-0-e8d565e0cd45@collabora.com?part=8
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Louis-Alexis Eyraud" <louisalexis.eyraud@collabora.com>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-scsi@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v14 08/23] scsi: ufs: mediatek: Add dual 0.9V supply support
Date: Fri, 16 Oct 2026 12:43:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-174329@kernel.org> (raw)
In-Reply-To: <20261016-mt8196-ufs-v14-8-e8d565e0cd45@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] scsi: ufs: mediatek: bypass of allow_pwr_on leaves regulator enabled on error
--
commit 169f13062deb73e7db2227752ba9ee6ad0ec3257
Author: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
scsi: ufs: mediatek: Add dual 0.9V supply support
This commit adds support for an additional 0.9V supply pin on the MT8196
SoC compared to the MT8183 SoC. It introduces management for a second
optional 0.9V regulator named "avdd09-1".
> diff --git a/drivers/ufs/host/ufs-mediatek.c b/drivers/ufs/host/ufs-mediatek.c
> index bcb7f350984c0..c8c5f85507af6 100644
> --- a/drivers/ufs/host/ufs-mediatek.c
> +++ b/drivers/ufs/host/ufs-mediatek.c
[ ... ]
> @@ -513,20 +514,43 @@ static int ufs_mtk_wait_link_state(struct ufs_hba *hba, u32 state,
> static int ufs_mtk_09v_off(struct ufs_mtk_host *host, bool allow_pwr_on)
> {
> struct arm_smccc_res res;
> - int ret;
> + int ret, ret2;
>
> - if (!host->reg_avdd09)
> + if (!host->reg_avdd09 && !host->reg_avdd09_1)
> return 0;
>
> ufs_mtk_va09_pwr_ctrl(res, 0);
> - ret = regulator_disable(host->reg_avdd09);
> - if (ret) {
> - dev_err(host->hba->dev, "Failed to disable avdd09-supply: %pe\n",
> - ERR_PTR(ret));
> - if (allow_pwr_on)
> - ufs_mtk_va09_pwr_ctrl(res, 1);
>
> - return ret;
> + if (host->reg_avdd09) {
> + ret = regulator_disable(host->reg_avdd09);
> + if (ret) {
> + dev_err(host->hba->dev, "Failed to disable avdd09-supply: %pe\n",
> + ERR_PTR(ret));
> + if (allow_pwr_on)
> + ufs_mtk_va09_pwr_ctrl(res, 1);
> +
> + return ret;
> + }
> + }
> +
> + if (host->reg_avdd09_1) {
> + ret = regulator_disable(host->reg_avdd09_1);
> + if (ret) {
> + dev_err(host->hba->dev, "Failed to disable avdd09-1-supply: %pe\n",
> + ERR_PTR(ret));
> +
> + if (host->reg_avdd09) {
> + ret2 = regulator_enable(host->reg_avdd09);
[Severity: Medium]
When regulator_disable() fails for reg_avdd09_1, does this unintentionally
re-enable the avdd09 regulator even if allow_pwr_on is false?
For example, ufs_mtk_mphy_power_on() calls ufs_mtk_09v_off(host, false) on
its error path to force regulators off.
If the allow_pwr_on parameter is false to prevent rolling back to a powered-on
state, unconditionally calling regulator_enable() here seems to defeat the
purpose of the flag. This could leave the regulator actively powered on after
a forced shutdown.
Should this regulator_enable() be conditioned on allow_pwr_on as well?
> + if (ret2)
> + dev_err(host->hba->dev,
> + "Failed to re-enable avdd09-supply: %pe\n",
> + ERR_PTR(ret2));
> + }
> + if (allow_pwr_on)
> + ufs_mtk_va09_pwr_ctrl(res, 1);
> +
> + return ret;
> + }
> }
>
> return 0;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261016-mt8196-ufs-v14-0-e8d565e0cd45@collabora.com?part=8
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-16 12:43 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 12:32 [PATCH v14 00/23] MediaTek UFS Cleanup and MT8196 Enablement Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:32 ` [PATCH v14 01/23] dt-bindings: phy: Add mediatek,mt8196-ufsphy variant Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:32 ` [PATCH v14 02/23] dt-bindings: ufs: mediatek,ufs: Complete the binding Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:46 ` sashiko-bot
2026-10-16 12:46 ` sashiko-bot
2026-10-16 12:32 ` [PATCH v14 03/23] dt-bindings: ufs: mediatek,ufs: Add mt8196 variant Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:32 ` [PATCH v14 04/23] scsi: ufs: mediatek: Move MTK_SIP_UFS_CONTROL to mtk_sip_svc.h Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:32 ` [PATCH v14 05/23] phy: mediatek: ufs: Add support for resets Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:46 ` sashiko-bot
2026-10-16 12:46 ` sashiko-bot
2026-10-16 12:32 ` [PATCH v14 06/23] scsi: ufs: mediatek: Rework resets Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:32 ` [PATCH v14 07/23] scsi: ufs: mediatek: Rework 0.9V regulator Louis-Alexis Eyraud
2026-10-16 12:32 ` Louis-Alexis Eyraud
2026-10-16 12:44 ` sashiko-bot
2026-10-16 12:44 ` sashiko-bot
2026-10-16 12:33 ` [PATCH v14 08/23] scsi: ufs: mediatek: Add dual 0.9V supply support Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:43 ` sashiko-bot [this message]
2026-10-16 12:43 ` sashiko-bot
2026-10-16 12:33 ` [PATCH v14 09/23] scsi: ufs: mediatek: Rework init function Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 10/23] scsi: ufs: mediatek: Rework the crypt-boost stuff Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:43 ` sashiko-bot
2026-10-16 12:43 ` sashiko-bot
2026-10-16 12:33 ` [PATCH v14 11/23] scsi: ufs: mediatek: Handle misc host voltage regulators Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 12/23] scsi: ufs: mediatek: Remove undocumented downstream reset cruft Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 13/23] scsi: ufs: mediatek: Remove vendor kernel quirks cruft Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:43 ` sashiko-bot
2026-10-16 12:43 ` sashiko-bot
2026-10-16 12:33 ` [PATCH v14 14/23] scsi: ufs: mediatek: Use the common PHY framework Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:50 ` sashiko-bot
2026-10-16 12:50 ` sashiko-bot
2026-10-16 12:33 ` [PATCH v14 15/23] scsi: ufs: mediatek: Remove mediatek,ufs-broken-rtc property Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 16/23] scsi: ufs: mediatek: Rework _ufs_mtk_clk_scale error paths Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 17/23] scsi: ufs: mediatek: Clean up logging prints Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 18/23] scsi: ufs: mediatek: Rework ufs_mtk_wait_idle_state Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 19/23] scsi: ufs: mediatek: Don't acquire dvfsrc-vcore twice Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 20/23] scsi: ufs: mediatek: Rework hardware version reading Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 21/23] scsi: ufs: mediatek: Remove ret local from link_startup_notify Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 22/23] scsi: ufs: mediatek: Remove undocumented "clk-scale-up-vcore-min" Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
2026-10-16 12:33 ` [PATCH v14 23/23] scsi: ufs: mediatek: Add MT8196 compatible, update copyright Louis-Alexis Eyraud
2026-10-16 12:33 ` Louis-Alexis Eyraud
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=sashiko-outbox-174329@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=louisalexis.eyraud@collabora.com \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@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.