All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 8 Jul 2020 13:36:41 +0200	[thread overview]
Message-ID: <29d9d787-bec2-7c41-30d4-d03c4cf75cdc@kernel.org> (raw)
In-Reply-To: <09661b70-0a19-e70a-1985-4da6024ec291@redhat.com>

Hi,

On 08. 07. 20, 13:24, Hans de Goede wrote:
>> It also has only 32 but EFI. It doesn't recognize 64-bit binaries. I had
>> to load 32-bit grub first to load the installer from a USB. So this is
>> EFI-mixed mode as it is called.
> 
> Hmm, ok, with CHT I would really expect there to be a 64 bit UEFI and
> your DSDT and the fact that my untested patch broke your boot, all do
> show that this is Cherry Trail / Cherryview and not a Bay Trail.
> 
> I guess that doing:
> 
> cat /proc/cpuinfo  | grep "model name"
> 
> Will output something like this:
> 
> model name      : Intel(R) Atom(TM) x5-Z8350  CPU @ 1.44GHz
> model name      : Intel(R) Atom(TM) x5-Z8350  CPU @ 1.44GHz
> model name      : Intel(R) Atom(TM) x5-Z8350  CPU @ 1.44GHz
> model name      : Intel(R) Atom(TM) x5-Z8350  CPU @ 1.44GHz
> 
> Note the model bould be some other Z8xxx nummer, likely it is a
> Z8350, and if not a Z8300 but any Z8xxx number is CHT.

Yes, correct:
model name      : Intel(R) Atom(TM) x5-Z8350  CPU @ 1.44GHz

> Further confirming that this really is Cherry Trail. Which
> at least means that my patches might help a bit.

They do not :(. The interrupts are still storming.

FWIW I tried the acpi_osi="Windows 2015" kernel parameter. No success too.

> But ideally we would still be able to get the BIOS to see
> us as Windows and set its OSID variable to 1. So we don't
> try to use the wrong GPIOs as IRQ at all. Can you try loading
> the BIOS setup-defaults / optimal defaults?

Loaded the optimal values. Still the same

> If that does not get rid of the IN3496 device (changes its
> status to 0), then try this:
> 
> Maybe you have a "Boot Architecture" option under the "Boot"
> menu in the BIOS? I know you are already at 32 bits, but
> maybe changing it to 64 bits helps? (after installing a 64 bit
> shim + grub)

Unfortunately, there is nothing like that. It's discussed on the net,
that these UMAXes have only 32bit EFI.

thanks,
-- 
js

  reply	other threads:[~2020-07-08 11:36 UTC|newest]

Thread overview: 21+ 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-09  8:29         ` 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 [this message]
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
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=29d9d787-bec2-7c41-30d4-d03c4cf75cdc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.