systemd version the issue has been seen with

251

Used distribution

Debian Testing

Linux kernel version used

5.19.0

CPU architectures issue was seen on

aarch64

Component

hardware database files

Expected behaviour you didn't see

In /etc/udev/hwdb.d/61-sensor-local.hwdb, I would expect the following rule to match on my system

sensor:modalias:platform:cros-ec-accel
 ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1

Unexpected behaviour you saw

Above rule did not take effect. Only the following catch-all rule would work:

sensor:modalias:platform:*
 ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1

Steps to reproduce the problem

Get a Chromebook with aarch64 chip. Install Linux in developer mode. Observe sudo su -s /bin/sh geoclue -c monitor-sensor shows the sensor reads "upside down". Try fixing with first rule that matches the sensor's modalias.

Additional program output to the terminal or log subsystem illustrating the issue

Note that CONFIG_DMIID documented in 60-sensor.hwdb is not applicable to the aarch64 platform.

I suspect there is some x86 related behavior hardcoded that breaks the modalias based matching on aarch64 systems.

Once this is fixed, all the rules for individual chromebooks at

can be replaced by a single rule matching all sensor:modalias:platform:cros-ec-accel as the ACCEL_MOUNT_MATRIX=-1, 0, 0; 0, -1, 0; 0, 0, -1 on all Chromebooks.