From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 216037] Second MXC6655 accelerometer is not detected on transformer Aquarius NS483 laptop
Date: Sat, 14 Sep 2024 11:29:07 +0000 [thread overview]
Message-ID: <bug-216037-217253-aUDCF10lCD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216037-217253@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216037
--- Comment #6 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
Andy, thank you for the Cc.
Nikolai, thank you for reporting this and thank you for already doing some
initial investigation and providing a DSDT.
Looking at the _CRS for the Device (ACMG) {} then it has 2 I2cSerialBusV2
resources, likely one for each accelerometer.
We have hit this case before with BOSC0200 ACPI devices describing bmc150
accelerometers, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iio/accel/bmc150-accel-i2c.c#n125
I think we need to add a function like bmc150_acpi_dual_accel_probe() to
drivers/iio/accel/mxc4005.c minus the extra special suspend/resume handling.
Nikolai, do you think you can write a patch for this yourself (mostly copy +
pasting the bmc150_acpi_dual_accel_probe() function) ?
--
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-09-14 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 16:08 [Bug 216037] New: Second MXC6655 accelerometer is not detected on transformer Aquarius NS483 laptop bugzilla-daemon
2022-05-27 16:09 ` [Bug 216037] " bugzilla-daemon
2022-05-27 16:10 ` bugzilla-daemon
2022-05-27 16:11 ` bugzilla-daemon
2022-05-27 16:12 ` bugzilla-daemon
2024-09-09 14:47 ` bugzilla-daemon
2024-09-14 11:29 ` bugzilla-daemon [this message]
2026-05-13 13:28 ` 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-216037-217253-aUDCF10lCD@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.