From: rubini@gnudd.com (Alessandro Rubini)
To: linux-arm-kernel@lists.infradead.org
Subject: amba, tegra-ahb and pci (Kconfig question)
Date: Mon, 28 May 2012 10:34:43 +0200 [thread overview]
Message-ID: <20120528083443.GA8599@mail.gnudd.com> (raw)
In-Reply-To: <20120528082452.GH24149@n2100.arm.linux.org.uk>
> Normally, ARM_AMBA is selected when required, so this would be:
>
> config PCI_AMBA
> bool "PCI-to-AMBA bridge"
> depends on PCI
> select ARM_AMBA
But this would open the new question in a zillion boards that are
not interested in it. It's the board that selects arm-amba, in my opinion.
> I guess I should look at moving ARM_AMBA to drivers/amba/Kconfig too...
If you want I can submit a patch for this (btw, the rename to primecell
is dead, isn't it?)
thanks
/alessandro
next prev parent reply other threads:[~2012-05-28 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 8:17 amba, tegra-ahb and pci (Kconfig question) Alessandro Rubini
2012-05-28 8:24 ` Russell King - ARM Linux
2012-05-28 8:34 ` Alessandro Rubini [this message]
2012-05-28 10:23 ` Ben Dooks
2012-05-28 10:33 ` Russell King - ARM Linux
2012-05-29 2:34 ` Stephen Warren
2012-05-29 6:31 ` Alessandro Rubini
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=20120528083443.GA8599@mail.gnudd.com \
--to=rubini@gnudd.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 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).