From: richardliu@ms1.techarea.org (Richard Liu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI Domains Support
Date: Mon, 21 Dec 2009 14:00:25 +0800 [thread overview]
Message-ID: <4B2F0EF9.101@ms1.techarea.org> (raw)
In-Reply-To: <20091220012728.GD12578@verge.net.au>
Simon Horman wrote:
> On Thu, Dec 17, 2009 at 09:01:06PM +0800, Richard Liu wrote:
>
>> Dear Simon:
>>
>> Simon Horman wrote:
>>
>> ARM is a highly custom platform, just reverse for other platform add
>> their code,
>> Some platforms might need PCI domains, but some platforms not.
>>
>
> Understood. Do you have any platforms in mind that wouldn't want
> PCI domains? I was just thinking that perhaps PCI_DOMAINS could be added
> later as needed, reducing noise in the code until the need arises.
> But perhaps I'm reading the situation incorrectly.
>
Actually, most ARM platforms didn't need PCI domains.
So, original patch is
+config PCI_DOMAINS
+ def_bool y
+ depends on PCI && ARCH_CXXXXXX
+
But I removed the "&& ARCH_CXXXXXXX" before I provided the patch.
Because ARCH_CXXXXXXX is not exist in ARM Linux kernel now (maybe it
would be committed at someday)
I traced other ARM platforms,
some platforms like Marvell Orion5x seems has both PCI and PCIe host
controller,
Maybe they can use PCI domain to control their PCI/PCIe host controller.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091221/2622c2af/attachment-0001.htm>
next prev parent reply other threads:[~2009-12-21 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 14:13 [Fwd: [PATCH] PCI Domains Support] Richard Liu
2009-12-17 0:06 ` Simon Horman
2009-12-17 13:01 ` [PATCH] PCI Domains Support Richard Liu
2009-12-20 1:27 ` Simon Horman
2009-12-21 6:00 ` Richard Liu [this message]
2009-12-22 4:55 ` Simon Horman
2009-12-25 21:58 ` Richard Liu
2009-12-23 4:07 ` Simon Horman
2009-12-31 3:37 ` Richard Liu
2009-12-31 4:36 ` Simon Horman
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=4B2F0EF9.101@ms1.techarea.org \
--to=richardliu@ms1.techarea.org \
--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 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).