2013-03-22 04:51:13 +07:00
|
|
|
config ARCH_U8500
|
|
|
|
|
bool "ST-Ericsson U8500 Series" if ARCH_MULTI_V7
|
|
|
|
|
depends on MMU
|
|
|
|
|
select ARCH_HAS_CPUFREQ
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
|
|
|
|
select ARM_AMBA
|
|
|
|
|
select CLKDEV_LOOKUP
|
|
|
|
|
select CPU_V7
|
|
|
|
|
select GENERIC_CLOCKEVENTS
|
2013-02-28 06:28:14 +07:00
|
|
|
select HAVE_ARM_SCU if SMP
|
2013-02-16 07:02:20 +07:00
|
|
|
select HAVE_ARM_TWD if SMP
|
2013-03-22 04:51:13 +07:00
|
|
|
select HAVE_SMP
|
|
|
|
|
select MIGHT_HAVE_CACHE_L2X0
|
|
|
|
|
help
|
|
|
|
|
Support for ST-Ericsson's Ux500 architecture
|
|
|
|
|
|
2010-05-03 13:27:31 +07:00
|
|
|
if ARCH_U8500
|
|
|
|
|
|
|
|
|
|
config UX500_SOC_COMMON
|
|
|
|
|
bool
|
|
|
|
|
default y
|
2013-04-30 18:19:23 +07:00
|
|
|
select ABX500_CORE
|
|
|
|
|
select AB8500_CORE
|
2011-09-20 12:45:46 +07:00
|
|
|
select ARM_ERRATA_754322
|
2012-08-16 16:36:04 +07:00
|
|
|
select ARM_ERRATA_764369 if SMP
|
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 23:12:25 +07:00
|
|
|
select ARM_GIC
|
2012-02-26 02:48:52 +07:00
|
|
|
select CACHE_L2X0
|
2012-10-18 19:01:25 +07:00
|
|
|
select CLKSRC_NOMADIK_MTU
|
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 23:12:25 +07:00
|
|
|
select COMMON_CLK
|
2012-04-27 04:57:25 +07:00
|
|
|
select PINCTRL
|
|
|
|
|
select PINCTRL_NOMADIK
|
2013-01-08 16:41:02 +07:00
|
|
|
select PINCTRL_ABX500
|
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 23:12:25 +07:00
|
|
|
select PL310_ERRATA_753970 if CACHE_PL310
|
2010-05-03 13:27:31 +07:00
|
|
|
|
2010-12-08 12:38:01 +07:00
|
|
|
config UX500_SOC_DB8500
|
2012-02-26 02:48:50 +07:00
|
|
|
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 23:12:25 +07:00
|
|
|
select CPU_FREQ_TABLE if CPU_FREQ
|
2011-05-16 03:53:56 +07:00
|
|
|
select MFD_DB8500_PRCMU
|
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 23:12:25 +07:00
|
|
|
select PINCTRL_DB8500
|
2013-01-28 20:43:55 +07:00
|
|
|
select PINCTRL_DB8540
|
2013-01-08 16:59:53 +07:00
|
|
|
select PINCTRL_AB8500
|
2013-01-28 20:23:45 +07:00
|
|
|
select PINCTRL_AB8505
|
2013-01-28 20:29:35 +07:00
|
|
|
select PINCTRL_AB9540
|
2013-01-28 20:35:19 +07:00
|
|
|
select PINCTRL_AB8540
|
2012-04-13 20:08:01 +07:00
|
|
|
select REGULATOR
|
2011-04-01 19:43:33 +07:00
|
|
|
select REGULATOR_DB8500_PRCMU
|
2010-12-08 12:38:01 +07:00
|
|
|
|
2011-03-31 14:07:20 +07:00
|
|
|
menu "Ux500 target platform (boards)"
|
2009-11-28 14:17:18 +07:00
|
|
|
|
2012-03-01 00:15:20 +07:00
|
|
|
config MACH_MOP500
|
|
|
|
|
bool "U8500 Development platform, MOP500 versions"
|
|
|
|
|
select I2C
|
|
|
|
|
select I2C_NOMADIK
|
2013-05-15 19:36:41 +07:00
|
|
|
select REGULATOR
|
2012-09-03 20:33:39 +07:00
|
|
|
select REGULATOR_FIXED_VOLTAGE
|
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 23:12:25 +07:00
|
|
|
select SOC_BUS
|
|
|
|
|
select UX500_SOC_DB8500
|
2009-11-28 14:17:18 +07:00
|
|
|
help
|
2012-03-01 00:15:20 +07:00
|
|
|
Include support for the MOP500 development platform.
|
2010-05-03 14:46:51 +07:00
|
|
|
|
2011-03-31 14:07:20 +07:00
|
|
|
config MACH_HREFV60
|
2012-03-01 00:15:20 +07:00
|
|
|
bool "U8500 Development platform, HREFv60 version"
|
|
|
|
|
select MACH_MOP500
|
|
|
|
|
help
|
|
|
|
|
Include support for the HREFv60 new development platform.
|
|
|
|
|
Includes HREFv70, v71 etc.
|
2011-03-31 14:07:20 +07:00
|
|
|
|
2011-03-25 22:29:01 +07:00
|
|
|
config MACH_SNOWBALL
|
|
|
|
|
bool "U8500 Snowball platform"
|
2012-03-01 00:15:20 +07:00
|
|
|
select MACH_MOP500
|
2011-03-25 22:29:01 +07:00
|
|
|
help
|
|
|
|
|
Include support for the snowball development platform.
|
|
|
|
|
|
2012-02-26 02:48:50 +07:00
|
|
|
config UX500_AUTO_PLATFORM
|
|
|
|
|
def_bool y
|
2012-03-01 00:15:20 +07:00
|
|
|
select MACH_MOP500
|
2012-02-26 02:48:50 +07:00
|
|
|
help
|
|
|
|
|
At least one platform needs to be selected in order to build
|
|
|
|
|
a working kernel. If everything else is disabled, this
|
2012-03-01 00:15:20 +07:00
|
|
|
automatically enables MACH_MOP500.
|
2012-03-29 02:34:33 +07:00
|
|
|
|
2012-03-03 04:51:38 +07:00
|
|
|
config MACH_UX500_DT
|
|
|
|
|
bool "Generic U8500 support using device tree"
|
2012-03-29 02:34:33 +07:00
|
|
|
depends on MACH_MOP500
|
2012-03-03 04:51:38 +07:00
|
|
|
select USE_OF
|
|
|
|
|
|
2010-12-08 12:38:01 +07:00
|
|
|
endmenu
|
2010-05-03 13:27:31 +07:00
|
|
|
|
2010-05-03 13:38:06 +07:00
|
|
|
config UX500_DEBUG_UART
|
|
|
|
|
int "Ux500 UART to use for low-level debug"
|
|
|
|
|
default 2
|
|
|
|
|
help
|
|
|
|
|
Choose the UART on which kernel low-level debug messages should be
|
|
|
|
|
output.
|
|
|
|
|
|
2010-05-03 13:27:31 +07:00
|
|
|
endif
|