All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Aleksandr Bezzubikov <zuban32s@gmail.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
	marcel@redhat.com, stable@vger.kernel.org
Subject: Re: pci: shpchp: set the bridge busmaster if MSI are enabled
Date: Tue, 1 Aug 2017 18:57:42 +0300	[thread overview]
Message-ID: <20170801185648-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1500387145-4216-1-git-send-email-zuban32s@gmail.com>

On Tue, Jul 18, 2017 at 05:12:25PM +0300, Aleksandr Bezzubikov wrote:
> An MSI-based SHPC built in PCI bridges can configure hotplugged devices
> only if they notify the bridge with MSI.
> But they can't trigger interrupt without the bridge being busmaster,
> that's why it should be enabled.
> 
> Signed-off-by: Aleksandr Bezzubikov <zuban32s@gmail.com>
> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>


Given there's pci_enable_msi above, not enabling bus master
seems like a very strange thing to do.

Acked-by: Michael S. Tsirkin <mst@redhat.com>

This also looks like a good candidate for stable.

> ---
>  drivers/pci/hotplug/shpchp_hpc.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/pci/hotplug/shpchp_hpc.c b/drivers/pci/hotplug/shpchp_hpc.c
> index de0ea47..e5824c7 100644
> --- a/drivers/pci/hotplug/shpchp_hpc.c
> +++ b/drivers/pci/hotplug/shpchp_hpc.c
> @@ -1062,6 +1062,8 @@ int shpc_init(struct controller *ctrl, struct pci_dev *pdev)
>  		if (rc) {
>  			ctrl_info(ctrl, "Can't get msi for the hotplug controller\n");
>  			ctrl_info(ctrl, "Use INTx for the hotplug controller\n");
> +		} else {
> +			pci_set_master(pdev);
>  		}
>  
>  		rc = request_irq(ctrl->pci_dev->irq, shpc_isr, IRQF_SHARED,

  parent reply	other threads:[~2017-08-01 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 14:12 [PATCH] pci: shpchp: set the bridge busmaster if MSI are enabled Aleksandr Bezzubikov
2017-07-19 13:36 ` Marcel Apfelbaum
2017-08-01 15:56   ` Marcel Apfelbaum
2017-07-23 20:18 ` Alexander Bezzubikov
2017-07-24 14:56   ` Alex Williamson
2017-07-24 15:07     ` Alexander Bezzubikov
2017-08-01 15:57 ` Michael S. Tsirkin [this message]
2017-08-02 22:35 ` Bjorn Helgaas
2017-08-02 22:48   ` Alexander Bezzubikov
2017-08-03 16:34     ` 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=20170801185648-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=marcel@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=zuban32s@gmail.com \
    /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.