From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] s/FOOTBRIDGE/ARCH_FOOTBRIDGE/
Date: Wed, 2 Jul 2014 09:13:12 +0200 [thread overview]
Message-ID: <20140702071312.GO14781@pengutronix.de> (raw)
In-Reply-To: <20140701221428.GC32514@n2100.arm.linux.org.uk>
Hello Russell,
On Tue, Jul 01, 2014 at 11:14:28PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jul 01, 2014 at 10:37:03PM +0200, Uwe Kleine-K?nig wrote:
> > I'm not sure that FOOTBRIDGE and ARCH_FOOTBRIDGE are semantically
> > identical; if not, feel free to nack this series.
>
> CONFIG_FOOTBRIDGE means that we have a DC21285 in the system. We
> used to have ARCH_FOOTBRIDGE and ARCH_CO285 which both selected
> CONFIG_FOOTBRIDGE.
>
> ARCH_FOOTBRIDGE was for either host or addin mode using a PAGE_OFFSET
> of 0xc0000000. ARCH_CO285 had a PAGE_OFFSET of 0x80000000 as they
> wanted to be able to map almost all of PCI memory space.
>
> So think of CONFIG_FOOTBRIDGE as meaning that we have the physical
> device, and CONFIG_ARCH_FOOTBRIDGE meaning that we want to support
> boards with the device on.
I expected something like that. Is it possible to "have" the device on a
cpu != StrongARM? If so I wonder why ARCH_FOOTBRIDGE is a "ARM system
type". And if not, wouldn't it be possible and better to have all
platforms which select CPU_SA110 (ARCH_EBSA110, ARCH_FOOTBRIDGE; what
about RPC?) in a single mach dir and make FOOTBRIDGE an option there?
It's hard to find information on the net about these chips, even
http://developer.intel.com/design/strong/sa110.htm only talks about x86
stuff only, so please excuse my unknowingness.
> So, it may make sense to rename CONFIG_FOOTBRIDGE to CONFIG_DC21285
> if that makes the configuration symbol intention clearer.
Maybe even better CONFIG_HAS_DC21285?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-07-02 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 20:37 [PATCH 0/3] s/FOOTBRIDGE/ARCH_FOOTBRIDGE/ Uwe Kleine-König
2014-07-01 20:37 ` [PATCH 1/3] serial: DC21285: depend on ARCH_FOOTBRIDGE instead of FOOTBRIDGE Uwe Kleine-König
2014-07-01 20:37 ` [PATCH 2/3] watchdog: get rid of FOOTBRIDGE in dependencies Uwe Kleine-König
2014-07-01 20:37 ` [PATCH 3/3] ARM: drop Kconfig symbol FOOTBRIDGE Uwe Kleine-König
2014-07-01 22:14 ` [PATCH 0/3] s/FOOTBRIDGE/ARCH_FOOTBRIDGE/ Russell King - ARM Linux
2014-07-02 7:13 ` Uwe Kleine-König [this message]
2014-07-02 16:26 ` Russell King - ARM Linux
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=20140702071312.GO14781@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).