2019-05-19 15:07:45 +03:00
# SPDX-License-Identifier: GPL-2.0-only
2014-04-15 19:30:43 +04:00
menuconfig ARCH_MMP
bool "Marvell PXA168/910/MMP2"
depends on ARCH_MULTI_V5 || ARCH_MULTI_V7
select GPIO_PXA
2016-06-02 15:10:16 +03:00
select GPIOLIB
2014-04-15 19:30:43 +04:00
select PINCTRL
select PLAT_PXA
help
Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
2009-01-20 09:15:18 +03:00
if ARCH_MMP
2014-04-15 19:30:43 +04:00
menu "Marvell PXA168/910/MMP2 Implementations"
if ATAGS
2009-01-20 09:15:18 +03:00
config MACH_ASPENITE
bool "Marvell's PXA168 Aspenite Development Board"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2009-01-20 09:15:18 +03:00
select CPU_PXA168
help
Say 'Y' here if you want to support the Marvell PXA168-based
Aspenite Development Board.
config MACH_ZYLONITE2
bool "Marvell's PXA168 Zylonite2 Development Board"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2009-01-20 09:15:18 +03:00
select CPU_PXA168
help
Say 'Y' here if you want to support the Marvell PXA168-based
Zylonite2 Development Board.
2010-01-12 03:54:50 +03:00
config MACH_AVENGERS_LITE
bool "Marvell's PXA168 Avengers Lite Development Board"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2010-01-12 03:54:50 +03:00
select CPU_PXA168
help
Say 'Y' here if you want to support the Marvell PXA168-based
Avengers Lite Development Board.
2009-03-20 08:27:30 +03:00
config MACH_TAVOREVB
bool "Marvell's PXA910 TavorEVB Development Board"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2009-03-20 08:27:30 +03:00
select CPU_PXA910
help
Say 'Y' here if you want to support the Marvell PXA910-based
TavorEVB Development Board.
2009-03-20 08:33:49 +03:00
config MACH_TTC_DKB
bool "Marvell's PXA910 TavorEVB Development Board"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2009-03-20 08:33:49 +03:00
select CPU_PXA910
help
Say 'Y' here if you want to support the Marvell PXA910-based
TTC_DKB Development Board.
2010-11-25 06:33:13 +03:00
config MACH_BROWNSTONE
bool "Marvell's Brownstone Development Platform"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V7
2010-11-25 06:33:13 +03:00
select CPU_MMP2
help
Say 'Y' here if you want to support the Marvell MMP2-based
Brown Development Platform.
MMP2-based board can't be co-existed with PXA168-based &
PXA910-based development board. Since MMP2 is compatible to
ARMv7 architecture.
2009-12-04 17:41:28 +03:00
config MACH_FLINT
bool "Marvell's Flint Development Platform"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V7
2009-12-04 17:41:28 +03:00
select CPU_MMP2
help
Say 'Y' here if you want to support the Marvell MMP2-based
Flint Development Platform.
MMP2-based board can't be co-existed with PXA168-based &
PXA910-based development board. Since MMP2 is compatible to
2010-11-25 09:21:32 +03:00
ARMv7 architecture.
2009-12-04 17:41:28 +03:00
2010-01-06 17:07:15 +03:00
config MACH_MARVELL_JASPER
bool "Marvell's Jasper Development Platform"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V7
2010-01-06 17:07:15 +03:00
select CPU_MMP2
help
Say 'Y' here if you want to support the Marvell MMP2-base
Jasper Development Platform.
MMP2-based board can't be co-existed with PXA168-based &
PXA910-based development board. Since MMP2 is compatible to
2010-11-25 09:21:32 +03:00
ARMv7 architecture.
2010-01-06 17:07:15 +03:00
2010-09-13 07:51:34 +04:00
config MACH_TETON_BGA
bool "Marvell's PXA168 Teton BGA Development Board"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2010-09-13 07:51:34 +04:00
select CPU_PXA168
help
Say 'Y' here if you want to support the Marvell PXA168-based
Teton BGA Development Board.
2011-08-16 08:28:57 +04:00
config MACH_GPLUGD
2011-05-02 10:00:00 +04:00
bool "Marvell's PXA168 GuruPlug Display (gplugD) Board"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2011-05-02 10:00:00 +04:00
select CPU_PXA168
help
Say 'Y' here if you want to support the Marvell PXA168-based
GuruPlug Display (gplugD) Board
2014-04-15 19:30:43 +04:00
endif
2011-05-02 10:00:00 +04:00
2012-04-10 11:12:45 +04:00
config MACH_MMP_DT
bool "Support MMP (ARMv5) platforms from device tree"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V5
2012-10-03 19:44:32 +04:00
select PINCTRL
select PINCTRL_SINGLE
2014-10-31 05:13:53 +03:00
select COMMON_CLK
select ARCH_HAS_RESET_CONTROLLER
select CPU_MOHAWK
2012-04-10 11:12:45 +04:00
help
Include support for Marvell MMP2 based platforms using
the device tree. Needn't select any other machine while
MACH_MMP_DT is enabled.
config MACH_MMP2_DT
bool "Support MMP2 (ARMv7) platforms from device tree"
2014-04-15 19:30:43 +04:00
depends on ARCH_MULTI_V7
2012-10-03 19:44:32 +04:00
select PINCTRL
select PINCTRL_SINGLE
2014-10-31 05:13:53 +03:00
select ARCH_HAS_RESET_CONTROLLER
select CPU_PJ4
2012-04-10 11:12:45 +04:00
help
Include support for Marvell MMP2 based platforms using
the device tree.
2009-01-20 09:15:18 +03:00
endmenu
config CPU_PXA168
bool
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-06 20:12:25 +04:00
select CPU_MOHAWK
2009-01-20 09:15:18 +03:00
help
Select code specific to PXA168
2009-03-20 07:50:22 +03:00
config CPU_PXA910
bool
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-06 20:12:25 +04:00
select CPU_MOHAWK
2009-03-20 07:50:22 +03:00
help
Select code specific to PXA910
2009-12-04 17:41:28 +03:00
config CPU_MMP2
bool
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-06 20:12:25 +04:00
select CPU_PJ4
2009-12-04 17:41:28 +03:00
help
2010-11-24 06:54:21 +03:00
Select code specific to MMP2. MMP2 is ARMv7 compatible.
2012-05-03 10:19:13 +04:00
config USB_EHCI_MV_U2O
bool "EHCI support for PXA USB OTG controller"
depends on USB_EHCI_MV
help
Enables support for OTG controller which can be switched to host mode.
2013-12-05 05:36:21 +04:00
config MMP_SRAM
bool
2009-01-20 09:15:18 +03:00
endif
