From: Oza Pawandeep <poza@codeaurora.org>
To: linux-pci@vger.kernel.org, okaya@codeaurora.org, timur@codeaurora.org
Cc: Oza Pawandeep <poza@codeaurora.org>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dongdong Liu <liudongdong3@huawei.com>,
linux-arm-msm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] PCI/portdrv: Add/Remove port services to the list
Date: Wed, 15 Nov 2017 10:26:46 +0530 [thread overview]
Message-ID: <1510721808-27164-3-git-send-email-poza@codeaurora.org> (raw)
In-Reply-To: <1510721808-27164-1-git-send-email-poza@codeaurora.org>
This patch adds and removes the port service to the service list.
Signed-off-by: Oza Pawandeep <poza@codeaurora.org>
diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
index a592103..6bfe986 100644
--- a/drivers/pci/pcie/portdrv_core.c
+++ b/drivers/pci/pcie/portdrv_core.c
@@ -454,6 +454,8 @@ static int pcie_port_probe_service(struct device *dev)
if (status)
return status;
+ list_add_tail(&pciedev->slist, &pciedev->port->service_list);
+
get_device(dev);
return 0;
}
@@ -477,6 +479,9 @@ static int pcie_port_remove_service(struct device *dev)
pciedev = to_pcie_device(dev);
driver = to_service_driver(dev->driver);
+
+ list_del(&pciedev->slist);
+
if (driver && driver->remove) {
driver->remove(pciedev);
put_device(dev);
diff --git a/include/linux/pcieport_if.h b/include/linux/pcieport_if.h
index b69769d..9d05621 100644
--- a/include/linux/pcieport_if.h
+++ b/include/linux/pcieport_if.h
@@ -31,6 +31,7 @@ struct pcie_device {
u32 service; /* Port service this device represents */
void *priv_data; /* Service Private Data */
struct device device; /* Generic Device Interface */
+ struct list_head slist; /* List of services */
};
#define to_pcie_device(d) container_of(d, struct pcie_device, device)
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.,
a Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-11-15 4:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 4:56 [PATCH v2 0/4] PCI: query active service list Oza Pawandeep
2017-11-15 4:56 ` [PATCH v2 1/4] PCI: Add port service list node for pci_dev Oza Pawandeep
2017-11-15 4:56 ` Oza Pawandeep [this message]
2017-11-15 4:56 ` [PATCH v2 3/4] PCI/portdrv: Implement interface to query the registered service Oza Pawandeep
2017-11-15 4:56 ` [PATCH v2 4/4] PCI/AER: Dont do recovery when DPC is enabled Oza Pawandeep
2017-11-15 21:14 ` Bjorn Helgaas
2017-11-16 14:03 ` Sinan Kaya
2017-11-16 20:17 ` Bjorn Helgaas
2017-11-16 20:52 ` Sinan Kaya
2017-11-18 0:02 ` Bjorn Helgaas
2017-11-19 16:41 ` Sinan Kaya
2017-11-21 16:25 ` David Laight
2017-11-21 16:43 ` Sinan Kaya
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=1510721808-27164-3-git-send-email-poza@codeaurora.org \
--to=poza@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=gabriele.paoloni@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=okaya@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=timur@codeaurora.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).