From: Wolfram Sang <wsa@kernel.org>
To: Marius Hoch <mail@mariushoch.de>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450
Date: Sun, 29 Oct 2023 18:17:06 +0100 [thread overview]
Message-ID: <ZT6TknMc+34NCqPG@shikoro> (raw)
In-Reply-To: <20230514103634.235917-1-mail@mariushoch.de>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
On Sun, May 14, 2023 at 12:36:32PM +0200, Marius Hoch wrote:
> 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(+)
Where are we with this patch set? Other solution found already?
Discussion stalled? Too much other things going on?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-10-29 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 10:36 [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450 Marius Hoch
2023-05-14 10:36 ` [PATCH 1/2] " Marius Hoch
2023-05-14 12:06 ` kernel test robot
2023-05-14 12:06 ` kernel test robot
2023-06-04 14:38 ` Jean Delvare
2023-06-18 13:08 ` Marius Hoch
2023-05-14 10:36 ` [PATCH 2/2] i2c: i801: Force no IRQ for further Dell Latitudes Marius Hoch
2023-05-23 18:03 ` [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450 Jean Delvare
2023-06-03 9:24 ` Marius Hoch
2023-06-04 14:01 ` Jean Delvare
2023-06-04 14:31 ` Jean Delvare
2023-06-04 20:41 ` Rudolf Marek
2023-06-18 12:52 ` Marius Hoch
2023-06-18 13:42 ` Marius Hoch
2023-06-19 15:19 ` Jean Delvare
2023-07-19 19:27 ` Pali Rohár
2023-10-29 17:17 ` 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=ZT6TknMc+34NCqPG@shikoro \
--to=wsa@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@mariushoch.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