From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: arch-vt8500 and wm8850 support
Date: Wed, 14 Nov 2012 11:17:32 +0000 [thread overview]
Message-ID: <201211141117.33485.arnd@arndb.de> (raw)
In-Reply-To: <1352879641.2728.8.camel@gitbox>
On Wednesday 14 November 2012, Tony Prisk wrote:
> Hi Arnd,
>
> Just looking for a little advice re: adding support for the WM8850
> variant.
>
> At the moment we have the ARM926 variants under ARCH_VT8500. The WM8850
> is ARMv7, but uses all the same drivers as the ARM926 versions. At the
> moment, all the drivers depend on ARCH_VT8500.
>
> The obvious solution (to me at least) seems to be to have 3 groups -
> ARCH_VT8500 keeps everything it has now except 'select CPU_ARM926T', and
> we add 2 additional groups - the first for all the current models, which
> selects CPU_ARM926T and ARCH_VT8500, and a second for WM8850 which
> selects CPU_V7 and ARCH_VT8500.
Yes, makes sense. Actually with the move to multiplatform, you already
need to make the decision for the CPU earlier on, since the multiplatform
kernel can only be built either for ARMv4/v5 or for ARMv6/v7.
I would suggest doing it like
config ARCH_VT8500
bool
select FOO
select BAR
config ARCH_WM8505
bool "WonderMedia WM8505 or VIA VT8500"
depends on ARCH_MULTI_V5
select ARCH_VT8500
select CPU_ARM926
config ARCH_WM8650
bool "WonderMedia WM 8650"
depends on ARCH_MULTI_V6
select ARCH_VT8500
select CPU_V6
config ARCH_WM8850
bool "WonderMedia WM 8750/8850"
depends on ARCH_MULTI_V7
select ARCH_VT8500
select CPU_V7
This keeps ARCH_VT8500 as the overall name for the family, but
lists only the WonderMedia parts in the configuration.
Arnd
next prev parent reply other threads:[~2012-11-14 11:17 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 [this message]
2012-11-14 11:22 ` Alexey Charkov
2012-11-14 17:42 ` Tony Prisk
2012-11-14 23:26 ` 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=201211141117.33485.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).