public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: regressions@lists.linux.dev
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: pmic_glink: disable UCSI on sc8280xp
Date: Mon, 17 Jun 2024 09:56:21 +0200	[thread overview]
Message-ID: <Zm_sJb3_xfMgLsnj@hovoldconsulting.com> (raw)
In-Reply-To: <20240608114529.23060-1-johan+linaro@kernel.org>

[ Trimming CC list ]

Hi Thorsten,

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>
> ---
>  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

I noticed that this one did not make into the regression tracker. This
may be related to the fact that this is the second time I'm disabling
UCSI on sc8280xp and apparently I used the same patch Subject last time
so they end up in the same thread on lore:

	https://lore.kernel.org/lkml/20240608114529.23060-1-johan+linaro@kernel.org/

Bjorn has picked up this effective revert for 6.10 now, but I still
figured I'd mentioned this to you in case you want to add it to the
tracker and/or see what can be done to your scripts to avoid having
regressions like this fall through the cracks in the future.

Johan

[ Trying again: ]

#regzbot introduced: 3f91a0bf4a0b

  parent reply	other threads:[~2024-06-17  7:56 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
2024-06-14 22:48 ` Bjorn Andersson
2024-06-17  7:56 ` Johan Hovold [this message]
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=Zm_sJb3_xfMgLsnj@hovoldconsulting.com \
    --to=johan@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