2010-02-24 07:40:29 +00:00
|
|
|
# arch/arm/mach-s5pv210/Kconfig
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2010 Samsung Electronics Co., Ltd.
|
|
|
|
|
# http://www.samsung.com/
|
|
|
|
|
#
|
|
|
|
|
# Licensed under GPLv2
|
|
|
|
|
|
|
|
|
|
# Configuration options for the S5PV210/S5PC110
|
|
|
|
|
|
|
|
|
|
if ARCH_S5PV210
|
|
|
|
|
|
|
|
|
|
config CPU_S5PV210
|
|
|
|
|
bool
|
2010-05-17 07:56:26 +00:00
|
|
|
select S5P_EXT_INT
|
2011-10-04 11:25:51 +00:00
|
|
|
select S5P_PM if PM
|
2011-10-04 11:25:51 +00:00
|
|
|
select S5P_SLEEP 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 SAMSUNG_DMADEV
|
2013-01-10 02:47:03 +00:00
|
|
|
select SAMSUNG_HRT
|
2010-02-24 07:40:29 +00:00
|
|
|
help
|
|
|
|
|
Enable S5PV210 CPU support
|
|
|
|
|
|
2010-05-20 06:13:07 +00:00
|
|
|
config S5PV210_SETUP_I2C1
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 1.
|
|
|
|
|
|
|
|
|
|
config S5PV210_SETUP_I2C2
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 2.
|
|
|
|
|
|
2010-06-08 08:11:43 +00:00
|
|
|
config S5PV210_SETUP_IDE
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for S5PV210 IDE GPIO configurations
|
|
|
|
|
|
2010-05-20 06:13:04 +00:00
|
|
|
config S5PV210_SETUP_FB_24BPP
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for S5PV210 with an 24bpp RGB display helper.
|
|
|
|
|
|
2010-06-21 07:28:28 +00:00
|
|
|
config S5PV210_SETUP_KEYPAD
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for keypad.
|
|
|
|
|
|
2010-05-20 06:13:07 +00:00
|
|
|
config S5PV210_SETUP_SDHCI
|
|
|
|
|
bool
|
|
|
|
|
select S5PV210_SETUP_SDHCI_GPIO
|
|
|
|
|
help
|
|
|
|
|
Internal helper functions for S5PV210 based SDHCI systems
|
|
|
|
|
|
|
|
|
|
config S5PV210_SETUP_SDHCI_GPIO
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for SDHCI gpio.
|
|
|
|
|
|
2011-03-10 12:49:31 +00:00
|
|
|
config S5PV210_SETUP_FIMC
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for the camera interfaces.
|
|
|
|
|
|
2011-12-23 01:14:55 +00:00
|
|
|
config S5PV210_SETUP_SPI
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for SPI GPIO configurations.
|
|
|
|
|
|
2012-03-08 10:52:25 +00:00
|
|
|
config S5PV210_SETUP_USB_PHY
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for USB PHY controller
|
|
|
|
|
|
2010-07-13 02:11:47 +00:00
|
|
|
menu "S5PC110 Machines"
|
2010-05-20 09:48:43 +00:00
|
|
|
|
|
|
|
|
config MACH_AQUILA
|
2010-07-13 02:11:47 +00:00
|
|
|
bool "Aquila"
|
2010-05-20 09:48:43 +00:00
|
|
|
select CPU_S5PV210
|
|
|
|
|
select S3C_DEV_FB
|
2010-08-05 09:00:12 +00:00
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC1
|
|
|
|
|
select S3C_DEV_HSMMC2
|
2010-08-06 12:49:18 +00:00
|
|
|
select S5PV210_SETUP_FB_24BPP
|
|
|
|
|
select S5PV210_SETUP_SDHCI
|
2012-05-12 23:24:14 +00:00
|
|
|
select S5PV210_SETUP_USB_PHY
|
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 S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
|
|
|
|
select S5P_DEV_ONENAND
|
2010-05-20 09:48:43 +00:00
|
|
|
help
|
|
|
|
|
Machine support for the Samsung Aquila target based on S5PC110 SoC
|
|
|
|
|
|
2010-05-19 14:15:32 +00:00
|
|
|
config MACH_GONI
|
|
|
|
|
bool "GONI"
|
|
|
|
|
select CPU_S5PV210
|
2010-07-14 10:38:18 +00:00
|
|
|
select S3C_DEV_FB
|
2010-08-05 09:00:18 +00:00
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC1
|
|
|
|
|
select S3C_DEV_HSMMC2
|
2010-10-04 07:39:22 +00:00
|
|
|
select S3C_DEV_I2C1
|
2010-10-04 09:38:12 +00:00
|
|
|
select S3C_DEV_I2C2
|
2010-09-30 11:59:46 +00:00
|
|
|
select S3C_DEV_USB_HSOTG
|
2010-08-06 12:49:18 +00:00
|
|
|
select S5PV210_SETUP_FB_24BPP
|
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 S5PV210_SETUP_FIMC
|
2010-10-04 07:39:22 +00:00
|
|
|
select S5PV210_SETUP_I2C1
|
2010-10-04 09:38:12 +00:00
|
|
|
select S5PV210_SETUP_I2C2
|
2010-09-08 23:17:43 +00:00
|
|
|
select S5PV210_SETUP_KEYPAD
|
2010-08-06 12:49:18 +00:00
|
|
|
select S5PV210_SETUP_SDHCI
|
2012-03-08 10:52:25 +00:00
|
|
|
select S5PV210_SETUP_USB_PHY
|
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 S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
|
|
|
|
select S5P_DEV_MFC
|
|
|
|
|
select S5P_DEV_ONENAND
|
|
|
|
|
select S5P_DEV_TV
|
|
|
|
|
select S5P_GPIO_INT
|
|
|
|
|
select SAMSUNG_DEV_KEYPAD
|
2010-05-19 14:15:32 +00:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung GONI board
|
|
|
|
|
S5PC110(MCP) is one of package option of S5PV210
|
2010-02-24 07:40:29 +00:00
|
|
|
|
2010-07-13 02:11:47 +00:00
|
|
|
config MACH_SMDKC110
|
|
|
|
|
bool "SMDKC110"
|
|
|
|
|
select CPU_S5PV210
|
2010-07-21 03:51:56 +00:00
|
|
|
select S3C_DEV_I2C1
|
|
|
|
|
select S3C_DEV_I2C2
|
2010-07-21 08:36:02 +00:00
|
|
|
select S3C_DEV_RTC
|
2010-07-13 02:11:47 +00:00
|
|
|
select S3C_DEV_WDT
|
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 S5PV210_SETUP_I2C1
|
|
|
|
|
select S5PV210_SETUP_I2C2
|
|
|
|
|
select S5PV210_SETUP_IDE
|
2012-03-09 15:00:44 +00:00
|
|
|
select S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
2012-03-09 15:00:35 +00:00
|
|
|
select S5P_DEV_MFC
|
2010-08-06 12:49:18 +00:00
|
|
|
select SAMSUNG_DEV_IDE
|
2010-07-13 02:11:47 +00:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung SMDKC110
|
|
|
|
|
S5PC110(MCP) is one of package option of S5PV210
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
menu "S5PV210 Machines"
|
|
|
|
|
|
2010-02-24 07:40:29 +00:00
|
|
|
config MACH_SMDKV210
|
|
|
|
|
bool "SMDKV210"
|
|
|
|
|
select CPU_S5PV210
|
2010-11-26 04:19:49 +00:00
|
|
|
select S3C_DEV_FB
|
2010-06-14 01:18:56 +00:00
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC1
|
|
|
|
|
select S3C_DEV_HSMMC2
|
|
|
|
|
select S3C_DEV_HSMMC3
|
2010-07-21 03:51:56 +00:00
|
|
|
select S3C_DEV_I2C1
|
|
|
|
|
select S3C_DEV_I2C2
|
2010-08-06 12:49:18 +00:00
|
|
|
select S3C_DEV_RTC
|
2012-06-20 07:29:52 +00:00
|
|
|
select S3C_DEV_USB_HSOTG
|
2010-08-06 12:49:18 +00:00
|
|
|
select S3C_DEV_WDT
|
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 S5PV210_SETUP_FB_24BPP
|
|
|
|
|
select S5PV210_SETUP_I2C1
|
|
|
|
|
select S5PV210_SETUP_I2C2
|
|
|
|
|
select S5PV210_SETUP_IDE
|
|
|
|
|
select S5PV210_SETUP_KEYPAD
|
|
|
|
|
select S5PV210_SETUP_SDHCI
|
|
|
|
|
select S5PV210_SETUP_USB_PHY
|
2012-03-09 15:00:40 +00:00
|
|
|
select S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
2012-03-09 16:23:43 +00:00
|
|
|
select S5P_DEV_JPEG
|
2012-03-09 15:00:31 +00:00
|
|
|
select S5P_DEV_MFC
|
2010-05-20 02:39:54 +00:00
|
|
|
select SAMSUNG_DEV_ADC
|
2011-07-20 14:45:22 +00:00
|
|
|
select SAMSUNG_DEV_BACKLIGHT
|
2010-06-08 08:11:43 +00:00
|
|
|
select SAMSUNG_DEV_IDE
|
2010-06-21 07:47:16 +00:00
|
|
|
select SAMSUNG_DEV_KEYPAD
|
2011-02-28 17:32:32 +00:00
|
|
|
select SAMSUNG_DEV_PWM
|
2010-05-20 02:39:54 +00:00
|
|
|
select SAMSUNG_DEV_TS
|
2010-02-24 07:40:29 +00:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung SMDKV210
|
|
|
|
|
|
2010-09-29 11:51:03 +00:00
|
|
|
config MACH_TORBRECK
|
|
|
|
|
bool "Torbreck"
|
|
|
|
|
select ARCH_SPARSEMEM_ENABLE
|
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 CPU_S5PV210
|
2010-09-29 11:51:03 +00:00
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC1
|
|
|
|
|
select S3C_DEV_HSMMC2
|
|
|
|
|
select S3C_DEV_HSMMC3
|
|
|
|
|
select S3C_DEV_I2C1
|
|
|
|
|
select S3C_DEV_I2C2
|
|
|
|
|
select S3C_DEV_RTC
|
|
|
|
|
select S3C_DEV_WDT
|
|
|
|
|
select S5PV210_SETUP_I2C1
|
|
|
|
|
select S5PV210_SETUP_I2C2
|
|
|
|
|
select S5PV210_SETUP_SDHCI
|
|
|
|
|
help
|
|
|
|
|
Machine support for aESOP Torbreck
|
|
|
|
|
|
2010-07-13 02:11:47 +00:00
|
|
|
endmenu
|
2010-02-24 07:40:29 +00:00
|
|
|
|
|
|
|
|
endif
|
