From: Jean Delvare <jdelvare@suse.de>
To: "Pali Rohár" <pali@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Andi Shyti <andi.shyti@kernel.org>, Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Marius Hoch <mail@mariushoch.de>,
Mario Limonciello <mario.limonciello@amd.com>,
Dell.Client.Kernel@dell.com, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Ideas for a generic solution to support accelerometer lis3lv02d in Dell laptops/notebooks?
Date: Tue, 13 Feb 2024 15:07:08 +0100 [thread overview]
Message-ID: <20240213150708.57148f6a@endymion.delvare> (raw)
In-Reply-To: <20231223125350.xqggx3nyzyjjmnut@pali>
On Sat, 23 Dec 2023 13:53:50 +0100, Pali Rohár wrote:
> smbus is not really bus which provides discovering and identifying
> devices on the bus.
For completeness, SMBus version 2.0 actually added support for device
discovery and even dynamic slave address allocation. This is explained
in chapter 5, section 5.6 (SMBus Address resolution protocol).
Unfortunately, this is an optional feature which requires active
cooperation from each device connected to the bus. If any device on the
bus supports SMBus ARP then you should get an answer when probing
(7-bit) I2C address 0x61.
Long ago I had a plan to add support for SMBus ARP to the kernel, but
gave up because I couldn't find any system implementing it. If the
accelerometer device in Dell laptops supported ARP then we could use it
to figure out the device's address, unfortunately this doesn't seem to
be the case.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2024-02-13 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 9:39 Ideas for a generic solution to support accelerometer lis3lv02d in Dell laptops/notebooks? Paul Menzel
2023-12-23 12:19 ` Pali Rohár
2023-12-23 12:45 ` Hans de Goede
2023-12-23 12:53 ` Pali Rohár
2023-12-23 13:40 ` Hans de Goede
2023-12-23 14:21 ` Pali Rohár
2024-02-13 14:07 ` Jean Delvare [this message]
2024-02-15 18:16 ` Pali Rohár
2024-02-15 19:08 ` Wolfram Sang
2024-02-27 20:51 ` Pali Rohár
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=20240213150708.57148f6a@endymion.delvare \
--to=jdelvare@suse.de \
--cc=Dell.Client.Kernel@dell.com \
--cc=andi.shyti@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@mariushoch.de \
--cc=mario.limonciello@amd.com \
--cc=pali@kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=wsa@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