From: Vidya Sagar <vidyas@nvidia.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, <jingoohan1@gmail.com>,
<gustavo.pimentel@synopsys.com>, <lorenzo.pieralisi@arm.com>,
<andrew.murray@arm.com>, <bhelgaas@google.com>,
<thierry.reding@gmail.com>
Cc: <Jisheng.Zhang@synaptics.com>, <jonathanh@nvidia.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kthota@nvidia.com>, <mmaddireddy@nvidia.com>,
<sagar.tv@gmail.com>
Subject: Re: [PATCH 4/4] PCI: pci-epf-test: Add support to defer core initialization
Date: Sun, 1 Dec 2019 19:59:17 +0530 [thread overview]
Message-ID: <958fcc14-6794-0328-5c31-0dcc845ee646@nvidia.com> (raw)
In-Reply-To: <e8e3b8b6-d115-b4d4-19c5-1eae1d8abd0f@ti.com>
On 11/27/2019 2:50 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On 13/11/19 2:38 PM, Vidya Sagar wrote:
>> Add support to defer core initialization and to receive a notifier
>> when core is ready to accommodate platforms where core is not for
>> initialization untile reference clock from host is available.
>>
>> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
>> ---
>> drivers/pci/endpoint/functions/pci-epf-test.c | 114 ++++++++++++------
>> 1 file changed, 77 insertions(+), 37 deletions(-)
>>
>> diff --git a/drivers/pci/endpoint/functions/pci-epf-test.c b/drivers/pci/endpoint/functions/pci-epf-test.c
>> index bddff15052cc..068024fab544 100644
>> --- a/drivers/pci/endpoint/functions/pci-epf-test.c
>> +++ b/drivers/pci/endpoint/functions/pci-epf-test.c
>> @@ -360,18 +360,6 @@ static void pci_epf_test_cmd_handler(struct work_struct *work)
>> msecs_to_jiffies(1));
>> }
>>
>> -static int pci_epf_test_notifier(struct notifier_block *nb, unsigned long val,
>> - void *data)
>> -{
>> - struct pci_epf *epf = container_of(nb, struct pci_epf, nb);
>> - struct pci_epf_test *epf_test = epf_get_drvdata(epf);
>> -
>> - queue_delayed_work(kpcitest_workqueue, &epf_test->cmd_handler,
>> - msecs_to_jiffies(1));
>> -
>> - return NOTIFY_OK;
>> -}
>> -
>> static void pci_epf_test_unbind(struct pci_epf *epf)
>> {
>> struct pci_epf_test *epf_test = epf_get_drvdata(epf);
>> @@ -428,6 +416,78 @@ static int pci_epf_test_set_bar(struct pci_epf *epf)
>> return 0;
>> }
>>
>> +static int pci_epf_test_core_init(struct pci_epf *epf)
>> +{
>> + struct pci_epf_header *header = epf->header;
>> + const struct pci_epc_features *epc_features;
>> + struct pci_epc *epc = epf->epc;
>> + struct device *dev = &epf->dev;
>> + bool msix_capable = false;
>> + bool msi_capable = true;
>> + int ret;
>> +
>> + epc_features = pci_epc_get_features(epc, epf->func_no);
>> + if (epc_features) {
>> + msix_capable = epc_features->msix_capable;
>> + msi_capable = epc_features->msi_capable;
>> + }
>> +
>> + ret = pci_epc_write_header(epc, epf->func_no, header);
>> + if (ret) {
>> + dev_err(dev, "Configuration header write failed\n");
>> + return ret;
>> + }
>> +
>> + ret = pci_epf_test_set_bar(epf);
>> + if (ret)
>> + return ret;
>> +
>> + if (msi_capable) {
>> + ret = pci_epc_set_msi(epc, epf->func_no, epf->msi_interrupts);
>> + if (ret) {
>> + dev_err(dev, "MSI configuration failed\n");
>> + return ret;
>> + }
>> + }
>> +
>> + if (msix_capable) {
>> + ret = pci_epc_set_msix(epc, epf->func_no, epf->msix_interrupts);
>> + if (ret) {
>> + dev_err(dev, "MSI-X configuration failed\n");
>> + return ret;
>> + }
>> + }
>> +
>> + return 0;
>> +}
>> +
>> +static int pci_epf_test_notifier(struct notifier_block *nb, unsigned long val,
>> + void *data)
>> +{
>> + struct pci_epf *epf = container_of(nb, struct pci_epf, nb);
>> + struct pci_epf_test *epf_test = epf_get_drvdata(epf);
>> + int ret;
>> +
>> + switch (val) {
>> + case CORE_INIT:
>> + ret = pci_epf_test_core_init(epf);
>> + if (ret)
>> + return NOTIFY_BAD;
>> + break;
>> +
>> + case LINK_UP:
>> + queue_delayed_work(kpcitest_workqueue, &epf_test->cmd_handler,
>> + msecs_to_jiffies(1));
>> + break;
>> +
>> + default:
>> + dev_err(&epf->dev, "Invalid EPF test notifier event\n");
>> + return NOTIFY_BAD;
>> + }
>> +
>> + return NOTIFY_OK;
>> +}
>> +
>> static int pci_epf_test_alloc_space(struct pci_epf *epf)
>> {
>> struct pci_epf_test *epf_test = epf_get_drvdata(epf);
>> @@ -496,12 +556,11 @@ static int pci_epf_test_bind(struct pci_epf *epf)
>> {
>> int ret;
>> struct pci_epf_test *epf_test = epf_get_drvdata(epf);
>> - struct pci_epf_header *header = epf->header;
>> const struct pci_epc_features *epc_features;
>> enum pci_barno test_reg_bar = BAR_0;
>> struct pci_epc *epc = epf->epc;
>> - struct device *dev = &epf->dev;
>> bool linkup_notifier = false;
>> + bool skip_core_init = false;
>> bool msix_capable = false;
>> bool msi_capable = true;
>>
>> @@ -511,6 +570,7 @@ static int pci_epf_test_bind(struct pci_epf *epf)
>> epc_features = pci_epc_get_features(epc, epf->func_no);
>> if (epc_features) {
>> linkup_notifier = epc_features->linkup_notifier;
>> + skip_core_init = epc_features->skip_core_init;
>> msix_capable = epc_features->msix_capable;
>> msi_capable = epc_features->msi_capable;
>
> Are these used anywhere in this function?
Nope. I'll remove them.
>> test_reg_bar = pci_epc_get_first_free_bar(epc_features);
>> @@ -520,34 +580,14 @@ static int pci_epf_test_bind(struct pci_epf *epf)
>> epf_test->test_reg_bar = test_reg_bar;
>> epf_test->epc_features = epc_features;
>>
>> - ret = pci_epc_write_header(epc, epf->func_no, header);
>> - if (ret) {
>> - dev_err(dev, "Configuration header write failed\n");
>> - return ret;
>> - }
>> -
>> ret = pci_epf_test_alloc_space(epf);
>> if (ret)
>> return ret;
>>
>> - ret = pci_epf_test_set_bar(epf);
>> - if (ret)
>> - return ret;
>> -
>> - if (msi_capable) {
>> - ret = pci_epc_set_msi(epc, epf->func_no, epf->msi_interrupts);
>> - if (ret) {
>> - dev_err(dev, "MSI configuration failed\n");
>> - return ret;
>> - }
>> - }
>> -
>> - if (msix_capable) {
>> - ret = pci_epc_set_msix(epc, epf->func_no, epf->msix_interrupts);
>> - if (ret) {
>> - dev_err(dev, "MSI-X configuration failed\n");
>> + if (!skip_core_init) {
>> + ret = pci_epf_test_core_init(epf);
>> + if (ret)
>> return ret;
>> - }
>> }
>>
>> if (linkup_notifier) {
>
> This could as well be moved to pci_epf_test_core_init().
Yes, but I would like to keep only the code that touches hardware in pci_epf_test_core_init()
to minimize the time it takes to execute it. Is there any strong reason to move it? if not,
I would prefer to leave it here in this function itself.
>
> Thanks
> Kishon
>
next prev parent reply other threads:[~2019-12-01 14:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:08 [PATCH 0/4] " Vidya Sagar
2019-11-13 9:08 ` [PATCH 1/4] PCI: dwc: Add new feature to skip " Vidya Sagar
2019-11-27 8:14 ` Kishon Vijay Abraham I
2019-11-27 8:40 ` Vidya Sagar
2019-11-27 9:18 ` Kishon Vijay Abraham I
2019-11-27 9:48 ` Christoph Hellwig
2019-11-29 14:40 ` Vidya Sagar
2019-12-05 9:59 ` Vidya Sagar
2019-12-05 10:04 ` Kishon Vijay Abraham I
2020-01-03 9:40 ` Vidya Sagar
2019-11-13 9:08 ` [PATCH 2/4] PCI: endpoint: Add notification for core init completion Vidya Sagar
2019-11-27 8:18 ` Kishon Vijay Abraham I
2019-11-27 8:22 ` Kishon Vijay Abraham I
2019-11-13 9:08 ` [PATCH 3/4] PCI: dwc: Add API to notify core initialization completion Vidya Sagar
2019-11-13 9:08 ` [PATCH 4/4] PCI: pci-epf-test: Add support to defer core initialization Vidya Sagar
2019-11-27 9:20 ` Kishon Vijay Abraham I
2019-12-01 14:29 ` Vidya Sagar [this message]
2019-12-05 11:22 ` Kishon Vijay Abraham I
2020-01-03 9:40 ` Vidya Sagar
2019-11-18 6:55 ` [PATCH 0/4] " Vidya Sagar
2019-11-18 16:43 ` Jingoo Han
2019-11-25 4:33 ` Vidya Sagar
2019-11-25 4:45 ` Kishon Vijay Abraham I
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=958fcc14-6794-0328-5c31-0dcc845ee646@nvidia.com \
--to=vidyas@nvidia.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=andrew.murray@arm.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mmaddireddy@nvidia.com \
--cc=sagar.tv@gmail.com \
--cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®