2014-06-10 22:06:10 +08:00
|
|
|
menu "TI OMAP/AM/DM/DRA Family"
|
|
|
|
|
depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
|
|
|
|
|
|
2010-07-05 21:31:47 +08:00
|
|
|
config ARCH_OMAP2
|
2012-03-06 08:02:18 +08:00
|
|
|
bool "TI OMAP2"
|
2013-04-23 21:30:51 +08:00
|
|
|
depends on ARCH_MULTI_V6
|
2013-05-01 06:02:26 +08:00
|
|
|
select ARCH_OMAP2PLUS
|
2010-07-05 21:31:47 +08:00
|
|
|
select CPU_V6
|
2012-07-05 23:05:15 +08:00
|
|
|
select SOC_HAS_OMAP2_SDRC
|
2010-07-05 21:31:47 +08:00
|
|
|
|
|
|
|
|
config ARCH_OMAP3
|
2012-03-06 08:02:18 +08:00
|
|
|
bool "TI OMAP3"
|
2013-04-23 21:30:51 +08:00
|
|
|
depends on ARCH_MULTI_V7
|
2013-05-01 06:02:26 +08:00
|
|
|
select ARCH_OMAP2PLUS
|
2011-10-02 03:09:39 +08:00
|
|
|
select ARM_CPU_SUSPEND if PM
|
2012-09-14 17:20:34 +08:00
|
|
|
select OMAP_INTERCONNECT
|
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_OPP if PM
|
2014-12-19 22:37:54 +08:00
|
|
|
select PM if CPU_IDLE
|
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_HAS_OMAP2_SDRC
|
2010-07-05 21:31:47 +08:00
|
|
|
|
|
|
|
|
config ARCH_OMAP4
|
2012-03-06 08:02:18 +08:00
|
|
|
bool "TI OMAP4"
|
2013-04-23 21:30:51 +08:00
|
|
|
depends on ARCH_MULTI_V7
|
2013-05-01 06:02:26 +08:00
|
|
|
select ARCH_OMAP2PLUS
|
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 ARCH_NEEDS_CPU_IDLE_COUPLED if SMP
|
|
|
|
|
select ARM_CPU_SUSPEND if PM
|
|
|
|
|
select ARM_ERRATA_720789
|
|
|
|
|
select ARM_GIC
|
2013-02-28 07:28:14 +08:00
|
|
|
select HAVE_ARM_SCU if SMP
|
2013-02-16 08:02:20 +08:00
|
|
|
select HAVE_ARM_TWD if SMP
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select OMAP_INTERCONNECT
|
2014-06-19 17:19:10 +08:00
|
|
|
select PL310_ERRATA_588369 if CACHE_L2X0
|
|
|
|
|
select PL310_ERRATA_727915 if CACHE_L2X0
|
2010-12-09 23:13:47 +08:00
|
|
|
select PM_OPP if PM
|
2014-12-19 22:37:54 +08:00
|
|
|
select PM if CPU_IDLE
|
2013-03-21 22:42:17 +08:00
|
|
|
select ARM_ERRATA_754322
|
|
|
|
|
select ARM_ERRATA_775420
|
2010-07-05 21:31:47 +08:00
|
|
|
|
2012-04-03 17:24:58 +08:00
|
|
|
config SOC_OMAP5
|
|
|
|
|
bool "TI OMAP5"
|
2013-04-23 21:30:51 +08:00
|
|
|
depends on ARCH_MULTI_V7
|
2013-05-01 06:02:26 +08:00
|
|
|
select ARCH_OMAP2PLUS
|
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_CPU_SUSPEND if PM
|
2012-04-03 17:24:58 +08:00
|
|
|
select ARM_GIC
|
2013-06-03 21:55:41 +08:00
|
|
|
select HAVE_ARM_SCU if SMP
|
2014-02-02 06:35:44 +08:00
|
|
|
select HAVE_ARM_TWD if SMP
|
2012-11-12 22:33:44 +08:00
|
|
|
select HAVE_ARM_ARCH_TIMER
|
2013-07-25 07:55:23 +08:00
|
|
|
select ARM_ERRATA_798181 if SMP
|
2012-04-03 17:24:58 +08:00
|
|
|
|
2013-05-01 06:02:26 +08:00
|
|
|
config SOC_AM33XX
|
2013-08-09 05:32:08 +08:00
|
|
|
bool "TI AM33XX"
|
2013-05-01 06:02:26 +08:00
|
|
|
depends on ARCH_MULTI_V7
|
|
|
|
|
select ARCH_OMAP2PLUS
|
|
|
|
|
select ARM_CPU_SUSPEND if PM
|
|
|
|
|
|
|
|
|
|
config SOC_AM43XX
|
|
|
|
|
bool "TI AM43x"
|
|
|
|
|
depends on ARCH_MULTI_V7
|
|
|
|
|
select ARCH_OMAP2PLUS
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select MACH_OMAP_GENERIC
|
2014-04-22 16:28:03 +08:00
|
|
|
select MIGHT_HAVE_CACHE_L2X0
|
2013-05-01 06:02:26 +08:00
|
|
|
|
2014-01-10 17:25:28 +08:00
|
|
|
config SOC_DRA7XX
|
|
|
|
|
bool "TI DRA7XX"
|
|
|
|
|
depends on ARCH_MULTI_V7
|
|
|
|
|
select ARCH_OMAP2PLUS
|
|
|
|
|
select ARM_CPU_SUSPEND if PM
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select HAVE_ARM_ARCH_TIMER
|
2013-12-03 18:27:25 +08:00
|
|
|
select IRQ_CROSSBAR
|
2015-03-26 07:25:09 +08:00
|
|
|
select ARM_ERRATA_798181 if SMP
|
2014-01-10 17:25:28 +08:00
|
|
|
|
2013-05-01 06:02:26 +08:00
|
|
|
config ARCH_OMAP2PLUS
|
|
|
|
|
bool
|
|
|
|
|
select ARCH_HAS_BANDGAP
|
|
|
|
|
select ARCH_HAS_HOLES_MEMORYMODEL
|
|
|
|
|
select ARCH_OMAP
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
2013-09-26 06:44:39 +08:00
|
|
|
select MACH_OMAP_GENERIC
|
2014-11-21 01:13:42 +08:00
|
|
|
select MEMORY
|
2015-04-21 01:36:31 +08:00
|
|
|
select MFD_SYSCON
|
2013-05-01 06:02:26 +08:00
|
|
|
select OMAP_DM_TIMER
|
2014-11-21 01:13:42 +08:00
|
|
|
select OMAP_GPMC
|
2013-05-01 06:02:26 +08:00
|
|
|
select PINCTRL
|
|
|
|
|
select SOC_BUS
|
2013-07-09 16:31:23 +08:00
|
|
|
select TI_PRIV_EDMA
|
2014-09-16 05:15:02 +08:00
|
|
|
select OMAP_IRQCHIP
|
2013-05-01 06:02:26 +08:00
|
|
|
help
|
|
|
|
|
Systems based on OMAP2, OMAP3, OMAP4 or OMAP5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
if ARCH_OMAP2PLUS
|
|
|
|
|
|
|
|
|
|
menu "TI OMAP2/3/4 Specific Features"
|
|
|
|
|
|
|
|
|
|
config ARCH_OMAP2PLUS_TYPICAL
|
|
|
|
|
bool "Typical OMAP configuration"
|
|
|
|
|
default y
|
|
|
|
|
select AEABI
|
|
|
|
|
select HIGHMEM
|
|
|
|
|
select I2C
|
|
|
|
|
select I2C_OMAP
|
|
|
|
|
select MENELAUS if ARCH_OMAP2
|
2013-02-07 18:51:46 +08:00
|
|
|
select NEON if CPU_V7
|
2014-12-19 22:37:54 +08:00
|
|
|
select PM
|
2013-05-01 06:02:26 +08:00
|
|
|
select REGULATOR
|
|
|
|
|
select TWL4030_CORE if ARCH_OMAP3 || ARCH_OMAP4
|
|
|
|
|
select TWL4030_POWER if ARCH_OMAP3 || ARCH_OMAP4
|
|
|
|
|
select VFP
|
|
|
|
|
help
|
|
|
|
|
Compile a kernel suitable for booting most boards
|
|
|
|
|
|
|
|
|
|
config SOC_HAS_OMAP2_SDRC
|
|
|
|
|
bool "OMAP2 SDRAM Controller support"
|
|
|
|
|
|
|
|
|
|
config SOC_HAS_REALTIME_COUNTER
|
|
|
|
|
bool "Real time free running counter"
|
2013-02-07 15:55:39 +08:00
|
|
|
depends on SOC_OMAP5 || SOC_DRA7XX
|
2013-05-01 06:02:26 +08:00
|
|
|
default y
|
|
|
|
|
|
2005-11-10 22:26:51 +08:00
|
|
|
comment "OMAP Core Type"
|
2012-03-06 08:02:18 +08:00
|
|
|
depends on ARCH_OMAP2
|
2005-11-10 22:26:51 +08:00
|
|
|
|
2011-01-28 08:39:40 +08:00
|
|
|
config SOC_OMAP2420
|
2005-11-10 22:26:51 +08:00
|
|
|
bool "OMAP2420 support"
|
2012-03-06 08:02:18 +08:00
|
|
|
depends on ARCH_OMAP2
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2006-06-27 07:16:12 +08:00
|
|
|
select OMAP_DM_TIMER
|
2012-07-05 23:05:15 +08:00
|
|
|
select SOC_HAS_OMAP2_SDRC
|
2005-11-10 22:26:51 +08:00
|
|
|
|
2011-01-28 08:39:40 +08:00
|
|
|
config SOC_OMAP2430
|
2006-12-07 09:14:05 +08:00
|
|
|
bool "OMAP2430 support"
|
2012-03-06 08:02:18 +08:00
|
|
|
depends on ARCH_OMAP2
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2012-07-05 23:05:15 +08:00
|
|
|
select SOC_HAS_OMAP2_SDRC
|
2006-12-07 09:14:05 +08:00
|
|
|
|
2011-01-28 08:39:40 +08:00
|
|
|
config SOC_OMAP3430
|
2008-10-09 22:51:41 +08:00
|
|
|
bool "OMAP3430 support"
|
2012-03-06 08:02:18 +08:00
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2012-07-05 23:05:15 +08:00
|
|
|
select SOC_HAS_OMAP2_SDRC
|
2008-10-09 22:51:41 +08:00
|
|
|
|
2012-05-11 02:10:07 +08:00
|
|
|
config SOC_TI81XX
|
2011-12-14 02:46:44 +08:00
|
|
|
bool "TI81XX support"
|
2012-03-06 08:02:18 +08:00
|
|
|
depends on ARCH_OMAP3
|
2011-02-17 00:31:39 +08:00
|
|
|
default y
|
|
|
|
|
|
2009-12-12 08:16:32 +08:00
|
|
|
config OMAP_PACKAGE_CBC
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config OMAP_PACKAGE_CBB
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config OMAP_PACKAGE_CUS
|
|
|
|
|
bool
|
|
|
|
|
|
2009-12-12 08:16:33 +08:00
|
|
|
config OMAP_PACKAGE_CBP
|
|
|
|
|
bool
|
|
|
|
|
|
2013-09-26 06:44:39 +08:00
|
|
|
comment "OMAP Legacy Platform Data Board Type"
|
2012-03-06 08:02:18 +08:00
|
|
|
depends on ARCH_OMAP2PLUS
|
2005-11-10 22:26:51 +08:00
|
|
|
|
|
|
|
|
config MACH_OMAP_GENERIC
|
2013-09-26 06:44:39 +08:00
|
|
|
bool
|
2005-11-10 22:26:51 +08:00
|
|
|
|
2009-08-29 01:51:37 +08:00
|
|
|
config MACH_OMAP2_TUSB6010
|
|
|
|
|
bool
|
2011-01-28 08:39:40 +08:00
|
|
|
depends on ARCH_OMAP2 && SOC_OMAP2420
|
2009-08-29 01:51:37 +08:00
|
|
|
default y if MACH_NOKIA_N8X0
|
|
|
|
|
|
2008-10-10 16:28:23 +08:00
|
|
|
config MACH_OMAP_LDP
|
|
|
|
|
bool "OMAP3 LDP board"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2009-12-12 08:16:32 +08:00
|
|
|
select OMAP_PACKAGE_CBB
|
2008-10-10 16:28:23 +08:00
|
|
|
|
2010-09-28 00:05:47 +08:00
|
|
|
config MACH_OMAP3530_LV_SOM
|
|
|
|
|
bool "OMAP3 Logic 3530 LV SOM board"
|
|
|
|
|
depends on ARCH_OMAP3
|
|
|
|
|
default y
|
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 OMAP_PACKAGE_CBB
|
2010-09-28 00:05:47 +08:00
|
|
|
help
|
|
|
|
|
Support for the LogicPD OMAP3530 SOM Development kit
|
|
|
|
|
for full description please see the products webpage at
|
|
|
|
|
http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap35x-development-kit
|
|
|
|
|
|
|
|
|
|
config MACH_OMAP3_TORPEDO
|
|
|
|
|
bool "OMAP3 Logic 35x Torpedo board"
|
|
|
|
|
depends on ARCH_OMAP3
|
|
|
|
|
default y
|
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 OMAP_PACKAGE_CBB
|
2010-09-28 00:05:47 +08:00
|
|
|
help
|
|
|
|
|
Support for the LogicPD OMAP35x Torpedo Development kit
|
|
|
|
|
for full description please see the products webpage at
|
|
|
|
|
http://www.logicpd.com/products/development-kits/zoom-omap35x-torpedo-development-kit
|
|
|
|
|
|
2015-01-21 00:49:08 +08:00
|
|
|
config MACH_OMAP3517EVM
|
|
|
|
|
bool "OMAP3517/ AM3517 EVM board"
|
|
|
|
|
depends on ARCH_OMAP3
|
|
|
|
|
default y
|
|
|
|
|
|
2008-12-11 09:36:54 +08:00
|
|
|
config MACH_OMAP3_PANDORA
|
|
|
|
|
bool "OMAP3 Pandora"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2009-12-12 08:16:32 +08:00
|
|
|
select OMAP_PACKAGE_CBB
|
2012-01-20 21:38:31 +08:00
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2009-03-24 09:38:16 +08:00
|
|
|
|
2009-10-23 05:48:13 +08:00
|
|
|
config MACH_NOKIA_N810
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config MACH_NOKIA_N810_WIMAX
|
|
|
|
|
bool
|
|
|
|
|
|
2009-08-29 01:51:38 +08:00
|
|
|
config MACH_NOKIA_N8X0
|
|
|
|
|
bool "Nokia N800/N810"
|
2011-01-28 08:39:40 +08:00
|
|
|
depends on SOC_OMAP2420
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2009-10-23 05:48:13 +08:00
|
|
|
select MACH_NOKIA_N810
|
|
|
|
|
select MACH_NOKIA_N810_WIMAX
|
2009-08-29 01:51:38 +08:00
|
|
|
|
2009-03-24 09:38:17 +08:00
|
|
|
config MACH_NOKIA_RX51
|
2012-10-18 05:03:00 +08:00
|
|
|
bool "Nokia N900 (RX-51) phone"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2009-12-12 08:16:32 +08:00
|
|
|
select OMAP_PACKAGE_CBB
|
2009-05-29 05:04:04 +08:00
|
|
|
|
2009-12-09 07:33:14 +08:00
|
|
|
config OMAP3_SDRC_AC_TIMING
|
|
|
|
|
bool "Enable SDRC AC timing register changes"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP3
|
2009-12-09 07:33:14 +08:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If you know that none of your system initiators will attempt to
|
|
|
|
|
access SDRAM during CORE DVFS, select Y here. This should boost
|
|
|
|
|
SDRAM performance at lower CORE OPPs. There are relatively few
|
|
|
|
|
users who will wish to say yes at this point - almost everyone will
|
|
|
|
|
wish to say no. Selecting yes without understanding what is
|
|
|
|
|
going on could result in system crashes;
|
|
|
|
|
|
2015-06-06 07:13:40 +08:00
|
|
|
config OMAP4_ERRATA_I688
|
|
|
|
|
bool "OMAP4 errata: Async Bridge Corruption"
|
|
|
|
|
depends on (ARCH_OMAP4 || SOC_OMAP5) && !ARCH_MULTIPLATFORM
|
|
|
|
|
select ARCH_HAS_BARRIERS
|
|
|
|
|
help
|
|
|
|
|
If a data is stalled inside asynchronous bridge because of back
|
|
|
|
|
pressure, it may be accepted multiple times, creating pointer
|
|
|
|
|
misalignment that will corrupt next transfers on that data path
|
|
|
|
|
until next reset of the system (No recovery procedure once the
|
|
|
|
|
issue is hit, the path remains consistently broken). Async bridge
|
|
|
|
|
can be found on path between MPU to EMIF and MPU to L3 interconnect.
|
|
|
|
|
This situation can happen only when the idle is initiated by a
|
|
|
|
|
Master Request Disconnection (which is trigged by software when
|
|
|
|
|
executing WFI on CPU).
|
|
|
|
|
The work-around for this errata needs all the initiators connected
|
|
|
|
|
through async bridge must ensure that data path is properly drained
|
|
|
|
|
before issuing WFI. This condition will be met if one Strongly ordered
|
|
|
|
|
access is performed to the target right before executing the WFI.
|
|
|
|
|
In MPU case, L3 T2ASYNC FIFO and DDR T2ASYNC FIFO needs to be drained.
|
|
|
|
|
IO barrier ensure that there is no synchronisation loss on initiators
|
|
|
|
|
operating on both interconnect port simultaneously.
|
2010-07-05 21:31:47 +08:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
endif
|
2014-06-10 22:06:10 +08:00
|
|
|
|
|
|
|
|
endmenu
|