devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: add missing DT binding for linux,pci-domain property
Date: Tue, 04 Nov 2014 13:07:47 +0100	[thread overview]
Message-ID: <2606632.6m38glseTk@wuerfel> (raw)
In-Reply-To: <20141104120052.GE11102@e106497-lin.cambridge.arm.com>

On Tuesday 04 November 2014 12:00:52 Liviu Dudau wrote:
> 
> While the description is potentially correct, what it fails to explain is that the
> choice of using the property or generating an unstable (across boots) unique
> number is actually the choice of the host bridge driver at the moment. I know that
> my earlier implementations were defaulting to the automatic numbering, but that has
> been dropped from the final series as Rob Herring was objecting to it.
> 
> There is still scope to adopt a wide policy here, but for now it should say something
> to the tune:
> 
>    If present this property assigns a fixed PCI domain number to a host bridge,
>    otherwise an unstable (across boots) unique number will be assigned.
>    If you decide to use the property to assign a fixed PCI domain number to a host
>    bridge you have to ensure that all the host bridge drivers present in the system
>    follow the same policy. Otherwise, potentially conflicting domain numbers
>    may be assigned to root busses behind different host bridges.

But with the latest change to the domain handling, all drivers would implement
this. I would just mention that Linux kernels older than 3.19 are probably
going to ignore this property.

	Arnd

  reply	other threads:[~2014-11-04 12:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 11:47 [PATCH] PCI: add missing DT binding for linux,pci-domain property Lucas Stach
2014-11-04 12:00 ` Liviu Dudau
2014-11-04 12:07   ` Arnd Bergmann [this message]
2014-11-04 12:20     ` Lucas Stach
2014-11-06 15:08     ` Lucas Stach
2014-11-06 19:55       ` Arnd Bergmann
2014-11-04 17:05 ` Kumar Gala
2014-11-05 23:17 ` Bjorn Helgaas
2014-11-06 10:05   ` Liviu Dudau
2014-11-06 11:42     ` Arnd Bergmann
2014-11-06 12:36       ` Liviu Dudau
2014-11-06 13:29         ` Arnd Bergmann
2014-11-06 14:57     ` Rob Herring
2014-11-06 15:30       ` Liviu Dudau
2014-11-06 19:46         ` Rob Herring
2014-11-07 10:17           ` Liviu Dudau
2014-11-07 14:00             ` Rob Herring
2014-11-07 15:23               ` Liviu Dudau
2014-11-07 15:37                 ` Rob Herring

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=2606632.6m38glseTk@wuerfel \
    --to=arnd@arndb.de \
    --cc=Liviu.Dudau@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=Pawel.Moll@arm.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=l.stach@pengutronix.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh+dt@kernel.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).