From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] powerpc/pci: move pci_64.c device tree scanning code into pci-common.c
Date: Fri, 21 Aug 2009 16:05:29 +1000 [thread overview]
Message-ID: <1250834729.7625.5.camel@pasglop> (raw)
In-Reply-To: <20090821053014.2289.59798.stgit@localhost.localdomain>
On Thu, 2009-08-20 at 23:30 -0600, Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
>
> The PCI device tree scanning code in pci_64.c is some useful functionality.
> It allows PCI devices to be described in the device tree instead of being
> probed for, which in turn allows pci devices to use all of the device tree
> facilities to describe complex PCI bus architectures like GPIO and IRQ
> routing (perhaps not a common situation for desktop or server systems,
> but useful for embedded systems with on-board PCI devices).
>
> This patch moves the device tree scanning into pci-common.c so it is
> available for 32-bit powerpc machines too.
I'd rather move it into a separate pci-of-scan.c file so we can more
easily try to move it to drivers/of or drivers/pci for use by other
archs later on.
Ben.
next prev parent reply other threads:[~2009-08-21 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 5:30 [RFC PATCH 0/3] Make 64-bit PCI device tree scanning code common Grant Likely
2009-08-21 5:30 ` [PATCH 1/3] powerpc/pci: Remove dead checks for CONFIG_PPC_OF Grant Likely
2009-08-21 5:46 ` Stephen Rothwell
2009-08-21 5:30 ` [PATCH 2/3] powerpc/pci: move pci_64.c device tree scanning code into pci-common.c Grant Likely
2009-08-21 6:01 ` Stephen Rothwell
2009-08-21 14:54 ` Grant Likely
2009-08-21 15:17 ` Stephen Rothwell
2009-08-21 6:05 ` Benjamin Herrenschmidt [this message]
2009-08-21 14:54 ` Grant Likely
2009-08-21 5:30 ` [PATCH 3/3] powerpc/pci: Merge ppc32 and ppc64 versions of phb_scan() Grant Likely
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=1250834729.7625.5.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.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).