regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Mark Brown <broonie@kernel.org>,
	Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Pali Rohár" <pali@kernel.org>,
	"Andi Shyti" <andi.shyti@kernel.org>,
	linux-i2c@vger.kernel.org, "Liam Girdwood" <lgirdwood@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] `lis3lv02d_i2c_suspend()` causes `unbalanced disables for regulator-dummy` and `Failed to disable Vdd_IO: -EIO`
Date: Wed, 14 Feb 2024 17:04:07 +0100	[thread overview]
Message-ID: <e752d061-0e94-48c2-ba17-3111a847785d@redhat.com> (raw)
In-Reply-To: <6e20e772-e50e-4600-8325-1878badbbdc8@leemhuis.info>

Hi,

On 2/14/24 16:34, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 08.02.24 15:34, Mark Brown wrote:
>> On Fri, Feb 02, 2024 at 12:38:04PM +0100, Paul Menzel wrote:
>>
>>> Testing commit 2f189493ae32 (i2c: i801: Add lis3lv02d for Dell XPS 15 7590)
>>> [1], it’s very likely this commit, it turns out, that Linux logs the warning
>>> below during ACPI S3 suspend:
> 
> Mark, many thx for your reply:
> 
>> The driver is just buggy here AFAICT,
> 
> /me reads that as "buggy even before 2f189493ae32, that commit just
> exposed the problem"
> 
>> it's powering off the device in
>> both runtime suspend and runtime resume so if the device is runtime
>> suspended when system suspend happens then it'll power off the device
>> again.  The runtime suspend and system suspend need to talk to each
>> other here.
> 
> Well, that was 6 days ago and nothing further happened. Makes me wonder:
> Who will look into this? And when?

I have a laptop with a lis3lv02d where I can try to reproduced Paul's
problem. I expect this to reproduce on any Dell with the lis3lv02d 
so reverting 2f189493ae32 won't help, it fixes the problem on
Paul's model but not on other Dell models which use the lis3lv02d
driver.

Anways I plan to look at this sometime next week.

Regards,

Hans



  reply	other threads:[~2024-02-14 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 11:38 [REGRESSION] `lis3lv02d_i2c_suspend()` causes `unbalanced disables for regulator-dummy` and `Failed to disable Vdd_IO: -EIO` Paul Menzel
2024-02-08 14:34 ` Mark Brown
2024-02-14 15:34   ` Linux regression tracking (Thorsten Leemhuis)
2024-02-14 16:04     ` Hans de Goede [this message]
2024-02-20 19:15 ` Hans de Goede

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=e752d061-0e94-48c2-ba17-3111a847785d@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andi.shyti@kernel.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=regressions@lists.linux.dev \
    --cc=wsa+renesas@sang-engineering.com \
    /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;
as well as URLs for NNTP newsgroup(s).