From: Ian W MORRISON <ianwmorrison@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
stable@vger.kernel.org, Daniel Drake <drake@endlessm.com>
Subject: Re: [PATCH v2] gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist
Date: Wed, 28 Aug 2019 23:16:42 +1000 [thread overview]
Message-ID: <CAFXWsS89-fB=LGLRpeSrH8Y97=fqhZ7d77WORjXdS1YU5Xbfsg@mail.gmail.com> (raw)
In-Reply-To: <c07a8e2e-61a7-7ce7-4f73-48978be98d27@redhat.com>
On Wed, 28 Aug 2019 at 22:21, Hans de Goede <hdegoede@redhat.com> wrote:
>
> Hi,
>
> On 28-08-19 14:20, Hans de Goede wrote:
> > Hi,
> >
> > On 28-08-19 13:37, Andy Shevchenko wrote:
> >> On Tue, Aug 27, 2019 at 10:28:35PM +0200, Hans de Goede wrote:
> >>> Another day; another DSDT bug we need to workaround...
> >>>
> >>> Since commit ca876c7483b6 ("gpiolib-acpi: make sure we trigger edge events
> >>> at least once on boot") we call _AEI edge handlers at boot.
> >>>
> >>> In some rare cases this causes problems. One example of this is the Minix
> >>> Neo Z83-4 mini PC, this device has a clear DSDT bug where it has some copy
> >>> and pasted code for dealing with Micro USB-B connector host/device role
> >>> switching, while the mini PC does not even have a micro-USB connector.
> >>> This code, which should not be there, messes with the DDC data pin from
> >>> the HDMI connector (switching it to GPIO mode) breaking HDMI support.
> >>>
> >>> To avoid problems like this, this commit adds a new
> >>> gpiolib_acpi.run_edge_events_on_boot kernel commandline option, which
> >>> allows disabling the running of _AEI edge event handlers at boot.
> >>>
> >>> The default value is -1/auto which uses a DMI based blacklist, the initial
> >>> version of this blacklist contains the Neo Z83-4 fixing the HDMI breakage.
> >>
> >> Thank you!
> >>
> >> Assuming it works for Ian,
> >> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > Note I have access to a Minix Neo Z83-4 myself now and I did test that
> > this fixes it and that passing gpiolib_acpi.run_edge_events_on_boot=0
> > breaks HDMI again (so the option works).
>
> Erm that should be gpiolib_acpi.run_edge_events_on_boot=1 (not 0) breaks
> HDMI.
>
Many thanks again Hans. I've also tested the patch including the various command
line options on my MINIX Z83-4 and they work fine.
Best regards,
Ian
next prev parent reply other threads:[~2019-08-28 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 20:28 [PATCH v2] gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist Hans de Goede
2019-08-28 11:37 ` Mika Westerberg
2019-08-28 11:37 ` Andy Shevchenko
2019-08-28 12:20 ` Hans de Goede
2019-08-28 12:21 ` Hans de Goede
2019-08-28 13:16 ` Ian W MORRISON [this message]
2019-09-11 9:48 ` Linus Walleij
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='CAFXWsS89-fB=LGLRpeSrH8Y97=fqhZ7d77WORjXdS1YU5Xbfsg@mail.gmail.com' \
--to=ianwmorrison@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=drake@endlessm.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=stable@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).