Re: Lid sensor on Yoga 11e

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 25-10-17 01:17, Steven Presser wrote:
Hi Lars,

This happens because the ACPI ID ("BOSC0200") is reused on the Yoga 11e, having previously been used on (apparently) various tablets. I'm not sure what the best way to do it is, but we probably need to get that driver either a) improved to handle the dual-sensors or b) blacklisted on this hardware.  I'm happy to do the work if someone can point me in the right direction.

Hmm interesting I would expect there to be 2 ACPI devices for the
2 accelerometers and then things should just work fine.

Unless there is one DSDT entry / ACPI device with 2 i2c ACPI resources
to point to the 2 different accelerometers. That would not be the
first time I see that, we've some i2c helpers now to make dealing
with this easier.

Can you put an acpidump of the machine somewhere so that I can check
what is in the DSDT ?

On the rotation, the DSDT table has the rotation corrections embedded.  I suspect that Lenovo is using non-standard names on the 11e, since it's non-standard hardware and that that's throwing the existing driver for a loop.

Interesting, I don't think non-standard names is going to be an issue
here, the bmc150-accel driver which deals with the BOSC0200 devices
does not have any parsing code for orientation info in the DSDT at all.

Regards,

Hans





Steve


On 10/24/2017 12:43 AM, Lars Kellogg-Stedman wrote:
Sorry, one last item on this topic before I turn in.  The kernel driver is only monitoring the screen accelerometer at i2c-2, address 0x19.  The keyboard accelerometer at address 0x18 doesn't appear to be recognized by the kernel, but one can access it over the i2c bus.

On Tue, Oct 24, 2017 at 12:19 AM, Lars Kellogg-Stedman <lars@xxxxxxxxxx <mailto:lars@xxxxxxxxxx>> wrote:

    On Mon, Oct 23, 2017 at 10:06 PM, Lars Kellogg-Stedman <lars@xxxxxxxxxx <mailto:lars@xxxxxxxxxx>> wrote:

        ...which is all very exciting, and would be even more exciting if it were working correctly. Unfortunately, the screen orientation appears to be off by 90°...


    A problem which can be solved by dropping the following into /etc/udev/hwdb.d/61-sensor-local.hwdb:

    sensor:modalias:acpi:BOSC0200:*:dmi:*ThinkPadYoga11e3rdGen*
      ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, 1

    With that in place, screen orientation is correct...but the device is still stuck in tablet mode, with the keyboard/mouse disabled.

-- Lars Kellogg-Stedman <lars@xxxxxxxxxx <mailto:lars@xxxxxxxxxx>> | larsks@{twitter, irc, github, ...}




--
Lars Kellogg-Stedman <lars@xxxxxxxxxx <mailto:lars@xxxxxxxxxx>> | larsks@{twitter, irc, github, ...}


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot


_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel




[Index of Archives]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Photo]     [Yosemite Photos]     [Yosemite Advice]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux