2012-02-06 00:38:19 +00:00
|
|
|
# arch/arm/mach-s3c24xx/Kconfig
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2012 Samsung Electronics Co., Ltd.
|
|
|
|
|
# http://www.samsung.com/
|
|
|
|
|
#
|
|
|
|
|
# Copyright 2007 Simtec Electronics
|
|
|
|
|
#
|
|
|
|
|
# Licensed under GPLv2
|
|
|
|
|
|
|
|
|
|
if ARCH_S3C24XX
|
|
|
|
|
|
2013-02-01 00:54:38 +00:00
|
|
|
config PLAT_S3C24XX
|
|
|
|
|
def_bool y
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
|
|
|
|
select NO_IOPORT
|
|
|
|
|
select S3C_DEV_NAND
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
help
|
|
|
|
|
Base platform code for any Samsung S3C24XX device
|
|
|
|
|
|
2012-02-06 00:38:19 +00:00
|
|
|
menu "SAMSUNG S3C24XX SoCs Support"
|
|
|
|
|
|
|
|
|
|
comment "S3C24XX SoCs"
|
|
|
|
|
|
|
|
|
|
config CPU_S3C2410
|
|
|
|
|
bool "SAMSUNG S3C2410"
|
|
|
|
|
default y
|
|
|
|
|
select CPU_ARM920T
|
|
|
|
|
select CPU_LLSERIAL_S3C2410
|
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 16:12:25 +00:00
|
|
|
select S3C2410_CLOCK
|
2013-10-20 20:32:48 +00:00
|
|
|
select S3C2410_DMA if S3C24XX_DMA
|
2013-04-04 12:54:15 +00:00
|
|
|
select ARM_S3C2410_CPUFREQ if ARM_S3C24XX_CPUFREQ
|
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 16:12:25 +00:00
|
|
|
select S3C2410_PM if PM
|
2013-06-17 14:45:37 +00:00
|
|
|
select SAMSUNG_WDT_RESET
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Support for S3C2410 and S3C2410A family from the S3C24XX line
|
|
|
|
|
of Samsung Mobile CPUs.
|
|
|
|
|
|
2012-02-06 01:02:01 +00:00
|
|
|
config CPU_S3C2412
|
|
|
|
|
bool "SAMSUNG S3C2412"
|
|
|
|
|
select CPU_ARM926T
|
|
|
|
|
select CPU_LLSERIAL_S3C2440
|
|
|
|
|
select S3C2412_DMA if S3C24XX_DMA
|
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 16:12:25 +00:00
|
|
|
select S3C2412_PM if PM
|
2012-02-06 01:02:01 +00:00
|
|
|
help
|
|
|
|
|
Support for the S3C2412 and S3C2413 SoCs from the S3C24XX line
|
|
|
|
|
|
2012-02-06 01:59:47 +00:00
|
|
|
config CPU_S3C2416
|
|
|
|
|
bool "SAMSUNG S3C2416/S3C2450"
|
|
|
|
|
select CPU_ARM926T
|
|
|
|
|
select CPU_LLSERIAL_S3C2440
|
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 16:12:25 +00:00
|
|
|
select S3C2416_PM if PM
|
2012-03-02 22:49:12 +00:00
|
|
|
select S3C2443_COMMON
|
2012-03-07 09:53:17 +00:00
|
|
|
select S3C2443_DMA if S3C24XX_DMA
|
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 16:12:25 +00:00
|
|
|
select SAMSUNG_CLKSRC
|
2012-02-06 01:59:47 +00:00
|
|
|
help
|
|
|
|
|
Support for the S3C2416 SoC from the S3C24XX line
|
|
|
|
|
|
2012-02-06 04:10:11 +00:00
|
|
|
config CPU_S3C2440
|
|
|
|
|
bool "SAMSUNG S3C2440"
|
|
|
|
|
select CPU_ARM920T
|
|
|
|
|
select CPU_LLSERIAL_S3C2440
|
|
|
|
|
select S3C2410_CLOCK
|
|
|
|
|
select S3C2410_PM if PM
|
|
|
|
|
select S3C2440_DMA if S3C24XX_DMA
|
|
|
|
|
help
|
|
|
|
|
Support for S3C2440 Samsung Mobile CPU based systems.
|
|
|
|
|
|
|
|
|
|
config CPU_S3C2442
|
|
|
|
|
bool "SAMSUNG S3C2442"
|
|
|
|
|
select CPU_ARM920T
|
|
|
|
|
select CPU_LLSERIAL_S3C2440
|
|
|
|
|
select S3C2410_CLOCK
|
2013-10-20 20:32:48 +00:00
|
|
|
select S3C2410_DMA if S3C24XX_DMA
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C2410_PM if PM
|
|
|
|
|
help
|
|
|
|
|
Support for S3C2442 Samsung Mobile CPU based systems.
|
|
|
|
|
|
|
|
|
|
config CPU_S3C244X
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on CPU_S3C2440 || CPU_S3C2442
|
2013-06-17 14:45:37 +00:00
|
|
|
select SAMSUNG_WDT_RESET
|
2012-02-06 04:10:11 +00:00
|
|
|
|
2012-02-06 04:21:03 +00:00
|
|
|
config CPU_S3C2443
|
|
|
|
|
bool "SAMSUNG S3C2443"
|
|
|
|
|
select CPU_ARM920T
|
|
|
|
|
select CPU_LLSERIAL_S3C2440
|
2012-03-02 22:49:12 +00:00
|
|
|
select S3C2443_COMMON
|
2012-02-06 04:21:03 +00:00
|
|
|
select S3C2443_DMA if S3C24XX_DMA
|
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 16:12:25 +00:00
|
|
|
select SAMSUNG_CLKSRC
|
2012-02-06 04:21:03 +00:00
|
|
|
help
|
|
|
|
|
Support for the S3C2443 SoC from the S3C24XX line
|
|
|
|
|
|
2012-03-07 09:47:01 +00:00
|
|
|
# common code
|
|
|
|
|
|
2013-02-01 00:54:38 +00:00
|
|
|
config S3C2410_CLOCK
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Clock code for the S3C2410, and similar processors which
|
|
|
|
|
is currently includes the S3C2410, S3C2440, S3C2442.
|
|
|
|
|
|
|
|
|
|
config S3C24XX_DCLK
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Clock code for supporting DCLK/CLKOUT on S3C24XX architectures
|
|
|
|
|
|
2012-03-07 09:47:01 +00:00
|
|
|
config S3C24XX_SMDK
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common machine code for SMDK2410 and SMDK2440
|
|
|
|
|
|
2012-03-07 09:47:05 +00:00
|
|
|
config S3C24XX_SIMTEC_AUDIO
|
|
|
|
|
bool
|
|
|
|
|
depends on (ARCH_BAST || MACH_VR1000 || MACH_OSIRIS || MACH_ANUBIS)
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Add audio devices for common Simtec S3C24XX boards
|
|
|
|
|
|
|
|
|
|
config S3C24XX_SIMTEC_PM
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common power management code for systems that are
|
|
|
|
|
compatible with the Simtec style of power management
|
|
|
|
|
|
2012-03-07 09:47:11 +00:00
|
|
|
config S3C24XX_SIMTEC_USB
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
USB management code for common Simtec S3C24XX boards
|
|
|
|
|
|
2012-03-07 09:47:15 +00:00
|
|
|
config S3C24XX_SETUP_TS
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Compile in platform device definition for Samsung TouchScreen.
|
|
|
|
|
|
2013-02-01 00:54:38 +00:00
|
|
|
config S3C24XX_DMA
|
|
|
|
|
bool "S3C2410 DMA support"
|
|
|
|
|
select S3C_DMA
|
|
|
|
|
help
|
|
|
|
|
S3C2410 DMA support. This is needed for drivers like sound which
|
|
|
|
|
use the S3C2410's DMA system to move data to and from the
|
|
|
|
|
peripheral blocks.
|
|
|
|
|
|
|
|
|
|
config S3C2410_DMA_DEBUG
|
|
|
|
|
bool "S3C2410 DMA support debug"
|
2013-04-04 01:03:53 +00:00
|
|
|
depends on S3C2410_DMA
|
2013-02-01 00:54:38 +00:00
|
|
|
help
|
|
|
|
|
Enable debugging output for the DMA code. This option sends info
|
|
|
|
|
to the kernel log, at priority KERN_DEBUG.
|
|
|
|
|
|
2012-02-06 00:38:19 +00:00
|
|
|
config S3C2410_DMA
|
|
|
|
|
bool
|
2012-02-06 04:10:11 +00:00
|
|
|
depends on S3C24XX_DMA && (CPU_S3C2410 || CPU_S3C2442)
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
DMA device selection for S3C2410 and compatible CPUs
|
|
|
|
|
|
|
|
|
|
config S3C2410_PM
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Power Management code common to S3C2410 and better
|
|
|
|
|
|
2013-02-01 00:54:38 +00:00
|
|
|
# low-level serial option nodes
|
|
|
|
|
|
|
|
|
|
config CPU_LLSERIAL_S3C2410_ONLY
|
|
|
|
|
bool
|
|
|
|
|
default y if CPU_LLSERIAL_S3C2410 && !CPU_LLSERIAL_S3C2440
|
|
|
|
|
|
|
|
|
|
config CPU_LLSERIAL_S3C2440_ONLY
|
|
|
|
|
bool
|
|
|
|
|
default y if CPU_LLSERIAL_S3C2440 && !CPU_LLSERIAL_S3C2410
|
|
|
|
|
|
|
|
|
|
config CPU_LLSERIAL_S3C2410
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Selected if there is an S3C2410 (or register compatible) serial
|
|
|
|
|
low-level implementation needed
|
|
|
|
|
|
|
|
|
|
config CPU_LLSERIAL_S3C2440
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Selected if there is an S3C2440 (or register compatible) serial
|
|
|
|
|
low-level implementation needed
|
|
|
|
|
|
2013-04-04 12:54:15 +00:00
|
|
|
config S3C24XX_PLL
|
|
|
|
|
bool "Support CPUfreq changing of PLL frequency (EXPERIMENTAL)"
|
2013-07-14 12:02:19 +00:00
|
|
|
depends on ARM_S3C24XX_CPUFREQ
|
2013-04-04 12:54:15 +00:00
|
|
|
help
|
|
|
|
|
Compile in support for changing the PLL frequency from the
|
|
|
|
|
S3C24XX series CPUfreq driver. The PLL takes time to settle
|
|
|
|
|
after a frequency change, so by default it is not enabled.
|
|
|
|
|
|
|
|
|
|
This also means that the PLL tables for the selected CPU(s) will
|
|
|
|
|
be built which may increase the size of the kernel image.
|
|
|
|
|
|
2013-02-01 00:54:38 +00:00
|
|
|
# cpu frequency items common between s3c2410 and s3c2440/s3c2442
|
|
|
|
|
|
|
|
|
|
config S3C2410_IOTIMING
|
|
|
|
|
bool
|
2013-04-04 12:54:15 +00:00
|
|
|
depends on ARM_S3C24XX_CPUFREQ
|
2013-02-01 00:54:38 +00:00
|
|
|
help
|
|
|
|
|
Internal node to select io timing code that is common to the s3c2410
|
|
|
|
|
and s3c2440/s3c2442 cpu frequency support.
|
|
|
|
|
|
|
|
|
|
config S3C2410_CPUFREQ_UTILS
|
2013-04-04 12:54:15 +00:00
|
|
|
bool
|
|
|
|
|
depends on ARM_S3C24XX_CPUFREQ
|
|
|
|
|
help
|
|
|
|
|
Internal node to select timing code that is common to the s3c2410
|
|
|
|
|
and s3c2440/s3c244 cpu frequency support.
|
2013-02-01 00:54:38 +00:00
|
|
|
|
|
|
|
|
# cpu frequency support common to s3c2412, s3c2413 and s3c2442
|
|
|
|
|
|
|
|
|
|
config S3C2412_IOTIMING
|
|
|
|
|
bool
|
2013-04-04 12:54:15 +00:00
|
|
|
depends on ARM_S3C24XX_CPUFREQ && (CPU_S3C2412 || CPU_S3C2443)
|
2013-02-01 00:54:38 +00:00
|
|
|
help
|
|
|
|
|
Intel node to select io timing code that is common to the s3c2412
|
|
|
|
|
and the s3c2443.
|
|
|
|
|
|
2012-04-21 14:55:33 +00:00
|
|
|
# cpu-specific sections
|
|
|
|
|
|
|
|
|
|
if CPU_S3C2410
|
|
|
|
|
|
2013-01-21 23:16:35 +00:00
|
|
|
config S3C2410_PLL
|
|
|
|
|
bool
|
2013-04-04 12:54:15 +00:00
|
|
|
depends on ARM_S3C2410_CPUFREQ && S3C24XX_PLL
|
2013-01-21 23:16:35 +00:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Select the PLL table for the S3C2410
|
|
|
|
|
|
2012-03-07 09:47:11 +00:00
|
|
|
config S3C24XX_SIMTEC_NOR
|
2012-02-06 00:38:19 +00:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Internal node to specify machine has simtec NOR mapping
|
|
|
|
|
|
|
|
|
|
config MACH_BAST_IDE
|
|
|
|
|
bool
|
|
|
|
|
select HAVE_PATA_PLATFORM
|
|
|
|
|
help
|
|
|
|
|
Internal node for machines with an BAST style IDE
|
|
|
|
|
interface
|
|
|
|
|
|
|
|
|
|
comment "S3C2410 Boards"
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# The "S3C2410 Boards" list is ordered alphabetically by option text.
|
|
|
|
|
# (without ARCH_ or MACH_)
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config MACH_AML_M5900
|
|
|
|
|
bool "AML M5900 Series"
|
2012-03-07 09:47:05 +00:00
|
|
|
select S3C24XX_SIMTEC_PM if PM
|
2012-02-06 00:38:19 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using the American Microsystems M5900 Series
|
|
|
|
|
<http://www.amltd.com>
|
|
|
|
|
|
|
|
|
|
config ARCH_BAST
|
|
|
|
|
bool "Simtec Electronics BAST (EB2410ITX)"
|
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 16:12:25 +00:00
|
|
|
select ISA
|
|
|
|
|
select MACH_BAST_IDE
|
2013-04-04 12:54:15 +00:00
|
|
|
select S3C2410_IOTIMING if ARM_S3C2410_CPUFREQ
|
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 16:12:25 +00:00
|
|
|
select S3C24XX_DCLK
|
2012-03-07 09:47:11 +00:00
|
|
|
select S3C24XX_SIMTEC_NOR
|
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 16:12:25 +00:00
|
|
|
select S3C24XX_SIMTEC_PM if PM
|
2012-03-07 09:47:11 +00:00
|
|
|
select S3C24XX_SIMTEC_USB
|
2012-02-06 00:38:19 +00:00
|
|
|
select S3C_DEV_HWMON
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Simtec Electronics EB2410ITX
|
|
|
|
|
development board (also known as BAST)
|
|
|
|
|
|
|
|
|
|
config BAST_PC104_IRQ
|
|
|
|
|
bool "BAST PC104 IRQ support"
|
|
|
|
|
depends on ARCH_BAST
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say Y here to enable the PC104 IRQ routing on the
|
|
|
|
|
Simtec BAST (EB2410ITX)
|
|
|
|
|
|
|
|
|
|
config ARCH_H1940
|
|
|
|
|
bool "IPAQ H1940"
|
|
|
|
|
select PM_H1940 if PM
|
2012-03-07 09:47:15 +00:00
|
|
|
select S3C24XX_SETUP_TS
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_NAND
|
|
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the HP IPAQ H1940
|
|
|
|
|
|
|
|
|
|
config H1940BT
|
|
|
|
|
tristate "Control the state of H1940 bluetooth chip"
|
|
|
|
|
depends on ARCH_H1940
|
|
|
|
|
select RFKILL
|
|
|
|
|
help
|
|
|
|
|
This is a simple driver that is able to control
|
|
|
|
|
the state of built in bluetooth chip on h1940.
|
|
|
|
|
|
|
|
|
|
config PM_H1940
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Internal node for H1940 and related PM
|
|
|
|
|
|
|
|
|
|
config MACH_N30
|
|
|
|
|
bool "Acer N30 family"
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want suppt for the Acer N30, Acer N35,
|
|
|
|
|
Navman PiN570, Yakumo AlphaX or Airis NC05 PDAs.
|
|
|
|
|
|
|
|
|
|
config MACH_OTOM
|
|
|
|
|
bool "NexVision OTOM Board"
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Nex Vision OTOM board
|
|
|
|
|
|
|
|
|
|
config MACH_QT2410
|
|
|
|
|
bool "QT2410"
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Armzone QT2410
|
|
|
|
|
|
|
|
|
|
config ARCH_SMDK2410
|
|
|
|
|
bool "SMDK2410/A9M2410"
|
2012-03-07 09:47:01 +00:00
|
|
|
select S3C24XX_SMDK
|
2013-02-08 21:41:36 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the SMDK2410 or the derived module A9M2410
|
|
|
|
|
<http://www.fsforth.de>
|
|
|
|
|
|
|
|
|
|
config MACH_TCT_HAMMER
|
|
|
|
|
bool "TCT Hammer Board"
|
|
|
|
|
select S3C_DEV_USB_HOST
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using the TinCanTools Hammer Board
|
|
|
|
|
<http://www.tincantools.com>
|
|
|
|
|
|
|
|
|
|
config MACH_VR1000
|
|
|
|
|
bool "Thorcom VR1000"
|
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 16:12:25 +00:00
|
|
|
select MACH_BAST_IDE
|
2012-02-06 00:38:19 +00:00
|
|
|
select S3C24XX_DCLK
|
2012-03-07 09:47:11 +00:00
|
|
|
select S3C24XX_SIMTEC_NOR
|
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 16:12:25 +00:00
|
|
|
select S3C24XX_SIMTEC_PM if PM
|
2012-03-07 09:47:11 +00:00
|
|
|
select S3C24XX_SIMTEC_USB
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 00:38:19 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Thorcom VR1000 board.
|
|
|
|
|
|
|
|
|
|
endif # CPU_S3C2410
|
|
|
|
|
|
2012-02-06 01:02:01 +00:00
|
|
|
config S3C2412_PM_SLEEP
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Internal config node to apply sleep for S3C2412 power management.
|
|
|
|
|
Can be selected by another SoCs such as S3C2416 with similar
|
|
|
|
|
sleep procedure.
|
|
|
|
|
|
|
|
|
|
if CPU_S3C2412
|
|
|
|
|
|
|
|
|
|
config CPU_S3C2412_ONLY
|
|
|
|
|
bool
|
2013-04-04 01:03:53 +00:00
|
|
|
depends on !CPU_S3C2410 && !CPU_S3C2416 && !CPU_S3C2440 && \
|
2013-04-04 01:04:00 +00:00
|
|
|
!CPU_S3C2442 && !CPU_S3C2443
|
2012-02-06 01:02:01 +00:00
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config S3C2412_DMA
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Internal config node for S3C2412 DMA support
|
|
|
|
|
|
|
|
|
|
config S3C2412_PM
|
|
|
|
|
bool
|
2013-02-08 19:13:15 +00:00
|
|
|
select S3C2412_PM_SLEEP
|
2013-02-12 18:09:10 +00:00
|
|
|
select SAMSUNG_WAKEMASK
|
2012-02-06 01:02:01 +00:00
|
|
|
help
|
|
|
|
|
Internal config node to apply S3C2412 power management
|
|
|
|
|
|
|
|
|
|
comment "S3C2412 Boards"
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# The "S3C2412 Boards" list is ordered alphabetically by option text.
|
|
|
|
|
# (without ARCH_ or MACH_)
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config MACH_JIVE
|
|
|
|
|
bool "Logitech Jive"
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 01:02:01 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Logitech Jive.
|
|
|
|
|
|
|
|
|
|
config MACH_JIVE_SHOW_BOOTLOADER
|
2013-01-17 02:53:15 +00:00
|
|
|
bool "Allow access to bootloader partitions in MTD"
|
|
|
|
|
depends on MACH_JIVE
|
2012-02-06 01:02:01 +00:00
|
|
|
|
|
|
|
|
config MACH_S3C2413
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Internal node for S3C2413 version of SMDK2413, so that
|
|
|
|
|
machine_is_s3c2413() will work when MACH_SMDK2413 is
|
|
|
|
|
selected
|
|
|
|
|
|
|
|
|
|
config MACH_SMDK2412
|
|
|
|
|
bool "SMDK2412"
|
|
|
|
|
select MACH_SMDK2413
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using an SMDK2412
|
|
|
|
|
|
|
|
|
|
Note, this shares support with SMDK2413, so will automatically
|
|
|
|
|
select MACH_SMDK2413.
|
|
|
|
|
|
|
|
|
|
config MACH_SMDK2413
|
|
|
|
|
bool "SMDK2413"
|
|
|
|
|
select MACH_S3C2413
|
2012-03-07 09:47:01 +00:00
|
|
|
select S3C24XX_SMDK
|
2012-02-06 01:02:01 +00:00
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 01:02:01 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using an SMDK2413
|
|
|
|
|
|
|
|
|
|
config MACH_VSTMS
|
|
|
|
|
bool "VMSTMS"
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 01:02:01 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using an VSTMS board
|
|
|
|
|
|
|
|
|
|
endif # CPU_S3C2412
|
|
|
|
|
|
2012-02-06 01:59:47 +00:00
|
|
|
if CPU_S3C2416
|
|
|
|
|
|
|
|
|
|
config S3C2416_PM
|
|
|
|
|
bool
|
|
|
|
|
select S3C2412_PM_SLEEP
|
|
|
|
|
help
|
|
|
|
|
Internal config node to apply S3C2416 power management
|
|
|
|
|
|
|
|
|
|
config S3C2416_SETUP_SDHCI
|
|
|
|
|
bool
|
|
|
|
|
select S3C2416_SETUP_SDHCI_GPIO
|
|
|
|
|
help
|
|
|
|
|
Internal helper functions for S3C2416 based SDHCI systems
|
|
|
|
|
|
|
|
|
|
config S3C2416_SETUP_SDHCI_GPIO
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for SDHCI gpio.
|
|
|
|
|
|
|
|
|
|
comment "S3C2416 Boards"
|
|
|
|
|
|
|
|
|
|
config MACH_SMDK2416
|
|
|
|
|
bool "SMDK2416"
|
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 16:12:25 +00:00
|
|
|
select S3C2416_SETUP_SDHCI
|
2012-03-07 09:47:01 +00:00
|
|
|
select S3C24XX_SMDK
|
2012-02-06 01:59:47 +00:00
|
|
|
select S3C_DEV_FB
|
|
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC1
|
|
|
|
|
select S3C_DEV_NAND
|
|
|
|
|
select S3C_DEV_USB_HOST
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using an SMDK2416
|
|
|
|
|
|
2013-05-20 16:06:04 +00:00
|
|
|
config MACH_S3C2416_DT
|
|
|
|
|
bool "Samsung S3C2416 machine using devicetree"
|
|
|
|
|
select CLKSRC_OF
|
|
|
|
|
select USE_OF
|
|
|
|
|
select PINCTRL
|
|
|
|
|
select PINCTRL_S3C24XX
|
|
|
|
|
help
|
|
|
|
|
Machine support for Samsung S3C2416 machines with device tree enabled.
|
|
|
|
|
Select this if a fdt blob is available for the S3C2416 SoC based board.
|
|
|
|
|
Note: This is under development and not all peripherals can be supported
|
|
|
|
|
with this machine file.
|
|
|
|
|
|
2012-02-06 01:59:47 +00:00
|
|
|
endif # CPU_S3C2416
|
|
|
|
|
|
2012-02-06 04:10:11 +00:00
|
|
|
if CPU_S3C2440
|
|
|
|
|
|
|
|
|
|
config S3C2440_DMA
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Support for S3C2440 specific DMA code5A
|
|
|
|
|
|
2013-01-21 23:39:09 +00:00
|
|
|
config S3C2440_XTAL_12000000
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Indicate that the build needs to support 12MHz system
|
|
|
|
|
crystal.
|
|
|
|
|
|
|
|
|
|
config S3C2440_XTAL_16934400
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Indicate that the build needs to support 16.9344MHz system
|
|
|
|
|
crystal.
|
|
|
|
|
|
|
|
|
|
config S3C2440_PLL_12000000
|
|
|
|
|
bool
|
2013-04-04 12:54:15 +00:00
|
|
|
depends on ARM_S3C2440_CPUFREQ && S3C2440_XTAL_12000000
|
|
|
|
|
default y if S3C24XX_PLL
|
2013-01-21 23:39:09 +00:00
|
|
|
help
|
|
|
|
|
PLL tables for S3C2440 or S3C2442 CPUs with 12MHz crystals.
|
|
|
|
|
|
|
|
|
|
config S3C2440_PLL_16934400
|
|
|
|
|
bool
|
2013-04-04 12:54:15 +00:00
|
|
|
depends on ARM_S3C2440_CPUFREQ && S3C2440_XTAL_16934400
|
|
|
|
|
default y if S3C24XX_PLL
|
2013-01-21 23:39:09 +00:00
|
|
|
help
|
|
|
|
|
PLL tables for S3C2440 or S3C2442 CPUs with 16.934MHz crystals.
|
|
|
|
|
|
2012-02-06 04:10:11 +00:00
|
|
|
comment "S3C2440 Boards"
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# The "S3C2440 Boards" list is ordered alphabetically by option text.
|
|
|
|
|
# (without ARCH_ or MACH_)
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config MACH_ANUBIS
|
|
|
|
|
bool "Simtec Electronics ANUBIS"
|
|
|
|
|
select HAVE_PATA_PLATFORM
|
|
|
|
|
select S3C2440_XTAL_12000000
|
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 16:12:25 +00:00
|
|
|
select S3C24XX_DCLK
|
|
|
|
|
select S3C24XX_SIMTEC_PM if PM
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Simtec Electronics ANUBIS
|
|
|
|
|
development system
|
|
|
|
|
|
|
|
|
|
config MACH_AT2440EVB
|
|
|
|
|
bool "Avantech AT2440EVB development board"
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 04:10:11 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the AT2440EVB development board
|
|
|
|
|
|
|
|
|
|
config MACH_MINI2440
|
|
|
|
|
bool "MINI2440 development board"
|
2014-02-12 20:22:13 +00:00
|
|
|
select EEPROM_AT24 if I2C
|
2012-02-06 04:10:11 +00:00
|
|
|
select LEDS_CLASS
|
2012-11-25 14:53:40 +00:00
|
|
|
select LEDS_TRIGGERS
|
2012-02-06 04:10:11 +00:00
|
|
|
select LEDS_TRIGGER_BACKLIGHT
|
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 16:12:25 +00:00
|
|
|
select NEW_LEDS
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C_DEV_NAND
|
|
|
|
|
select S3C_DEV_USB_HOST
|
2012-11-22 05:29:18 +00:00
|
|
|
select S3C_SETUP_CAMIF
|
2012-02-06 04:10:11 +00:00
|
|
|
help
|
|
|
|
|
Say Y here to select support for the MINI2440. Is a 10cm x 10cm board
|
|
|
|
|
available via various sources. It can come with a 3.5" or 7" touch LCD.
|
|
|
|
|
|
|
|
|
|
config MACH_NEXCODER_2440
|
|
|
|
|
bool "NexVision NEXCODER 2440 Light Board"
|
|
|
|
|
select S3C2440_XTAL_12000000
|
|
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 04:10:11 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board
|
|
|
|
|
|
|
|
|
|
config MACH_OSIRIS
|
|
|
|
|
bool "Simtec IM2440D20 (OSIRIS) module"
|
2013-04-04 12:54:15 +00:00
|
|
|
select S3C2410_IOTIMING if ARM_S3C2440_CPUFREQ
|
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 16:12:25 +00:00
|
|
|
select S3C2440_XTAL_12000000
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C24XX_DCLK
|
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 16:12:25 +00:00
|
|
|
select S3C24XX_SIMTEC_PM if PM
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 04:10:11 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Simtec IM2440D20 module, also
|
|
|
|
|
known as the Osiris.
|
|
|
|
|
|
|
|
|
|
config MACH_OSIRIS_DVS
|
|
|
|
|
tristate "Simtec IM2440D20 (OSIRIS) Dynamic Voltage Scaling driver"
|
|
|
|
|
depends on MACH_OSIRIS
|
2014-03-21 12:49:04 +00:00
|
|
|
depends on TPS65010
|
2012-02-06 04:10:11 +00:00
|
|
|
help
|
|
|
|
|
Say Y/M here if you want to have dynamic voltage scaling support
|
|
|
|
|
on the Simtec IM2440D20 (OSIRIS) module via the TPS65011.
|
|
|
|
|
|
|
|
|
|
The DVS driver alters the voltage supplied to the ARM core
|
|
|
|
|
depending on the frequency it is running at. The driver itself
|
|
|
|
|
does not do any of the frequency alteration, which is left up
|
|
|
|
|
to the cpufreq driver.
|
|
|
|
|
|
|
|
|
|
config MACH_RX3715
|
|
|
|
|
bool "HP iPAQ rx3715"
|
|
|
|
|
select PM_H1940 if PM
|
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 16:12:25 +00:00
|
|
|
select S3C2440_XTAL_16934400
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C_DEV_NAND
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using the HP iPAQ rx3715.
|
|
|
|
|
|
|
|
|
|
config ARCH_S3C2440
|
|
|
|
|
bool "SMDK2440"
|
|
|
|
|
select S3C2440_XTAL_16934400
|
2012-03-07 09:47:01 +00:00
|
|
|
select S3C24XX_SMDK
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C_DEV_NAND
|
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 16:12:25 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
2012-02-06 04:10:11 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you are using the SMDK2440.
|
|
|
|
|
|
|
|
|
|
config SMDK2440_CPU2440
|
|
|
|
|
bool "SMDK2440 with S3C2440 CPU module"
|
|
|
|
|
default y if ARCH_S3C2440
|
|
|
|
|
select S3C2440_XTAL_16934400
|
|
|
|
|
|
|
|
|
|
endif # CPU_S3C2440
|
|
|
|
|
|
|
|
|
|
if CPU_S3C2442
|
|
|
|
|
|
|
|
|
|
comment "S3C2442 Boards"
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# The "S3C2442 Boards" list is ordered alphabetically by option text.
|
|
|
|
|
# (without ARCH_ or MACH_)
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config MACH_NEO1973_GTA02
|
|
|
|
|
bool "Openmoko GTA02 / Freerunner phone"
|
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 16:12:25 +00:00
|
|
|
select I2C
|
2012-02-06 04:10:11 +00:00
|
|
|
select MFD_PCF50633
|
|
|
|
|
select PCF50633_GPIO
|
|
|
|
|
select POWER_SUPPLY
|
2012-08-04 07:52:19 +00:00
|
|
|
select S3C24XX_PWM
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C_DEV_USB_HOST
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using the Openmoko GTA02 / Freerunner GSM Phone
|
|
|
|
|
|
|
|
|
|
config MACH_RX1950
|
|
|
|
|
bool "HP iPAQ rx1950"
|
|
|
|
|
select I2C
|
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 16:12:25 +00:00
|
|
|
select PM_H1940 if PM
|
2013-04-04 12:54:15 +00:00
|
|
|
select S3C2410_IOTIMING if ARM_S3C2440_CPUFREQ
|
2012-02-06 04:10:11 +00:00
|
|
|
select S3C2440_XTAL_16934400
|
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 16:12:25 +00:00
|
|
|
select S3C24XX_DCLK
|
|
|
|
|
select S3C24XX_PWM
|
|
|
|
|
select S3C_DEV_NAND
|
2012-02-06 04:10:11 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you're using HP iPAQ rx1950
|
|
|
|
|
|
2013-03-22 10:03:55 +00:00
|
|
|
endif # CPU_S3C2442
|
2012-02-06 04:10:11 +00:00
|
|
|
|
2012-03-02 22:49:12 +00:00
|
|
|
if CPU_S3C2443 || CPU_S3C2416
|
|
|
|
|
|
|
|
|
|
config S3C2443_COMMON
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common code for the S3C2443 and similar processors, which includes
|
|
|
|
|
the S3C2416 and S3C2450.
|
|
|
|
|
|
2012-02-06 04:21:03 +00:00
|
|
|
config S3C2443_DMA
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Internal config node for S3C2443 DMA support
|
|
|
|
|
|
2012-04-25 01:07:10 +00:00
|
|
|
config S3C2443_SETUP_SPI
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for SPI GPIO configurations
|
|
|
|
|
|
2012-03-07 09:53:17 +00:00
|
|
|
endif # CPU_S3C2443 || CPU_S3C2416
|
|
|
|
|
|
|
|
|
|
if CPU_S3C2443
|
|
|
|
|
|
2012-02-06 04:21:03 +00:00
|
|
|
comment "S3C2443 Boards"
|
|
|
|
|
|
|
|
|
|
config MACH_SMDK2443
|
|
|
|
|
bool "SMDK2443"
|
2012-03-07 09:47:01 +00:00
|
|
|
select S3C24XX_SMDK
|
2012-02-06 04:21:03 +00:00
|
|
|
select S3C_DEV_HSMMC1
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are using an SMDK2443
|
|
|
|
|
|
|
|
|
|
endif # CPU_S3C2443
|
|
|
|
|
|
2012-02-06 00:38:19 +00:00
|
|
|
endmenu # SAMSUNG S3C24XX SoCs Support
|
|
|
|
|
|
|
|
|
|
endif # ARCH_S3C24XX
|
