linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jean Delvare <jdelvare@suse.com>
Cc: linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dell.Client.Kernel@dell.com, "Pali Rohár" <pali@kernel.org>
Subject: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
Date: Mon, 27 Feb 2023 15:23:13 +0100	[thread overview]
Message-ID: <97708c11-ac85-fb62-2c8e-d37739ca826f@molgen.mpg.de> (raw)

Dear Linux folks,


On the Dell Precision 3540, BIOS 1.23.0 12/19/2022, with Debian 
sid/unstable, Linux 6.1.12 logs the warning below:

     Accelerometer lis3lv02d is present on SMBus but its address is 
unknown, skipping registration

This warning was already logged by

     Linux version 5.19.0-2-amd64 (debian-kernel@lists.debian.org) 
(gcc-11 (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) 
2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)

with firmware BIOS 1.15.0 12/08/2021.

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`.


Kind regards,

Paul


PS: Some more logs:

```
[    0.000000] Linux version 6.1.0-5-amd64 
(debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU 
ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 
6.1.12-1 (2023-02-15)
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.1.0-5-amd64 
root=UUID=c9342a55-b747-4442-b2f4-bc03eb7a51cf ro quiet noisapnp 
log_buf_len=2M cryptomgr.notests btusb.enable_autosuspend=y 
random.trust_cpu=on drm.debug=0xe log_buf_len=8M
[…]
[    0.000000] DMI: Dell Inc. Precision 3540/0M14W7, BIOS 1.23.0 12/19/2022
[…]
[   20.631866] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[   20.631925] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[   20.662022] i801_smbus 0000:00:1f.4: Accelerometer lis3lv02d is 
present on SMBus but its address is unknown, skipping registration
[…]
```

             reply	other threads:[~2023-02-27 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 14:23 Paul Menzel [this message]
2023-02-27 19:27 ` Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration Wolfram Sang
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=97708c11-ac85-fb62-2c8e-d37739ca826f@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --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 \
    /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).