linux-kernel - [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20230514103634.235917-1-mail@mariushoch.de>
Date:   Sun, 14 May 2023 12:36:32 +0200
From:   Marius Hoch <mail@...iushoch.de>
To:     Jean Delvare <jdelvare@...e.com>, linux-i2c@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     Marius Hoch <mail@...iushoch.de>
Subject: [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450

The Dell Latitude E7450 uses IRQ 18 for the accelerometer,
but also claims that the SMBus uses IRQ 18. This will
result in:

i801_smbus 0000:00:1f.3: PCI INT C: failed to register GSI
i801_smbus 0000:00:1f.3: Failed to enable SMBus PCI device (-16)
i801_smbus: probe of 0000:00:1f.3 failed with error -16

Force the SMBus IRQ to IRQ_NOTCONNECTED in this case, so that
we fall back to polling, which also seems to be what the (very
dated) Windows 7 drivers on the Dell Latitude E7450 do.

This was tested on Dell Latitude E7450.

I chose to explicitly list all affected devices here, but
alternatively it would be possible to do this programmatically:
If the initial pcim_enable_device fails and we're on (any)
Dell Latitude, re-try with IRQ_NOTCONNECTED.

Marius Hoch (2):
  i2c: i801: Force no IRQ for Dell Latitude E7450
  i2c: i801: Force no IRQ for further Dell Latitudes

 drivers/i2c/busses/i2c-i801.c | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

base-commit: cc3c44c9fda264c6d401be04e95449a57c1231c6
-- 
2.40.1