2011-11-06 12:54:56 +08:00
|
|
|
# arch/arm/mach-exynos/Kconfig
|
2010-07-16 11:15:38 +08:00
|
|
|
#
|
2011-02-14 14:05:27 +08:00
|
|
|
# Copyright (c) 2010-2011 Samsung Electronics Co., Ltd.
|
2010-07-16 11:15:38 +08:00
|
|
|
# http://www.samsung.com/
|
|
|
|
|
#
|
|
|
|
|
# Licensed under GPLv2
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
# Configuration options for the EXYNOS4
|
2010-07-16 11:15:38 +08:00
|
|
|
|
2011-11-06 12:54:56 +08:00
|
|
|
if ARCH_EXYNOS
|
|
|
|
|
|
|
|
|
|
menu "SAMSUNG EXYNOS SoCs Support"
|
|
|
|
|
|
|
|
|
|
config ARCH_EXYNOS4
|
|
|
|
|
bool "SAMSUNG EXYNOS4"
|
2012-03-13 22:44:39 +08:00
|
|
|
default y
|
2011-12-07 23:38:04 +08:00
|
|
|
select HAVE_SMP
|
2011-11-29 23:56:19 +08:00
|
|
|
select MIGHT_HAVE_CACHE_L2X0
|
2011-11-06 12:54:56 +08:00
|
|
|
help
|
|
|
|
|
Samsung EXYNOS4 SoCs based systems
|
|
|
|
|
|
2012-03-13 22:44:39 +08:00
|
|
|
config ARCH_EXYNOS5
|
|
|
|
|
bool "SAMSUNG EXYNOS5"
|
|
|
|
|
select HAVE_SMP
|
|
|
|
|
help
|
|
|
|
|
Samsung EXYNOS5 (Cortex-A15) SoC based systems
|
2011-11-06 12:54:56 +08:00
|
|
|
|
|
|
|
|
comment "EXYNOS SoCs"
|
2010-07-16 11:15:38 +08:00
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config CPU_EXYNOS4210
|
2011-11-06 12:54:56 +08:00
|
|
|
bool "SAMSUNG EXYNOS4210"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_EXYNOS4
|
2011-10-02 03:09:39 +08:00
|
|
|
select ARM_CPU_SUSPEND 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-07 00:12:25 +08:00
|
|
|
select PM_GENERIC_DOMAINS
|
2011-10-04 19:25:51 +08:00
|
|
|
select S5P_PM if PM
|
2011-10-04 19:25:51 +08: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-07 00:12:25 +08:00
|
|
|
select SAMSUNG_DMADEV
|
2010-07-16 11:15:38 +08:00
|
|
|
help
|
2011-02-14 14:05:27 +08:00
|
|
|
Enable EXYNOS4210 CPU support
|
2010-07-16 11:15:38 +08:00
|
|
|
|
2011-08-24 16:25:09 +08:00
|
|
|
config SOC_EXYNOS4212
|
2011-11-06 12:54:56 +08:00
|
|
|
bool "SAMSUNG EXYNOS4212"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_EXYNOS4
|
2011-10-04 19:25:51 +08:00
|
|
|
select S5P_PM if PM
|
2011-10-04 19:25:51 +08: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-07 00:12:25 +08:00
|
|
|
select SAMSUNG_DMADEV
|
2011-08-24 16:25:09 +08:00
|
|
|
help
|
|
|
|
|
Enable EXYNOS4212 SoC support
|
|
|
|
|
|
2011-10-04 16:08:56 +08:00
|
|
|
config SOC_EXYNOS4412
|
2011-11-06 12:54:56 +08:00
|
|
|
bool "SAMSUNG EXYNOS4412"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_EXYNOS4
|
2012-02-15 12:16:15 +08:00
|
|
|
select SAMSUNG_DMADEV
|
2011-10-04 16:08:56 +08:00
|
|
|
help
|
|
|
|
|
Enable EXYNOS4412 SoC support
|
|
|
|
|
|
2012-03-13 22:44:39 +08:00
|
|
|
config SOC_EXYNOS5250
|
|
|
|
|
bool "SAMSUNG EXYNOS5250"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_EXYNOS5
|
2012-02-17 11:23:51 +08:00
|
|
|
select S5P_PM if PM
|
|
|
|
|
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-07 00:12:25 +08:00
|
|
|
select SAMSUNG_DMADEV
|
2012-03-13 22:44:39 +08:00
|
|
|
help
|
|
|
|
|
Enable EXYNOS5250 SoC support
|
|
|
|
|
|
2011-03-11 09:39:57 +08:00
|
|
|
config EXYNOS4_MCT
|
2011-07-16 09:49:53 +08:00
|
|
|
bool
|
|
|
|
|
default y
|
2011-03-11 09:39:57 +08:00
|
|
|
help
|
|
|
|
|
Use MCT (Multi Core Timer) as kernel timers
|
|
|
|
|
|
2012-05-12 15:40:52 +08:00
|
|
|
config EXYNOS_DEV_DMA
|
2011-10-24 19:57:43 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Compile in amba device definitions for DMA controller
|
|
|
|
|
|
2011-03-25 09:46:16 +08:00
|
|
|
config EXYNOS4_DEV_AHCI
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Compile in platform device definitions for AHCI
|
|
|
|
|
|
2012-05-12 05:42:33 +08:00
|
|
|
config EXYNOS_DEV_DRM
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Compile in platform device definitions for core DRM device
|
|
|
|
|
|
2011-07-21 14:46:26 +08:00
|
|
|
config EXYNOS4_SETUP_FIMD0
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for FIMD0.
|
|
|
|
|
|
2012-04-05 00:23:02 +08:00
|
|
|
config EXYNOS_DEV_SYSMMU
|
2011-02-14 14:05:27 +08:00
|
|
|
bool
|
|
|
|
|
help
|
2012-04-05 00:23:02 +08:00
|
|
|
Common setup code for SYSTEM MMU in EXYNOS platforms
|
2011-02-14 14:05:27 +08:00
|
|
|
|
2011-07-20 23:34:58 +08:00
|
|
|
config EXYNOS4_DEV_DWMCI
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Compile in platform device definitions for DWMCI
|
|
|
|
|
|
2011-12-23 10:19:36 +08:00
|
|
|
config EXYNOS4_DEV_USB_OHCI
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Compile in platform device definition for USB OHCI
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_I2C1
|
2010-08-05 16:10:24 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 1.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_I2C2
|
2010-08-05 16:10:24 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 2.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_I2C3
|
2010-10-12 06:49:24 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 3.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_I2C4
|
2010-10-12 06:49:24 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 4.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_I2C5
|
2010-10-12 06:49:24 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 5.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_I2C6
|
2010-10-12 06:49:24 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 6.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_I2C7
|
2010-10-12 06:49:24 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for i2c bus 7.
|
|
|
|
|
|
2011-03-05 08:44:09 +08:00
|
|
|
config EXYNOS4_SETUP_KEYPAD
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for keypad.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_SDHCI
|
2010-10-06 10:09:42 +08:00
|
|
|
bool
|
2011-02-14 14:05:27 +08:00
|
|
|
select EXYNOS4_SETUP_SDHCI_GPIO
|
2010-10-06 10:09:42 +08:00
|
|
|
help
|
2011-02-14 14:05:27 +08:00
|
|
|
Internal helper functions for EXYNOS4 based SDHCI systems.
|
2010-10-06 10:09:42 +08:00
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SETUP_SDHCI_GPIO
|
2010-10-06 10:09:42 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for SDHCI gpio.
|
|
|
|
|
|
2011-03-10 20:49:31 +08:00
|
|
|
config EXYNOS4_SETUP_FIMC
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for the camera interfaces.
|
|
|
|
|
|
2011-06-03 15:04:14 +08:00
|
|
|
config EXYNOS4_SETUP_USB_PHY
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for USB PHY controller
|
|
|
|
|
|
2012-05-13 08:00:47 +08:00
|
|
|
config EXYNOS_SETUP_SPI
|
2011-12-26 15:42:15 +08:00
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Common setup code for SPI GPIO configurations.
|
|
|
|
|
|
2010-07-16 11:15:38 +08:00
|
|
|
# machine support
|
|
|
|
|
|
2011-11-06 12:54:56 +08:00
|
|
|
if ARCH_EXYNOS4
|
2010-08-06 19:33:46 +08:00
|
|
|
|
2011-08-24 16:25:09 +08:00
|
|
|
comment "EXYNOS4210 Boards"
|
|
|
|
|
|
2010-08-06 19:12:06 +08:00
|
|
|
config MACH_SMDKC210
|
|
|
|
|
bool "SMDKC210"
|
2011-08-18 20:14:28 +08:00
|
|
|
select MACH_SMDKV310
|
2010-08-06 19:12:06 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung SMDKC210
|
2010-08-06 19:33:46 +08:00
|
|
|
|
|
|
|
|
config MACH_SMDKV310
|
|
|
|
|
bool "SMDKV310"
|
2011-02-14 14:05:27 +08:00
|
|
|
select CPU_EXYNOS4210
|
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-07 00:12:25 +08:00
|
|
|
select EXYNOS4_DEV_AHCI
|
|
|
|
|
select EXYNOS4_DEV_USB_OHCI
|
|
|
|
|
select EXYNOS4_SETUP_FIMD0
|
|
|
|
|
select EXYNOS4_SETUP_I2C1
|
|
|
|
|
select EXYNOS4_SETUP_KEYPAD
|
|
|
|
|
select EXYNOS4_SETUP_SDHCI
|
|
|
|
|
select EXYNOS4_SETUP_USB_PHY
|
|
|
|
|
select EXYNOS_DEV_DMA
|
|
|
|
|
select EXYNOS_DEV_DRM
|
|
|
|
|
select EXYNOS_DEV_SYSMMU
|
|
|
|
|
select S3C24XX_PWM
|
|
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC1
|
|
|
|
|
select S3C_DEV_HSMMC2
|
|
|
|
|
select S3C_DEV_HSMMC3
|
|
|
|
|
select S3C_DEV_I2C1
|
2010-09-20 14:25:51 +08:00
|
|
|
select S3C_DEV_RTC
|
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-07 00:12:25 +08:00
|
|
|
select S3C_DEV_USB_HSOTG
|
2010-09-20 14:33:04 +08:00
|
|
|
select S3C_DEV_WDT
|
2011-09-28 10:13:30 +08:00
|
|
|
select S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
|
|
|
|
select S5P_DEV_FIMC3
|
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-07 00:12:25 +08:00
|
|
|
select S5P_DEV_FIMD0
|
2012-03-09 22:51:45 +08:00
|
|
|
select S5P_DEV_G2D
|
2011-09-27 06:37:18 +08:00
|
|
|
select S5P_DEV_I2C_HDMIPHY
|
2012-03-10 00:19:21 +08:00
|
|
|
select S5P_DEV_JPEG
|
2011-08-12 17:21:27 +08:00
|
|
|
select S5P_DEV_MFC
|
2011-09-27 06:37:18 +08:00
|
|
|
select S5P_DEV_TV
|
2011-09-28 09:33:25 +08:00
|
|
|
select S5P_DEV_USB_EHCI
|
2011-07-20 22:45:21 +08:00
|
|
|
select SAMSUNG_DEV_BACKLIGHT
|
2011-02-22 16:16:58 +08:00
|
|
|
select SAMSUNG_DEV_KEYPAD
|
2011-07-20 22:45:21 +08:00
|
|
|
select SAMSUNG_DEV_PWM
|
2010-08-06 19:33:46 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung SMDKV310
|
|
|
|
|
|
2011-03-04 14:24:23 +08:00
|
|
|
config MACH_ARMLEX4210
|
|
|
|
|
bool "ARMLEX4210"
|
|
|
|
|
select CPU_EXYNOS4210
|
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-07 00:12:25 +08:00
|
|
|
select EXYNOS4_DEV_AHCI
|
|
|
|
|
select EXYNOS4_SETUP_SDHCI
|
|
|
|
|
select EXYNOS_DEV_DMA
|
2011-03-04 14:24:23 +08:00
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC2
|
|
|
|
|
select S3C_DEV_HSMMC3
|
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-07 00:12:25 +08:00
|
|
|
select S3C_DEV_RTC
|
|
|
|
|
select S3C_DEV_WDT
|
2011-03-04 14:24:23 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung ARMLEX4210 based on EXYNOS4210
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config MACH_UNIVERSAL_C210
|
|
|
|
|
bool "Mobile UNIVERSAL_C210 Board"
|
2012-05-12 05:17:59 +08:00
|
|
|
select CLKSRC_MMIO
|
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-07 00:12:25 +08:00
|
|
|
select CPU_EXYNOS4210
|
|
|
|
|
select EXYNOS4_SETUP_FIMC
|
|
|
|
|
select EXYNOS4_SETUP_FIMD0
|
|
|
|
|
select EXYNOS4_SETUP_I2C1
|
|
|
|
|
select EXYNOS4_SETUP_I2C3
|
|
|
|
|
select EXYNOS4_SETUP_I2C5
|
|
|
|
|
select EXYNOS4_SETUP_SDHCI
|
|
|
|
|
select EXYNOS4_SETUP_USB_PHY
|
|
|
|
|
select EXYNOS_DEV_DMA
|
|
|
|
|
select EXYNOS_DEV_DRM
|
|
|
|
|
select EXYNOS_DEV_SYSMMU
|
2012-05-12 05:17:59 +08:00
|
|
|
select HAVE_SCHED_CLOCK
|
2011-02-14 14:05:27 +08:00
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC2
|
|
|
|
|
select S3C_DEV_HSMMC3
|
|
|
|
|
select S3C_DEV_I2C1
|
2011-06-22 12:43:39 +08:00
|
|
|
select S3C_DEV_I2C3
|
2011-03-04 09:19:52 +08:00
|
|
|
select S3C_DEV_I2C5
|
2012-05-13 07:27:33 +08:00
|
|
|
select S3C_DEV_USB_HSOTG
|
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-07 00:12:25 +08:00
|
|
|
select S5P_DEV_CSIS0
|
|
|
|
|
select S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
|
|
|
|
select S5P_DEV_FIMC3
|
|
|
|
|
select S5P_DEV_FIMD0
|
|
|
|
|
select S5P_DEV_G2D
|
2011-09-16 17:48:32 +08:00
|
|
|
select S5P_DEV_I2C_HDMIPHY
|
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-07 00:12:25 +08:00
|
|
|
select S5P_DEV_JPEG
|
2011-07-21 15:43:20 +08:00
|
|
|
select S5P_DEV_MFC
|
2011-02-14 14:05:27 +08:00
|
|
|
select S5P_DEV_ONENAND
|
2011-09-16 17:48:32 +08:00
|
|
|
select S5P_DEV_TV
|
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-07 00:12:25 +08:00
|
|
|
select S5P_GPIO_INT
|
|
|
|
|
select S5P_HRT
|
2011-09-27 06:18:55 +08:00
|
|
|
select S5P_SETUP_MIPIPHY
|
2011-02-14 14:05:27 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung Mobile Universal S5PC210 Reference
|
|
|
|
|
Board.
|
|
|
|
|
|
2011-02-28 19:39:43 +08:00
|
|
|
config MACH_NURI
|
|
|
|
|
bool "Mobile NURI Board"
|
|
|
|
|
select CPU_EXYNOS4210
|
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-07 00:12:25 +08:00
|
|
|
select EXYNOS4_SETUP_FIMC
|
|
|
|
|
select EXYNOS4_SETUP_FIMD0
|
|
|
|
|
select EXYNOS4_SETUP_I2C1
|
|
|
|
|
select EXYNOS4_SETUP_I2C3
|
|
|
|
|
select EXYNOS4_SETUP_I2C5
|
|
|
|
|
select EXYNOS4_SETUP_I2C6
|
|
|
|
|
select EXYNOS4_SETUP_SDHCI
|
|
|
|
|
select EXYNOS4_SETUP_USB_PHY
|
|
|
|
|
select EXYNOS_DEV_DMA
|
|
|
|
|
select EXYNOS_DEV_DRM
|
2011-02-28 19:39:43 +08:00
|
|
|
select S3C_DEV_HSMMC
|
|
|
|
|
select S3C_DEV_HSMMC2
|
|
|
|
|
select S3C_DEV_HSMMC3
|
|
|
|
|
select S3C_DEV_I2C1
|
2011-03-23 14:25:14 +08:00
|
|
|
select S3C_DEV_I2C3
|
2011-02-28 19:39:43 +08:00
|
|
|
select S3C_DEV_I2C5
|
2012-01-31 12:27:02 +08:00
|
|
|
select S3C_DEV_I2C6
|
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-07 00:12:25 +08:00
|
|
|
select S3C_DEV_RTC
|
2012-05-13 07:25:24 +08:00
|
|
|
select S3C_DEV_USB_HSOTG
|
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-07 00:12:25 +08:00
|
|
|
select S3C_DEV_WDT
|
2011-10-13 14:41:00 +08:00
|
|
|
select S5P_DEV_CSIS0
|
|
|
|
|
select S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
|
|
|
|
select S5P_DEV_FIMC3
|
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-07 00:12:25 +08:00
|
|
|
select S5P_DEV_FIMD0
|
2011-12-27 16:16:47 +08:00
|
|
|
select S5P_DEV_G2D
|
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-07 00:12:25 +08:00
|
|
|
select S5P_DEV_JPEG
|
2011-07-21 15:43:25 +08:00
|
|
|
select S5P_DEV_MFC
|
2011-04-08 12:22:11 +08:00
|
|
|
select S5P_DEV_USB_EHCI
|
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-07 00:12:25 +08:00
|
|
|
select S5P_GPIO_INT
|
2011-10-13 14:41:00 +08:00
|
|
|
select S5P_SETUP_MIPIPHY
|
2011-07-20 20:08:18 +08:00
|
|
|
select SAMSUNG_DEV_ADC
|
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-07 00:12:25 +08:00
|
|
|
select SAMSUNG_DEV_PWM
|
2011-02-28 19:39:43 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung Mobile NURI Board.
|
|
|
|
|
|
2011-07-21 15:19:19 +08:00
|
|
|
config MACH_ORIGEN
|
|
|
|
|
bool "ORIGEN"
|
|
|
|
|
select CPU_EXYNOS4210
|
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-07 00:12:25 +08:00
|
|
|
select EXYNOS4_DEV_USB_OHCI
|
|
|
|
|
select EXYNOS4_SETUP_FIMD0
|
|
|
|
|
select EXYNOS4_SETUP_SDHCI
|
|
|
|
|
select EXYNOS4_SETUP_USB_PHY
|
|
|
|
|
select EXYNOS_DEV_DMA
|
|
|
|
|
select EXYNOS_DEV_DRM
|
|
|
|
|
select EXYNOS_DEV_SYSMMU
|
|
|
|
|
select S3C24XX_PWM
|
2011-08-31 15:57:37 +08:00
|
|
|
select S3C_DEV_HSMMC
|
2011-07-21 15:19:19 +08:00
|
|
|
select S3C_DEV_HSMMC2
|
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-07 00:12:25 +08:00
|
|
|
select S3C_DEV_RTC
|
2012-05-20 06:46:40 +08:00
|
|
|
select S3C_DEV_USB_HSOTG
|
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-07 00:12:25 +08:00
|
|
|
select S3C_DEV_WDT
|
2011-08-31 14:52:27 +08:00
|
|
|
select S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
|
|
|
|
select S5P_DEV_FIMC3
|
2011-10-03 08:12:56 +08:00
|
|
|
select S5P_DEV_FIMD0
|
2011-12-29 15:46:16 +08:00
|
|
|
select S5P_DEV_G2D
|
2011-09-17 10:42:43 +08:00
|
|
|
select S5P_DEV_I2C_HDMIPHY
|
2012-03-10 00:19:27 +08:00
|
|
|
select S5P_DEV_JPEG
|
2011-10-13 14:38:21 +08:00
|
|
|
select S5P_DEV_MFC
|
2011-09-17 10:42:43 +08:00
|
|
|
select S5P_DEV_TV
|
2011-10-03 08:12:56 +08:00
|
|
|
select S5P_DEV_USB_EHCI
|
2011-08-31 14:58:52 +08:00
|
|
|
select SAMSUNG_DEV_BACKLIGHT
|
|
|
|
|
select SAMSUNG_DEV_PWM
|
2011-07-21 15:19:19 +08:00
|
|
|
help
|
|
|
|
|
Machine support for ORIGEN based on Samsung EXYNOS4210
|
|
|
|
|
|
2011-08-24 16:25:09 +08:00
|
|
|
comment "EXYNOS4212 Boards"
|
|
|
|
|
|
|
|
|
|
config MACH_SMDK4212
|
|
|
|
|
bool "SMDK4212"
|
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-07 00:12:25 +08:00
|
|
|
select EXYNOS4_SETUP_FIMD0
|
|
|
|
|
select EXYNOS4_SETUP_I2C1
|
|
|
|
|
select EXYNOS4_SETUP_I2C3
|
|
|
|
|
select EXYNOS4_SETUP_I2C7
|
|
|
|
|
select EXYNOS4_SETUP_KEYPAD
|
|
|
|
|
select EXYNOS4_SETUP_SDHCI
|
|
|
|
|
select EXYNOS4_SETUP_USB_PHY
|
|
|
|
|
select EXYNOS_DEV_DMA
|
|
|
|
|
select EXYNOS_DEV_DRM
|
|
|
|
|
select EXYNOS_DEV_SYSMMU
|
|
|
|
|
select S3C24XX_PWM
|
2011-08-24 16:25:09 +08:00
|
|
|
select S3C_DEV_HSMMC2
|
|
|
|
|
select S3C_DEV_HSMMC3
|
|
|
|
|
select S3C_DEV_I2C1
|
|
|
|
|
select S3C_DEV_I2C3
|
|
|
|
|
select S3C_DEV_I2C7
|
|
|
|
|
select S3C_DEV_RTC
|
2012-07-13 17:41:31 +08:00
|
|
|
select S3C_DEV_USB_HSOTG
|
2011-08-24 16:25:09 +08:00
|
|
|
select S3C_DEV_WDT
|
2012-05-12 15:36:22 +08:00
|
|
|
select S5P_DEV_FIMC0
|
|
|
|
|
select S5P_DEV_FIMC1
|
|
|
|
|
select S5P_DEV_FIMC2
|
|
|
|
|
select S5P_DEV_FIMC3
|
2012-07-13 17:58:53 +08:00
|
|
|
select S5P_DEV_FIMD0
|
2012-05-12 15:36:19 +08:00
|
|
|
select S5P_DEV_MFC
|
2011-08-24 16:25:09 +08:00
|
|
|
select SAMSUNG_DEV_BACKLIGHT
|
|
|
|
|
select SAMSUNG_DEV_KEYPAD
|
|
|
|
|
select SAMSUNG_DEV_PWM
|
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-07 00:12:25 +08:00
|
|
|
select SOC_EXYNOS4212
|
2011-08-24 16:25:09 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung SMDK4212
|
|
|
|
|
|
2011-10-04 16:09:26 +08:00
|
|
|
comment "EXYNOS4412 Boards"
|
|
|
|
|
|
|
|
|
|
config MACH_SMDK4412
|
|
|
|
|
bool "SMDK4412"
|
|
|
|
|
select MACH_SMDK4212
|
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-07 00:12:25 +08:00
|
|
|
select SOC_EXYNOS4412
|
2011-10-04 16:09:26 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung SMDK4412
|
2011-11-06 12:54:56 +08:00
|
|
|
endif
|
2011-10-04 16:09:26 +08:00
|
|
|
|
2012-02-10 12:13:15 +08:00
|
|
|
comment "Flattened Device Tree based board for EXYNOS SoCs"
|
2011-11-07 00:24:27 +08:00
|
|
|
|
|
|
|
|
config MACH_EXYNOS4_DT
|
|
|
|
|
bool "Samsung Exynos4 Machine using device tree"
|
2012-04-14 22:53:51 +08:00
|
|
|
depends on ARCH_EXYNOS4
|
2011-11-07 00:24:27 +08:00
|
|
|
select ARM_AMBA
|
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-07 00:12:25 +08:00
|
|
|
select CPU_EXYNOS4210
|
2011-11-07 00:24:27 +08:00
|
|
|
select HAVE_SAMSUNG_KEYPAD if INPUT_KEYBOARD
|
2012-09-07 05:14:26 +08:00
|
|
|
select PINCTRL
|
|
|
|
|
select PINCTRL_EXYNOS4
|
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-07 00:12:25 +08:00
|
|
|
select USE_OF
|
2011-11-07 00:24:27 +08:00
|
|
|
help
|
|
|
|
|
Machine support for Samsung Exynos4 machine with device tree enabled.
|
|
|
|
|
Select this if a fdt blob is available for the Exynos4 SoC based board.
|
|
|
|
|
Note: This is under development and not all peripherals can be supported
|
|
|
|
|
with this machine file.
|
|
|
|
|
|
2012-02-10 12:13:15 +08:00
|
|
|
config MACH_EXYNOS5_DT
|
|
|
|
|
bool "SAMSUNG EXYNOS5 Machine using device tree"
|
2012-04-14 22:53:51 +08:00
|
|
|
depends on ARCH_EXYNOS5
|
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-07 00:12:25 +08:00
|
|
|
select ARM_AMBA
|
2012-02-10 12:13:15 +08:00
|
|
|
select SOC_EXYNOS5250
|
|
|
|
|
select USE_OF
|
|
|
|
|
help
|
2012-08-29 02:40:06 +08:00
|
|
|
Machine support for Samsung EXYNOS5 machine with device tree enabled.
|
|
|
|
|
Select this if a fdt blob is available for the EXYNOS5 SoC based board.
|
2012-02-10 12:13:15 +08:00
|
|
|
|
2011-11-06 12:54:56 +08:00
|
|
|
if ARCH_EXYNOS4
|
2010-10-06 10:09:42 +08:00
|
|
|
|
2011-11-06 12:54:56 +08:00
|
|
|
comment "Configuration for HSMMC 8-bit bus width"
|
2010-10-06 10:09:42 +08:00
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SDHCI_CH0_8BIT
|
2010-10-06 10:09:42 +08:00
|
|
|
bool "Channel 0 with 8-bit bus"
|
|
|
|
|
help
|
|
|
|
|
Support HSMMC Channel 0 8-bit bus.
|
|
|
|
|
If selected, Channel 1 is disabled.
|
|
|
|
|
|
2011-02-14 14:05:27 +08:00
|
|
|
config EXYNOS4_SDHCI_CH2_8BIT
|
2010-10-06 10:09:42 +08:00
|
|
|
bool "Channel 2 with 8-bit bus"
|
|
|
|
|
help
|
|
|
|
|
Support HSMMC Channel 2 8-bit bus.
|
|
|
|
|
If selected, Channel 3 is disabled.
|
2011-11-06 12:54:56 +08:00
|
|
|
endif
|
2010-10-06 10:09:42 +08:00
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2010-07-16 11:15:38 +08:00
|
|
|
endif
|