From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Fan Wu <fanwu01@zju.edu.cn>
Cc: linux-usb@vger.kernel.org, bryan.odonoghue@linaro.org,
gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] usb: typec: qcom-pmic: cancel reset_work on stop
Date: Mon, 24 Aug 2026 13:22:25 +0200 [thread overview]
Message-ID: <aowpcQnisJNRNh29@black.igk.intel.com> (raw)
In-Reply-To: <20260819161448.76597-1-fanwu01@zju.edu.cn>
On Wed, Aug 19, 2026 at 04:14:48PM +0000, Fan Wu wrote:
> pdphy_stop() disables IRQs but leaves reset_work pending. If the IRQ
> handler schedules it just before disable_irq(), the work runs after
> remove() frees the struct via devm.
>
> Call cancel_work_sync() after disabling IRQs to close the window.
>
> This issue was found by an in-house static analysis tool.
>
> Fixes: a4422ff22142 ("usb: typec: qcom: Add Qualcomm PMIC Type-C driver")
> Cc: stable@vger.kernel.org
> Assisted-by: Codex:gpt-5.6
> Signed-off-by: Fan Wu <fanwu01@zju.edu.cn>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c
> index c8b1463e6..abb9d0321 100644
> --- a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c
> +++ b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.c
> @@ -544,6 +544,8 @@ static void qcom_pmic_typec_pdphy_stop(struct pmic_typec *tcpm)
> for (i = 0; i < pmic_typec_pdphy->nr_irqs; i++)
> disable_irq(pmic_typec_pdphy->irq_data[i].irq);
>
> + cancel_work_sync(&pmic_typec_pdphy->reset_work);
> +
> qcom_pmic_typec_pdphy_reset_on(pmic_typec_pdphy);
>
> regulator_disable(pmic_typec_pdphy->vdd_pdphy);
--
heikki
prev parent reply other threads:[~2026-08-24 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:14 [PATCH] usb: typec: qcom-pmic: cancel reset_work on stop Fan Wu
2026-08-20 8:17 ` Konrad Dybcio
2026-08-20 10:15 ` Bryan O'Donoghue
2026-08-24 11:22 ` Heikki Krogerus [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=aowpcQnisJNRNh29@black.igk.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=bryan.odonoghue@linaro.org \
--cc=fanwu01@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.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.