From: Jiri Slaby <jirislaby@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy@kernel.org>
Subject: Re: chv-gpio interrupt storm on UMAX VisionBook 10Wi Pro
Date: Thu, 9 Jul 2020 13:10:34 +0200 [thread overview]
Message-ID: <032ecb14-e8be-19cd-9150-91c633f28a2c@kernel.org> (raw)
In-Reply-To: <ca4dfb41-843c-d859-2128-c985aec97a99@redhat.com>
Hi,
On 09. 07. 20, 12:01, Hans de Goede wrote:
>> Any other idea what file/volume I should create in EFI fs?
>
> No I'm afraid not. The ACPI subsystem will execute the DSDT's
> _INI method (line 21712 in the disassembled DSDT) pretty early on.
>
> I think the best way to workaround this is to use a DSDT override
> where you set OSID=1 in that _INI method.
Yep, that indeed works.
> This is far from ideal, but so are the other options. Unfortunately
> this will not help any other users with the same device, but it at
> least should get it working for you.
If we only had sources of that BIOS (or at least binary)...
Now, I need to find a way how to persuade dracut to automatically pick
up the updated DSDT.
thanks,
--
js
next prev parent reply other threads:[~2020-07-09 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 7:18 chv-gpio interrupt storm on UMAX VisionBook 10Wi Pro Jiri Slaby
2020-07-08 7:47 ` Linus Walleij
2020-07-08 8:23 ` Hans de Goede
2020-07-08 8:46 ` Hans de Goede
2020-07-09 8:29 ` [PATCH] pinctrl: cherryview: Enable glitch filter for GPIOs used as kernel test robot
2020-07-08 8:52 ` chv-gpio interrupt storm on UMAX VisionBook 10Wi Pro Jiri Slaby
2020-07-08 10:15 ` Hans de Goede
2020-07-08 11:02 ` Jiri Slaby
2020-07-08 11:24 ` Hans de Goede
2020-07-08 11:36 ` Jiri Slaby
2020-07-08 11:47 ` Hans de Goede
2020-07-09 8:30 ` Jiri Slaby
2020-07-09 8:34 ` Andy Shevchenko
2020-07-09 8:36 ` Andy Shevchenko
2020-07-09 10:01 ` Hans de Goede
2020-07-09 11:10 ` Jiri Slaby [this message]
2020-07-09 11:19 ` Jiri Slaby
2020-07-09 11:53 ` Hans de Goede
2020-07-08 11:30 ` Hans de Goede
2020-07-08 11:38 ` Jiri Slaby
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=032ecb14-e8be-19cd-9150-91c633f28a2c@kernel.org \
--to=jirislaby@kernel.org \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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).