From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 216037] New: Second MXC6655 accelerometer is not detected on transformer Aquarius NS483 laptop
Date: Fri, 27 May 2022 16:08:40 +0000 [thread overview]
Message-ID: <bug-216037-217253@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216037
Bug ID: 216037
Summary: Second MXC6655 accelerometer is not detected on
transformer Aquarius NS483 laptop
Product: Drivers
Version: 2.5
Kernel Version: 5.17.11
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IIO
Assignee: drivers_iio@kernel-bugs.kernel.org
Reporter: nickel@altlinux.org
Regression: No
A couple of accelerometers are used to detect the hinge angle in convertible
laptops(one for display, one for base/keyboard).
A discussion on the topic is available at [1]
But in my case while DSDT describes two I2C devices (if I interpret it right):
>Device (ACMG)
> {
> Name (_ADR, Zero) // _ADR: Address
> Name (_HID, "MXC6655") // _HID: Hardware ID
> Name (_CID, "MXC6655") // _CID: Compatible ID
> Name (_DDN, "Accelerometer with Angle Calculation") // _DDN: DOS
> Device Name
> Name (_UID, One) // _UID: Unique ID
> Method (_CRS, 0, NotSerialized) // _CRS: Current Resource
> Settings
> {
> Name (RBUF, ResourceTemplate ()
> {
> I2cSerialBusV2 (0x0015, ControllerInitiated, 0x00061A80,
> AddressingMode7Bit, "\\_SB.PC00.I2C1",
> 0x00, ResourceConsumer, , Exclusive,
> )
> I2cSerialBusV2 (0x0015, ControllerInitiated, 0x00061A80,
> AddressingMode7Bit, "\\_SB.PC00.I2C2",
> 0x00, ResourceConsumer, , Exclusive,
> )
> })
> Return (RBUF) /* \_SB_.PC00.I2C1.ACMG._CRS.RBUF */
> }
only one of them is detected (display side one, up and running, by the way):
> P: /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-16/i2c-MXC6655:00
> L: 0
> E:
> DEVPATH=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-16/i2c-MXC6655:00
> E: SUBSYSTEM=i2c
> E: DRIVER=mxc4005
> E: MODALIAS=acpi:MXC6655:MXC6655:
>
> P:
> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-16/i2c-MXC6655:00/iio:device0
> N: iio:device0
> L: 0
> E:
> DEVPATH=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-16/i2c-MXC6655:00/iio:device0
> E: SUBSYSTEM=iio
> E: DEVNAME=/dev/iio:device0
> E: DEVTYPE=iio_device
> E: MAJOR=238
> E: MINOR=0
> E: USEC_INITIALIZED=4954716
> E: IIO_SENSOR_PROXY_TYPE=iio-poll-accel iio-buffer-accel
> E: SYSTEMD_WANTS=iio-sensor-proxy.service
> E: TAGS=:systemd:
> E: CURRENT_TAGS=:systemd:
There should be 2 I2C devices with DRIVER=mxc4005, shouldn't they?
Attaching detailed logs also.
[1] https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/338
--
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 reply other threads:[~2022-05-27 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 16:08 bugzilla-daemon [this message]
2022-05-27 16:09 ` [Bug 216037] Second MXC6655 accelerometer is not detected on transformer Aquarius NS483 laptop 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
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@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).