From: sashiko-bot@kernel.org
To: "Krishna Kurapati" <krishna.kurapati@oss.qualcomm.com>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com,
linux-phy@lists.infradead.org
Subject: Re: [PATCH] phy: qcom: m31-eusb2: Fix return value of init call
Date: Sat, 18 Jul 2026 09:36:57 +0000 [thread overview]
Message-ID: <20260718093658.111191F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260718-m31-eusb2-fix-v1-1-8588a1b94d76@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Hardware initialization failures during register configuration in `m31eusb2_phy_init` are ignored, leading to a silent failure.
--
--- Patch [1]: [PATCH] phy: qcom: m31-eusb2: Fix return value of init call ---
commit 65f666fe30cbc54b37ee682f3064a24fcc24b16f
Author: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
phy: qcom: m31-eusb2: Fix return value of init call
The init call previously returned 0 even when repeater initialization or clock
enablement failed. This patch updates the failure path to return the actual
error value.
> diff --git a/drivers/phy/qualcomm/phy-qcom-m31-eusb2.c b/drivers/phy/qualcomm/phy-qcom-m31-eusb2.c
> index 0bec8657149c9..275df38256de3 100644
> --- a/drivers/phy/qualcomm/phy-qcom-m31-eusb2.c
> +++ b/drivers/phy/qualcomm/phy-qcom-m31-eusb2.c
[ ... ]
> m31eusb2_phy_write_sequence(phy, data->setup_seq, data->setup_seq_nregs);
> m31eusb2_phy_write_readback(phy->base,
> USB_PHY_HS_PHY_CTRL_COMMON0, FSEL,
> FIELD_PREP(FSEL, data->fsel));
> m31eusb2_phy_write_sequence(phy, data->override_seq, data->override_seq_nregs);
> m31eusb2_phy_write_sequence(phy, data->reset_seq, data->reset_seq_nregs);
>
> return 0;
[Severity: High]
This is a pre-existing issue, but since this patch fixes error handling in
m31eusb2_phy_init(), should we also check the return values of these register
configuration functions?
If m31eusb2_phy_write_sequence() or m31eusb2_phy_write_readback() fails, the
error is currently ignored. The function successfully returns 0 without
executing the disable_repeater and disable_vreg cleanup paths. This could leave
the PHY hardware in an incorrectly initialized state.
>
> disable_repeater:
> phy_exit(phy->repeater);
> disable_vreg:
> regulator_bulk_disable(M31_EUSB_NUM_VREGS, phy->vregs);
>
> - return 0;
> + return ret;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260718-m31-eusb2-fix-v1-1-8588a1b94d76@oss.qualcomm.com?part=1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2026-07-18 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 9:31 [PATCH] phy: qcom: m31-eusb2: Fix return value of init call Krishna Kurapati
2026-07-18 9:31 ` Krishna Kurapati
2026-07-18 9:36 ` sashiko-bot [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=20260718093658.111191F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--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.