linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pingfan Liu <kernelfans@gmail.com>
To: linux-pci@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Christoph Hellwig <hch@infradead.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: [patchV2 0/2] shpchp: no claim on pcie port device
Date: Wed, 13 Jun 2018 14:29:55 +0800	[thread overview]
Message-ID: <1528871397-17917-1-git-send-email-kernelfans@gmail.com> (raw)

The Linux Device Driver Model allows a physical device to be handled
by only a single driver. But at present, both shpchp and portdrv_pci
claim PCI_CLASS_BRIDGE_PCI. This cause problems, such as the wrong
shutdown seq. This series keeps shpchp driver away from pcie port device.

V1 -> V2:
implement the checking in the process of matching, instead of probing,
which is too late.

Pingfan Liu (2):
  pci: introduce an extra method for matching in pci_driver
  pci/shpchp: no claim on pcie port device

 drivers/pci/hotplug/shpchp_core.c | 13 +++++++++++++
 drivers/pci/pci-driver.c          |  4 ++++
 include/linux/pci.h               |  2 ++
 3 files changed, 19 insertions(+)

-- 
2.7.4

             reply	other threads:[~2018-06-13  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13  6:29 Pingfan Liu [this message]
2018-06-13  6:29 ` [patchV2 1/2] pci: introduce an extra method for matching in pci_driver Pingfan Liu
2018-06-13  6:37   ` Christoph Hellwig
2018-06-13  7:28     ` Pingfan Liu
2018-06-13  6:29 ` [patchV2 2/2] pci/shpchp: no claim on pcie port device Pingfan Liu
2018-06-13 13:13   ` Bjorn Helgaas
2018-06-25  2:59     ` Pingfan Liu

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=1528871397-17917-1-git-send-email-kernelfans@gmail.com \
    --to=kernelfans@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=hch@infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).