shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-25 23:21:33 +03:00
Code
b1ba0ce800
systemd-stable/hwdb.d/60-sensor.hwdb

954 lines
39 KiB
Plaintext
Raw Normal View History

udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
# This file is part of systemd.
#
# The lookup keys are composed in:
# 60-sensor.rules
#
# Match string formats:
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 10:22:35 +03:00
# sensor:modalias:<parent modalias pattern>:dmi:<dmi pattern>
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
#
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 10:22:35 +03:00
# The device modalias can be seen in the `modalias` file of the sensor parent,
# for example:
# cat /sys/`udevadm info -q path -n /dev/iio:device0`/../modalias
hwdb: Add information on where to find identifiers
2018-07-23 14:56:09 +03:00
#
# The full DMI string of the running machine can be read from
# /sys/class/dmi/id/modalias
# That requires a kernel built with CONFIG_DMIID set, which is common.
# The full DMI string is not needed here and the meaning of individual parts
# can be seen in the source of the DMIID kernel module
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/firmware/dmi-id.c
#
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
# To add local entries, create a new file
# /etc/udev/hwdb.d/61-sensor-local.hwdb
# and add your rules there. To load the new rules execute (as root):
# systemd-hwdb update
hwdb: fix comment suggested `udevadm trigger` command (#8465)
2018-03-16 17:25:14 +03:00
# udevadm trigger -v -p DEVNAME=/dev/iio:deviceXXX
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
# where /dev/iio:deviceXXX is the device in question.
#
# If your changes are generally applicable, preferably send them as a pull
# request to
# https://github.com/systemd/systemd
# or create a bug report on https://github.com/systemd/systemd/issues and
# include your new rules, a description of the device, and the output of
# udevadm info --export-db
#
hwdb: references added to hwdb rules format, needed to write syntax-correctly rules
2017-01-29 01:48:15 +03:00
# For hwdb format and systemd behavior:
# https://www.freedesktop.org/software/systemd/man/hwdb.html
#
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
# Allowed properties are:
# ACCEL_MOUNT_MATRIX=<matrix>
hwdb: 60-sensor.hwdb: Add proximity sensor udev property (#14845) Devices with proximity sensors can specify a near level that indicates when an object is considered close to the device.
2020-03-03 16:40:00 +03:00
# PROXIMITY_NEAR_LEVEL=<value>
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
#
# where <matrix> is a mount-matrix in the format specified in the IIO
# subsystem[1]. The default, when unset, is equivalent to:
# ACCEL_MOUNT_MATRIX=1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 10:22:35 +03:00
# eg. the identity matrix,
hwdb: 60-sensor.hwdb: Add proximity sensor udev property (#14845) Devices with proximity sensors can specify a near level that indicates when an object is considered close to the device.
2020-03-03 16:40:00 +03:00
# and <value> is an integer value above which an object is considered
# close by a proximity sensor:
# PROXIMITY_NEAR_LEVEL=100
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
#
# [1]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dfc57732ad38f93ae6232a3b4e64fd077383a0f1
hwdb: references added to hwdb rules format, needed to write syntax-correctly rules
2017-01-29 01:48:15 +03:00
#
hwdb: Document expected MOUNT_MATRIX on devices with non upright display (#7177) On some devices the display (LCD panel) is mounted non upright in the device's casing, e.g. mounted upside-down or 90 degree rotated. Document the expected ACCEL_MOUNT_MATRIX settings for such devices.
2017-10-25 10:47:27 +03:00
# Note for devices where the display (LCD panel) is mounted non upright
# in the device's casing, e.g. mounted upside-down or 90 degree rotated,
# the ACCEL_MOUNT_MATRIX should be such that the x and y axis matches the
# x and y axis of the display, not those of the casing, so that desktop
# environments using the accelerometer data for rotation will e.g.
# automatically flip their output for an upside-down display when the device
# is held upright.
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
#
hwdb: add ACCEL_LOCATION to the allowed properties Signed-off-by: Luís Ferreira <contact@lsferreira.net>
2019-04-13 21:12:45 +03:00
# ACCEL_LOCATION=<location>
#
# where <location> is the location of the sensor. This value could be 'base'
# or 'display'. The default, when unset, is equivalent to:
# ACCEL_LOCATION=display
#
hwdb: Document how to properly set the mount-matrix for the base-accelerometer in 360 degree hinges style 2-in-1s with 2 accelerometers Document how the mount-matrix for the base-accelerometer must be set on 360 degree hinges style 2-in-1s with 2 sensors (one in the display and 1 in the base). Note the choice to define the lid being fully closed as an angle of 0 degrees is based on the ACPI tables of devices with a BOSC0200 ACPI device-node describing both sensors. In this case the ACPI tables contain mount-matrix info (and the kernel will soon support reading this and exporting it to userspace) and the mount-matrices defined in these ACPI tables are such that the angle of the G-force vector measured by the sensors is identical for both sensors when the laptop's lid is fully closed. This also feels more natural then defining the laptop being fully open (180 degrees open) as the home / 0 degree angle position.
2020-11-18 23:11:14 +03:00
# A note about setting ACCEL_MOUNT_MATRIX for ACCEL_LOCATION=base sensors,
# on 360 degree hinges style 2-in-1s with 2 sensors (one in the display and
# 1 in the base). Userspace will use both sensors to calculate the angle between
# the 2 halves and the angle is defined as being 0 when the device is folded
# as a regular clamshell laptop with its lid closed. This means that the
# base-accelerometer's mount-matrix must be such, that after applying
# the mount-matrices to both sensors, the base-accelerometer's readings must
# be identical to the display-accelerometer's readings (when the lid is
# closed).
#
udev: Add rules for accelerometer orientation quirks This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
2016-12-06 19:16:43 +03:00
# Sort by brand, model
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# Acer
#########################################
hwdb: Add accel orientation quirk for Acer Aspire Switch 10 SW3-016 2-in-1 Add a quirk to fix the accelerometer orientation on the Acer Aspire Switch 10 SW3-016 2-in-1.
2020-11-18 19:11:50 +03:00
sensor:modalias:acpi:KIOX0009*:dmi:*:svnAcer:pnAspireSW3-016:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, -1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svn*Acer*:*pn*AspireSW5-011:*
hwdb: added accelerometer quirk for Aspire Switch 10 (sw5-011)
2018-06-25 12:40:12 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svn*Acer*:*pn*AspireSW5-012:*
hwdb: Add ACCEL_MOUNT_MATRIX for the Acer Aspire Switch 10 convertible SW5-012 (#7394)
2017-11-20 15:43:48 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*svnAcer*:*TP-SW5-017-17BU:*
Add sensor configuration for Acer SW5-017-17BU
2020-08-27 02:46:30 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, -1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
sensor:modalias:acpi:BMA250E*:dmi:*:svnAcer:pnIconiaW1-810:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: fix trailing newline issue
2019-03-18 18:06:14 +03:00
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500:*:dmi:*Acer*:pnOneS1002:*
Update 60-sensor.hwdb for Acer Acer One 10 S1002 Tested on GNOME iio-sensor-proxy. With this config touchscreen auto-rotation works fine.
2019-03-17 21:54:16 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, -1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
hwdb: Add accelerometer orientation quirk for the Acer One 10 aka S1003 Add accelerometer orientation quirk for the Acer One 10 2-in-1 also known as the Acer S1003.
2018-10-12 11:38:00 +03:00
sensor:modalias:acpi:KIOX0009*:dmi:*:svnAcer:pnOneS1003:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: fix whitespace issue
2020-01-21 16:23:14 +03:00
Add Acer Switch SW312-31 to sensor hwdb See issue #13732
2019-10-16 00:43:36 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnAcer*:pnSwitchSW312-31:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Acer One 10 aka S1003 Add accelerometer orientation quirk for the Acer One 10 2-in-1 also known as the Acer S1003.
2018-10-12 11:38:00 +03:00
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*svn*Acer*:*pn*Spin*SP111-32:*
sensor:modalias:acpi:BOSC0200*:dmi:*svn*Acer*:*pn*Spin*SP111-33:*
sensor:modalias:acpi:BOSC0200*:dmi:*svnAcer*:*pnSpinSP111-34:*
ACCEL_MOUNT_MATRIX for additional Acer Spin model This fixes the broken rotation on the Acer Spin 1 I recently bought (exact model is SP111-34N-P4BZ). It is possible that all of the SP111 models would use the same matrix, but to be on the safe side, I added a new entry.
2020-05-21 23:41:25 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Archos 80 Cesium tablet. Add accelerometer orientation quirk for the Archos 80 Cesium 8" windows tablet.
2018-05-28 17:39:16 +03:00
#########################################
# Archos
#########################################
sensor:modalias:acpi:SMO8500*:dmi:*:svnARCHOS:pnARCHOS80Cesium:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Asus TP500LB accelerometer support
2017-01-29 01:48:55 +03:00
#########################################
# AsusTek
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:*pnT100CHI:*
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:pnT300CHI:*
hwdb: Add Asus T300CHI accelerator matrix
2018-10-29 05:06:03 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; 1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:*pnM80TA:*
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:*pnT100TA:*
Fix orientation detection for Asus Transformer T100TAF, copied T100TA rule
2022-04-30 16:06:55 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:*pnT100TAF:*
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:pnT200TA:*
hwdb: Add accel mount settings for Asus T200TA 2-in-1 (#7810) Add accel mount settings for the INVN6500 accelerometer found in Asus T200TA 2-in-1 devices to 60-sensor.hwdb.
2018-01-04 21:43:27 +03:00
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:*pnTP201SA:*
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:pn*E205SA:*
hwdb: Add accelerometer orientation quirk for Asus TP200SA
2018-07-06 16:17:52 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svn*ASUSTeK*:*pn*TP300LA:*
sensor:modalias:acpi:INVN6500*:dmi:*svn*ASUSTeK*:*pn*TP300LD:*
accelerator mount matrix for Asus TP300LD (#6789)
2017-09-11 09:36:05 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnASUSTeK*:*pn*Q551LN:*
Added ACCEL_MOUNT_MATRIX for Asus Q551LN in hwdb/60-sensor.hwdb
2019-07-03 21:42:45 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:KXJ2109*:dmi:*:svnASUSTeK*:pnME176C:*
hwdb: Add accelerometer mount matrix for ASUS MeMO Pad 7 (ME176C)
2019-02-09 23:17:18 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*svn*ASUSTeK*:*pn*TP300LJ:*
hwdb: Asus TP300LJ accelerometer quirks (#5681) iio-sensor-proxy expects the accelerometer oriented as follows: positive x - to the right, positive y - up (opposite to gravity). The hardware in the Asus TP300LJ-DW049H is however oriented differently: positive x - down, positive y - to the left This commit adds a ACCEL_MOUNT_MATRIX quirk for this particular laptop model.
2017-04-03 10:53:10 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*svn*ASUSTeK*:*pn*TP500LAB:*
sensor:modalias:acpi:SMO8500*:dmi:*svn*ASUSTeK*:*pn*TP500LB:*
hwdb: Add Asus TP550LA
2021-05-09 11:59:50 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*svn*ASUSTeK*:*pn*TP550LA:*
hwdb: readded accelerometer orientation entry for AsusTek TP500LB (#7958)
2018-01-23 03:50:09 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*svn*ASUSTeK*:*pn*TP300LD:*
hwdb: Add accel orientation for AsusTek TP300LAB
2020-10-19 03:00:27 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*svn*ASUSTeK*:*pn*TP300LAB:*
hwdb: fix accelerometer mount matrix for Asus TP300LD (#8327) (#8463)
2018-03-19 12:25:07 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: add accelerometer mount matrix for Asus TP300LD (#8327)
2018-03-02 14:11:28 +03:00
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*svn*ASUSTeK*:*pn*TP412UA:*
hwdb: Added correct ACCEL_MOUNT_MATRIX for the Asus TP412UA
2018-07-26 14:35:55 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accel mount settings for Axxo TW-1011 2-in-1 (#7439) Add accel mount settings for the SMO8500 accelerometer found in Axxo TW-1011 2-in-1 devices to 60-sensor.hwdb.
2017-11-23 18:25:42 +03:00
#########################################
# Axxo
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*:svnStandard:pnWCBT1011::*
hwdb: Add accel mount settings for Axxo TW-1011 2-in-1 (#7439) Add accel mount settings for the SMO8500 accelerometer found in Axxo TW-1011 2-in-1 devices to 60-sensor.hwdb.
2017-11-23 18:25:42 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# Chuwi
#########################################
hwdb: Add accelerometer orientation entry for Chuwi Vi8 (CWI506) tablet Add an accelerometer orientation entry for the Chuwi Vi8 (CWI506) tablet.
2017-12-20 12:57:38 +03:00
# Chuwi Vi8 (CWI506)
sensor:modalias:acpi:BMA250E*:dmi:bvnINSYDECorp.:bvrCHUWI.D86JLBNR*:svnInsyde:pni86:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
# Chuwi Vi8 Plus (CWI519)
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnHampoo:pnD2D3_Vi8A1:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Chuwi Vi10 tablet Add accelerometer orientation quirk for the Chuwi Vi10 (CWI505) tablet. While at it also update the Chuwi Hi8 Pri comment to include the CWI model-number.
2018-06-08 10:29:09 +03:00
# Chuwi Vi10 (CWI505)
sensor:modalias:acpi:BMA250E*:dmi:bvnINSYDECorp.:bvrG1D_S165*:svnilife:pnS165:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: mount matrix for Chuwi Hi8 (CWI509) (#17355)
2020-10-15 09:17:31 +03:00
# Chuwi Hi8 (CWI509)
sensor:modalias:acpi:BMA250E*:dmi:*svnilife*:pnS806:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Chuwi Vi10 tablet Add accelerometer orientation quirk for the Chuwi Vi10 (CWI505) tablet. While at it also update the Chuwi Hi8 Pri comment to include the CWI model-number.
2018-06-08 10:29:09 +03:00
# Chuwi Hi8 Pro (CWI513)
hwdb: Add accelerometer orientation entry for Chuwi Hi8 Pro tablet (#6998) Add an accelerometer orientation entry for the Chuwi Hi8 Pro tablet.
2017-10-05 02:06:55 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnHampoo:pnX1D3_C806N:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: 60-sensor.hwdb Chuwi Hi10 CWI515 accelerometer orientation.
2019-12-29 21:44:32 +03:00
# Chuwi Hi10 (CWI515)
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:*:svnDefaultstring:pnDefaultstring:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
Add Chuwi Hi10 to 60-sensor.hwdb (#13351)
2019-08-22 10:12:31 +03:00
# Chuwi Hi10 (CWI1515)
hwdb: fix whitespace issue
2020-01-21 16:23:14 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvrP02A_C106.60E:*:svnDefaultstring:pnDefaultstring:*
Add Chuwi Hi10 to 60-sensor.hwdb (#13351)
2019-08-22 10:12:31 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for the Chuwi Hi10 Plus (CWI527) Add a quirk for the accelerometer orientation for the Chuwi Hi10 Plus (CWI527) tablet.
2021-09-24 16:26:43 +03:00
# Chuwi Hi10 Plus (CWI527)
sensor:modalias:acpi:BOSC0200*:dmi:*:svnCHUWIINNOVATIONANDTECHNOLOGY*:pnHi10plustablet:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
# Chuwi Hi10 Pro (CWI529)
hwdb: Add accelerometer orientation entry for Chuwi Hi10 Pro
2017-12-28 01:49:14 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svn*CHUWIINNOVATIONANDTECHNOLOGY*:pnHi10protablet:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Chuwi Hi10 X Add a quirk to fix the accelerometer orientation on the Chuwi Hi10 X so that the display is not rotated 90 degree counter clockwise anymore.
2020-05-29 22:43:49 +03:00
# Chuwi Hi10 X
sensor:modalias:acpi:MXC6655*:dmi:*:svnCHUWIInnovationAndTechnology*:pnHi10X:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for the Chuwi Hi10 Go tablet
2021-12-14 16:57:38 +03:00
# Chuwi Hi10 Go
sensor:modalias:acpi:MXC6655*:dmi:*:svnCHUWIINNOVATIONLIMITED:pnHi10Go:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0,-1, 0; 0, 0, 1
hwdb: Fix Chuwi Hi12 orientation sensor (#8266) hwdb: Fix Chuwi Hi12 orientation sensor
2018-02-23 21:57:13 +03:00
# Chuwi Hi12
sensor:modalias:acpi:BOSC0200*:dmi:*:svnHampoo:pnP02BD6_HI-122LP:*
hwdb: Chuwi Hi12 (#17042) Different bios version includes different pn. Submitted change fixed my inverted screen after reboot. I've stepped back to the bios version 5.11 28.04.2016 in an attempt to troubleshoot Windows Hello locking the sign in on reboot. The screen again rotated, but 90 degrees to the right. I created a new hwdb line to resolve that issue. The bios version changes the dmi string including the svn and pn.
2020-09-17 17:52:52 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnDefaultstring:pnDefaultstring:*
sensor:modalias:acpi:BOSC0200*:dmi:*:svnHampoo:pnE4D6_HI-122LP:*
hwdb: Fix Chuwi Hi12 orientation sensor (#8266) hwdb: Fix Chuwi Hi12 orientation sensor
2018-02-23 21:57:13 +03:00
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
Update version including Chuwi Hi13 (#6744)
2017-09-06 11:18:20 +03:00
# Chuwi Hi13
hwdb: update the Chuwi HI13 pattern (#12469) Correct the searching pattern for Chuwi Hi13. Follow-up for c70b51a7b98c3538aba7bbfee455b850b0aa714e.
2019-05-06 16:55:22 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnChuwi*:pnHi13:*
Update version including Chuwi Hi13 (#6744)
2017-09-06 11:18:20 +03:00
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accel orientation quirk for the Chuwi Hi13 (CWI534) with BMA250 sensor Recently the kernel has gotten support for reading the mount-matrix for BMA250 sensors represented by a BOSC0200 ACPI device from the ACPI tables, so that we don't need to add quirks for these. At least that was the theory. The Chuwi Hi13 (CWI534) with BMA250 sensor has the sensor mounted such that it works / needs the normal(ized) matrix, but the ACPI tables actually contain a wrong matrix inverting the X and Y axis. Add a quirk to override /sys/bus/iio/devices/iio:device?/in_mount_matrix with the norm-matrix, since the ACPI derived matrix is actually wrong on these devices (sigh)
2021-07-01 16:28:25 +03:00
# Chuwi Hi13 (CWI534) with BMA250 sensor
# Note this sets the norm matrix, since the matrix which the kernel reads
# from the ACPI tables is actually wrong on these models
sensor:modalias:acpi:BOSC0200*:dmi:*:svnChuwi*:pnHi13:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, 1, 0; 0, 0, 1
Added Chuwi HiBook support (#7465)
2017-11-25 17:40:55 +03:00
# Chuwi HiBook
Corrected Chuwi HiBook entry (#7483)
2017-11-27 18:32:07 +03:00
# Chuwi HiBook does not have its product name filled, so we
# match the entire dmi-alias, assuming that the use of a BOSC0200 +
# bios-version + bios-date combo is unique
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/07/2016:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnHampoo:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/28/2016:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnHampoo:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
Fix Mount Matrix for Chuwi HiBook
2017-12-24 17:20:07 +03:00
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
Added Chuwi HiBook support (#7465)
2017-11-25 17:40:55 +03:00
Added Chuwi Hibook Pro (Model: CWI526) (#15770)
2020-05-11 11:25:02 +03:00
# Chuwi HiBook Pro (CWI526)
sensor:modalias:acpi:BOSC0200*:dmi:*:svnHampoo*:pnP1D6_C109K:*
hwdb: whitespace fix
2020-05-29 00:25:33 +03:00
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
Added Chuwi Hibook Pro (Model: CWI526) (#15770)
2020-05-11 11:25:02 +03:00
hwdb: Add accelerometer orientation quirk for the Chuwi CoreBook tablet
2018-11-14 10:18:23 +03:00
# Chuwi CoreBook
# Chuwi CoreBook does not have its product name filled, so we
# match the entire dmi-alias
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvrY13D_KB133.103:bd06/01/2018:*svnHampoo:pnDefaultstring:pvrV100:rvnHampoo:rnY13D_KB133:rvrV100:cvnDefaultstring:ct9:cvrDefaultstring:*
hwdb: Add accelerometer orientation quirk for the Chuwi CoreBook tablet
2018-11-14 10:18:23 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
Add matrix for the Chuwi SurBook Mini (CWI540)
2021-08-29 21:49:20 +03:00
# Chuwi SurBook Mini (CWI540)
sensor:modalias:acpi:BOSC0200*:dmi:*:svnHampoo*:pnC3W6_AP108_4GB:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
hwdb: Add accelerometer orientation quirk for the Connect Tablet9 tablet Add accelerometer orientation quirk for the Connect Tablet9 tablet.
2018-06-30 22:56:59 +03:00
# Connect
#########################################
sensor:modalias:acpi:KIOX000A*:dmi:*:svnConnect:pnTablet9:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
#########################################
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
# Cube
#########################################
# Cube iWork8 Air
sensor:modalias:acpi:KIOX000A*:dmi:*:svncube:pni1-TF:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: add cube i7
2020-02-27 15:16:34 +03:00
# Cube i7
sensor:modalias:acpi:SMO8500*:dmi:*:svncube:pni7:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: add Cube Mix Plus (i18B) rotation info Added Cube Mix Plus (i18B) Rotation information. Also Combined the sensor lines with the different Cube i7 stylus models because they use the same ACCEL_MOUNT_MATRIX
2021-01-14 02:08:36 +03:00
# Cube i7 Stylus, i7 Stylus I8L Model, i7 Book (i16) and Mix Plus (i18B)
hwdb: Add Cube i7 Stylus sensor rotation matrix (#6722)
2017-09-01 11:51:41 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnCube:pni7Stylus:*
hwdb: add accel mount settings for Cube i7 Stylus I8L Model (#9207) There are different Cube i7 Stylus generations. Those are identified with the printed serial code sticker on motherboard (Printed serial code on casing is not always true) Order of Model (Old - New): W WA WWA WN(I8WN) I8L(With W on casing) I own a I8L generation so the hw identification for my model does not work. # cat /sys/class/dmi/id/sys_vendor Cube # сat /sys/class/dmi/id/product_name i8-L
2018-06-06 13:02:35 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnCube:pni8-L:*
hwdb: add Cube Mix Plus (i18B) rotation info Added Cube Mix Plus (i18B) Rotation information. Also Combined the sensor lines with the different Cube i7 stylus models because they use the same ACCEL_MOUNT_MATRIX
2021-01-14 02:08:36 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnCube:pni16:*
sensor:modalias:acpi:KIOX000A*:dmi:*:svnCube:pni18B:*
hwdb: add accel mount settings for Cube i7 Stylus I8L Model (#9207) There are different Cube i7 Stylus generations. Those are identified with the printed serial code sticker on motherboard (Printed serial code on casing is not always true) Order of Model (Old - New): W WA WWA WN(I8WN) I8L(With W on casing) I own a I8L generation so the hw identification for my model does not work. # cat /sys/class/dmi/id/sys_vendor Cube # сat /sys/class/dmi/id/product_name i8-L
2018-06-06 13:02:35 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
Update 60-sensor.hwdb (#9991)
2018-09-03 06:07:23 +03:00
# Cube iWork 10 Flagship
sensor:modalias:acpi:BOSC0200*:dmi:*:svnCube:pnI15-TC:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
Add Cube iWork 11 Stylus
2019-12-07 17:15:02 +03:00
# Cube iWork 11 Stylus
sensor:modalias:acpi:KIOX000A*:dmi:*:svncube:pni8-T:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
Update 60-sensor.hwdb Removed the blank
2020-09-18 04:33:31 +03:00
Update 60-sensor.hwdb Add Cube KNote 5 ACCEL matrix
2020-09-17 17:56:00 +03:00
# Cube KNote 5
sensor:modalias:acpi:KIOX000A*:dmi:*:svnALLDOCUBE:pni1102:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
Add Cube iWork 11 Stylus
2019-12-07 17:15:02 +03:00
hwdb: Add accel orientation quirk for the Cyberbook T116 tablet Add a quirk for the accelerometer orientation for the Cyberbook T116 rugged tablet.
2021-09-28 20:49:38 +03:00
#########################################
# Cyberbook
#########################################
# Cyberbook T116
sensor:modalias:acpi:KIOX000A*:dmi:*:rvnDefaultstring:rnCherryTrailCR:*:sku20170531:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: 60-sensors: Fix alphabetic sorting by vendor name The Cytrix entry was added at the end instead of sorted alphabetically by vendor name.
2018-03-09 16:50:04 +03:00
#########################################
# Cytrix (Mytrix)
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:*KIOX000A*:dmi:*svn*CytrixTechnology:*pn*Complex11t:*
hwdb: 60-sensors: Fix alphabetic sorting by vendor name The Cytrix entry was added at the end instead of sorted alphabetically by vendor name.
2018-03-09 16:50:04 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Mark Intel Sensor Hub's accel sensor on Vostro 5581 as being in the base This laptop uses the accelerometer as a freefall sensor, so mark it as in base to prevent screen rotation.
2019-11-11 19:30:46 +03:00
#########################################
# Dell
#########################################
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:pnVostro5581:*
Add additional Dell models that require ACCEL_LOCATION=base This is a related commit to the bug reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938259 This adds additional 4 models that without this param, the screen rotates when the clamshell laptop rotates, which is an unwanted behavior. This commit also merges entries that needs the same param. Signed-off-by: Yao Wei (魏銘廷) <yao.wei@canonical.com>
2021-09-08 08:55:49 +03:00
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:sku0A36:*
Use SKU to identify Dell clamshell models for accelerometer properties As per request from Dell, we need to use sku property of modalias that is patched into linux 5.13 for model identification: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
2021-07-27 09:05:28 +03:00
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:sku0A3E:*
Add additional Dell models that require ACCEL_LOCATION=base This is a related commit to the bug reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938259 This adds additional 4 models that without this param, the screen rotates when the clamshell laptop rotates, which is an unwanted behavior. This commit also merges entries that needs the same param. Signed-off-by: Yao Wei (魏銘廷) <yao.wei@canonical.com>
2021-09-08 08:55:49 +03:00
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:sku0B09:*
Use SKU to identify Dell clamshell models for accelerometer properties As per request from Dell, we need to use sku property of modalias that is patched into linux 5.13 for model identification: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
2021-07-27 09:05:28 +03:00
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:sku0B0B:*
Add additional Dell models that require ACCEL_LOCATION=base This is a related commit to the bug reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938259 This adds additional 4 models that without this param, the screen rotates when the clamshell laptop rotates, which is an unwanted behavior. This commit also merges entries that needs the same param. Signed-off-by: Yao Wei (魏銘廷) <yao.wei@canonical.com>
2021-09-08 08:55:49 +03:00
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:sku0B0D:*
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:sku0B11:*
Add ACCEL_LOCATION property for Dell clamshell models
2020-10-08 05:27:18 +03:00
ACCEL_LOCATION=base
Add a device to 60-sensor.hwdb Adding support for a Dell Venue 8 Pro tablet. Rotation was off by 90° to the left initially, the proposed change fixes the issue on my device.
2020-03-28 03:29:34 +03:00
# Dell Venue 8 Pro 3845
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnDellInc.*:pnVenue8Pro3845:*
Add a device to 60-sensor.hwdb Adding support for a Dell Venue 8 Pro tablet. Rotation was off by 90° to the left initially, the proposed change fixes the issue on my device.
2020-03-28 03:29:34 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Dell venue 10 pro 5055 accel mount matrix (#14104)
2019-11-22 10:51:44 +03:00
# Dell Venue 10 Pro 5055
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*svnDell*:pnVenue10Pro5055:*
hwdb: Dell venue 10 pro 5055 accel mount matrix (#14104)
2019-11-22 10:51:44 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; 1, 0, 0; 0, 0, 1
Add accel mount matrix for BayTrail-based tablets by DEXP This commit adds accel mount matrix for DEXP Ursus 10XW and Z110i tablets. In current state (*svn*DEXP*:*pn*DEXPOEM*) it will apply to many (if not almost all) BayTrail-based tablets with Windows by DEXP (with same DMI strings) but this expected to cause no (or very little) harm as this devices is mostly very similar with slight difference. However, if correction of this quirk becomes necessary in the future, this DMI strings could be used to distinguish 10XW and Z110i from other tablets by DEXP. DEXP Ursus 10XW: dmi:bvnTechvisionHASHVersion96AC8868:bvr5.6.5:bd12/26/2014:svnDEXP:pnDEXPOEM:pvr1.0:rvnDEXP:rnDEXPOEM:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: DEXP Ursus Z110i Apollo: dmi:bvnTechvisionHASHVersion1DE28747:bvr5.6.5:bd03/14/2015:svnDEXP:pnDEXPOEM:pvr1.0:rvnDEXP:rnDEXPOEM:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
2018-06-27 19:32:19 +03:00
#########################################
# DEXP
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*svn*DEXP*:*pn*DEXPOEM:*
Add accel mount matrix for BayTrail-based tablets by DEXP This commit adds accel mount matrix for DEXP Ursus 10XW and Z110i tablets. In current state (*svn*DEXP*:*pn*DEXPOEM*) it will apply to many (if not almost all) BayTrail-based tablets with Windows by DEXP (with same DMI strings) but this expected to cause no (or very little) harm as this devices is mostly very similar with slight difference. However, if correction of this quirk becomes necessary in the future, this DMI strings could be used to distinguish 10XW and Z110i from other tablets by DEXP. DEXP Ursus 10XW: dmi:bvnTechvisionHASHVersion96AC8868:bvr5.6.5:bd12/26/2014:svnDEXP:pnDEXPOEM:pvr1.0:rvnDEXP:rnDEXPOEM:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: DEXP Ursus Z110i Apollo: dmi:bvnTechvisionHASHVersion1DE28747:bvr5.6.5:bd03/14/2015:svnDEXP:pnDEXPOEM:pvr1.0:rvnDEXP:rnDEXPOEM:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
2018-06-27 19:32:19 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: add Digibras F10-30 rotation information (#18215)
2021-01-12 23:48:15 +03:00
#########################################
# Digibras
#########################################
# Digibras F10-30
sensor:modalias:acpi:SMO8500*:dmi:*:svnDigibras:pnF10-30:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
Update 60-sensor.hwdb Added mount matrix for Digma CITI E203 hybrid
2019-01-25 00:03:30 +03:00
#########################################
# DIGMA
#########################################
# Digma CITI E203
sensor:modalias:acpi:BOSC0200*:dmi:*:svnDigma:pnCITIE203ES2010EW:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Endless ELT-NL3 accelerometer support The Endless ELT-NL3 laptop has an accelerometer but its values are not being interpreted correctly, meaning that it's very easy to end up with the screen rotated inappropriately. Add an appropriate mount matrix to correct the values. P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00 E: DRIVER=cmpc_accel_v4 E: ID_VENDOR_FROM_DATABASE=Accton Technology Corporation E: MODALIAS=acpi:ACCE0001: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8 E: ABS=7 E: ACCEL_MOUNT_MATRIX=0, 1, 0; 0, 0, -1; -1, 0, 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8 E: EV=9 E: ID_FOR_SEAT=input-acpi-ACCE0001_00 E: ID_INPUT=1 E: ID_INPUT_ACCELEROMETER=1 E: ID_PATH=acpi-ACCE0001:00 E: ID_PATH_TAG=acpi-ACCE0001_00 E: IIO_SENSOR_PROXY_TYPE=input-accel E: MODALIAS=input:b0000v0000p0000e0000-e0,3,kra0,1,2,mlsfw E: NAME="cmpc_accel_v4" E: PRODUCT=0/0/0/0 E: PROP=0 E: SUBSYSTEM=input E: SYSTEMD_WANTS=iio-sensor-proxy.service E: TAGS=:seat:systemd: P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8/event7 N: input/event7 E: ACCEL_MOUNT_MATRIX=0, 1, 0; 0, 0, -1; -1, 0, 0 E: DEVNAME=/dev/input/event7 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8/event7 E: ID_INPUT=1 E: ID_INPUT_ACCELEROMETER=1 E: ID_PATH=acpi-ACCE0001:00 E: ID_PATH_TAG=acpi-ACCE0001_00 E: IIO_SENSOR_PROXY_TYPE=input-accel E: MAJOR=13 E: MINOR=71 E: SUBSYSTEM=input E: SYSTEMD_WANTS=iio-sensor-proxy.service E: TAGS=:power-switch:systemd:
2017-02-28 20:54:53 +03:00
#########################################
# Endless
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:ACCE0001*:dmi:*svnEndless*:*pnELT-NL3:*
hwdb: Endless ELT-NL3 accelerometer support The Endless ELT-NL3 laptop has an accelerometer but its values are not being interpreted correctly, meaning that it's very easy to end up with the screen rotated inappropriately. Add an appropriate mount matrix to correct the values. P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00 E: DRIVER=cmpc_accel_v4 E: ID_VENDOR_FROM_DATABASE=Accton Technology Corporation E: MODALIAS=acpi:ACCE0001: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8 E: ABS=7 E: ACCEL_MOUNT_MATRIX=0, 1, 0; 0, 0, -1; -1, 0, 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8 E: EV=9 E: ID_FOR_SEAT=input-acpi-ACCE0001_00 E: ID_INPUT=1 E: ID_INPUT_ACCELEROMETER=1 E: ID_PATH=acpi-ACCE0001:00 E: ID_PATH_TAG=acpi-ACCE0001_00 E: IIO_SENSOR_PROXY_TYPE=input-accel E: MODALIAS=input:b0000v0000p0000e0000-e0,3,kra0,1,2,mlsfw E: NAME="cmpc_accel_v4" E: PRODUCT=0/0/0/0 E: PROP=0 E: SUBSYSTEM=input E: SYSTEMD_WANTS=iio-sensor-proxy.service E: TAGS=:seat:systemd: P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8/event7 N: input/event7 E: ACCEL_MOUNT_MATRIX=0, 1, 0; 0, 0, -1; -1, 0, 0 E: DEVNAME=/dev/input/event7 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACCE0001:00/input/input8/event7 E: ID_INPUT=1 E: ID_INPUT_ACCELEROMETER=1 E: ID_PATH=acpi-ACCE0001:00 E: ID_PATH_TAG=acpi-ACCE0001_00 E: IIO_SENSOR_PROXY_TYPE=input-accel E: MAJOR=13 E: MINOR=71 E: SUBSYSTEM=input E: SYSTEMD_WANTS=iio-sensor-proxy.service E: TAGS=:power-switch:systemd:
2017-02-28 20:54:53 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 0, 0, -1; -1, 0, 0
hwdb: add accelerometer mount matrix for Eve V (#8382)
2018-03-08 10:44:11 +03:00
#########################################
hwdb: Add accel orientation quirk for the Estar Beauty HD tablet Add a quirk to fix the accelerometer orientation on the Estar Beauty HD (marked as model-number MID 7316R on the back) tablet.
2020-12-23 23:45:18 +03:00
# Estar
#########################################
sensor:modalias:acpi:SMO8500*:dmi:*:svnEstar:pneSTARBEAUTYHDIntelQuadcore:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
#########################################
hwdb: add accelerometer mount matrix for Eve V (#8382)
2018-03-08 10:44:11 +03:00
# Eve Technology
#########################################
sensor:modalias:acpi:KIOX000A*:dmi:*:svnEVE*:pnEveV:*
ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Geoflex laptop Add a quirk to fix the accelerometer orientation on the Geoflex laptop so that the display is upright rather than upside-down.
2020-04-11 19:01:37 +03:00
#########################################
# Geo Computers
#########################################
# Geoflex
sensor:modalias:acpi:KIOX010A*:dmi:*:svnGEO*:pnGeoFlex*:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accel orientation quirk for the Glavey TM800A550L tablet Add a quirk to fix the accelerometer orientation on the Glavey TM800A550L tablet.
2021-04-28 14:57:10 +03:00
#########################################
# Glavey
#########################################
# Glavey TM800A550L
sensor:modalias:acpi:KXCJ9000*:dmi:*:bvrZY-8-BI-PX4S70VTR400-X423B-005-D:*:rvnAMICorporation:rnAptioCRB:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add Chromebook accelerometer orientation quirk Chromebooks have their accelerometer set to a negative orientation.
2019-09-25 00:45:44 +03:00
#########################################
# Google Chromebooks
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:platform:cros-ec-accel:dmi:*:svnGOOGLE:*
hwdb: Add Chromebook accelerometer orientation quirk Chromebooks have their accelerometer set to a negative orientation.
2019-09-25 00:45:44 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1
Fix Chromebook Caroline board accelerometer not having correct orientation
2020-04-30 20:21:41 +03:00
# caroline board (Samsung Chromebook Pro) reports itself as svnGoogle
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:platform:cros-ec-accel:dmi:*:svnGoogle:pnCaroline*:*
Fix Chromebook Caroline board accelerometer not having correct orientation
2020-04-30 20:21:41 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1
hwbd entry for Dell Inspiron Chromebook 14 2-in-1 sensor (#16109)
2020-06-09 14:31:58 +03:00
# Dell Inspiron Chromebook 14 2-in-1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:platform:cros-ec-accel:dmi:*svnGoogle:pnVayne*:*
hwbd entry for Dell Inspiron Chromebook 14 2-in-1 sensor (#16109)
2020-06-09 14:31:58 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1
hwdb: Add Google Pixel Slate (nocturne) (#16377)
2020-07-07 09:45:31 +03:00
# nocturne board (Google Pixel Slate)
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:platform:cros-ec-accel:dmi:*Google_Nocturne*:*
hwdb: Add Google Pixel Slate (nocturne) (#16377)
2020-07-07 09:45:31 +03:00
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# GP-electronic
#########################################
sensor:modalias:acpi:KIOX000A*:dmi:bvnINSYDECorp.:bvrBYT70A.YNCHENG.WIN.007:*:svnInsyde:pnT701:*
hwdb: Update GP-electronic T701 accel mount settings (#7220) The GP-electronic T701 has its LCD panel mounted upside-down, initially my plan was to fix this by transparently rotating the image in the i915 driver (my "drm/i915: Deal with upside-down mounted LCD" patch), but that approach has been rejected instead the kernel will now export a "panel orientation" property on the drm-connector for the panel and let userspace deal with it. Since the upside-down-ness of the panel is now no longer transparently hidden from userspace, the current accel mount quirk for the T701 needs to be updated to take the upside-down-ness into account.
2017-10-30 16:33:54 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
hwdb: Add accel location quirk for the GPD win The acceleromater in the GPD win is in the base, mark it as such so that iio-sensor-proxy does not try to use it for display rotation. Note as mentioned in the added comment the DMI strings are unfortunately somewhat generic, but the combination of using all DMI strings including the BIOS build data + the sensor modalias should be unique enough.
2019-08-20 23:55:20 +03:00
#########################################
# GPD
#########################################
# GPD win (version 1, with the X5-Z8750 CPU)
# Note we match all dmi fields including the BIOS date checking for all known
# BIOS dates, since the strings are unfortunately very generic.
# Out of a sample set of 15 similar boards only the GPDwin has board_vendor=AMI
# and no other devices have both board_name *and* product_name set to
# "Default string". So combined with the sensor modalias and BIOS date this
# should be unique enough to identify the GPDwin
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/25/2016:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/18/2016:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/23/2016:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/26/2016:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd02/21/2017:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd03/20/2017:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/25/2017:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
hwdb: Add accel location quirk for the GPD win The acceleromater in the GPD win is in the base, mark it as such so that iio-sensor-proxy does not try to use it for display rotation. Note as mentioned in the added comment the DMI strings are unfortunately somewhat generic, but the combination of using all DMI strings including the BIOS build data + the sensor modalias should be unique enough.
2019-08-20 23:55:20 +03:00
ACCEL_LOCATION=base
hwdb: Add accel orientation quirk for the GPD Pocket 3
2022-01-20 11:54:00 +03:00
# GPD Pocket 3
sensor:modalias:acpi:MXC6655*:dmi:*:svnGPD:pnG1621-02:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add sensor rule for Hometech Wi101 This commit was done to add sensor rule for Hometech Wi101. Note that this rule might be too general and need fixes. I couldn't test this on any other device since this one is the only one I have. Co-authored-by: Simeonlps <Simeonlps@users.noreply.github.com> Signed-off-by: Wind/owZ <windowz414@gnuweeb.org>
2021-08-22 03:19:18 +03:00
#########################################
# Hometech
########################################
# Nobody bothered to use Linux on any device of this manufacturer
# so current marks might be too general and need fixes.
# These values are based on Wi101 model.
sensor:modalias:acpi:BMA250E*:dmi:*:svnInsyde*:pni101c:*
ACCEL_MOUNT_MATRIX=0,1,0;-1,0,0;-1,0,0
hwdb: quirks for accelerometers in HP laptops This patch adds quirks for the two laptops I could test on (8540w and 8560w). The accelerometer is configured in the kernel to report values according to the base of the laptop. We want the values according to the screen instead. It is likely (but untested) to match all HP laptops with the lis3lv02d accelerometer on this list: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/platform/x86/hp_accel.c#n207
2017-03-03 23:35:57 +03:00
#########################################
# HP
#########################################
hwdb: Apply the same quirk to all the lis3lv02d devices HP laptops and desktop containing the lis3lv02d device (as supported by the drivers/platform/x86/hp_accel.c driver) are supposed to output their values according to their "standard" orientation, one that corresponds to "can play neverball". For all those devices, we need to convert that "neverball" orientation to a "Windows 8" orientation. We will not accept quirks for HP machines that use the lis3lv02d device, they should go in the hp_accel.c driver instead. Closes: #5160
2018-10-29 16:31:39 +03:00
hwdb: Mark lis3lv02d sensors in HP laptops as being in the base The lis3lv02d sensor used in many HP laptops is (almost) always intented primarily for freefall detection / HDD protection and (almost) always is located in the base of a classic clamshell laptop Before we had the ACCEL_LOCATION udev property the issues this caused with screen-rotation were fixed by applying a mount-matrix which translates base-coordinates to display-coordinates assuming the display is at an angle of exact 90 degrees to the base (swap Y and Z axis). The comment calls this translate "from "can play neverball" to "matches Windows 8 orientation"" but what it really does is translate base accel-axis to display accel-axis. Thus allows rotating the screen if you put the laptop on its side, but no-one normally does that with a 2Kg clamshell laptop. The obviously correct thing to do on classic clamshell laptops (not 2-in-1s) is to disable automatic screen rotation. This commit marks the accelerometer in these laptops as being part of the base, which will make iio-sensor-proxy disable automatic screen rotation. This commit also removes the orientation-matrix since the unmodified coordinates coming from the sensor are oriented correctly for a sensor in the base. Also see the "Bad accelerometer values cause incorrect screen rotation" systemd-devel mail-thread from September 2019.
2019-09-05 15:16:12 +03:00
# Most HP Laptop using the lis3lv02d device have it in the base,
# mark these sensors as such.
hwdb: Apply the same quirk to all the lis3lv02d devices HP laptops and desktop containing the lis3lv02d device (as supported by the drivers/platform/x86/hp_accel.c driver) are supposed to output their values according to their "standard" orientation, one that corresponds to "can play neverball". For all those devices, we need to convert that "neverball" orientation to a "Windows 8" orientation. We will not accept quirks for HP machines that use the lis3lv02d device, they should go in the hp_accel.c driver instead. Closes: #5160
2018-10-29 16:31:39 +03:00
sensor:modalias:platform:lis3lv02d:dmi:*svn*Hewlett-Packard*:*
hwdb: Also mark lis3lv02d sensors in "HP" laptops as being in the base We matched "*Hewlett-Packard*" laptops but not "*HP*" laptops, which caused a regression for the HP Elite Book 850 G3. Fixes: 4247938ee13e23eae1afcecbe646de5283b7afc2 Closes: #13543
2019-09-12 20:02:35 +03:00
sensor:modalias:platform:lis3lv02d:dmi:*svn*HP*:*
hwdb: Add HP Elitebook 850 G3 laptop accelerometer location quirk
2019-09-02 18:04:07 +03:00
ACCEL_LOCATION=base
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*:svnHewlett-Packard:pnHPStream7Tablet:*
hwdb: Add ACCEL_MOUNT_MATRIX for HP Stream 8 (#7279)
2017-11-09 17:38:34 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*:svnHewlett-Packard:pnHPStream8Tablet:*
hwdb: Add HP laptop accelerometer location quirk Add another HP laptop to the list of HP laptops with their accelerometer in the base. While at it also fixup the indentation of a neighboring quirk.
2019-08-28 10:28:30 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
fix typo
2022-05-02 19:16:32 +03:00
# HP Pavilion X2 10-n000nd
hwdb: Add accelerometer orientation quirk for the HP Pavilion x2 - 10-n000nd Add accelerometer orientation quirk for the HP Pavilion x2 - 10-n000nd 2-in-1.
2018-05-20 18:33:30 +03:00
sensor:modalias:i2c:bmc150_accel:dmi:*:svnHewlett-Packard:pnHPPavilionx2Detachable:*:rn815D:*
Fix orientation detection for HP Pavilion X2 10-k010nr
2022-05-02 00:49:18 +03:00
# HP Pavilion X2 10-k010nr
sensor:modalias:i2c:bmc150_accel:dmi:*:svnHewlett-Packard:pnHPPavilionx2DetachablePC10:*
hwdb: add sensor location for HP ProBook4535s https://bugzilla.redhat.com/show_bug.cgi?id=1717712
2019-08-22 09:55:09 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the HP Pavilion x2 - 10-n000nd Add accelerometer orientation quirk for the HP Pavilion x2 - 10-n000nd 2-in-1.
2018-05-20 18:33:30 +03:00
hwdb: Fix rotation for HP Pro Tablet 408 G1
2022-04-22 14:22:34 +03:00
# HP Pro Tablet 408 G1
sensor:modalias:i2c:bmc150_accel:dmi:*:svnHewlett-Packard:pnHPProTablet408:*:rn8048:*
ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# I.T.Works
#########################################
# The I.T.Works TW891 2-in-1's DMI has the product-name field set, but not
# the sys-vendor field. This makes the DMI data a bit generic, so we match
# the whole dmi modalias, except for the BIOS version/date
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:*:svnTobefilledbyO.E.M.:pnTW891:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTW891:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:*
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation entry for the I.T.Works TW701 tablet Add accelerometer orientation entry for the I.T.Works TW701 7" windows tablet, note this is the same hardware/PCB as the Trekstor ST70416-6 for which we already have the same quirk.
2018-02-18 23:42:43 +03:00
# I.T.Works TW701 7" windows tablet, same hw as Trekstor ST70416-6
sensor:modalias:acpi:BMA250*:dmi:*:bvritWORKS.G.WI71C.JGBMRB*:*:svnInsyde:pni71c:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
Add accel mount matrix for Irbis TW90
2019-07-07 18:17:56 +03:00
#########################################
hwdb: ACCEL_MOUNT_MATRIX for Irbis TW118 (#16786) This was required to get orientation sensor work properly in my tablet.
2020-08-20 11:23:35 +03:00
# Irbis
Add accel mount matrix for Irbis TW90
2019-07-07 18:17:56 +03:00
#########################################
hwdb: ACCEL_MOUNT_MATRIX for Irbis TW118 (#16786) This was required to get orientation sensor work properly in my tablet.
2020-08-20 11:23:35 +03:00
#TW90
Add accel mount matrix for Irbis TW90
2019-07-07 18:17:56 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnIRBIS:pnTW90:*
ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, 1
Add accel mount matrix for Irbis NB111 transformer
2020-09-25 21:03:50 +03:00
# NB111
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:KIOX010A*:dmi:*svn*IRBIS*:*pn*NB111:*
Add accel mount matrix for Irbis NB111 transformer
2020-09-25 21:03:50 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: ACCEL_MOUNT_MATRIX for Irbis TW118 (#16786) This was required to get orientation sensor work properly in my tablet.
2020-08-20 11:23:35 +03:00
#TW118
sensor:modalias:acpi:BOSC0200*:dmi:*:svnIRBIS:pnTW118:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: 60-sensors: Fix alphabetic sorting by vendor name The Cytrix entry was added at the end instead of sorted alphabetically by vendor name.
2018-03-09 16:50:04 +03:00
#########################################
# iOTA 360
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*svn*iOTA*:*pn*IOTA2210:*
hwdb: 60-sensors: Fix alphabetic sorting by vendor name The Cytrix entry was added at the end instead of sorted alphabetically by vendor name.
2018-03-09 16:50:04 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# Jumper
#########################################
# EZpad mini 3
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:bvnINSYDECorp.:bvrjumperx.T87.KFBNEE:*
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Added sensor geometry for Jumper EZpad 6 Pro (#7955)
2018-01-23 03:51:11 +03:00
# EZpad 6 Pro
sensor:modalias:acpi:BOSC0200*:dmi:*:svnJumper:pnEZpad:*:rvr.A006:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accel orientation quirk for the Jumper Ezpad 7 tablet Add a quirk to fix the accelerometer orientation on the Jumper Ezpad 7 tablet.
2021-01-24 00:36:58 +03:00
# EZpad 7
sensor:modalias:acpi:KIOX0009*:dmi:*:bvrJumper12x.WJ2012.bsBKRCP*:svnJumper:pnEZpad:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: add accel sensor entry for Jumper EZpad Go This commit fix the accelerometer orientation on the Jumper EZpad Go tablet. The tablet does not have its product name filled in dmi table, make the match string a bit generic. Here we assume that the use of a KIOX000A + bios-vendor + chassis-type combo is unique enough to match the currently available product in Jumper's x86 tablet series. For future reference, as in 2019, the tablet has a dmialias of: dmi:bvnAmericanMegatrendsInc.:bvrZB-BI-11.6-SF133AR200-059-J \ :bd05/21/2019:svnjumper:pnEZpad:pvrTobefilledbyO.E.M.:rvnTob \ efilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:c \ vnTobefilledbyO.E.M.:ct31:cvrTobefilledbyO.E.M.:
2019-11-24 02:10:56 +03:00
# EZpad Go
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:*:svnjumper:pnEZpad:*:ct31:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Kazam Vision tablet (#8845) Add accelerometer orientation quirk for the 8" Kazam Vision "gaming" tablet.
2018-04-28 11:43:06 +03:00
#########################################
# Kazam
#########################################
sensor:modalias:acpi:KIOX000A*:dmi:bvnINSYDECorp.:bvrVISION.I22K*:svnKAZAM:pnVISION:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for the KD Kurio Smart C15200 tablet Add a quirk to fix the accelerometer orientation on the KD Kurio Smart C15200 tablet.
2021-05-12 20:05:18 +03:00
#########################################
# KD / Kurio
#########################################
sensor:modalias:acpi:SMO8500*:dmi:*:svnKDInteractive:pnKurioSmart:*:rnKDM960BCP:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# Lamina
#########################################
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*svnLamina*:*pnT701BR.SE:*
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*svnLAMINA:pnT-1016BNORD:*
hwdb: Add ACCEL_MOUNT_MATRIX for the Lamina T-1016B.NORD 2-in-1 tablet (#6430)
2017-09-11 10:56:57 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: add Lenovo Yoga 510-14IKB sensor mount quirk (#6799)
2017-09-12 19:39:25 +03:00
#########################################
# Lenovo
#########################################
sensor:modalias:acpi:NCPE0388*:dmi:*:rnLenovoYOGA510-14IKB:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*ThinkPadYoga11e3rdGen:*
hwdb: Fix accel orientation quirk Z-axis for Lenovo ThinkPad Yoga 11e 3th gen The Lenovo ThinkPad Yoga 11e 360 degree hinges style 2-in-1s use 2 accelerometers, 1 in the display and 1 in the base. Kernel work is under way to also export the second accelerometer in the base as an iio-device; and userspace work is underway to use both accelerometers on 360 degree hinges style 2-in-1s (with 2 accels) to figure out the angle between the 2 halves. So far most orientation-matrix quirks have not cared much about the Z-axis being correct, but in these 2 accelerometer setups getting the Z-axis correct is important too.
2020-11-14 19:10:51 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, -1
hwdb: Add ACCEL_MOUNT_MATRIX for ThinkPad Yoga 11e (#7174) Accelerometer readings from the screen accelerometer on the Yoga 11e need to be rotated 90 degrees around the Z axis.
2017-10-25 14:23:51 +03:00
hwdb: Add accel orientation quirk for Lenovo ThinkPad Yoga 11e 4th gen Add a quirk to fix the accelerometer orientation on the Lenovo ThinkPad Yoga 11e 4th gen 360 degree hinges 2-in-1.
2020-11-14 19:09:04 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnLENOVO:*pvrThinkPadYoga11e4thGen:*
ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, -1
hwbd: 60-sensor.hwdb: Add Lenovo ThinkPad Yoga 11e 5th Gen (Type: 20LN, Gemini Lake)
2021-09-25 13:37:29 +03:00
# Lenovo ThinkPad Yoga 11e 5th Gen (20LN-S14900)
sensor:modalias:acpi:BOSC0200*:dmi:*pvrThinkPadYoga11e5thGen:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, -1
hwdb: Add Lenovo IdeaPad Miix 320 sensor mount quirk (#7707)
2018-01-18 23:09:58 +03:00
# Miix3-1030
hwdb: Add accelerometer orientation entry for Lenovo MIIX3-1030 tablet (#7713) Full dmi/id/modalias: dmi:bvnLENOVO:bvrB4CN29WW:bd12/04/2015:svnLENOVO:pn80HV:pvrLenovoMIIX3-1030:rvnLENOVO:rnMartini:rvrSDK0G98662WIN:cvnLENOVO:ct11:cvrLenovoMIIX3-1030: Tested on Lenovo MIIX3 with Debian 9
2017-12-21 16:17:33 +03:00
sensor:modalias:acpi:BMA250E*:dmi:bvnLENOVO:*:pvrLenovoMIIX3-1030:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel mount matrix for Lenovo Miix 3-830
2018-07-25 17:53:10 +03:00
# Miix3-830
sensor:modalias:acpi:SMO8500*:dmi:bvnLENOVO:*:pvrLenovoMIIX3-830:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: sensor: D330-IGM use pvr instead cvr We use pvr match for efifb pitch and drm orientation quirk and in touchpad toggle keymap. Also seems most consistent with the devices here. While at it, correct a typo, 81H3 and 81MD are product names not numbers, my bad. Signed-off-by: David Santamaría Rogado <howl.nsp@gmail.com>
2021-05-11 01:31:28 +03:00
# IdeaPad D330-10IGM (both 81H3 and 81MD product names)
sensor:modalias:acpi:BOSC0200*:dmi:*:svnLENOVO:*:pvrLenovoideapadD330-10IGM:*
hwdb: Add Lenovo IdeaPad D330 accel mount matrix I have the fhd screen with pentium without lte model. Don't know if other models could differ in the accelerometer.
2018-12-26 01:09:52 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; -1, 0, 0; 0, 0, 1
Add Lenovo IdeaPad Miix 300 ACCEL_MOUNT_MATRIX
2020-03-21 15:08:06 +03:00
# IdeaPad Miix 300
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8500*:dmi:bvnLENOVO:*:pvrMIIX300-*:*
Add Lenovo IdeaPad Miix 300 ACCEL_MOUNT_MATRIX
2020-03-21 15:08:06 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: IdeaPad Miix 310 with another bios version (#10661) another bios version for same model with portrait screen.
2018-11-07 06:59:24 +03:00
# IdeaPad Miix 310 note this only is for BIOS version (bvr) 1HCN4?WW and 1HCN2?WW, which has
hwdb: Add accelerometer orientation quirk for the Lenovo Ideapad Miix 310 Add an accelerometer orientation quirk for the Lenovo Ideapad Miix 310. Note this quirk is limited to the production batches which ship with a portrait panel, rather then with a landscape panel (recognized by the different BIOS version these 2 variants use).
2018-03-30 21:00:27 +03:00
# a portrait LCD panel, versions with bvr 1HCN3?WW have a landscape panel
sensor:modalias:acpi:KIOX000A*:dmi:bvnLENOVO:bvr1HCN4?WW:*:svnLENOVO:pn80SG:*
hwdb: IdeaPad Miix 310 with another bios version (#10661) another bios version for same model with portrait screen.
2018-11-07 06:59:24 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:bvnLENOVO:bvr1HCN2?WW:*:svnLENOVO:pn80SG:*
hwdb: Add accelerometer orientation quirk for the Lenovo Ideapad Miix 310 Add an accelerometer orientation quirk for the Lenovo Ideapad Miix 310. Note this quirk is limited to the production batches which ship with a portrait panel, rather then with a landscape panel (recognized by the different BIOS version these 2 variants use).
2018-03-30 21:00:27 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add a 2nd accelerometer orientation quirk for the Lenovo Ideapad Miix 320 (#8734) Different batches of the Lenovo Ideapad Miix 320 use a different sensor it seems. Add a quirk for the model which uses the SMO8840 (ST) sensor.
2018-04-17 17:51:33 +03:00
# IdeaPad Miix 320, different batches use a different sensor
hwdb: Add Lenovo IdeaPad Miix 320 sensor mount quirk (#7707)
2018-01-18 23:09:58 +03:00
sensor:modalias:acpi:*BOSC0200*:dmi:*:svnLENOVO*:pn80XF:*
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:SMO8840*:dmi:*:svnLENOVO:pn80XF:pvrLenovoMIIX320:*
hwdb: Add Lenovo IdeaPad Miix 320 sensor mount quirk (#7707)
2018-01-18 23:09:58 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
add device hwdb for IdeaPad Miix510-12ISK add ACCEL_MOUNT_MATRIX for IdeaPad Miix510-12ISK multiple match expressions for Miix510 series extend comments for miix510 series Signed-off-by: Bruce Zhang <zttt183525594@gmail.com> add device hwdb for IdeaPad Miix510-12ISK Signed-off-by: Bruce Zhang <zttt183525594@gmail.com>
2018-12-10 17:33:10 +03:00
# IdeaPad Miix 510, multiple expressions match different internal names
# pn80U1 matches IdeaPad Miix510-12ISK
Fix orientation sensor position for Lenovo Miix 510 Looks like the Miix 510 has the same sensor and placement as the Miix 320 (put it separate for clarity) Verified on own hardware
2018-06-18 01:24:11 +03:00
sensor:modalias:acpi:*BOSC0200*:dmi:*:svnLENOVO*:pn80XE:*
add device hwdb for IdeaPad Miix510-12ISK add ACCEL_MOUNT_MATRIX for IdeaPad Miix510-12ISK multiple match expressions for Miix510 series extend comments for miix510 series Signed-off-by: Bruce Zhang <zttt183525594@gmail.com> add device hwdb for IdeaPad Miix510-12ISK Signed-off-by: Bruce Zhang <zttt183525594@gmail.com>
2018-12-10 17:33:10 +03:00
sensor:modalias:acpi:*BOSC0200*:dmi:*:svnLENOVO*:pn80U1:*
Fix orientation sensor position for Lenovo Miix 510 Looks like the Miix 510 has the same sensor and placement as the Miix 320 (put it separate for clarity) Verified on own hardware
2018-06-18 01:24:11 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for the Lenovo Yoga 300-11IBR 2-in-1 Add a quirk for the accelerometer orientation and location for the 2 accelerometers inside the Lenovo Yoga 300-11IBR 2-in-1.
2021-05-22 17:22:36 +03:00
# Yoga 300-11IBR, display sensor
sensor:modalias:acpi:DUAL250E*:dmi:*:svnLENOVO:*:pvrLenovoYoga300-11IBR:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
ACCEL_LOCATION=display
# Yoga 300-11IBR, base sensor
sensor:modalias:i2c:bmc150_accel:dmi:*:svnLENOVO:*:pvrLenovoYoga300-11IBR:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, 1, 0; 0, 0, -1
ACCEL_LOCATION=base
hwdb: Add accelerometer orientation quirk for the Linx 1010B tablet (#8784)
2018-04-23 11:49:54 +03:00
#########################################
# LINX
#########################################
# Linx 1010B
sensor:modalias:acpi:BOSC0200*:dmi:*:svnLINX*:pnLINX1010B:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, -1
hwdb: add Linx Vision 8 rotation information (#18228)
2021-01-13 23:52:11 +03:00
# Linx 12X64, 12V64 and Vision 8
hwdb: Add support for Linx 12V64 (#12665) This fixes the accelerometer for the Linx 12V64. Note that even though the configuration for both models is the same, the 12V64 and 12X64 are different models.
2019-05-25 23:42:00 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnLINX*:pnLINX12*64:*
hwdb: add Linx Vision 8 rotation information (#18228)
2021-01-13 23:52:11 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnLINX:pnVISION004:*
Add accelerometer mount matrix for Linx 12X64
2018-07-18 01:00:16 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
Add correct rotation support for Mediacom Winpad 7.0 W700 this patch enables correct bios detection and matrix for the aforementioned tiny tablet (touchscreen support commit pending now in kernel) thnx
2021-05-03 05:02:08 +03:00
#########################################
# Mediacom
#########################################
# Mediacom Winpad 7.0 W700
sensor:modalias:acpi:BMA250*:dmi:*svnMEDIACOM*:pnWinPad7W10-WPW700:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Medion Akoya E2212T Add accelerometer orientation quirk for the Medion Akoya E2212T 2-in-1.
2019-02-21 14:50:10 +03:00
#########################################
# Medion
#########################################
hwdb: add Medion Akoya E2228T MD61900 (#18317) Add a model-specific entry for Medion Akoya E2228T MD61900 accelerometer to 60-sensor.hwdb so the orientation is detected correctly.
2021-01-21 11:21:50 +03:00
# Medion Akoya E2228T MD61900
sensor:modalias:acpi:KIOX020A*:dmi:*:svnMEDION:pnE2228TMD61900:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1
ACCEL_LOCATION=base
hwdb: Add Medion Akoya E1239T MD60568 to 60-sensor.hwdb Unlike newer Medion Akoya E* models for which we have a generic wildcard match, this model uses a somewhat older KIOX0009 accelerometer. Not only does our generic catch all not match, we also need a different matrix for this model, so add a model-specific entry for it.
2020-02-11 14:27:10 +03:00
# Medion Akoya E1239T MD60568
sensor:modalias:acpi:KIOX0009*:dmi:*:svnMEDION:pnE1239TMD60568:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
# Medion Akoya E2212T MD99720
hwdb: Add accelerometer orientation quirk for the Medion Akoya E2212T Add accelerometer orientation quirk for the Medion Akoya E2212T 2-in-1.
2019-02-21 14:50:10 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*:svnMEDION:pnAkoyaE2212TMD99720:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add Medion Akoya E2215T MD60198 sensor orientation quirk Add sensor orientation quirk for the Medion Akoya E2215T so that desktop-environments show their graphics the right way up.
2019-10-19 14:29:37 +03:00
# Medion Akoya E2215T MD60198
hwdb: Fix accel orientation quirk for Medion Akoya E2215T MD60198 Commit 3d864658ea01 ("hwdb: assume all Medion Akoya E-models have the same matrix"), unified the entries for most Medion Akoya E* modes, including the entry for the Medion Akoya E2215T MD60198. But the accelerometer on the E2215T has an ACPI-id of KIOX000A, rather then KIOX010A as the other models have, so that commit broke the ACCEL_MOUNT_MATRIX for the E2215T. Add a separate match for the E2215T so that it gets the correct ACCEL_MOUNT_MATRIX again.
2020-05-08 00:16:21 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*svnMEDION:pnE2215TMD60198:*
hwdb: Add Medion Akoya E3216 MD60900 (#12323) Fixes: #12312
2019-04-16 11:23:28 +03:00
# Medion Akoya E3216 MD60900
hwdb: acceleration mount matrix for a Medion Akoya E3221 (#13310)
2019-08-14 19:15:50 +03:00
# Medion Akoya E3221 MD61237
hwdb: add Medion Akoya E2292 (#13498) Fixes #13480.
2019-09-16 22:10:15 +03:00
# Medion Akoya E2292 MD63390
Add accel mount matrix for Medion Akoya E2293 Add ACCEL_MOUNT_MATRIX for Medion Akoya E2293 MD61130
2019-08-24 01:48:41 +03:00
# Medion Akoya E2293 MD61130
hwdb: assume all Medion Akoya E-models have the same matrix Since up to now all known Akoya E* models have the same Matrix, we assume all other Akoya E* models work the same.
2019-12-10 01:28:09 +03:00
# Medion Akoya E2293 MD61144
# Medion Akoya E3222 MD62450
# and presumably all other Akoya Exxxx
sensor:modalias:acpi:KIOX010A*:dmi:*:svnMEDION:pnE*:*
hwdb: make comment more precise Based on https://github.com/systemd/systemd/pull/14296#issuecomment-567159538.
2019-12-19 12:15:08 +03:00
# Medion Akoya E3222 MD62450
hwdb: assume all Medion Akoya E-models have the same matrix Since up to now all known Akoya E* models have the same Matrix, we assume all other Akoya E* models work the same.
2019-12-10 01:28:09 +03:00
sensor:modalias:acpi:KIOX010A*:dmi:*:svnMEDION:pnMEDION*:*
Add accel mount matrix for Medion Akoya E2293 Add ACCEL_MOUNT_MATRIX for Medion Akoya E2293 MD61130
2019-08-24 01:48:41 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add base accelerometer orientation quirk for base sensor of Medion Akoya E* series The KIOX010A and KIOX02A ACPI hw-ids (HIDs) are used in 360 degree hinges style 2-in-1s which have 2 accelerometers, 1 in the display (as usual) and a second accelerometer in the base. So far 60-sensor.hwdb has only defined a mount-matrix for the sensor with the KIOX010A HID, which is the sensor in the display half of the device. The reason for this is that sofar userspace has only cared actually used the sensor in the display (for automatic display rotation. Work is underway to make userspace use both sensors: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/216 Recently an entry was added for the Medion Akoya's E2221T base-sensor, but that was added to mark it with ACCEL_LOCATION=base and the entry simply used the identity-matrix for ACCEL_MOUNT_MATRIX since nothing is using the mount-matrix info for the second accelerometer. I believe that this entry was added because on some devices the second accelerometer gets enumerated first and then iio-sensor-proxy will wrongly use the second sensor for display-rotation, unless it is marked with ACCEL_LOCATION=base. Instead of adding info for the second accelerometer on a per device basis use the same generic dmi matches as used for the first (KIOX010A) sensor, replacing the special case added for the E2221T and also update the ACCEL_MOUNT_MATRIX with the actual mount-matrix for the KIOX020A sensor in the base of these devices. This was tested on a Medion Akoya E2228T.
2020-11-18 20:48:43 +03:00
ACCEL_LOCATION=display
Add accel mount matrix for Medion Akoya E2293 Add ACCEL_MOUNT_MATRIX for Medion Akoya E2293 MD61130
2019-08-24 01:48:41 +03:00
hwdb: Add base accelerometer orientation quirk for base sensor of Medion Akoya E* series The KIOX010A and KIOX02A ACPI hw-ids (HIDs) are used in 360 degree hinges style 2-in-1s which have 2 accelerometers, 1 in the display (as usual) and a second accelerometer in the base. So far 60-sensor.hwdb has only defined a mount-matrix for the sensor with the KIOX010A HID, which is the sensor in the display half of the device. The reason for this is that sofar userspace has only cared actually used the sensor in the display (for automatic display rotation. Work is underway to make userspace use both sensors: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/216 Recently an entry was added for the Medion Akoya's E2221T base-sensor, but that was added to mark it with ACCEL_LOCATION=base and the entry simply used the identity-matrix for ACCEL_MOUNT_MATRIX since nothing is using the mount-matrix info for the second accelerometer. I believe that this entry was added because on some devices the second accelerometer gets enumerated first and then iio-sensor-proxy will wrongly use the second sensor for display-rotation, unless it is marked with ACCEL_LOCATION=base. Instead of adding info for the second accelerometer on a per device basis use the same generic dmi matches as used for the first (KIOX010A) sensor, replacing the special case added for the E2221T and also update the ACCEL_MOUNT_MATRIX with the actual mount-matrix for the KIOX020A sensor in the base of these devices. This was tested on a Medion Akoya E2228T.
2020-11-18 20:48:43 +03:00
# Same as above, but for base sensor
sensor:modalias:acpi:KIOX020A*:dmi:*:svnMEDION:pnE*:*
sensor:modalias:acpi:KIOX020A*:dmi:*:svnMEDION:pnMEDION*:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, -1
hwdb: add Medion Akoya E2221T MD60691 (#17147)
2020-09-24 10:33:43 +03:00
ACCEL_LOCATION=base
hwdb: Add accel orientation quirk for MPMAN MPWIN895CL tablet Add a quirk to fix the accelerometer orientation on the MPMAN MPWIN895CL tablet.
2020-04-05 17:01:32 +03:00
#########################################
# MPMAN
#########################################
hwdb: Add accel orientation quirk for MPMAN Converter 9 2-in-1 Add a quirk to fix the accelerometer orientation on the MPMAN Converter 9 2-in-1.
2020-08-04 15:54:57 +03:00
# MPMAN Converter 9, same hw as the I.T.Works TW891 2-in-1
sensor:modalias:acpi:SMO8500*:dmi:*:svnMPMAN:pnConverter9:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
# MPMAN MPWIN895C
hwdb: Add accel orientation quirk for MPMAN MPWIN895CL tablet Add a quirk to fix the accelerometer orientation on the MPMAN MPWIN895CL tablet.
2020-04-05 17:01:32 +03:00
sensor:modalias:acpi:BMA250E*:dmi:*:svnMPMAN:pnMPWIN8900CL:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the MSI S100 2-in-1 Add an accelerometer orientation quirk for the MSI S100 2-in-1.
2018-03-30 18:10:21 +03:00
#########################################
# MSI
#########################################
sensor:modalias:acpi:SMO8500*:dmi:*:svnMicro-StarInternationalCo.,Ltd.:pnS100:*
ACCEL_MOUNT_MATRIX=0, -1, 0; 1, 0, 0; 0, 0, 1
Add accelerometer orientation quirk for the MYRIA MY8307 2-in-1.
2019-03-14 16:59:37 +03:00
#########################################
# MYRIA
#########################################
# MY8307
sensor:modalias:acpi:BOSC0200*:dmi:*:svnCompletElectroServ:pnMY8307:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
Update 60-sensor.hwdb hwdb: Add accelerometer orientation quirk for the MYRIA MY8312
2020-12-23 21:34:37 +03:00
# MY8312
sensor:modalias:acpi:KIOX010A*:dmi:*:svnCompletElectroServSA:pnMY8312:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Nuvision/TMAX TM800W560L Add accelerometer orientation quirk for the Nuvision/TMAX TM800W560L 8" Windows signature edition tablet.
2018-06-02 13:09:43 +03:00
#########################################
# Nuvision (TMax)
#########################################
hwdb: Fix rotation for Nuvision Solo 10 Draw (#11686) Model number TM101W610L This fixes issue #11683 Also add proper label for other Nuvision tablet.
2019-02-12 17:21:45 +03:00
# Nuvision/TMAX 8" Windows signature edition. TM800W560L
hwdb: Add accelerometer orientation quirk for the Nuvision/TMAX TM800W560L Add accelerometer orientation quirk for the Nuvision/TMAX TM800W560L 8" Windows signature edition tablet.
2018-06-02 13:09:43 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTMAX:pnTM800W560L:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Fix rotation for Nuvision Solo 10 Draw (#11686) Model number TM101W610L This fixes issue #11683 Also add proper label for other Nuvision tablet.
2019-02-12 17:21:45 +03:00
# Nuvision Solo 10 Draw. TM101W610L
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTMAX:pnTM101W610L:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Fix rotation for Nuvision Encite Split 11 Model number NES11-C432SSA
2020-02-13 00:43:06 +03:00
# Nuvision Encite Split 11. NES11-C432SSA
sensor:modalias:acpi:BOSC0200*:dmi:*:svnNuvision:pnNES11:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Onda V891w tablet Add accelerometer orientation quirk for the Onda V891w tablet, this does a partial match on the BIOS version because the other strings are somewhat generic. The BIOS match is done for both the W89* and D89* BIOS versions which are for the Windows only and Dual boot versions respectively.
2018-06-02 16:47:27 +03:00
#########################################
hwdb: Add accel orientation quirk for Odys Fusion Win 12 2in1
2020-06-13 17:48:53 +03:00
# Odys
#########################################
sensor:modalias:acpi:BOSC0200*:dmi:bvnINSYDECorp.:bvrODYS.FUSIONWIN12:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
#########################################
hwdb: Add accelerometer orientation quirk for the Onda V891w tablet Add accelerometer orientation quirk for the Onda V891w tablet, this does a partial match on the BIOS version because the other strings are somewhat generic. The BIOS match is done for both the W89* and D89* BIOS versions which are for the Windows only and Dual boot versions respectively.
2018-06-02 16:47:27 +03:00
# Onda
#########################################
hwdb: Add accelerometer orientation quirk for the Onda V80 Plus tablet Add accelerometer orientation quirk for the Onda V80 Plus tablet.
2018-10-12 14:10:35 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnONDA:pnV80PLUS:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Onda V891w tablet Add accelerometer orientation quirk for the Onda V891w tablet, this does a partial match on the BIOS version because the other strings are somewhat generic. The BIOS match is done for both the W89* and D89* BIOS versions which are for the Windows only and Dual boot versions respectively.
2018-06-02 16:47:27 +03:00
sensor:modalias:acpi:BMA250E*:dmi:bvnINSYDECorp.:bvrONDA.D89*:svnInsyde:pnONDATablet:*
hwdb: Add Onda V820w accelerometer transformation matrix Added accelerometer transformation matrix for the Onda V820w Tablet
2018-11-14 06:03:21 +03:00
sensor:modalias:acpi:BMA250E*:dmi:bvnINSYDECorp.:bvrONDA.D86*:svnONDA:pnV820wDualOS:*
hwdb: Add accelerometer orientation quirk for the Onda V891w tablet Add accelerometer orientation quirk for the Onda V891w tablet, this does a partial match on the BIOS version because the other strings are somewhat generic. The BIOS match is done for both the W89* and D89* BIOS versions which are for the Windows only and Dual boot versions respectively.
2018-06-02 16:47:27 +03:00
sensor:modalias:acpi:BMA250E*:dmi:bvnINSYDECorp.:bvrONDA.W89*:svnInsyde:pnONDATablet:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Onda v975w tablet Add accelerometer orientation quirk for the Onda v975w tablet.
2018-09-07 14:14:52 +03:00
# Onda v975w, generic DMI strings, match entire dmi modalias inc. bios-date
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:SMO8500*:dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd07/25/2014:*svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:*
hwdb: Add accelerometer orientation quirk for the Onda v975w tablet Add accelerometer orientation quirk for the Onda v975w tablet.
2018-09-07 14:14:52 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
Added sensor configuration for One-netbook OneMix 3 Pro
2020-08-25 06:08:08 +03:00
#########################################
# One-netbook
#########################################
hwdb: add accel matrix for One-netbook OneMix 2s
2021-06-29 23:51:58 +03:00
# One-netbook OneMix 2s
# OneMix 2s has no product name filled, matching entire dmi-alias
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd10/26/2018:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
hwdb: add accel matrix for One-netbook OneMix 2s
2021-06-29 23:51:58 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
Added sensor configuration for One-netbook OneMix 3 Pro
2020-08-25 06:08:08 +03:00
# One-netbook OneMix 3 Pro
sensor:modalias:acpi:BOSC0200*:dmi:*svnONE-NETBOOKTECHNOLOGYCO*:pnOne-Mix3Pro:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: add accel matrix for One-netbook OneMix 3s (#19549)
2021-05-10 23:20:58 +03:00
# One-netbook OneMix 3s
# OneMix 3s has no product name filled, matching entire dmi-alias
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/17/2019:*svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:*
hwdb: add accel matrix for One-netbook OneMix 3s (#19549)
2021-05-10 23:20:58 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# Peaq
#########################################
sensor:modalias:acpi:SMO8500*:dmi:*:svnPEAQ:pnPEAQPMMC1010MD99187:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
#########################################
# Pipo
#########################################
sensor:modalias:acpi:KIOX000A*:dmi:*:svnPIPO:pnW2S:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwbd: 60-sensor.hwdb: Add Pipo W2Pro Add accelerometer matrix for Pipo W2Pro tablet. Y-axis was backwards (normal <--> bottom-up).
2022-02-04 20:47:08 +03:00
# Pipo W2Pro
sensor:modalias:acpi:KIOX0008*:dmi:*svnPIPO:pnW2pro:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Pipo W4 tablet Add an accelerometer orientation quirk for the Pipo W4 tablet.
2018-03-31 00:39:29 +03:00
# Pipo W4
sensor:modalias:acpi:SMO8500*:dmi:*:bvrV8L_WIN32_CHIPHD_*_DX:*:rvnAMICorporation:rnAptioCRB:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# Ployer
#########################################
sensor:modalias:acpi:BMA250E*:dmi:*:svnShenzhenPLOYER*:pnMOMO7W:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
#########################################
# Point of View
#########################################
# The Point of View TAB-P800W does not have its product name filled, so we
# match the entire dmi-alias, assuming that the use of a BMA250E +
# bios-version + bios-date combo is unique
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:BMA250E*:dmi:bvnAmericanMegatrendsInc.:bvr3BAIR1013:bd08/22/2014:*svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:*
sensor:modalias:acpi:BMA250E*:dmi:bvnAmericanMegatrendsInc.:bvr3BAIR1014:bd10/24/2014:*svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:*
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the PoV P1005W-232 tablet Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2018-12-07 22:50:30 +03:00
# Point of View TAB-P1005W-232 (v2.0)
sensor:modalias:acpi:KIOX000A*:dmi:*:rvnPOV:rnI102A:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the PoV TAB-P1006W-232-3G Add accelerometer orientation quirk for the Point of View TAB-P1006W-232-3G tablet.
2018-12-20 18:08:46 +03:00
# Point of View TAB-P1006W-232-3G (v1.0)
sensor:modalias:i2c:bmc150_accel:dmi:bvnINSYDECorp.:*:svnInsyde:pnBayTrail:*:rvn105B:rn0E57:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Predia Basic tablet Add a quirk to fix the accelerometer orientation on the Predia Basic tablet.
2020-10-29 13:29:41 +03:00
#########################################
# Predia
#########################################
# Predia Basic tablet, most DMI strings are generic, match on BIOS version
sensor:modalias:acpi:BOSC0200*:dmi:bvnINSYDECorp.:bvrMx.WT107.KUBNGEA*svnInsyde:pnCherryTrail:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Prowise PT301 tablet
2018-12-07 20:35:51 +03:00
#########################################
# Prowise
#########################################
sensor:modalias:acpi:SMO8500*:dmi:*:svnProwise:pnPT301:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Reeder A8iW Tablet Add a quirk to fix the accelerometer orientation on the Reeder A8iW tablet.
2021-02-13 19:13:20 +03:00
#########################################
# Reeder
#########################################
hwdb: whitespace fixes
2021-02-19 17:19:56 +03:00
# A8iW-Rev.A
hwdb: Add accel orientation quirk for Reeder A8iW Tablet Add a quirk to fix the accelerometer orientation on the Reeder A8iW tablet.
2021-02-13 19:13:20 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*:rvnReeder:rnA8iW-Rev.A:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
Add Schneider SCT101CTM to sensor hwdb
2019-10-21 02:48:34 +03:00
#########################################
# Schneider
#########################################
# SCT101CTM
hwdb: add trailing ":*" everywhere No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 10:23:30 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:bvnAmericanMegatrendsInc.:bvrSCH12i.WJ210Z.KtBJRCA03:*
Add Schneider SCT101CTM to sensor hwdb
2019-10-21 02:48:34 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add accelerometer orientation entry for Teclast X80 Pro tablet Add an accelerometer orientation entry for the Teclast X80 Pro tablet.
2017-12-20 13:06:13 +03:00
#########################################
# Teclast
#########################################
hwdb: add accelerometer orientation quirk for the Teclast F5 (#11005)
2018-12-17 11:33:35 +03:00
# Teclast F5
sensor:modalias:acpi:KIOX010A*:dmi:*:svnTECLAST:pnF5:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Sort 60-sensor.hwdb Teclast entries alphabetically Sort 60-sensor.hwdb Teclast entries alphabetically (by model name), and add a comment with the model name to the few entries which were missing this.
2019-12-01 17:46:32 +03:00
# Teclast F6 Pro (2 sensors)
hwdb: Add accelerometer orientation quirk for the Teclast F6 Pro
2019-04-03 21:10:50 +03:00
sensor:modalias:acpi:KIOX010A*:dmi:*:svnTECLAST:pnF6Pro:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1
hwdb: add base sensor and ACCEL_LOCATION property for Teclast F6 Pro device sensors
2019-05-01 03:23:44 +03:00
ACCEL_LOCATION=display
sensor:modalias:acpi:KIOX020A*:dmi:*:svnTECLAST:pnF6Pro:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
ACCEL_LOCATION=base
hwdb: Add accelerometer orientation quirk for the Teclast F6 Pro
2019-04-03 21:10:50 +03:00
hwdb: Add accel orientation quirk for the Teclast Tbook 11 tablet Add a quirk to fix the accelerometer orientation on the Teclast Tbook 11 tablet.
2021-04-17 20:55:47 +03:00
# Teclast Tbook 11 (E5A6)
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTECLAST:pnTbooK11:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
Added Teclast X4 ACCEL_MOUNT_MATRIX (#19540)
2021-05-07 23:17:25 +03:00
# Teclast X4 2-in-1 (G4M6)
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTECLAST:pnX4:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Sort 60-sensor.hwdb Teclast entries alphabetically Sort 60-sensor.hwdb Teclast entries alphabetically (by model name), and add a comment with the model name to the few entries which were missing this.
2019-12-01 17:46:32 +03:00
# Teclast X80 Plus (H5C5)
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTECLAST:pnDefaultstring:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
# Teclast X80 Pro (E3E6)
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTECLAST:pnX80Pro:*
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Teclast X89 tablet Add a quirk to fix the accelerometer orientation on the Teclast X89 tablet.
2019-12-01 17:55:00 +03:00
# Teclast X89 (E7ED), "tPAD" is too generic also match on BIOS date
sensor:modalias:acpi:SMO8500*:dmi:*bd12/19/2014:*:rvnTECLAST:rntPAD:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Sort 60-sensor.hwdb Teclast entries alphabetically Sort 60-sensor.hwdb Teclast entries alphabetically (by model name), and add a comment with the model name to the few entries which were missing this.
2019-12-01 17:46:32 +03:00
# Teclast X98 Plus I (A5C6), generic DMI strings, match entire dmi modalias inc. bios-date
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:KIOX000A*:dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd11/03/2015:*svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:*
hwdb: Sort 60-sensor.hwdb Teclast entries alphabetically Sort 60-sensor.hwdb Teclast entries alphabetically (by model name), and add a comment with the model name to the few entries which were missing this.
2019-12-01 17:46:32 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
# Teclast X98 Plus II
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTECLAST:pnX98PlusII:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Thundersoft TST168 tablet Add a quirk to fix the accelerometer orientation on the Thundersoft TST168 tablet.
2019-12-13 15:01:02 +03:00
#########################################
# Thundersoft
#########################################
# Thundersoft TST168 tablet, generic DMI strings, match entire dmi modalias inc. bios-date
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:BMA250E*:dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd04/15/2014:*svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:*
hwdb: Add accel orientation quirk for Thundersoft TST168 tablet Add a quirk to fix the accelerometer orientation on the Thundersoft TST168 tablet.
2019-12-13 15:01:02 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Toshiba Encore WT10A tablet Add a quirk to correct the accelerometer orientation on Toshiba Encore WT10A tablets.
2020-05-31 11:25:50 +03:00
#########################################
# Toshiba
#########################################
hwdb: Add accel orientation quirk for the Toshiba WT8-B tablet Add a quirk to fix the accelerometer orientation on the Toshiba WT8-B tablet.
2021-05-04 18:38:33 +03:00
# Toshiba Encore WT8-B tablet
hwdb: remove trailing whitespace
2021-05-11 00:03:52 +03:00
sensor:modalias:acpi:INVN6500*:dmi:*:svnTOSHIBA:pnTOSHIBAENCORE2WT8-B:*
hwdb: Add accel orientation quirk for the Toshiba WT8-B tablet Add a quirk to fix the accelerometer orientation on the Toshiba WT8-B tablet.
2021-05-04 18:38:33 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Toshiba Encore WT10A tablet Add a quirk to correct the accelerometer orientation on Toshiba Encore WT10A tablets.
2020-05-31 11:25:50 +03:00
# Toshiba Encore WT10A tablet
sensor:modalias:acpi:INVN6500*:dmi:*:svnTOSHIBA:pnTOSHIBAWT10-A-103:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
#########################################
# Trekstor
#########################################
sensor:modalias:acpi:BMA250*:dmi:*:bvrTREK.G.WI71C.JGBMRBA*:*:svnInsyde:pnST70416-6:*
hwdb: 60-sensors: Add DMI strings for Trekstor Surftab 7.0 newer BIOS versions (#7904) Some newer BIOS versions of the TrekStor SurfTab wintron 7.0 tablet use different (better) DMI strings, update the existing 60-sensors.hwdb entry for this tablet to also work with the newer BIOS.
2018-01-17 12:15:41 +03:00
sensor:modalias:acpi:BMA250*:dmi:*:bvrTREK.G.WI71C.JGBMRBA*:*:svnTrekStor:pnSurfTabwintron7.0ST70416-6:*
hwdb: Add ACCEL_MOUNT_MATRIX for a number of Intel Bay Trail based devices (#6357) This commit adds ACCEL_MOUNT_MATRIX entries for the following devices: -Acer Iconia Tab8 W1-810 -Asustek T100CHI Transformer 2-in-1 -Asustek T100TA Transformer 2-in-1 -Chuwi Vi8 Plus tablet -Cube iWork8 Air (i1-TF) tablet -GP-electronic T701 7" tablet -HP Stream 7 tablet -I.T.Works TW891 2-in-1 -Jumper Ezpad mini 3 -Lamina I8270 7" tablet -Peaq MMC1010 2-in-1 -Pipo W2S 8" tablet -Ployer Momo7w tablet -Point of View TAB-P800W 8" tablet -Trekstor Surftab Wintron 7.0 ST70416-6 7" tablet
2017-07-14 19:29:59 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
hwdb: Add accelerometer orientation quirk for the Yours Y8W81 tablet Add an accelerometer orientation quirk for the Yours Y8W81 8" tablet. For future reference: this tablet has the same case and mostly the same internals as the Chuwi Vi8. Both seem to be from an ODM called inet-tek. Both are labelled: "INET-I86M-REVxx" on the PCB, with the Chuwi Vi8 being REV03 (and having a ALC5640 audio codec) and the Yours Y8W81 being REV21 (and having a ALC5651 audio codec).
2018-03-09 16:55:11 +03:00
hwdb: Add accel orientation quirk for the Trekstor Surftab Wintron 10.1 ST10432-3 tablet Add a quirk to fix the accelerometer orientation on the Trekstor Surftab Wintron 10.1 ST10432-3 tablet.
2021-02-16 23:24:40 +03:00
# SurfTab Wintron 10.1 ST10432-3, generic DMI string, use partial BIOS version match
sensor:modalias:acpi:SMO8500*:dmi:*:bvrWintron.R25M.02.0*:*:svnInsyde:pnBayTrail:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Trekstor Surftab Twin 10.1 ST10432-8 The Trekstor Surftab Twin 10.1 ST10432-8 accelerometer has its x-axis inverted, add a quirk for this.
2020-05-31 17:21:36 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTrekStor:pnSurfTabtwin10.1:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, 1
Added Trekstor Primetab S11B
2019-12-14 19:48:06 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTREKSTOR*:pnPrimetabS11B:*
hwdb: Add ACCEL_MOUNT_MATRIX for Trekstor T13B tablet
2018-11-24 15:24:39 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnTREKSTOR:pnPrimetabT13B:*
hwdb: rotation for Trekstor Surf Tab Twin 11.6 aka VolksTablet (#11771)
2019-02-20 21:05:25 +03:00
sensor:modalias:acpi:BOSC0200*:dmi:*:svnTrekStor*:pnSurfTabtwin11.6:*
hwdb: Add ACCEL_MOUNT_MATRIX for Trekstor T13B tablet
2018-11-24 15:24:39 +03:00
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
added alternative version of SurfTab Twin
2020-07-29 21:02:55 +03:00
# alternative version of Trekstor's SurfTab Twin 11.6
sensor:modalias:acpi:BOSC0200*:dmi:*:bvrTP15-VT5.2.1.3:*:svnTrekStor*:pnSurfTabtwin11.6:*
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, 1, 0; 0, 0, -1
hwdb: Update Primebook C11B sensor entry to also work with older BIOS versions Older Primebook C11B BIOS versions use "Primebook C11B" as product name instead of "PRIMEBOOK C11B", update the Primebook C11B 60-sensor.hwdb entries to match on both spellings.
2019-09-23 12:00:50 +03:00
sensor:modalias:acpi:KIOX010A*:dmi:*:svnTREKSTOR:pnPrimebookC11B:*
hwdb: Add accel. mount matrix and location for the Trekstor Primebook C11B The Trekstor Primebook C11B 2-in-1 has 2 accelerometers. Add mount-matrix and location info for both to 60-sensor.hwdb.
2019-08-25 21:34:34 +03:00
sensor:modalias:acpi:KIOX010A*:dmi:*:svnTREKSTOR:pnPRIMEBOOKC11B:*
Added Trekstor Yourbook C11B to 60-sensor.hwdb Added the Trekstor Yourbook C11B which is equivalent to Trekstor Primebook C11B.
2021-02-12 19:57:26 +03:00
sensor:modalias:acpi:KIOX010A*:dmi:*:svnTREKSTOR:pnYourbookC11B:*
sensor:modalias:acpi:KIOX010A*:dmi:*:svnTREKSTOR:pnYOURBOOKC11B:*
hwdb: Add accel. mount matrix and location for the Trekstor Primebook C11B The Trekstor Primebook C11B 2-in-1 has 2 accelerometers. Add mount-matrix and location info for both to 60-sensor.hwdb.
2019-08-25 21:34:34 +03:00
ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1
ACCEL_LOCATION=display
hwdb: Update Primebook C11B sensor entry to also work with older BIOS versions Older Primebook C11B BIOS versions use "Primebook C11B" as product name instead of "PRIMEBOOK C11B", update the Primebook C11B 60-sensor.hwdb entries to match on both spellings.
2019-09-23 12:00:50 +03:00
sensor:modalias:acpi:KIOX020A*:dmi:*:svnTREKSTOR:pnPrimebookC11B:*
hwdb: Add accel. mount matrix and location for the Trekstor Primebook C11B The Trekstor Primebook C11B 2-in-1 has 2 accelerometers. Add mount-matrix and location info for both to 60-sensor.hwdb.
2019-08-25 21:34:34 +03:00
sensor:modalias:acpi:KIOX020A*:dmi:*:svnTREKSTOR:pnPRIMEBOOKC11B:*
Added Trekstor Yourbook C11B to 60-sensor.hwdb Added the Trekstor Yourbook C11B which is equivalent to Trekstor Primebook C11B.
2021-02-12 19:57:26 +03:00
sensor:modalias:acpi:KIOX020A*:dmi:*:svnTREKSTOR:pnYourbookC11B:*
sensor:modalias:acpi:KIOX020A*:dmi:*:svnTREKSTOR:pnYOURBOOKC11B:*
hwdb: Add accel. mount matrix and location for the Trekstor Primebook C11B The Trekstor Primebook C11B 2-in-1 has 2 accelerometers. Add mount-matrix and location info for both to 60-sensor.hwdb.
2019-08-25 21:34:34 +03:00
ACCEL_MOUNT_MATRIX=0, 1, 0; 1, 0, 0; 0, 0, 1
ACCEL_LOCATION=base
hwdb: add accelerometer mount matrix for Umax VisionBook 10Wi Plus
2018-07-07 01:29:43 +03:00
#########################################
# Umax
#########################################
hwdb: Add accel orientation quirk for UMAX VisionBook 10Wi Pro
2020-07-02 14:06:04 +03:00
sensor:modalias:acpi:KIOX000A*:dmi:*:svnUMAX:pnVisionBook10WiPro:*
ACCEL_MOUNT_MATRIX=1, 0, 0; 0, -1, 0; 0, 0, 1
hwdb: add accelerometer mount matrix for Umax VisionBook 10Wi Plus
2018-07-07 01:29:43 +03:00
sensor:modalias:acpi:SMO8500*:dmi:*:svnUMAX:pnVisionBook10WiPlus:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
hwdb: Add accel orientation quirk for Voyo Winpad A15 tablet Add a quirk to fix the accelerometer orientation on the Voyo Winpad A15 tablet.
2020-11-15 13:23:04 +03:00
#########################################
# Voyo
#########################################
# Voyo Winpad A15
# The Winpad A15 does not have its product name filled, so we
# match the entire dmi-alias, assuming that the use of a SMO8500 +
# bios-version + bios-date combo is unique
hwdb: sensors: Fix some modalias matches no longer working with newer kernels Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the middle of the modalias (instead of adding them at the end). Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have been added between the ":bd<value>:" and ":svn<value>:" fields. Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed in later 5.13.y and 5.14.y releases, by moving the sku field to the end: https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/ Unfortunately the same cannot be done for the new br and efr fields since those have been added more then a year ago and hwdb even already has some newer entries relying on the new br field being there (and thus not working with older kernels). Fix the issue with the br and efr fields through the following changes: 1. Replace any matches on ":br<value>" from newer entries with an '*' 2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>" inserting an '*' where newer kernels will have the new br + efr fields This makes these matches working with old as well as new kernels. Link: https://github.com/systemd/systemd/issues/20550 Link: https://github.com/systemd/systemd/pull/20562
2021-08-31 16:49:33 +03:00
# '*' in ":*svn" is there because kernels >= 5.8 have inserted a br field there
sensor:modalias:acpi:SMO8500*:dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd11/20/2014:*svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:*
hwdb: Add accel orientation quirk for Voyo Winpad A15 tablet Add a quirk to fix the accelerometer orientation on the Voyo Winpad A15 tablet.
2020-11-15 13:23:04 +03:00
ACCEL_MOUNT_MATRIX=0, -1, 0; 1, 0, 0; 0, 0, -1
hwdb: Add accel orientation quirk for Wortmann Terra Pad 1061 Add a quirk to fix the accelerometer orientation on the Wortmann Terra Pad 1061 tablet.
2019-11-06 12:22:21 +03:00
#########################################
# Wortmann
#########################################
sensor:modalias:acpi:KIOX000A*:dmi:*:svnWortmann_AG:pnTERRA_PAD_1061:*
ACCEL_MOUNT_MATRIX=0, -1, 0; 1, 0, 0; 0, 0, -1
hwdb: Add accelerometer orientation quirk for the Yours Y8W81 tablet Add an accelerometer orientation quirk for the Yours Y8W81 8" tablet. For future reference: this tablet has the same case and mostly the same internals as the Chuwi Vi8. Both seem to be from an ODM called inet-tek. Both are labelled: "INET-I86M-REVxx" on the PCB, with the Chuwi Vi8 being REV03 (and having a ALC5640 audio codec) and the Yours Y8W81 being REV21 (and having a ALC5651 audio codec).
2018-03-09 16:55:11 +03:00
#########################################
# Yours
#########################################
sensor:modalias:acpi:BMA250E*:dmi:*:svnYOURS:pnY8W81:*
ACCEL_MOUNT_MATRIX=0, -1, 0; -1, 0, 0; 0, 0, 1
Copy Permalink