From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 218578] MXC6655 accelerometer not working with MXC4005 driver
Date: Mon, 18 Mar 2024 10:43:21 +0000 [thread overview]
Message-ID: <bug-218578-217253-5XgfUn25UH@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 #17 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
(In reply to Kirk Schnable from comment #16)
> Thanks for the continued support Hans! I have actually never compiled my
> own kernel before, but there's a first time for everything. I'm down to
> give it a go.
I see in your attached dmesg that you are actually running Fedora, in that case
I can actually provide pre-build kernel rpms with the patch for you.
I'll try to make some time to write a patch for this and provide rpms sometime
this week.
> Also FWIW, my further testing has indicated that there are also problems
> when coming out of a sleep state. Will your proposed fix also be likely to
> correct that behavior too?
That is good to know, that means that the driver also needs to reset the chip
on resume (and restore any non default settings). I'll add this to the patch.
--
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-18 10:43 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
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 [this message]
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-5XgfUn25UH@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.