From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: arch-vt8500 and wm8850 support
Date: Wed, 14 Nov 2012 23:26:22 +0000 [thread overview]
Message-ID: <201211142326.23023.arnd@arndb.de> (raw)
In-Reply-To: <1352914966.3238.3.camel@gitbox>
On Wednesday 14 November 2012, Tony Prisk wrote:
> Makes sense - That's basically what I had in mind. My concern is with
> the bit that made no sense to me - the non-multiplatform version of the
> same. At the moment, we have the default xx_SINGLE for ARCH_VT8500.
> Would I need to add an additional xx_SINGLE variant for each different
> version?
I think either one option or two (v5 and v6/v7), but we don't need three
separate ones, as it should be possible to build v6 and v7 together.
> We would need ARCH_WM8505 (To cover VT8500/WM8505/WM8650 ARM926),
> ARCH_WM8750 (for ARMv6) and ARCH_WM8850 (for ARMv7).
Ah, right, I was mixing up the numbers.
> Do I need a ARCH_WM8750_SINGLE, ARCH_WM8850_SINGLE etc for each one to
> allow use to continue using earlyprintk?
You just need to ensure that we always set at least one of them, and
that ARCH_WM8505 isn't set at the same time as one of the v6/v7 parts.
Maybe something like
config ARCH_VT8500
bool
select FOO
select BAR
config ARCH_WM8505
bool "WonderMedia WM8505/WM8650 or VIA VT8500" if !ARCH_VT8500_SINGLE
depends on ARCH_MULTI_V5
default ARCH_VT8500_SINGLE
select ARCH_VT8500
select CPU_ARM926
config ARCH_WM8750
bool "WonderMedia WM 8750"
depends on ARCH_MULTI_V6 || ARCH_WM8750_SINGLE
select ARCH_VT8500
select CPU_V6
config ARCH_WM8850
bool "WonderMedia WM 8850/8950"
depends on ARCH_MULTI_V7 || ARCH_WM8750_SINGLE
select ARCH_VT8500
select CPU_V7
config ARCH_WM8850_AUTO
def_bool y
depends on ARCH_WM8750_SINGLE && !ARCH_WM8750
select ARCH_WM8850 # ensure that ARCH_WM8850 is on if ARCH_WM8750 is off
Arnd
prev parent reply other threads:[~2012-11-14 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 7:54 arch-vt8500 and wm8850 support Tony Prisk
2012-11-14 11:17 ` Arnd Bergmann
2012-11-14 11:22 ` Alexey Charkov
2012-11-14 17:42 ` Tony Prisk
2012-11-14 23:26 ` Arnd Bergmann [this message]
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=201211142326.23023.arnd@arndb.de \
--to=arnd@arndb.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).