2010-07-05 21:31:47 +08:00
|
|
|
if ARCH_OMAP2PLUS
|
|
|
|
|
|
|
|
|
|
menu "TI OMAP2/3/4 Specific Features"
|
|
|
|
|
|
2010-07-05 21:31:48 +08:00
|
|
|
config ARCH_OMAP2PLUS_TYPICAL
|
|
|
|
|
bool "Typical OMAP configuration"
|
|
|
|
|
default y
|
|
|
|
|
select AEABI
|
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 HIGHMEM
|
2010-07-05 21:31:48 +08:00
|
|
|
select I2C
|
|
|
|
|
select I2C_OMAP
|
|
|
|
|
select MENELAUS if ARCH_OMAP2
|
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 NEON if ARCH_OMAP3 || ARCH_OMAP4 || SOC_OMAP5
|
|
|
|
|
select PM_RUNTIME
|
|
|
|
|
select REGULATOR
|
|
|
|
|
select SERIAL_OMAP
|
|
|
|
|
select SERIAL_OMAP_CONSOLE
|
2010-07-05 21:31:48 +08:00
|
|
|
select TWL4030_CORE if ARCH_OMAP3 || ARCH_OMAP4
|
|
|
|
|
select TWL4030_POWER if ARCH_OMAP3 || ARCH_OMAP4
|
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 VFP
|
2010-07-05 21:31:48 +08:00
|
|
|
help
|
|
|
|
|
Compile a kernel suitable for booting most boards
|
|
|
|
|
|
2012-07-05 23:05:15 +08:00
|
|
|
config SOC_HAS_OMAP2_SDRC
|
|
|
|
|
bool "OMAP2 SDRAM Controller support"
|
|
|
|
|
|
2012-08-13 16:54:24 +08:00
|
|
|
config SOC_HAS_REALTIME_COUNTER
|
|
|
|
|
bool "Real time free running counter"
|
|
|
|
|
|
2010-07-05 21:31:47 +08:00
|
|
|
config ARCH_OMAP2
|
2012-03-06 08:02:18 +08:00
|
|
|
bool "TI OMAP2"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
|
|
|
|
default y
|
2010-07-05 21:31:47 +08:00
|
|
|
select CPU_V6
|
2011-09-06 17:23:45 +08:00
|
|
|
select MULTI_IRQ_HANDLER
|
2012-07-05 23:05:15 +08:00
|
|
|
select SOC_HAS_OMAP2_SDRC
|
2012-04-27 18:57:51 +08:00
|
|
|
select COMMON_CLK
|
2010-07-05 21:31:47 +08:00
|
|
|
|
|
|
|
|
config ARCH_OMAP3
|
2012-03-06 08:02:18 +08:00
|
|
|
bool "TI OMAP3"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
|
|
|
|
default y
|
2010-12-09 23:13:46 +08:00
|
|
|
select ARCH_HAS_OPP
|
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 CPU_V7
|
2011-09-06 20:27:10 +08:00
|
|
|
select MULTI_IRQ_HANDLER
|
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
|
|
|
|
|
select PM_RUNTIME if CPU_IDLE
|
|
|
|
|
select SOC_HAS_OMAP2_SDRC
|
2012-04-27 18:57:51 +08:00
|
|
|
select COMMON_CLK
|
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 USB_ARCH_HAS_EHCI if USB_SUPPORT
|
2010-07-05 21:31:47 +08:00
|
|
|
|
|
|
|
|
config ARCH_OMAP4
|
2012-03-06 08:02:18 +08:00
|
|
|
bool "TI OMAP4"
|
|
|
|
|
default y
|
|
|
|
|
depends on 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_HAS_OPP
|
|
|
|
|
select ARCH_NEEDS_CPU_IDLE_COUPLED if SMP
|
|
|
|
|
select ARM_CPU_SUSPEND if PM
|
|
|
|
|
select ARM_ERRATA_720789
|
|
|
|
|
select ARM_GIC
|
2011-12-13 00:17:34 +08:00
|
|
|
select CACHE_L2X0
|
2010-07-05 21:31:47 +08:00
|
|
|
select CPU_V7
|
2011-12-07 23:38:04 +08:00
|
|
|
select HAVE_SMP
|
2011-02-22 16:57:47 +08:00
|
|
|
select LOCAL_TIMERS 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
|
2010-09-16 01:10:19 +08:00
|
|
|
select PL310_ERRATA_588369
|
2011-02-22 17:00:44 +08:00
|
|
|
select PL310_ERRATA_727915
|
2010-12-09 23:13:47 +08:00
|
|
|
select PM_OPP 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_RUNTIME if CPU_IDLE
|
2012-02-24 08:41:52 +08:00
|
|
|
select USB_ARCH_HAS_EHCI if USB_SUPPORT
|
2012-04-27 18:57:51 +08:00
|
|
|
select COMMON_CLK
|
2010-07-05 21:31:47 +08:00
|
|
|
|
2012-04-03 17:24:58 +08:00
|
|
|
config SOC_OMAP5
|
|
|
|
|
bool "TI OMAP5"
|
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_ARCH_TIMER
|
|
|
|
|
select ARM_CPU_SUSPEND if PM
|
2012-04-03 17:24:58 +08:00
|
|
|
select ARM_GIC
|
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_V7
|
2012-04-03 17:24:58 +08:00
|
|
|
select HAVE_SMP
|
2012-08-13 16:54:24 +08:00
|
|
|
select SOC_HAS_REALTIME_COUNTER
|
2012-04-27 18:57:51 +08:00
|
|
|
select COMMON_CLK
|
2012-04-03 17:24:58 +08:00
|
|
|
|
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
|
|
|
|
|
|
2012-05-11 02:10:07 +08:00
|
|
|
config SOC_AM33XX
|
2011-12-14 02:46:43 +08:00
|
|
|
bool "AM33XX support"
|
|
|
|
|
default y
|
ARM: OMAP2+: am33xx: Make am33xx as a separate class
Initially, we decided to make am33xx family of device to fall
under omap3 class (cpu_is_omap34xx() = true), since it carries
Cortex-A8 core. But while adding complete baseport support
(like, clock, power and hwmod) support, it is observed that,
we are creating more and more problems by treating am33xx device
as omap3 family, as nothing matches between them
(except cortex-A8 mpu).
So, after long discussion we have came to the conclusion that,
we should not consider am33xx device as omap3 family, instead
create separate class (SOC_AM33XX) under OMAP2PLUS.
This means, for am33xx device, cpu_is_omap34xx() will return false,
and only cpu_is_am33xx() will be true.
Please refer to the link below, for mailing-list discussion on this -
http://www.spinics.net/lists/linux-omap/msg69439.html
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
[tony@atomide.com: fixed typo, updated for soc_is changes]
Signed-off-by: Tony Lindgren <tony@atomide.com>
2012-07-05 23:05:15 +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 CPU_V7
|
ARM: OMAP2+: am33xx: Make am33xx as a separate class
Initially, we decided to make am33xx family of device to fall
under omap3 class (cpu_is_omap34xx() = true), since it carries
Cortex-A8 core. But while adding complete baseport support
(like, clock, power and hwmod) support, it is observed that,
we are creating more and more problems by treating am33xx device
as omap3 family, as nothing matches between them
(except cortex-A8 mpu).
So, after long discussion we have came to the conclusion that,
we should not consider am33xx device as omap3 family, instead
create separate class (SOC_AM33XX) under OMAP2PLUS.
This means, for am33xx device, cpu_is_omap34xx() will return false,
and only cpu_is_am33xx() will be true.
Please refer to the link below, for mailing-list discussion on this -
http://www.spinics.net/lists/linux-omap/msg69439.html
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
[tony@atomide.com: fixed typo, updated for soc_is changes]
Signed-off-by: Tony Lindgren <tony@atomide.com>
2012-07-05 23:05:15 +08:00
|
|
|
select MULTI_IRQ_HANDLER
|
2012-04-27 18:57:51 +08:00
|
|
|
select COMMON_CLK
|
2011-12-14 02:46:43 +08:00
|
|
|
|
2010-07-05 21:31:36 +08:00
|
|
|
config OMAP_PACKAGE_ZAF
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config OMAP_PACKAGE_ZAC
|
|
|
|
|
bool
|
|
|
|
|
|
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
|
|
|
|
|
|
2010-08-10 23:27:48 +08:00
|
|
|
config OMAP_PACKAGE_CBL
|
|
|
|
|
bool
|
|
|
|
|
|
2010-09-24 22:56:59 +08:00
|
|
|
config OMAP_PACKAGE_CBS
|
|
|
|
|
bool
|
|
|
|
|
|
2005-11-10 22:26:51 +08:00
|
|
|
comment "OMAP 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
|
2011-09-21 03:24:47 +08:00
|
|
|
bool "Generic OMAP2+ board"
|
2012-03-06 08:02:18 +08:00
|
|
|
depends on ARCH_OMAP2PLUS
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2011-09-21 03:24:47 +08:00
|
|
|
help
|
|
|
|
|
Support for generic TI OMAP2+ boards using Flattened Device Tree.
|
|
|
|
|
More information at Documentation/devicetree
|
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
|
|
|
|
|
|
2005-11-10 22:26:51 +08:00
|
|
|
config MACH_OMAP_H4
|
|
|
|
|
bool "OMAP 2420 H4 board"
|
2011-01-28 08:39:40 +08:00
|
|
|
depends on SOC_OMAP2420
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2006-12-07 09:14:03 +08:00
|
|
|
select OMAP_DEBUG_DEVICES
|
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_ZAF
|
2005-11-10 22:26:51 +08:00
|
|
|
|
2006-04-03 00:46:30 +08:00
|
|
|
config MACH_OMAP_APOLLON
|
|
|
|
|
bool "OMAP 2420 Apollon board"
|
2011-01-28 08:39:40 +08:00
|
|
|
depends on SOC_OMAP2420
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2010-07-05 21:31:37 +08:00
|
|
|
select OMAP_PACKAGE_ZAC
|
2006-12-07 09:14:05 +08:00
|
|
|
|
|
|
|
|
config MACH_OMAP_2430SDP
|
|
|
|
|
bool "OMAP 2430 SDP board"
|
2011-01-28 08:39:40 +08:00
|
|
|
depends on SOC_OMAP2430
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2010-07-05 21:31:38 +08:00
|
|
|
select OMAP_PACKAGE_ZAC
|
2006-12-07 09:14:05 +08:00
|
|
|
|
2008-10-09 22:51:42 +08:00
|
|
|
config MACH_OMAP3_BEAGLE
|
|
|
|
|
bool "OMAP3 BEAGLE 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-09 22:51:42 +08:00
|
|
|
|
Add minimal support for DevKit8000
These patches add board support for the Timll DevKit8000.
The DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
Signed-off-by: Thomas Weber <weber@corscience.de>
Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-02-18 06:09:28 +08:00
|
|
|
config MACH_DEVKIT8000
|
2010-03-24 20:52:11 +08:00
|
|
|
bool "DEVKIT8000 board"
|
|
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2010-03-24 20:52:11 +08:00
|
|
|
select OMAP_PACKAGE_CUS
|
Add minimal support for DevKit8000
These patches add board support for the Timll DevKit8000.
The DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
Signed-off-by: Thomas Weber <weber@corscience.de>
Signed-off-by: Tony Lindgren <tony@atomide.com>
2010-02-18 06:09:28 +08:00
|
|
|
|
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
|
|
|
|
|
|
2008-10-09 22:51:43 +08:00
|
|
|
config MACH_OVERO
|
|
|
|
|
bool "Gumstix Overo 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-12-11 09:36:54 +08:00
|
|
|
|
2009-05-29 05:13:28 +08:00
|
|
|
config MACH_OMAP3EVM
|
|
|
|
|
bool "OMAP 3530 EVM board"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2010-01-09 02:29:08 +08:00
|
|
|
select OMAP_PACKAGE_CBB
|
2009-05-29 05:13:28 +08:00
|
|
|
|
2009-11-19 10:41:09 +08:00
|
|
|
config MACH_OMAP3517EVM
|
|
|
|
|
bool "OMAP3517/ AM3517 EVM 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
|
2009-11-19 10:41:09 +08:00
|
|
|
|
2010-11-17 06:26:58 +08:00
|
|
|
config MACH_CRANEBOARD
|
|
|
|
|
bool "AM3517/05 CRANE board"
|
|
|
|
|
depends on ARCH_OMAP3
|
|
|
|
|
select OMAP_PACKAGE_CBB
|
|
|
|
|
|
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
|
|
|
|
2012-08-18 00:03:43 +08:00
|
|
|
config MACH_TOUCHBOOK
|
2009-12-12 08:16:34 +08:00
|
|
|
bool "OMAP3 Touch Book"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2012-08-18 00:03:43 +08:00
|
|
|
select OMAP_PACKAGE_CBB
|
2009-12-12 08:16:34 +08:00
|
|
|
|
2009-03-24 09:38:16 +08:00
|
|
|
config MACH_OMAP_3430SDP
|
|
|
|
|
bool "OMAP 3430 SDP 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
|
2009-03-24 09:38:17 +08:00
|
|
|
|
2009-10-23 05:48:13 +08:00
|
|
|
config MACH_NOKIA_N800
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
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_N800
|
|
|
|
|
select MACH_NOKIA_N810
|
|
|
|
|
select MACH_NOKIA_N810_WIMAX
|
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_ZAC
|
2009-08-29 01:51:38 +08:00
|
|
|
|
2010-12-18 07:13:47 +08:00
|
|
|
config MACH_NOKIA_RM680
|
2012-10-18 05:03:00 +08:00
|
|
|
bool "Nokia N950 (RM-680) / N9 (RM-696) phones"
|
2010-12-18 07:13:47 +08:00
|
|
|
depends on ARCH_OMAP3
|
|
|
|
|
default y
|
2012-03-06 03:08:37 +08:00
|
|
|
select MACH_NOKIA_RM696
|
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-12-18 07:13:47 +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
|
|
|
|
|
|
|
|
config MACH_OMAP_ZOOM2
|
|
|
|
|
bool "OMAP3 Zoom2 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
|
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 REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2010-09-27 22:50:57 +08:00
|
|
|
select SERIAL_8250
|
|
|
|
|
select SERIAL_8250_CONSOLE
|
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 SERIAL_CORE_CONSOLE
|
2009-05-29 05:16:05 +08:00
|
|
|
|
2009-11-23 02:11:32 +08:00
|
|
|
config MACH_OMAP_ZOOM3
|
|
|
|
|
bool "OMAP3630 Zoom3 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:33 +08:00
|
|
|
select OMAP_PACKAGE_CBP
|
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 REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2010-09-27 22:50:57 +08:00
|
|
|
select SERIAL_8250
|
|
|
|
|
select SERIAL_8250_CONSOLE
|
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 SERIAL_CORE_CONSOLE
|
2009-11-23 02:11:32 +08:00
|
|
|
|
2009-11-19 10:41:07 +08:00
|
|
|
config MACH_CM_T35
|
2011-07-05 18:38:23 +08:00
|
|
|
bool "CompuLab CM-T35/CM-T3730 modules"
|
2010-02-13 04:26:48 +08:00
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2011-07-05 18:38:23 +08:00
|
|
|
select MACH_CM_T3730
|
2009-12-12 08:16:32 +08:00
|
|
|
select OMAP_PACKAGE_CUS
|
2009-11-19 10:41:07 +08:00
|
|
|
|
2010-09-22 00:03:09 +08:00
|
|
|
config MACH_CM_T3517
|
|
|
|
|
bool "CompuLab CM-T3517 module"
|
|
|
|
|
depends on ARCH_OMAP3
|
|
|
|
|
default y
|
|
|
|
|
select OMAP_PACKAGE_CBB
|
|
|
|
|
|
2011-07-05 18:38:23 +08:00
|
|
|
config MACH_CM_T3730
|
|
|
|
|
bool
|
|
|
|
|
|
2009-11-19 10:41:07 +08:00
|
|
|
config MACH_IGEP0020
|
2010-02-18 06:09:26 +08:00
|
|
|
bool "IGEP v2 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
|
2009-11-19 10:41:07 +08:00
|
|
|
|
2010-10-09 01:22:11 +08:00
|
|
|
config MACH_IGEP0030
|
|
|
|
|
bool "IGEP OMAP3 module"
|
|
|
|
|
depends on ARCH_OMAP3
|
|
|
|
|
default y
|
2011-05-13 05:31:04 +08:00
|
|
|
select MACH_IGEP0020
|
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-10-09 01:22:11 +08:00
|
|
|
|
2010-05-17 14:39:09 +08:00
|
|
|
config MACH_SBC3530
|
|
|
|
|
bool "OMAP3 SBC STALKER board"
|
|
|
|
|
depends on ARCH_OMAP3
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2010-05-17 14:39:09 +08:00
|
|
|
select OMAP_PACKAGE_CUS
|
|
|
|
|
|
2009-11-19 10:41:08 +08:00
|
|
|
config MACH_OMAP_3630SDP
|
|
|
|
|
bool "OMAP3630 SDP 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:33 +08:00
|
|
|
select OMAP_PACKAGE_CBP
|
2009-11-19 10:41:08 +08:00
|
|
|
|
2011-02-16 01:36:08 +08:00
|
|
|
config MACH_TI8168EVM
|
|
|
|
|
bool "TI8168 Evaluation Module"
|
2012-05-11 02:10:07 +08:00
|
|
|
depends on SOC_TI81XX
|
2011-02-16 01:36:08 +08:00
|
|
|
default y
|
2011-12-14 02:48:55 +08:00
|
|
|
|
|
|
|
|
config MACH_TI8148EVM
|
|
|
|
|
bool "TI8148 Evaluation Module"
|
2012-05-11 02:10:07 +08:00
|
|
|
depends on SOC_TI81XX
|
2011-12-14 02:48:55 +08:00
|
|
|
default y
|
2011-02-16 01:36:08 +08:00
|
|
|
|
2009-05-29 05:16:05 +08:00
|
|
|
config MACH_OMAP_4430SDP
|
|
|
|
|
bool "OMAP 4430 SDP board"
|
2010-07-05 21:31:47 +08:00
|
|
|
default y
|
2009-05-29 05:16:05 +08:00
|
|
|
depends on ARCH_OMAP4
|
2010-08-10 23:43:15 +08:00
|
|
|
select OMAP_PACKAGE_CBL
|
2010-09-27 16:50:33 +08:00
|
|
|
select OMAP_PACKAGE_CBS
|
2012-01-20 21:38:31 +08:00
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2009-12-01 21:03:31 +08:00
|
|
|
|
2010-08-02 18:18:05 +08:00
|
|
|
config MACH_OMAP4_PANDA
|
|
|
|
|
bool "OMAP4 Panda Board"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_OMAP4
|
2010-11-08 21:56:11 +08:00
|
|
|
select OMAP_PACKAGE_CBL
|
|
|
|
|
select OMAP_PACKAGE_CBS
|
2012-01-20 21:38:31 +08:00
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2010-08-02 18:18:05 +08:00
|
|
|
|
2009-12-01 21:03:31 +08:00
|
|
|
config OMAP3_EMU
|
|
|
|
|
bool "OMAP3 debugging peripherals"
|
|
|
|
|
depends on ARCH_OMAP3
|
2011-11-24 06:44:50 +08:00
|
|
|
select ARM_AMBA
|
2009-12-01 21:03:31 +08:00
|
|
|
select OC_ETM
|
|
|
|
|
help
|
|
|
|
|
Say Y here to enable debugging hardware of omap3
|
|
|
|
|
|
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;
|
|
|
|
|
|
2011-06-26 09:04:31 +08:00
|
|
|
config OMAP4_ERRATA_I688
|
2012-02-02 22:03:55 +08:00
|
|
|
bool "OMAP4 errata: Async Bridge Corruption"
|
|
|
|
|
depends on ARCH_OMAP4
|
2011-06-26 09:04:31 +08:00
|
|
|
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
|
