All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 218578] MXC6655 accelerometer not working with MXC4005 driver
Date: Wed, 13 Mar 2024 22:14:31 +0000	[thread overview]
Message-ID: <bug-218578-217253-hVAmpoGAio@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 #7 from Kirk Schnable (kernelbugzilla@kirkschnable.com) ---
Hello Hans,

Thanks for your response as well, and my apologies for the delay, I wanted to
do a bit of further testing.

It hadn't specifically occurred to me that rebooting from Windows might be
causing an issue.  I'm aware that Windows by default does save some state data
for a faster boot, but I didn't think any of this would make any difference in
a normal reboot once you hit GRUB and select your Linux installation.

Regardless, it does seem like making sure to do a cold boot every time has
resulted in the accelerometer working a bit more reliably.  However, before, I
was even rebooting from Fedora back into Fedora and still having trouble with
it, so I don't think it's specifically Windows causing the symptoms either. 
Not sure what to make of it yet...

In any case here are your requested details:

The path you specified did exist:
i2c-MXC6655:00 ->
../../../devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-MXC6655:00

# cat /sys/bus/i2c/devices/i2c-MXC6655\:00/firmware_node/path 
\_SB_.PCI0.I2C0.ACC0

I'm attaching the dmesg and acpidump.  These are from a persistent Fedora
install which was updated to 6.7.7-200.fc39.x86_64.

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.

  parent reply	other threads:[~2024-03-13 22:14 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
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 [this message]
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-hVAmpoGAio@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.