From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Lee Jones <lee@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] mfd: intel-lpss: Switch over to MSI interrupts
Date: Tue, 26 Mar 2024 18:21:47 +0200 [thread overview]
Message-ID: <ZgL2G4ItkFlQ7cqS@smile.fi.intel.com> (raw)
In-Reply-To: <20240325211915.GA1449994@bhelgaas>
On Mon, Mar 25, 2024 at 04:19:15PM -0500, Bjorn Helgaas wrote:
> On Tue, Mar 12, 2024 at 06:59:05PM +0200, Andy Shevchenko wrote:
...
> > - ret = pci_alloc_irq_vectors(pdev, 1, 1, PCI_IRQ_LEGACY);
> > + ret = pci_alloc_irq_vectors(pdev, 1, 1, PCI_IRQ_ALL_TYPES);
> > if (ret < 0)
> > return ret;
>
> I guess at least some of these devices do support INTx, since we
> always used INTx previously, right?
>
> There are a bunch of bug reports complaining about a lack of _PRT
> entries for them, e.g., these from
> https://bugzilla.kernel.org/show_bug.cgi?id=212261#c24:
But this is not related to my patch, and the mentioned bug report seems about
all AMD and Intel platforms.
Can you, please, elaborate what the relation to my patch?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-03-26 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 16:59 [PATCH v1 1/1] mfd: intel-lpss: Switch over to MSI interrupts Andy Shevchenko
2024-03-21 16:02 ` (subset) " Lee Jones
2024-03-25 21:19 ` Bjorn Helgaas
2024-03-26 10:06 ` Mateusz K
2024-03-26 14:41 ` Andy Shevchenko
2024-03-26 14:50 ` Mateusz K
2024-03-26 15:25 ` Andy Shevchenko
2024-03-26 15:24 ` Andy Shevchenko
2024-03-27 13:17 ` Lee Jones
2024-03-27 13:24 ` Andy Shevchenko
2024-03-27 14:12 ` Lee Jones
2024-03-27 14:23 ` Andy Shevchenko
2024-03-26 16:21 ` Andy Shevchenko [this message]
2024-03-26 21:01 ` Bjorn Helgaas
2024-03-26 21:22 ` Andy Shevchenko
2024-03-26 22:09 ` Bjorn Helgaas
2024-03-26 22:25 ` Andy Shevchenko
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=ZgL2G4ItkFlQ7cqS@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.