From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 218578] MXC6655 accelerometer not working with MXC4005 driver
Date: Sun, 10 Mar 2024 12:33:38 +0000 [thread overview]
Message-ID: <bug-218578-217253-7fLu1ci59H@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218578-217253@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218578
--- Comment #1 from Jonathan Cameron (jic23@kernel.org) ---
On Sat, 09 Mar 2024 17:55:32 +0000
bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218578
>
> Bug ID: 218578
> Summary: MXC6655 accelerometer not working with MXC4005 driver
> Product: Drivers
> Version: 2.5
> Hardware: Intel
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: IIO
> Assignee: drivers_iio@kernel-bugs.kernel.org
> Reporter: kernelbugzilla@kirkschnable.com
> Regression: No
>
> Created attachment 305970
> --> https://bugzilla.kernel.org/attachment.cgi?id=305970&action=edit
> Output from udevadm info -n /dev/iio\:device0 && also some samples of
> accelerometer raw values I see in /sys/bus/iio/devices/iio:device:0/.
>
> Hello,
>
> I recently bought two Chuwi tablets which contain MXC6655 accelerometers.
> The
> accelerometers work in Windows 11 and the tablet rotates as expected in
> Windows, but upon installing Linux the tablet auto rotation was not working.
>
Hi, thanks for the report,
First thought is that there may be some power control hidden in the ACPI
tables.
Could you dump
/sys/firmware/acpi/tables/DSDT
and run it through iasl -d (from acpica-tools)
Find the section related to his accelerometer and post all of that.
Sometimes there is a _DSM (device specific method) used to power things up
- this stuff is completely non standard unfortunately so we have to base
any support on table dumps from the particular devices.
Thanks,
Jonathan
> The Chuwi tablets are:
> - UBook X Pro 2023
> - UBook X 2023
>
> This does not appear to be distro specific, as I am seeing the same behavior
> on
> both:
> - Linux Mint 21.3, with kernel 5.15.0-91-generic
> - Fedora 39 Workstation, with kernel 6.5.6-300.fc39.x86_64
>
> I came across this thread indicating that support was added for this in 2020
> via the MXC4005 driver: https://www.spinics.net/lists/linux-iio/msg53171.html
>
> This seems to be double confirmed by another issue I found here on this bug
> tracker: https://bugzilla.kernel.org/show_bug.cgi?id=206703
>
> Unfortunately in my case, I see the MXC4005 driver is in fact loaded and
> running, however it appears the raw data is not changing. When looking at
> the
> output from iio-sensor-proxy with "monitor-sensor", the orientation always
> reports "left-up".
>
> I tried a test where I watched a cat of all of the files in
> /sys/bus/iio/devices/iio:device0/, and I never see the raw data changing when
> the tablet is rotated. I'm attaching the values I see from the raw data in
> the
> text file. Interestingly, Fedora reports different raw values, but
> iio-sensor-proxy still says orientation is left-up with these values. In
> both
> cases, the values don't change when the tablet is rotated.
>
> The output of "udevadm info -n /dev/iio\:device0" is attached too.
>
> lsmod reports that the mxc4005 driver is loaded, along with industrialio and
> industrialio_triggered_buffer. Unloading the mxc4005 module with rmmod
> causes
> it to disappear from iio-sensor-proxy as expected, but otherwise unloading
> and
> reloading the driver seems to have no effect on the symptoms.
>
> If there is any further information I can gather which will be helpful, or
> any
> testing I can help with, please let me know.
>
> Thanks!
>
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-03-10 12:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 17:55 [Bug 218578] New: MXC6655 accelerometer not working with MXC4005 driver bugzilla-daemon
2024-03-09 18:05 ` [Bug 218578] " bugzilla-daemon
2024-03-09 18:17 ` bugzilla-daemon
2024-03-10 12:33 ` [Bug 218578] New: " Jonathan Cameron
2024-03-10 12:33 ` bugzilla-daemon [this message]
2024-03-11 4:21 ` [Bug 218578] " bugzilla-daemon
2024-03-11 4:34 ` bugzilla-daemon
2024-03-11 18:29 ` bugzilla-daemon
2024-03-13 22:13 ` bugzilla-daemon
2024-03-13 22:14 ` bugzilla-daemon
2024-03-13 22:14 ` bugzilla-daemon
2024-03-14 9:35 ` bugzilla-daemon
2024-03-14 9:36 ` bugzilla-daemon
2024-03-14 9:37 ` bugzilla-daemon
2024-03-15 2:30 ` bugzilla-daemon
2024-03-15 2:31 ` bugzilla-daemon
2024-03-15 2:32 ` bugzilla-daemon
2024-03-15 2:33 ` bugzilla-daemon
2024-03-15 15:13 ` bugzilla-daemon
2024-03-17 23:45 ` bugzilla-daemon
2024-03-18 10:43 ` bugzilla-daemon
2024-03-20 8:38 ` bugzilla-daemon
2024-03-22 22:09 ` bugzilla-daemon
2024-03-26 11:45 ` bugzilla-daemon
2024-03-26 22:34 ` bugzilla-daemon
2024-03-26 22:37 ` bugzilla-daemon
2024-03-27 14:38 ` bugzilla-daemon
2024-04-04 22:33 ` bugzilla-daemon
2024-04-08 14:31 ` bugzilla-daemon
2024-04-10 22:29 ` bugzilla-daemon
2024-04-10 22:30 ` bugzilla-daemon
2024-04-17 16:57 ` bugzilla-daemon
2024-04-17 17:01 ` bugzilla-daemon
2024-04-17 19:32 ` bugzilla-daemon
2024-04-18 23:08 ` bugzilla-daemon
2024-04-19 7:37 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218578-217253-7fLu1ci59H@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-iio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).