linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>,
	"Kishon Vijay Abraham I" <kishon@ti.com>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Om Prakash Singh" <omp@nvidia.com>,
	"Vidya Sagar" <vidyas@nvidia.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] PCI: pci-epf-test: Register notifier if only core_init_notifier is enabled
Date: Tue, 8 Nov 2022 17:47:18 +0530	[thread overview]
Message-ID: <20221108121718.GB29115@thinkpad> (raw)
In-Reply-To: <20221102230902.GA6576@bhelgaas>

On Wed, Nov 02, 2022 at 06:09:02PM -0500, Bjorn Helgaas wrote:
> On Tue, Nov 01, 2022 at 06:31:07PM +0900, Kunihiko Hayashi wrote:
> > Hi Bjorn,
> > 
> > On 2022/10/29 2:06, Bjorn Helgaas wrote:
> > > On Thu, Aug 25, 2022 at 06:01:01PM +0900, Kunihiko Hayashi wrote:
> > > > Need to register pci_epf_test_notifier function event if only
> > > > core_init_notifier is enabled.
> > > > 
> > > > Fixes: 5e50ee27d4a5 ("PCI: pci-epf-test: Add support to defer core
> > > initialization")
> > > > Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> > > > Acked-by: Om Prakash Singh <omp@nvidia.com>
> > > > Acked-by: Kishon Vijay Abraham I <kishon@ti.com>
> > > > ---
> > > >   drivers/pci/endpoint/functions/pci-epf-test.c | 2 +-
> > > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> > > > This patch is a part of series "PCI: endpoint: Fix core_init_notifier
> > > feature".
> > > > The rest of the patches have been withdrawn.
> > > > 
> > > > Changes since v2:
> > > > - Add Acked-by lines
> > > > 
> > > > Changes since v1:
> > > > - Add Acked-by lines
> > > > 
> > > > diff --git a/drivers/pci/endpoint/functions/pci-epf-test.c
> > > b/drivers/pci/endpoint/functions/pci-epf-test.c
> > > > index 36b1801a061b..55283d2379a6 100644
> > > > --- a/drivers/pci/endpoint/functions/pci-epf-test.c
> > > > +++ b/drivers/pci/endpoint/functions/pci-epf-test.c
> > > > @@ -979,7 +979,7 @@ static int pci_epf_test_bind(struct pci_epf *epf)
> > > >   	if (ret)
> > > >   		epf_test->dma_supported = false;
> > > > -	if (linkup_notifier) {
> > > > +	if (linkup_notifier || core_init_notifier) {
> > > >   		epf->nb.notifier_call = pci_epf_test_notifier;
> > > >   		pci_epc_register_notifier(epc, &epf->nb);
> > > 
> > > Why does pci_epc_register_notifier() even exist?  It's not used at all
> > > except for this test code.
> > > 
> > > It would be better if infrastructure like this were connected with
> > > some user of it.
> >
> > This call was added by the commit 5779dd0a7dbd
> > ("PCI: endpoint: Use notification chain mechanism to notify EPC events to EPF").
> > 
> > I haven't followed the discussion, however, this commit say: "This
> > will also enable to add more events (in addition to linkup) in the
> > future."
> 
> 5779dd0a7dbd was 2.5 years ago.  It was probably a mistake to merge it
> then.  Usually we add infrastructure when we have a user for it,
> either in the very same patch or at least in a subsequent patch of the
> series.  
> 
> But Lorenzo has already merged this, so I guess this is moot.
> 
> He probably wouldn't object to a second patch that removes the fixed
> infrastructure if nobody uses it.  We can easily resurrect it if a
> need arises, and if that happens, we'll be glad that it has been
> fixed!
> 

I'm planning to submit a new EPF driver that makes use of this infrastructure
(although the callback mechanism).

Thanks,
Mani

> Bjorn

-- 
மணிவண்ணன் சதாசிவம்

      reply	other threads:[~2022-11-08 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  9:01 [PATCH v3] PCI: pci-epf-test: Register notifier if only core_init_notifier is enabled Kunihiko Hayashi
2022-10-27 14:02 ` Lorenzo Pieralisi
2022-10-28 17:06 ` Bjorn Helgaas
2022-11-01  9:31   ` Kunihiko Hayashi
2022-11-02 23:09     ` Bjorn Helgaas
2022-11-08 12:17       ` Manivannan Sadhasivam [this message]

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=20221108121718.GB29115@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=hayashi.kunihiko@socionext.com \
    --cc=helgaas@kernel.org \
    --cc=kishon@ti.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=omp@nvidia.com \
    --cc=vidyas@nvidia.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;
as well as URLs for NNTP newsgroup(s).