Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Lukas Wunner" <lukas@wunner.de>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] PCI/bwctrl: Remove IRQF_ONESHOT and handle hardirqs instead
Date: Fri, 15 Nov 2024 19:29:31 +0100	[thread overview]
Message-ID: <eb1da92d-b7b7-43ae-959e-3f02c6e2c91d@gmx.net> (raw)
In-Reply-To: <20241115165717.15233-1-ilpo.jarvinen@linux.intel.com>

Hi,

Am 15.11.24 um 17:57 schrieb Ilpo Järvinen:
> bwctrl cannot use IRQF_ONESHOT because it shares interrupt with other
> service drivers that are not using IRQF_ONESHOT nor compatible with it.
>
> Remove IRQF_ONESHOT from bwctrl and convert the irq thread to hardirq
> handler. Rename the handler to pcie_bwnotif_irq() to indicate its new
> purpose.
>
> The IRQ handler is simple enough to not require not require other
> changes.
>
> Fixes: 058a4cb11620 ("PCI/bwctrl: Re-add BW notification portdrv as PCIe BW controller")
> Reported-by: Stefan Wahren <wahrenst@gmx.net>
> Link: https://lore.kernel.org/linux-pci/dcd660fd-a265-4f47-8696-776a85e097a0@gmx.net/
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
this fixed the probing issue. Thanks

Tested-by: Stefan Wahren <wahrenst@gmx.net>

Is there anything more I can/should test?

> ---
>   drivers/pci/pcie/bwctrl.c | 8 +++-----
>   1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pci/pcie/bwctrl.c b/drivers/pci/pcie/bwctrl.c
> index ff5d12e01f9c..a6c65bbe3735 100644
> --- a/drivers/pci/pcie/bwctrl.c
> +++ b/drivers/pci/pcie/bwctrl.c
> @@ -230,7 +230,7 @@ static void pcie_bwnotif_disable(struct pci_dev *port)
>   				   PCI_EXP_LNKCTL_LBMIE | PCI_EXP_LNKCTL_LABIE);
>   }
>
> -static irqreturn_t pcie_bwnotif_irq_thread(int irq, void *context)
> +static irqreturn_t pcie_bwnotif_irq(int irq, void *context)
>   {
>   	struct pcie_device *srv = context;
>   	struct pcie_bwctrl_data *data = srv->port->link_bwctrl;
> @@ -302,10 +302,8 @@ static int pcie_bwnotif_probe(struct pcie_device *srv)
>   	if (ret)
>   		return ret;
>
> -	ret = devm_request_threaded_irq(&srv->device, srv->irq, NULL,
> -					pcie_bwnotif_irq_thread,
> -					IRQF_SHARED | IRQF_ONESHOT,
> -					"PCIe bwctrl", srv);
> +	ret = devm_request_irq(&srv->device, srv->irq, pcie_bwnotif_irq,
> +			       IRQF_SHARED, "PCIe bwctrl", srv);
>   	if (ret)
>   		return ret;
>


  reply	other threads:[~2024-11-15 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 16:57 [PATCH 1/1] PCI/bwctrl: Remove IRQF_ONESHOT and handle hardirqs instead Ilpo Järvinen
2024-11-15 18:29 ` Stefan Wahren [this message]
2024-11-15 21:02 ` Bjorn Helgaas
2024-11-16 14:40   ` Ilpo Järvinen
2024-11-16 16:10     ` Bjorn Helgaas

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=eb1da92d-b7b7-43ae-959e-3f02c6e2c91d@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.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