276ede0740
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. |
||
|---|---|---|
| .github | ||
| .lgtm/cpp-queries | ||
| .mkosi | ||
| catalog | ||
| coccinelle | ||
| docs | ||
| factory/etc | ||
| hwdb.d | ||
| man | ||
| modprobe.d | ||
| network | ||
| po | ||
| presets | ||
| rules.d | ||
| semaphoreci | ||
| shell-completion | ||
| src | ||
| sysctl.d | ||
| sysusers.d | ||
| test | ||
| tmpfiles.d | ||
| tools | ||
| travis-ci | ||
| units | ||
| xorg | ||
| .clang-format | ||
| .ctags | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .lgtm.yml | ||
| .mailmap | ||
| .travis.yml | ||
| .vimrc | ||
| .ycm_extra_conf.py | ||
| LICENSE.GPL2 | ||
| LICENSE.LGPL2.1 | ||
| Makefile | ||
| NEWS | ||
| README | ||
| README.md | ||
| TODO | ||
| azure-pipelines.yml | ||
| configure | ||
| meson.build | ||
| meson_options.txt | ||
| mkosi.build | ||
| zanata.xml | ||
README.md
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.