From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM PCI controller registration and representation using device tree?
Date: Sat, 02 Jun 2012 15:48:11 -0500 [thread overview]
Message-ID: <4FCA7C0B.5070304@gmail.com> (raw)
In-Reply-To: <4113992.BTnO0ZYQON@bender>
On 06/02/2012 09:18 AM, Florian Fainelli wrote:
> Hi,
>
> I was wondering if anyone had started working on representing the various PCI
> controllers found on SoCs to a device tree representation?
Reusing the existing PCI bindings is the right way to go.
> It seems like quite some generic code could be borrowed from PowerPC,
> especially the parsing of the PCI ranges, though I don't see ARM directly
> exposing a struct pci_controller to easily allow that.
The PowerPC PCI DT code needing to be re-factored to generic code was my
conclusion as well in my brief look at it.
Rob
>
> Any thoughts about this?
>
> Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Florian Fainelli <florian-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: ARM PCI controller registration and representation using device tree?
Date: Sat, 02 Jun 2012 15:48:11 -0500 [thread overview]
Message-ID: <4FCA7C0B.5070304@gmail.com> (raw)
In-Reply-To: <4113992.BTnO0ZYQON@bender>
On 06/02/2012 09:18 AM, Florian Fainelli wrote:
> Hi,
>
> I was wondering if anyone had started working on representing the various PCI
> controllers found on SoCs to a device tree representation?
Reusing the existing PCI bindings is the right way to go.
> It seems like quite some generic code could be borrowed from PowerPC,
> especially the parsing of the PCI ranges, though I don't see ARM directly
> exposing a struct pci_controller to easily allow that.
The PowerPC PCI DT code needing to be re-factored to generic code was my
conclusion as well in my brief look at it.
Rob
>
> Any thoughts about this?
>
> Thanks.
next prev parent reply other threads:[~2012-06-02 20:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 14:18 ARM PCI controller registration and representation using device tree? Florian Fainelli
2012-06-02 14:18 ` Florian Fainelli
2012-06-02 14:34 ` Russell King - ARM Linux
2012-06-02 14:34 ` Russell King - ARM Linux
2012-06-03 2:41 ` Arnd Bergmann
2012-06-03 2:41 ` Arnd Bergmann
2012-06-03 7:55 ` Russell King - ARM Linux
2012-06-03 7:55 ` Russell King - ARM Linux
2012-06-03 11:54 ` Arnd Bergmann
2012-06-03 11:54 ` Arnd Bergmann
2012-06-02 20:48 ` Rob Herring [this message]
2012-06-02 20:48 ` Rob Herring
2012-06-03 5:56 ` Arnd Bergmann
2012-06-03 5:56 ` Arnd Bergmann
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=4FCA7C0B.5070304@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 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.