From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
Yauhen Kharuzhy <jekhor@gmail.com>
Subject: Re: [PATCH 3/3] pinctrl: cherryview: Ignore INT33FF UID 5 ACPI device
Date: Thu, 18 Nov 2021 12:19:15 +0200 [thread overview]
Message-ID: <YZYoo/KcP9mSlJjt@lahna> (raw)
In-Reply-To: <20211117231614.758362-3-hdegoede@redhat.com>
On Thu, Nov 18, 2021 at 12:16:14AM +0100, Hans de Goede wrote:
> Many Cherry Trail DSDTs have an extra INT33FF device with UID 5,
> the intel_pinctrl_get_soc_data() call will fail for this extra
> unknown UID, leading to the following error in dmesg:
Yeah, this may be the "DSW" or Deep Sleep Well community that is
typically not available for software to use at all. No idea why they
expose it on some systems.
> cherryview-pinctrl: probe of INT33FF:04 failed with error -61
>
> Add a check for this extra UID and return -ENODEV for it to
> silence this false-positive error message.
>
> Cc: Yauhen Kharuzhy <jekhor@gmail.com>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2021-11-18 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 23:16 [PATCH 1/3] pinctrl: cherryview: Don't use pin/offset 0 to mark an interrupt-line as unused Hans de Goede
2021-11-17 23:16 ` [PATCH 2/3] pinctrl: cherryview: Do not allow the same intr-line to be used by 2 pins Hans de Goede
2021-11-18 10:17 ` Mika Westerberg
2021-11-17 23:16 ` [PATCH 3/3] pinctrl: cherryview: Ignore INT33FF UID 5 ACPI device Hans de Goede
2021-11-18 10:19 ` Mika Westerberg [this message]
2021-11-18 10:13 ` [PATCH 1/3] pinctrl: cherryview: Don't use pin/offset 0 to mark an interrupt-line as unused Mika Westerberg
2021-11-18 10:55 ` 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=YZYoo/KcP9mSlJjt@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=jekhor@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.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;
as well as URLs for NNTP newsgroup(s).