From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: Bjorn Helgaas <helgaas@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Bjorn Helgaas <bhelgaas@google.com>, Len Brown <lenb@kernel.org>,
Borislav Petkov <bp@suse.de>, Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] acpi,pci: handle duplicate IRQ routing entries returned from _PRT
Date: Sat, 12 Nov 2022 21:07:15 +0100 [thread overview]
Message-ID: <35cfe433-bafa-9aeb-20ad-2f275f585b6c@o2.pl> (raw)
In-Reply-To: <20221112002023.GA764787@bhelgaas>
W dniu 12.11.2022 o 01:20, Bjorn Helgaas pisze:
> [+cc Jean, linux-i2c]
>
> On Sat, Sep 17, 2022 at 11:09:44AM +0200, Mateusz Jończyk wrote:
>> On some platforms, the ACPI _PRT function returns duplicate interrupt
>> routing entries. Linux uses the first matching entry, but sometimes the
>> second matching entry contains the correct interrupt vector.
> Rafael, Jean, what do you think about this? It seems like kind of a
> lot of infrastructure to deal with this oddness, but I'm not really
> opposed to it.
>
> This is in i2c-i801.c, which seems to have some support for polling;
> maybe it could make smart enough to complain and automatically switch
> to polling if a timeout occurs.
>
> Or maybe we scan the entire _PRT and let the match win (instead of the
> first as we do today).
>
> Or ...?
>
> Google finds a lot of hits for "i801_smbus" "timeout waiting for
> interrupt", but I can't tell whether they're a similar _PRT issue or
> something else.
>
>> This happens on a Dell Latitude E6500 laptop with the i2c-i801 Intel
>> SMBus controller. This controller was nonfunctional unless its interrupt
>> usage was disabled (using the "disable_features=0x10" module parameter).
Hello,
I have prepared a lean patch that only prints a warning when there are
two matching entries in the table returned from _PRT (I will send it in the
next e-mail). Perhaps it could be merged and then after a release or two
it will be known how widespread this problem is.
Greetings,
Mateusz
next prev parent reply other threads:[~2022-11-12 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 9:09 [PATCH v2] acpi,pci: handle duplicate IRQ routing entries returned from _PRT Mateusz Jończyk
2022-09-27 19:28 ` Bjorn Helgaas
2022-09-29 18:03 ` Mateusz Jończyk
2022-11-12 0:20 ` Bjorn Helgaas
2022-11-12 20:07 ` Mateusz Jończyk [this message]
2022-11-12 20:09 ` [PATCH] acpi,pci: warn about " Mateusz Jończyk
2022-11-13 17:34 ` [PATCH v2] " Mateusz Jończyk
2022-11-15 8:36 ` Jean Delvare
2022-11-23 20:28 ` Mateusz Jończyk
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=35cfe433-bafa-9aeb-20ad-2f275f585b6c@o2.pl \
--to=mat.jonczyk@o2.pl \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=helgaas@kernel.org \
--cc=jdelvare@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@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