All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	Michal Simek <monstr@monstr.eu>,
	Grant Likely <grant.likely@linaro.org>,
	devicetree@vger.kernel.org
Subject: Re: [RFC] Architecture independent pcibios?
Date: Wed, 09 Oct 2013 07:28:55 +1100	[thread overview]
Message-ID: <1381264135.645.230.camel@pasglop> (raw)
In-Reply-To: <525438F6.3090600@gmail.com>

On Tue, 2013-10-08 at 11:55 -0500, Rob Herring wrote:

> > I wonder if pci_process_bridge_OF_ranges() would fit somewhere in
> > drivers/of?  The implementations I looked at are mostly concerned with
> > parsing OF resources, and they don't have much to do with PCI
> > directly.
> 
> This was being done until Ben weighed in:
> 
> https://lkml.org/lkml/2013/5/4/103

Well, I proposed an alternative (better) approach which I of course had
no time to actually implement yet :-)

I have done the changes I needed to do to powerpc
pci_process_bridge_OF_ranges so it would be possible to move that now to
a generic place, but I still think it's not a great idea. It means the
pci_controller structure with its resources will have to become generic
which somewhat overlaps with the pci_host_bridge that Bjorn introduced,
so that's really not great.

I still think an arch with DT and simpler PCI code that powerpc could
start looking at the transition to a better model that I hinted at...

Cheers,
Ben.



  parent reply	other threads:[~2013-10-08 20:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 14:42 [RFC] Architecture independent pcibios? Liviu Dudau
2013-10-08 16:32 ` Bjorn Helgaas
2013-10-08 16:32   ` Bjorn Helgaas
2013-10-08 16:55   ` Rob Herring
2013-10-08 17:20     ` Andrew Murray
2013-10-08 20:32       ` Benjamin Herrenschmidt
2013-10-08 20:28     ` Benjamin Herrenschmidt [this message]
2013-10-09  9:09       ` Liviu Dudau
2013-10-09 10:04         ` Liviu Dudau
2013-10-09 10:37         ` Benjamin Herrenschmidt
2013-10-09 10:45           ` Liviu Dudau
2013-10-09 14:30             ` Bjorn Helgaas
2013-10-09 16:23               ` Liviu Dudau
2013-10-15 11:48         ` Grant Likely
2013-10-08 17:13   ` Liviu Dudau
2013-10-08 18:58     ` Bjorn Helgaas
2013-10-08 20:31     ` Benjamin Herrenschmidt
2013-10-09 11:52       ` Michal Simek

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=1381264135.645.230.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Liviu.Dudau@arm.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=olof@lixom.net \
    --cc=robherring2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.