public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Wolfram Sang" <wsa@kernel.org>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
	"Cezary Rojewski" <cezary.rojewski@intel.com>,
	"Raul E Rangel" <rrangel@chromium.org>,
	linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [RFC] i2c: core: Do not enable wakeup by default
Date: Tue, 7 Feb 2023 12:33:55 +0200	[thread overview]
Message-ID: <Y+IpEwNSEtNk19D8@smile.fi.intel.com> (raw)
In-Reply-To: <20230207072540.27226-1-mika.westerberg@linux.intel.com>

On Tue, Feb 07, 2023 at 09:25:40AM +0200, Mika Westerberg wrote:
> After commit b38f2d5d9615 ("i2c: acpi: Use ACPI wake capability bit to
> set wake_irq") the I2C core has been setting I2C_CLIENT_WAKE for ACPI
> devices if they announce to be wake capable in their device description.
> However, on certain systems where audio codec has been connected through
> I2C this causes system suspend to wake up immediately because power to
> the codec is turned off which pulls the interrupt line "low" triggering
> wake up.
> 
> Possible reason why the interrupt is marked as wake capable is that some
> codecs apparently support "Wake on Voice" or similar functionality.
> 
> In any case, I don't think we should be enabling wakeup by default on
> all I2C devices that are wake capable. According to device_init_wakeup()
> documentation most devices should leave it disabled, with exceptions on
> devices such as keyboards, power buttons etc. Userspace can enable
> wakeup as needed by writing to device "power/wakeup" attribute.

I agree on the reasoning.

Should we have a Fixes tag?

Otherwise
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

In any case it would be nice if the initial contributors may have a chance
to test this and see how their setup is supposed to work.

> Reported-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> Hi,
> 
> Sending this as RFC because I'm not too familiar with the usage of
> I2C_CLIENT_WAKE and whether this is something that is expected behaviour
> in users of I2C devices. On ACPI side I think this is the correct thing
> to do at least.
> 
>  drivers/i2c/i2c-core-base.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
> index 087e480b624c..7046549bdae7 100644
> --- a/drivers/i2c/i2c-core-base.c
> +++ b/drivers/i2c/i2c-core-base.c
> @@ -527,7 +527,7 @@ static int i2c_device_probe(struct device *dev)
>  			goto put_sync_adapter;
>  		}
>  
> -		device_init_wakeup(&client->dev, true);
> +		device_init_wakeup(&client->dev, false);
>  
>  		if (wakeirq > 0 && wakeirq != client->irq)
>  			status = dev_pm_set_dedicated_wake_irq(dev, wakeirq);
> -- 
> 2.39.1
> 

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-02-07 10:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  7:25 [RFC] i2c: core: Do not enable wakeup by default Mika Westerberg
2023-02-07 10:33 ` Andy Shevchenko [this message]
2023-02-07 10:38   ` Cezary Rojewski
2023-02-07 16:33 ` Raul Rangel
2023-02-08  6:57   ` Mika Westerberg
2023-02-08  8:28     ` Amadeusz Sławiński
2023-02-08  9:29       ` Mika Westerberg
2023-02-09  9:13         ` Amadeusz Sławiński
2023-02-09  9:18           ` Mika Westerberg
2023-02-12 21:04             ` Wolfram Sang
2023-02-08 15:58       ` Raul Rangel
2023-02-09  2:30         ` Mario Limonciello
2023-02-09 14:14         ` Rafael J. Wysocki

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=Y+IpEwNSEtNk19D8@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=cezary.rojewski@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rrangel@chromium.org \
    --cc=wsa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox