From: Wolfram Sang <wsa@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Jean Delvare" <jdelvare@suse.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Pali Rohár" <pali@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] i2c: i801: Add 0x29 as I²C address for lis3lv02d in Dell Precision 3540
Date: Fri, 22 Dec 2023 11:40:03 +0100 [thread overview]
Message-ID: <ZYVng90Z9nIGSuNR@shikoro> (raw)
In-Reply-To: <20231220161003.68310-1-pmenzel@molgen.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
On Wed, Dec 20, 2023 at 05:10:01PM +0100, Paul Menzel wrote:
> On the Dell Precision 3540/0M14W7, BIOS 1.7.4 05/12/2020, Linux prints
> the warning below.
>
> i801_smbus 0000:00:1f.4: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
>
> With the help of Wolfram Sang, the test to probe it on I²C bus 6 at address
> 0x29 was successful.
>
> $ cd /sys/bus/pci/drivers/i801_smbus/0000:00:1f.4
> $ ls -d i2c-?
> i2c-6
> $ sudo i2cdetect 6
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-6.
> I will probe address range 0x08-0x77.
> Continue? [Y/n] Y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 08 -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- 29 -- -- -- -- -- --
> 30: 30 -- -- -- -- 35 UU UU -- -- -- -- -- -- -- --
> 40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --
> 50: UU -- 52 -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
>
> $ echo lis3lv02d 0x29 | sudo tee /sys/bus/i2c/devices/i2c-6/new_device
> $ sudo dmesg
> […]
> [ 2110.787000] i2c i2c-6: new_device: Instantiated device lis3lv02d at 0x29
> [ 2110.791932] lis3lv02d_i2c 6-0029: supply Vdd not found, using dummy regulator
> [ 2110.791981] lis3lv02d_i2c 6-0029: supply Vdd_IO not found, using dummy regulator
> [ 2110.809233] lis3lv02d: 8 bits 3DC sensor found
> [ 2110.900668] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23
>
> So, the device has that accelerometer. Add the I2C address to the
> mapping list.
>
> Link: https://lore.kernel.org/linux-i2c/97708c11-ac85-fb62-2c8e-d37739ca826f@molgen.mpg.de/
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-12-22 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 16:10 [PATCH 1/2] i2c: i801: Add 0x29 as I²C address for lis3lv02d in Dell Precision 3540 Paul Menzel
2023-12-20 16:10 ` [PATCH 2/2] i2c: i801: Add 0x29 as I²C address for lis3lv02d in Dell XPS 15 7590 Paul Menzel
2023-12-20 16:22 ` Pali Rohár
2023-12-22 0:28 ` Andi Shyti
2023-12-22 10:40 ` Wolfram Sang
2023-12-20 16:21 ` [PATCH 1/2] i2c: i801: Add 0x29 as I²C address for lis3lv02d in Dell Precision 3540 Pali Rohár
2023-12-22 0:25 ` Andi Shyti
2023-12-22 10:40 ` Wolfram Sang [this message]
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=ZYVng90Z9nIGSuNR@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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