From: Wolfram Sang <wsa@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Jean Delvare" <jdelvare@suse.com>,
linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Dell.Client.Kernel@dell.com, "Pali Rohár" <pali@kernel.org>
Subject: Re: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
Date: Mon, 27 Feb 2023 20:27:29 +0100 [thread overview]
Message-ID: <Y/0EIRsycj8EWjrz@ninjato> (raw)
In-Reply-To: <97708c11-ac85-fb62-2c8e-d37739ca826f@molgen.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
Hi Paul,
> What can a user do about this? It looks like the I2C addresses need to be
> added to `dell_lis3lv02d_devices[]` in `drivers/i2c/busses/i2c-i801.c`.
Complain to Dell about the missing address ;)
Until then:
> [ 20.631866] i801_smbus 0000:00:1f.4: SPD Write Disable is set
# cd /sys/bus/pci/drivers/i801_smbus/0000\:00\:1f.4
# ls -d i2c-?
The last digit of the printout is the bus number. Then:
# modprobe i2c-dev
# i2cdetect <bus_number>
And post the output here. If you are brave and see that the address 0x1d
or 0x29 are printed in your output, you could try adding an entry to the
array you already mentioned above with the address you found. It may be
safer to do some sanity checking before, though.
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-27 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 14:23 Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration Paul Menzel
2023-02-27 19:27 ` Wolfram Sang [this message]
2023-02-28 10:39 ` Paul Menzel
2023-02-28 10:50 ` Wolfram Sang
2023-02-28 10:56 ` Paul Menzel
2023-02-28 11:00 ` Wolfram Sang
2023-07-19 19:32 ` 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=Y/0EIRsycj8EWjrz@ninjato \
--to=wsa@kernel.org \
--cc=Dell.Client.Kernel@dell.com \
--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