Re: chv-gpio interrupt storm on UMAX VisionBook 10Wi Pro

[Hans de Goede <hdegoede@xxxxxxxxxx>]

Hi,

On 7/8/20 1:02 PM, Jiri Slaby wrote:
> Hi,
>
> On 08. 07. 20, 12:15, Hans de Goede wrote:
> > Hi,
> >
> > On 7/8/20 10:52 AM, Jiri Slaby wrote:
> > > On 08. 07. 20, 10:23, Hans de Goede wrote:
> > > > Hi all,
> > > >
> > > > On 7/8/20 9:47 AM, Linus Walleij wrote:
> > > > > On Wed, Jul 8, 2020 at 9:18 AM Jiri Slaby <jirislaby@xxxxxxxxxx> wrote:
> > > > >
> > > > > > I installed Linux on UMAX VisionBook 10Wi Pro. It sometimes boots, but
> > > > > > even then it encounters lags, soft lockups:
> > > > > > > watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
> > > > > > > watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:0H:6]
> > > > > > > watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [kworker/0:2:133]
> > > > > > > watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
> > > > >
> > > > > Adding Hans de Goede to Cc, he often deals with this kind of weirdness
> > > > > so he might have some ideas here.
> > > >
> > > > Thank you for looping me in Linus. I've read up on the rest of the
> > > > thread in the archives.
> > > >
> > > > So looking at this:
> > > > https://www.umax.cz/umax-visionbook-10wi/
> > > >
> > > > This device appears to be a pretty standard Cherry Trail based 2-in-1
> > > > with detachable keyboard. Which usually means (with all the
> > > > hw-enablement
> > > > I've been doing the last 2 years for these) that it will just work.
> > > > But no such luck this time it seems.
> ...
> > > > What I find interesting / weird is that you (Jiri) get an active
> > > > (/sys/bus/acpi/devices/INT3496\:00/status != 0) INT3496 device at
> > > > all. That typically only happens when the BIOS thinks you are booting
> > > > Android.
> > >
> > > 15 that is.
> >
> > Right, that is normal for an enabled device the ACPI method
> > implementing the status attribute for your tablet looks like this:
> >
> >              Method (_STA, 0, NotSerialized)  // _STA: Status
> >              {
> >                  If (((BDID == One) && (OSID != One)))
> >                  {
> >                      Return (0x0F)
> >                  }
> >
> >                  Return (Zero)
> >              }
> >
> > So now we know that BDID == One and OSID != One, OSID == One
> > typically is Windows...
> >
> > Looking at the buttons next, can you do:
> >
> > cat /sys/bus/acpi/devices/ACPI0011:00/status
>
> Gives 0
>
> > and:
> >
> > cat /sys/bus/acpi/devices/INTCFD9:00/status
>
> Gives 15
>
> > If the BIOS thinks you are booting normal Windows the first
> > one should output 15  (0xf) aka present and the second one
> > should output 0, but I suspect it is the other way around...
>
> Right.
>
> > So looking at the GPIO resource definitions for BDID == One
> > for the ACPI0011 device we have:
> >
> >                  Name (PBUF, ResourceTemplate ()
> >                  {
> >                      GpioInt (Edge, ActiveBoth, ExclusiveAndWake, PullUp,
> > 0x0BB8,
> >                          "\\_SB.GPO2", 0x00, ResourceConsumer, ,
> >                          )
> >                          {   // Pin list
> >                              0x0008
> >                          }
> >                      GpioInt (Edge, ActiveBoth, Exclusive, PullDefault,
> > 0x0BB8,
> >                          "\\_SB.GPO0", 0x00, ResourceConsumer, ,
> >                          )
> >                          {   // Pin list
> >                              0x004E
> >                          }
> >                      GpioInt (Edge, ActiveBoth, Exclusive, PullDefault,
> > 0x0BB8,
> >                          "\\_SB.GPO0", 0x00, ResourceConsumer, ,
> >                          )
> >                          {   // Pin list
> >                              0x0050
> >                          }
> >                  })
> >
> > With a mapping of first resource to KEY_POWER, second resource to
> > KEY_VOLUMEUP and third resource to KEY_VOLUMEDOWN
> >
> > The INTCFD9 device OTOH has the following resource definitions for BDID
> > == One
> >
> >                  Name (PBUF, ResourceTemplate ()
> >                  {
> >                      GpioInt (Edge, ActiveBoth, ExclusiveAndWake, PullUp,
> > 0x0BB8,
> >                          "\\_SB.GPO2", 0x00, ResourceConsumer, ,
> >                          )
> >                          {   // Pin list
> >                              0x0008
> >                          }
> >                      GpioInt (Edge, ActiveBoth, ExclusiveAndWake,
> > PullDefault, 0x
> >                          "\\_SB.GPO1", 0x00, ResourceConsumer, ,
> >                          )
> >                          {   // Pin list
> >                              0x0008
> >                          }
> >                      GpioInt (Edge, ActiveBoth, Exclusive, PullDefault,
> > 0x0BB8,
> >                          "\\_SB.GPO0", 0x00, ResourceConsumer, ,
> >                          )
> >                          {   // Pin list
> >                              0x004E
> >                          }
> >                      GpioInt (Edge, ActiveBoth, Exclusive, PullDefault,
> > 0x0BB8,
> >                          "\\_SB.GPO0", 0x00, ResourceConsumer, ,
> >                          )
> >                          {   // Pin list
> >                              0x0050
> >                          }
> >                  })
> >
> > With a mapping of resource1: power, resource2: home, resource3: volume_up,
> > resource4: volume_down.
> >
> > So what we see here is that the "Android" style INTCFD9 device has
> > an extra entry for the home-button and I guess (hard to see on the
> > pictures) that there is no physical home-button.
>
> I don't know what it should look like, but there is no button with
> house-like painting. There is only a standard "Home" button -- Fn+PgUp.
> And that works even without that module.

I just realized I did not reply to this bit. I meant a home button on
the tablet part of the 2-in-1, so next to the power and volume buttons
on the tablet's edge.

Regards,

Hans