2012-08-13 10:11:15 +02:00
menu "ST-Ericsson AB U300/U335 Platform"
2009-04-23 10:22:13 +01:00
comment "ST-Ericsson Mobile Platform Products"
2013-05-02 18:01:46 +02:00
config ARCH_U300
2013-06-20 02:26:37 +02:00
bool "ST-Ericsson U300 Series" if ARCH_MULTI_V5
2013-05-02 18:01:46 +02:00
depends on MMU
select ARCH_REQUIRE_GPIOLIB
select ARM_AMBA
select ARM_PATCH_PHYS_VIRT
select ARM_VIC
select CLKDEV_LOOKUP
select CLKSRC_MMIO
select CLKSRC_OF
select COMMON_CLK
select CPU_ARM926T
select GENERIC_CLOCKEVENTS
select HAVE_TCM
2011-05-02 20:54:38 +02:00
select PINCTRL
2011-11-16 09:22:59 +01:00
select PINCTRL_COH901
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 17:12:25 +01:00
select PINCTRL_U300
2013-05-02 18:01:46 +02:00
select SPARSE_IRQ
2013-06-13 21:21:31 +02:00
select MFD_SYSCON
2013-05-02 18:01:46 +02:00
select USE_OF
help
Support for ST-Ericsson U300 series mobile platforms.
2009-04-23 10:22:13 +01:00
2012-08-13 10:11:15 +02:00
comment "ST-Ericsson U300/U335 Feature Selections"
2009-04-23 10:22:13 +01:00
2013-05-02 18:01:46 +02:00
config MACH_U300
depends on ARCH_U300
bool "U300"
default y
2009-04-23 10:22:13 +01:00
config U300_DEBUG
2013-05-02 18:01:46 +02:00
depends on ARCH_U300
2009-04-23 10:22:13 +01:00
bool "Debug support for U300"
depends on PM
help
Debug support for U300 in sysfs, procfs etc.
2009-08-14 10:59:05 +01:00
config MACH_U300_SPIDUMMY
2013-05-02 18:01:46 +02:00
depends on ARCH_U300
2009-08-14 10:59:05 +01:00
bool "SSP/SPI dummy chip"
select SPI
select SPI_MASTER
select SPI_PL022
help
This creates a small kernel module that creates a dummy
SPI device to be used for loopback tests. Regularly used
to test reference designs. If you're not testing SPI,
you don't need it. Selecting this will activate the
SPI framework and ARM PL022 support.
2009-04-23 10:22:13 +01:00
endmenu
