From: sashiko-bot@kernel.org
To: "Louis-Alexis Eyraud" <louisalexis.eyraud@collabora.com>
Cc: linux-scsi@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
devicetree@vger.kernel.org, neil.armstrong@linaro.org,
vkoul@kernel.org, olteanv@gmail.com,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v12 13/24] scsi: ufs: mediatek: Remove vendor kernel quirks cruft
Date: Mon, 14 Sep 2026 12:45:46 +0000 [thread overview]
Message-ID: <20260914124546.7AC2F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914-mt8196-ufs-v12-13-9279d7ef814d@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incomplete cleanup: unused macro, enum, and SiP command left in header file
--
commit 5f2b17479ebe3d92418015f1a81b60d943aa3ac6
Author: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
scsi: ufs: mediatek: Remove vendor kernel quirks cruft
Both ufs_mtk_vreg_fix_vcc and ufs_mtk_vreg_fix_vccqx look like they are
vendor kernel hacks to work around existing downstream device trees.
Mainline does not need or want them, so remove them.
> diff --git a/drivers/ufs/host/ufs-mediatek.c b/drivers/ufs/host/ufs-mediatek.c
> index 3d108a0929205..3c10a9fd09dfc 100644
> --- a/drivers/ufs/host/ufs-mediatek.c
> +++ b/drivers/ufs/host/ufs-mediatek.c
> @@ -1053,73 +1053,6 @@ static void ufs_mtk_init_clocks(struct ufs_hba *hba)
> }
> }
>
> -#define MAX_VCC_NAME 30
> -static int ufs_mtk_vreg_fix_vcc(struct ufs_hba *hba)
> -{
[ ... ]
> - if (of_property_read_bool(np, "mediatek,ufs-vcc-by-num")) {
> - ufs_mtk_get_vcc_num(res);
> - if (res.a1 > UFS_VCC_NONE && res.a1 < UFS_VCC_MAX)
[Severity: Low]
With the removal of this function, does this also mean that
ufs_mtk_get_vcc_num(), enum ufs_mtk_vcc_num, and UFS_MTK_SIP_GET_VCC_NUM
are now entirely unused?
Looking at drivers/ufs/host/ufs-mediatek-sip.h, it seems like these were
only used here and could be removed as well to avoid leaving dead code behind:
drivers/ufs/host/ufs-mediatek-sip.h:
#define UFS_MTK_SIP_GET_VCC_NUM BIT(6)
...
enum ufs_mtk_vcc_num {
UFS_VCC_NONE = 0,
UFS_VCC_1,
UFS_VCC_2,
UFS_VCC_MAX
};
...
#define ufs_mtk_get_vcc_num(res) \
ufs_mtk_smc(UFS_MTK_SIP_GET_VCC_NUM, &(res))
Could these be cleaned up in this patch as well?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260914-mt8196-ufs-v12-0-9279d7ef814d@collabora.com?part=13
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Louis-Alexis Eyraud" <louisalexis.eyraud@collabora.com>
Cc: linux-scsi@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
devicetree@vger.kernel.org, neil.armstrong@linaro.org,
vkoul@kernel.org, olteanv@gmail.com,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v12 13/24] scsi: ufs: mediatek: Remove vendor kernel quirks cruft
Date: Mon, 14 Sep 2026 12:45:46 +0000 [thread overview]
Message-ID: <20260914124546.7AC2F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914-mt8196-ufs-v12-13-9279d7ef814d@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incomplete cleanup: unused macro, enum, and SiP command left in header file
--
commit 5f2b17479ebe3d92418015f1a81b60d943aa3ac6
Author: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
scsi: ufs: mediatek: Remove vendor kernel quirks cruft
Both ufs_mtk_vreg_fix_vcc and ufs_mtk_vreg_fix_vccqx look like they are
vendor kernel hacks to work around existing downstream device trees.
Mainline does not need or want them, so remove them.
> diff --git a/drivers/ufs/host/ufs-mediatek.c b/drivers/ufs/host/ufs-mediatek.c
> index 3d108a0929205..3c10a9fd09dfc 100644
> --- a/drivers/ufs/host/ufs-mediatek.c
> +++ b/drivers/ufs/host/ufs-mediatek.c
> @@ -1053,73 +1053,6 @@ static void ufs_mtk_init_clocks(struct ufs_hba *hba)
> }
> }
>
> -#define MAX_VCC_NAME 30
> -static int ufs_mtk_vreg_fix_vcc(struct ufs_hba *hba)
> -{
[ ... ]
> - if (of_property_read_bool(np, "mediatek,ufs-vcc-by-num")) {
> - ufs_mtk_get_vcc_num(res);
> - if (res.a1 > UFS_VCC_NONE && res.a1 < UFS_VCC_MAX)
[Severity: Low]
With the removal of this function, does this also mean that
ufs_mtk_get_vcc_num(), enum ufs_mtk_vcc_num, and UFS_MTK_SIP_GET_VCC_NUM
are now entirely unused?
Looking at drivers/ufs/host/ufs-mediatek-sip.h, it seems like these were
only used here and could be removed as well to avoid leaving dead code behind:
drivers/ufs/host/ufs-mediatek-sip.h:
#define UFS_MTK_SIP_GET_VCC_NUM BIT(6)
...
enum ufs_mtk_vcc_num {
UFS_VCC_NONE = 0,
UFS_VCC_1,
UFS_VCC_2,
UFS_VCC_MAX
};
...
#define ufs_mtk_get_vcc_num(res) \
ufs_mtk_smc(UFS_MTK_SIP_GET_VCC_NUM, &(res))
Could these be cleaned up in this patch as well?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260914-mt8196-ufs-v12-0-9279d7ef814d@collabora.com?part=13
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-09-14 12:45 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:38 [PATCH v12 00/24] MediaTek UFS Cleanup and MT8196 Enablement Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 01/24] dt-bindings: phy: Add mediatek,mt8196-ufsphy variant Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 02/24] dt-bindings: ufs: mediatek,ufs: Complete the binding Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 12:04 ` AngeloGioacchino Del Regno
2026-09-14 12:04 ` AngeloGioacchino Del Regno
2026-09-24 15:26 ` Rob Herring (Arm)
2026-09-24 15:26 ` Rob Herring (Arm)
2026-09-14 11:38 ` [PATCH v12 03/24] dt-bindings: ufs: mediatek,ufs: Add mt8196 variant Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 12:04 ` AngeloGioacchino Del Regno
2026-09-14 12:04 ` AngeloGioacchino Del Regno
2026-09-24 15:27 ` Rob Herring (Arm)
2026-09-24 15:27 ` Rob Herring (Arm)
2026-09-14 11:38 ` [PATCH v12 04/24] scsi: ufs: mediatek: Move MTK_SIP_UFS_CONTROL to mtk_sip_svc.h Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 05/24] phy: mediatek: ufs: Add support for resets Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 06/24] scsi: ufs: mediatek: Rework resets Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 07/24] scsi: ufs: mediatek: Rework 0.9V regulator Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 12:19 ` sashiko-bot
2026-09-14 12:19 ` sashiko-bot
2026-09-14 11:38 ` [PATCH v12 08/24] scsi: ufs: mediatek: Add dual 0.9V supply support Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 12:02 ` AngeloGioacchino Del Regno
2026-09-14 12:02 ` AngeloGioacchino Del Regno
2026-09-14 12:21 ` sashiko-bot
2026-09-14 12:21 ` sashiko-bot
2026-09-14 11:38 ` [PATCH v12 09/24] scsi: ufs: mediatek: Rework init function Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 10/24] scsi: ufs: mediatek: Rework the crypt-boost stuff Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 11/24] scsi: ufs: mediatek: Handle misc host voltage regulators Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 12/24] scsi: ufs: mediatek: Remove undocumented downstream reset cruft Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 11:38 ` [PATCH v12 13/24] scsi: ufs: mediatek: Remove vendor kernel quirks cruft Louis-Alexis Eyraud
2026-09-14 11:38 ` Louis-Alexis Eyraud
2026-09-14 12:45 ` sashiko-bot [this message]
2026-09-14 12:45 ` sashiko-bot
2026-09-14 11:39 ` [PATCH v12 14/24] scsi: ufs: mediatek: Use the common PHY framework Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 12:58 ` sashiko-bot
2026-09-14 12:58 ` sashiko-bot
2026-09-14 11:39 ` [PATCH v12 15/24] scsi: ufs: mediatek: Remove mediatek,ufs-broken-rtc property Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 12:52 ` sashiko-bot
2026-09-14 12:52 ` sashiko-bot
2026-09-14 11:39 ` [PATCH v12 16/24] scsi: ufs: mediatek: Rework _ufs_mtk_clk_scale error paths Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 13:03 ` sashiko-bot
2026-09-14 13:03 ` sashiko-bot
2026-09-14 11:39 ` [PATCH v12 17/24] scsi: ufs: mediatek: Clean up logging prints Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 11:39 ` [PATCH v12 18/24] scsi: ufs: mediatek: Rework ufs_mtk_wait_idle_state Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 11:39 ` [PATCH v12 19/24] scsi: ufs: mediatek: Don't acquire dvfsrc-vcore twice Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 11:39 ` [PATCH v12 20/24] scsi: ufs: mediatek: Rework hardware version reading Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 11:39 ` [PATCH v12 21/24] scsi: ufs: mediatek: Back up idle timer in per-instance struct Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 11:39 ` [PATCH v12 22/24] scsi: ufs: mediatek: Remove ret local from link_startup_notify Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 11:39 ` [PATCH v12 23/24] scsi: ufs: mediatek: Remove undocumented "clk-scale-up-vcore-min" Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 13:25 ` sashiko-bot
2026-09-14 13:25 ` sashiko-bot
2026-09-14 11:39 ` [PATCH v12 24/24] scsi: ufs: mediatek: Add MT8196 compatible, update copyright Louis-Alexis Eyraud
2026-09-14 11:39 ` Louis-Alexis Eyraud
2026-09-14 13:41 ` sashiko-bot
2026-09-14 13:41 ` sashiko-bot
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=20260914124546.7AC2F1F000FF@smtp.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.