From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 218578] MXC6655 accelerometer not working with MXC4005 driver
Date: Mon, 11 Mar 2024 04:34:03 +0000 [thread overview]
Message-ID: <bug-218578-217253-wLlCRzHIcK@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 #3 from Kirk Schnable (kernelbugzilla@kirkschnable.com) ---
Hello Jonathan,
Thanks for your response, and I have done some further testing today which has
led me to some interesting conclusions.
I have, as you requested, extracted the DSDT information relevant to the
accelerometer and attached it. I found 6 devices containing the word
"Accelerometer" so I pulled the details of all of them, but I think the first
one, ACC0, is the relevant one since it mentions the MXC6655 model number.
My further testing today has led me to conclude that this problem is more
"intermittent" than I'd first believed. It almost led me to incorrectly
conclude that I'd been mistaken about the whole thing in fact.
I made another post elsewhere and connected with another user of a similar
Chuwi tablet device who says their accelerometer is working reliably on Fedora
39 (after a workaround to correct the fact that the orientation is 90 degrees
off). They encouraged me to try it from the live environment, which I did not
expect to make any difference, however it actually worked exactly as he had
described. For the first time, I saw actual updates to the raw data, and the
screen was actually rotating (albeit, incorrectly).
This prompted me to perform another fresh install of Fedora. To my shock, the
fresh install worked at first boot too, then I started to try to fix the 90
degree orientation issue. I created a file in /etc/udev/hwdb.d/ with some
suggested settings and rebooted. After that, the accelerometer no longer
worked. So, I reverted the change and rebooted again. Still no accelerometer
readings anymore.
Thinking that maybe I'd broken that install somehow (even though I reverted all
the changes), I did another fresh install. This fresh install worked too until
I rebooted the system. I did nothing else but reboot the system. Totally
broken, even several reboots later.
I tried running DNF updates on this install (over 600 packages needing update),
and rebooted again. Still no accelerometer. An update clearly didn't break it
but an update also didn't fix it.
While attempting to begin a third fresh install to try to reproduce this and
see if this was a pattern, I performed the test again from the live environment
and got no accelerometer readings. This is the exact same USB I installed from
earlier that worked several times this morning.
Something is very strange. I would almost believe it was a faulty
accelerometer if it weren't for the fact that I used this tablet for 3 hours
today in Windows 11 and experienced no issues with the screen rotation.
I will say this much, I have yet to see the problem "go away" on an install
once it starts. The installs that work once and then break never start working
again. The live environment has been the most likely to work, but I have now
seen it not work. I dumped the ACPI data for you from a live session of Fedora
39 when the accelerometer was not working.
Hopefully this data is helpful. I am not knowledgeable enough about how these
ACPI components function under the hood, but it seems like the issue is less an
issue of "the accelerometer never works" and more of an issue of "the
accelerometer only works sometimes".
Thanks!
Kirk
--
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-11 4:34 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 ` [Bug 218578] " bugzilla-daemon
2024-03-11 4:21 ` bugzilla-daemon
2024-03-11 4:34 ` bugzilla-daemon [this message]
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-wLlCRzHIcK@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.