All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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: Mon, 25 Mar 2024 16:19:15 -0500	[thread overview]
Message-ID: <20240325211915.GA1449994@bhelgaas> (raw)
In-Reply-To: <20240312165905.1764507-1-andriy.shevchenko@linux.intel.com>

[+bcc Mateusz]

On Tue, Mar 12, 2024 at 06:59:05PM +0200, Andy Shevchenko wrote:
> Some devices support MSI interrupts. Let's at least try to use them in
> platforms that provide MSI capability.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/mfd/intel-lpss-pci.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/mfd/intel-lpss-pci.c b/drivers/mfd/intel-lpss-pci.c
> index 8c00e0c695c5..c36a101df7be 100644
> --- a/drivers/mfd/intel-lpss-pci.c
> +++ b/drivers/mfd/intel-lpss-pci.c
> @@ -54,7 +54,7 @@ static int intel_lpss_pci_probe(struct pci_dev *pdev,
>  	if (ret)
>  		return ret;
>  
> -	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:

  intel-lpss 0000:00:15.0: enabling device (0004 -> 0006)
  intel-lpss 0000:00:15.0: can't derive routing for PCI INT A
  intel-lpss 0000:00:15.0: PCI INT A: not connected
  intel-lpss: probe of 0000:00:15.0 failed with error -22
  intel-lpss 0000:00:15.2: enabling device (0004 -> 0006)
  intel-lpss 0000:00:15.2: can't derive routing for PCI INT C
  intel-lpss 0000:00:15.2: PCI INT C: not connected
  intel-lpss: probe of 0000:00:15.2 failed with error -22
  intel-lpss 0000:00:19.0: enabling device (0004 -> 0006)
  intel-lpss 0000:00:19.0: can't derive routing for PCI INT A
  intel-lpss 0000:00:19.0: PCI INT A: not connected
  intel-lpss: probe of 0000:00:19.0 failed with error -22
  intel-lpss 0000:00:19.1: enabling device (0004 -> 0006)
  intel-lpss 0000:00:19.1: can't derive routing for PCI INT B
  intel-lpss 0000:00:19.1: PCI INT B: not connected
  intel-lpss: probe of 0000:00:19.1 failed with error -22
  intel-lpss 0000:00:1e.0: enabling device (0004 -> 0006)
  intel-lpss 0000:00:1e.0: can't derive routing for PCI INT A
  intel-lpss 0000:00:1e.0: PCI INT A: not connected
  intel-lpss: probe of 0000:00:1e.0 failed with error -22
  intel-lpss 0000:00:1e.3: enabling device (0004 -> 0006)
  intel-lpss 0000:00:1e.3: can't derive routing for PCI INT D
  intel-lpss 0000:00:1e.3: PCI INT D: not connected
  intel-lpss: probe of 0000:00:1e.3 failed with error -22

I don't know if these are a _PRT bug (I think if a device advertises a
non-zero Interrupt Pin, the _PRT should tell us how it is routed), or
possibly a device bug (advertises Interrupt Pin == INTA when it should
advertise "no INTx used"), or something else.

Bjorn

  parent reply	other threads:[~2024-03-25 21:19 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 [this message]
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
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=20240325211915.GA1449994@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --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.