From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Cc: Raul Rangel <rrangel@chromium.org>, Wolfram Sang <wsa@kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
"Limonciello, Mario" <mario.limonciello@amd.com>
Subject: Re: [RFC] i2c: core: Do not enable wakeup by default
Date: Thu, 9 Feb 2023 11:18:19 +0200 [thread overview]
Message-ID: <Y+S6Wz5P/dMG8I8g@black.fi.intel.com> (raw)
In-Reply-To: <eadeb808-1925-164e-3e78-0f14c4f2bdc4@linux.intel.com>
Hi,
On Thu, Feb 09, 2023 at 10:13:00AM +0100, Amadeusz Sławiński wrote:
> > > Well, I tried custom DSDT and had problems, but I just remembered that I
> > > probably need to pass "revision+1" in file, so kernel sees it as a newer
> > > version, let me try again. Is it enough to replace "ExclusiveAndWake" with
> > > "Exclusive"?
> >
> > Yes, I think that should be enough.
>
> And yes, it seems to work when I bump revision. So will use it as workaround
> for now and see about fixing BIOS.
Okay good to know, then I think we can forget this patch.
next prev parent reply other threads:[~2023-02-09 9:17 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
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 [this message]
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+S6Wz5P/dMG8I8g@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cezary.rojewski@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mario.limonciello@amd.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