From: Grant Likely <grant.likely@secretlab.ca>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Yijing Wang <wangyijing@huawei.com>,
bhelgaas@google.com
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Liviu Dudau <Liviu.Dudau@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH v2] drivers: pci: move PCI domain assignment to\r generic PCI code
Date: Thu, 04 Dec 2014 10:36:59 +0000 [thread overview]
Message-ID: <20141204103659.34A77C40992@trevor.secretlab.ca> (raw)
In-Reply-To: <20141119093948.GA8751@red-moon>
On Wed, 19 Nov 2014 09:39:48 +0000
, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
wrote:
> On Wed, Nov 19, 2014 at 09:16:34AM +0000, Yijing Wang wrote:
> > Hi Lorenzo,
> > You should send this to Bjorn instead of cc. Other, why put the OF related
> > function in PCI core. Why not move it in drivers/of/of_pci.c ?
>
> I did, you missed v1, and the problem is that with ACPI forthcoming we
> do not want to have domain assignment scattered in different places,
> but part of core code (ie a single function that prevents mixed
> initialization from DT/counter and so on).
Bus specific OF code has generally been moving into the individual
subsystems. SPI and I2C are the prime examples. It's easier to
coordinate with the generic subsystem code when it lives in the same
place. The PCI code still lives in drivers/of/ simply because nobody has
been motivated enough to refactor it.
>
> Bjorn, are you fine with this patch ? Do you want me to resend it as
> part of the ARM 32 PCI domain refactoring [1] ? [1] depends on this
> patch going in first.
>
> Thanks,
> Lorenzo
>
> [1] http://www.spinics.net/lists/arm-kernel/msg375423.html
>
> > On 2014/11/11 0:41, Lorenzo Pieralisi wrote:
> > > The current logic used for PCI domain assignment in arm64
> > > pci_bus_assign_domain_nr() is flawed in that, depending on the host
> > > controllers configuration for a platform and the respective initialization
> > > sequence, core code may end up allocating PCI domain numbers from both DT and
> > > the core code generic domain counter, which would result in PCI domain
> > > allocation aliases/errors.
> > >
> > > This patch fixes the logic behind the PCI domain number assignment and
> > > moves the resulting code to generic PCI core code so that the same domain
> > > allocation logic is used on all platforms selecting
> > >
> > > CONFIG_PCI_DOMAINS_GENERIC
> > >
> > > instead of resorting to an arch specific implementation that might end up
> > > duplicating the PCI domain assignment logic wrongly.
> > >
> > > Cc: Arnd Bergmann <arnd@arndb.de>
> > > Cc: Liviu Dudau <liviu.dudau@arm.com>
> > > Cc: Bjorn Helgaas <bhelgaas@google.com>
> > > Cc: Rob Herring <robh+dt@kernel.org>
> > > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > > ---
> > > v1 => v2:
> > >
> > > - Moved generic pci_bus_assign_domain_nr() code to PCI core instead of
> > > adding an OF layer API
> > > - Updated commit log and code comments
> > >
> > > arch/arm64/kernel/pci.c | 22 ----------------------
> > > drivers/pci/pci.c | 50 +++++++++++++++++++++++++++++++++++++++++++++++++
> > > 2 files changed, 50 insertions(+), 22 deletions(-)
> > >
> > > diff --git a/arch/arm64/kernel/pci.c b/arch/arm64/kernel/pci.c
> > > index ce5836c..6f93c24 100644
> > > --- a/arch/arm64/kernel/pci.c
> > > +++ b/arch/arm64/kernel/pci.c
> > > @@ -46,25 +46,3 @@ int pcibios_add_device(struct pci_dev *dev)
> > >
> > > return 0;
> > > }
> > > -
> > > -
> > > -#ifdef CONFIG_PCI_DOMAINS_GENERIC
> > > -static bool dt_domain_found = false;
> > > -
> > > -void pci_bus_assign_domain_nr(struct pci_bus *bus, struct device *parent)
> > > -{
> > > - int domain = of_get_pci_domain_nr(parent->of_node);
> > > -
> > > - if (domain >= 0) {
> > > - dt_domain_found = true;
> > > - } else if (dt_domain_found == true) {
> > > - dev_err(parent, "Node %s is missing \"linux,pci-domain\" property in DT\n",
> > > - parent->of_node->full_name);
> > > - return;
> > > - } else {
> > > - domain = pci_get_new_domain_nr();
> > > - }
> > > -
> > > - bus->domain_nr = domain;
> > > -}
> > > -#endif
> > > diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> > > index 625a4ac..2279414 100644
> > > --- a/drivers/pci/pci.c
> > > +++ b/drivers/pci/pci.c
> > > @@ -10,6 +10,8 @@
> > > #include <linux/kernel.h>
> > > #include <linux/delay.h>
> > > #include <linux/init.h>
> > > +#include <linux/of.h>
> > > +#include <linux/of_pci.h>
> > > #include <linux/pci.h>
> > > #include <linux/pm.h>
> > > #include <linux/slab.h>
> > > @@ -4447,6 +4449,54 @@ int pci_get_new_domain_nr(void)
> > > {
> > > return atomic_inc_return(&__domain_nr);
> > > }
> > > +
> > > +#ifdef CONFIG_PCI_DOMAINS_GENERIC
> > > +
> > > +void pci_bus_assign_domain_nr(struct pci_bus *bus, struct device *parent)
> > > +{
> > > + static int use_dt_domains = -1;
> > > + int domain = of_get_pci_domain_nr(parent->of_node);
> > > +
> > > + /*
> > > + * Check DT domain and use_dt_domains values.
> > > + *
> > > + * If DT domain property is valid (domain >= 0) and
> > > + * use_dt_domains != 0, the DT assignment is valid since this means
> > > + * we have not previously allocated a domain number by using
> > > + * pci_get_new_domain_nr(); we should also update use_dt_domains to
> > > + * 1, to indicate that we have just assigned a domain number from
> > > + * DT.
> > > + *
> > > + * If DT domain property value is not valid (ie domain < 0), and we
> > > + * have not previously assigned a domain number from DT
> > > + * (use_dt_domains != 1) we should assign a domain number by
> > > + * using the:
> > > + *
> > > + * pci_get_new_domain_nr()
> > > + *
> > > + * API and update the use_dt_domains value to keep track of method we
> > > + * are using to assign domain numbers (use_dt_domains = 0).
> > > + *
> > > + * All other combinations imply we have a platform that is trying
> > > + * to mix domain numbers obtained from DT and pci_get_new_domain_nr(),
> > > + * which is a recipe for domain mishandling and it is prevented by
> > > + * invalidating the domain value (domain = -1) and printing a
> > > + * corresponding error.
> > > + */
> > > + if (domain >= 0 && use_dt_domains) {
> > > + use_dt_domains = 1;
> > > + } else if (domain < 0 && use_dt_domains != 1) {
> > > + use_dt_domains = 0;
> > > + domain = pci_get_new_domain_nr();
> > > + } else {
> > > + dev_err(parent, "Node %s has inconsistent \"linux,pci-domain\" property in DT\n",
> > > + parent->of_node->full_name);
> > > + domain = -1;
> > > + }
> > > +
> > > + bus->domain_nr = domain;
> > > +}
> > > +#endif
> > > #endif
> > >
> > > /**
> > >
> >
> >
> > --
> > Thanks!
> > Yijing
> >
> >
>
> _______________________________________________
> 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:[~2014-12-04 10:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 16:41 [RFC PATCH v2] drivers: pci: move PCI domain assignment to generic PCI code Lorenzo Pieralisi
[not found] ` <1415637706-2195-1-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
2014-11-12 10:09 ` Lorenzo Pieralisi
2014-11-12 10:19 ` Liviu Dudau
2014-11-12 10:39 ` Arnd Bergmann
2014-11-12 14:14 ` Lorenzo Pieralisi
2014-11-12 14:38 ` Arnd Bergmann
2014-11-19 9:16 ` Yijing Wang
2014-11-19 9:39 ` Lorenzo Pieralisi
2014-12-04 10:36 ` Grant Likely [this message]
2014-11-20 22:54 ` Bjorn Helgaas
2014-12-27 10:36 ` Lorenzo Pieralisi
2014-12-28 1:22 ` Bjorn Helgaas
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=20141204103659.34A77C40992@trevor.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=Catalin.Marinas@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=wangyijing@huawei.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).