From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Jay Fang <f.fangjian@huawei.com>
Cc: Sean V Kelley <sean.v.kelley@intel.com>, <bhelgaas@google.com>,
<rjw@rjwysocki.net>, <ashok.raj@kernel.org>,
<tony.luck@intel.com>,
<sathyanarayanan.kuppuswamy@linux.intel.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Subject: Re: [RFC PATCH 8/9] PCI/PME: Add RCEC PME handling
Date: Tue, 4 Aug 2020 10:47:13 +0100 [thread overview]
Message-ID: <20200804104713.0000767f@Huawei.com> (raw)
In-Reply-To: <edbcf3da-a1d5-e1b6-6a1a-a286429fc4e3@huawei.com>
On Tue, 4 Aug 2020 16:35:59 +0800
Jay Fang <f.fangjian@huawei.com> wrote:
> 在 2020/7/25 1:22, Sean V Kelley 写道:
> > The Root Complex Event Collectors(RCEC) appear as peers of Root Ports
> > and also have the PME capability. So add RCEC support to the current PME
> > service driver and attach the PME service driver to the RCEC device.
> >
> > Co-developed-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> > Signed-off-by: Sean V Kelley <sean.v.kelley@intel.com>
> > Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> > ---
> > drivers/pci/pcie/pme.c | 15 +++++++++++----
> > 1 file changed, 11 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/pci/pcie/pme.c b/drivers/pci/pcie/pme.c
> > index 6a32970bb731..87799166c96a 100644
> > --- a/drivers/pci/pcie/pme.c
> > +++ b/drivers/pci/pcie/pme.c
> > @@ -310,7 +310,10 @@ static int pcie_pme_can_wakeup(struct pci_dev *dev, void *ign)
> > static void pcie_pme_mark_devices(struct pci_dev *port)
> > {
> > pcie_pme_can_wakeup(port, NULL);
> > - if (port->subordinate)
> > +
> > + if (pci_pcie_type(port) == PCI_EXP_TYPE_RC_EC)
> > + pcie_walk_rcec(port, pcie_pme_can_wakeup, NULL);
> > + else if (port->subordinate)
> > pci_walk_bus(port->subordinate, pcie_pme_can_wakeup, NULL);
> > }
> >
> > @@ -320,10 +323,15 @@ static void pcie_pme_mark_devices(struct pci_dev *port)
> > */
> > static int pcie_pme_probe(struct pcie_device *srv)
> > {
> > - struct pci_dev *port;
> > + struct pci_dev *port = srv->port;
> > struct pcie_pme_service_data *data;
> > int ret;
> >
> > + /* Limit to Root Ports or Root Complex Event Collectors */
> > + if ((pci_pcie_type(port) != PCI_EXP_TYPE_RC_EC) &&
> > + (pci_pcie_type(port) != PCI_EXP_TYPE_ROOT_PORT))
> > + return -ENODEV;
> > +
> > data = kzalloc(sizeof(*data), GFP_KERNEL);
> > if (!data)
> > return -ENOMEM;
> > @@ -333,7 +341,6 @@ static int pcie_pme_probe(struct pcie_device *srv)
> > data->srv = srv;
> > set_service_data(srv, data);
> >
> > - port = srv->port;
> > pcie_pme_interrupt_enable(port, false);
> > pcie_clear_root_pme_status(port);
> >
> > @@ -445,7 +452,7 @@ static void pcie_pme_remove(struct pcie_device *srv)
> >
> > static struct pcie_port_service_driver pcie_pme_driver = {
> > .name = "pcie_pme",
> > - .port_type = PCI_EXP_TYPE_ROOT_PORT,
> > + .port_type = PCIE_ANY_PORT,
> Maybe we can use port_type for driver matching. There is no need
> to check the type of port in pcie_pme_probe function.
>
I walked into the same hole for the AER case.
port_type is effectively an enum so there is no way of specifying several
types unless you want to register different instances of pcie_port_service_driver
and that isn't currently possible.
The PCIE_ANY_PORT is a special case value.
https://elixir.bootlin.com/linux/latest/source/include/uapi/linux/pci_regs.h#L477
https://elixir.bootlin.com/linux/latest/source/drivers/pci/pci-driver.c#L1651
So odd corner case, but I think this is the right solution. Anything better
would require a lot more code to change.
Jonathan
>
> Jay
>
> > .service = PCIE_PORT_SERVICE_PME,
> >
> > .probe = pcie_pme_probe,
> >
next prev parent reply other threads:[~2020-08-04 9:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 17:22 [RFC PATCH 0/9] Add RCEC handling to PCI/AER Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 1/9] pci_ids: Add class code and extended capability for RCEC Sean V Kelley
2020-07-27 10:00 ` Jonathan Cameron
2020-07-27 10:21 ` Jonathan Cameron
2020-07-27 15:22 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 2/9] PCI: Extend Root Port Driver to support RCEC Sean V Kelley
2020-07-27 12:30 ` Jonathan Cameron
2020-07-27 15:05 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 3/9] PCI/portdrv: Add pcie_walk_rcec() to walk RCiEPs associated with RCEC Sean V Kelley
2020-07-27 10:49 ` Jonathan Cameron
2020-07-27 15:21 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 4/9] PCI/AER: Extend AER error handling to RCECs Sean V Kelley
2020-07-27 11:00 ` Jonathan Cameron
2020-07-27 14:58 ` Sean V Kelley
2020-07-27 14:04 ` Jonathan Cameron
2020-07-27 15:00 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 5/9] PCI/AER: Apply function level reset to RCiEP on fatal error Sean V Kelley
2020-07-25 10:05 ` kernel test robot
2020-07-27 11:17 ` Jonathan Cameron
2020-07-28 13:27 ` Zhuo, Qiuxu
2020-07-28 16:14 ` Sean V Kelley
2020-07-28 17:02 ` Jonathan Cameron
2020-07-28 17:42 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 6/9] PCI: Add 'rcec' field to pci_dev for associated RCiEPs Sean V Kelley
2020-07-27 11:23 ` Jonathan Cameron
2020-07-27 15:39 ` Sean V Kelley
2020-07-27 16:11 ` Jonathan Cameron
2020-07-27 16:28 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 7/9] PCI/AER: Add RCEC AER handling Sean V Kelley
2020-07-27 12:22 ` Jonathan Cameron
2020-07-27 15:19 ` Sean V Kelley
2020-07-27 17:14 ` Jonathan Cameron
2020-07-24 17:22 ` [RFC PATCH 8/9] PCI/PME: Add RCEC PME handling Sean V Kelley
2020-08-04 8:35 ` Jay Fang
2020-08-04 9:47 ` Jonathan Cameron [this message]
2020-07-24 17:22 ` [RFC PATCH 9/9] PCI/AER: Add RCEC AER error injection support Sean V Kelley
2020-07-27 12:37 ` [RFC PATCH 0/9] Add RCEC handling to PCI/AER Jonathan Cameron
2020-07-27 14:56 ` Sean V Kelley
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=20200804104713.0000767f@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=ashok.raj@kernel.org \
--cc=bhelgaas@google.com \
--cc=f.fangjian@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rjw@rjwysocki.net \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sean.v.kelley@intel.com \
--cc=tony.luck@intel.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.