linux-kernel - Re: [PATCH] platform/x86: dell-lis3lv02d: Add Precision 3551

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f2e0909b-0dc2-448c-bbc9-d7dfa351412c@molgen.mpg.de>
Date: Fri, 11 Jul 2025 09:18:21 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Jan-Niklas Burfeind <kernel@...ionpri.me>
Cc: linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org,
 Hans de Goede <hansg@...nel.org>
Subject: Re: [PATCH] platform/x86: dell-lis3lv02d: Add Precision 3551

Dear Jan-Niklas,


Thank you for your patch.

Am 10.07.25 um 21:09 schrieb Jan-Niklas Burfeind:
> This marks 0x29 as accelerometer address on Dell Precision 3551.
> 
> I followed previous works of Paul Menzel and Hans de Goede to verify it:
> 
> $ cd /sys/bus/pci/drivers/i801_smbus/0000\:00\:1f.4
> 
> $ ls -d i2c-?
> i2c-0
> 
> $ sudo modprobe i2c-dev
> 
> $ sudo i2cdetect 0
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-0.
> 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-0/new_device
> lis3lv02d 0x29
> 
> $ sudo dmesg
> [    0.000000] Linux version 6.12.28 (nixbld@...alhost) (gcc (GCC) 14.2.1 20250322, GNU ld (GNU Binutils) 2.44) #1-NixOS SMP PREEMPT_DYNAMIC Fri May  9 07:50:53 UTC 2025
> [...]
> [    0.000000] DMI: Dell Inc. Precision 3551/07YHW8, BIOS 1.18.0 10/03/2022
> [...]
> [ 3749.077624] lis3lv02d_i2c 0-0029: supply Vdd not found, using dummy regulator
> [ 3749.077732] lis3lv02d_i2c 0-0029: supply Vdd_IO not found, using dummy regulator
> [ 3749.098674] lis3lv02d: 8 bits 3DC sensor found
> [ 3749.182480] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input28
> [ 3749.182899] i2c i2c-0: new_device: Instantiated device lis3lv02d at 0x29
> 
> Signed-off-by: Jan-Niklas Burfeind <kernel@...ionpri.me>
> ---
>   drivers/platform/x86/dell/dell-lis3lv02d.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/platform/x86/dell/dell-lis3lv02d.c b/drivers/platform/x86/dell/dell-lis3lv02d.c
> index 0791118dd6b7..732de5f556f8 100644
> --- a/drivers/platform/x86/dell/dell-lis3lv02d.c
> +++ b/drivers/platform/x86/dell/dell-lis3lv02d.c
> @@ -49,6 +49,7 @@ static const struct dmi_system_id lis3lv02d_devices[] __initconst = {
>   	DELL_LIS3LV02D_DMI_ENTRY("Latitude E6330",     0x29),
>   	DELL_LIS3LV02D_DMI_ENTRY("Latitude E6430",     0x29),
>   	DELL_LIS3LV02D_DMI_ENTRY("Precision 3540",     0x29),
> +	DELL_LIS3LV02D_DMI_ENTRY("Precision 3551",     0x29),
>   	DELL_LIS3LV02D_DMI_ENTRY("Precision M6800",    0x29),
>   	DELL_LIS3LV02D_DMI_ENTRY("Vostro V131",        0x1d),
>   	DELL_LIS3LV02D_DMI_ENTRY("Vostro 5568",        0x29),

Reviewed-by: Paul Menzel <pmenzel@...gen.mpg.de>


Kind regards,

Paul


PS: Just a heads-up, that you have a DMARC policy set:

     $ dig txt _dmarc.aiyionpri.me +short
     "v=DMARC1;p=reject;"

I believe STRATO enabled this for all their customers, breaking 
deliveries for addressees enforcing the DMARC policy, as you do not have 
any SPF entries for example [1]. I recommend to deactivate the setting 
by selecting *Keine STRATO-DMARC-Regel* [2], and to look for another 
provider, as their support was not helpful at all and did not even 
understand the problem, and hasn’t replied to my latest response in 
several weeks. (And I didn’t get the initial emails informing about the 
change.)


[1]: 
https://www.borncity.com/blog/2025/06/06/strato-aktiviert-automatisch-eine-dmarc-pruefung-fuer-mails/
[2]: https://www.strato.de/faq/hosting/dmarc-bei-strato-aktivieren/