From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
regressions@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH] soc: qcom: pmic_glink: disable UCSI on sc8280xp
Date: Tue, 11 Jun 2024 11:52:59 +0300 [thread overview]
Message-ID: <ZmgQayq6RvJEQVgu@kuha.fi.intel.com> (raw)
In-Reply-To: <20240608114529.23060-1-johan+linaro@kernel.org>
On Sat, Jun 08, 2024 at 01:45:29PM +0200, Johan Hovold wrote:
> Disconnecting an external display triggers a hypervisor reset on the
> Lenovo ThinkPad X13s since 6.10-rc1 which enabled UCSI. Disable it again
> until the regression has been fixed properly.
>
> Fixes: 3f91a0bf4a0b ("soc: qcom: pmic_glink: reenable UCSI on sc8280xp")
> Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/soc/qcom/pmic_glink.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
>
> Dmitry reported off-list that his X13s was crashing when he disconnected
> an external display and I tracked it down to the enablement of UCSI in
> 6.10-rc1.
>
> I have not had time to debug this further, but I'm flagging this as a
> regression and sending an effective so that we have a fall back in case
> this is not fixed in timely manner.
>
> Note that this likely affects other Qualcomm SoCs as well.
>
> Johan
>
>
> #regzbot introduced: 3f91a0bf4a0b
>
>
>
> diff --git a/drivers/soc/qcom/pmic_glink.c b/drivers/soc/qcom/pmic_glink.c
> index 40fb09d69014..65279243072c 100644
> --- a/drivers/soc/qcom/pmic_glink.c
> +++ b/drivers/soc/qcom/pmic_glink.c
> @@ -348,11 +348,15 @@ static void pmic_glink_remove(struct platform_device *pdev)
> mutex_unlock(&__pmic_glink_lock);
> }
>
> +static const unsigned long pmic_glink_sc8280xp_client_mask = BIT(PMIC_GLINK_CLIENT_BATT) |
> + BIT(PMIC_GLINK_CLIENT_ALTMODE);
> +
> static const unsigned long pmic_glink_sm8450_client_mask = BIT(PMIC_GLINK_CLIENT_BATT) |
> BIT(PMIC_GLINK_CLIENT_ALTMODE) |
> BIT(PMIC_GLINK_CLIENT_UCSI);
>
> static const struct of_device_id pmic_glink_of_match[] = {
> + { .compatible = "qcom,sc8280xp-pmic-glink", .data = &pmic_glink_sc8280xp_client_mask },
> { .compatible = "qcom,pmic-glink", .data = &pmic_glink_sm8450_client_mask },
> {}
> };
> --
> 2.44.1
--
heikki
next prev parent reply other threads:[~2024-06-11 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 11:45 [PATCH] soc: qcom: pmic_glink: disable UCSI on sc8280xp Johan Hovold
2024-06-11 8:52 ` Heikki Krogerus [this message]
2024-06-14 22:48 ` Bjorn Andersson
2024-06-17 7:56 ` Johan Hovold
2024-06-17 8:49 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-17 9:08 ` Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 12:57 Johan Hovold
2023-12-08 16:34 ` Dmitry Baryshkov
2023-12-11 16:05 ` Johan Hovold
2023-12-17 17:21 ` Bjorn Andersson
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=ZmgQayq6RvJEQVgu@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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