2007-05-01 02:37:19 +08:00
|
|
|
if ARCH_DAVINCI
|
|
|
|
|
|
2009-04-16 03:41:40 +08:00
|
|
|
config AINTC
|
|
|
|
|
bool
|
|
|
|
|
|
2009-03-11 23:49:05 +08:00
|
|
|
config CP_INTC
|
|
|
|
|
bool
|
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 IRQ_DOMAIN
|
2009-03-11 23:49:05 +08:00
|
|
|
|
2009-06-04 09:36:54 +08:00
|
|
|
config ARCH_DAVINCI_DMx
|
|
|
|
|
bool
|
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_ARM926T
|
2009-06-04 09:36:54 +08:00
|
|
|
|
2007-05-01 02:37:19 +08:00
|
|
|
menu "TI DaVinci Implementations"
|
|
|
|
|
|
|
|
|
|
comment "DaVinci Core Type"
|
|
|
|
|
|
2009-04-15 00:30:11 +08:00
|
|
|
config ARCH_DAVINCI_DM644x
|
2007-05-01 02:37:19 +08:00
|
|
|
bool "DaVinci 644x based system"
|
2009-04-16 03:41:40 +08:00
|
|
|
select AINTC
|
2009-06-04 09:36:54 +08:00
|
|
|
select ARCH_DAVINCI_DMx
|
2007-05-01 02:37:19 +08:00
|
|
|
|
2009-04-30 03:10:55 +08:00
|
|
|
config ARCH_DAVINCI_DM355
|
2010-07-01 21:30:49 +08:00
|
|
|
bool "DaVinci 355 based system"
|
2009-04-16 03:41:40 +08:00
|
|
|
select AINTC
|
2009-06-04 09:36:54 +08:00
|
|
|
select ARCH_DAVINCI_DMx
|
2009-04-30 03:10:55 +08:00
|
|
|
|
2009-04-30 08:44:58 +08:00
|
|
|
config ARCH_DAVINCI_DM646x
|
2010-07-01 21:30:49 +08:00
|
|
|
bool "DaVinci 646x based system"
|
2009-04-16 03:41:40 +08:00
|
|
|
select AINTC
|
2009-06-04 09:36:54 +08:00
|
|
|
select ARCH_DAVINCI_DMx
|
|
|
|
|
|
|
|
|
|
config ARCH_DAVINCI_DA830
|
2010-07-01 21:30:50 +08:00
|
|
|
bool "DA830/OMAP-L137/AM17x based system"
|
2009-06-04 09:36:54 +08:00
|
|
|
select ARCH_DAVINCI_DA8XX
|
2009-07-17 23:36:19 +08:00
|
|
|
select CPU_DCACHE_WRITETHROUGH # needed on silicon revs 1.0, 1.1
|
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 CP_INTC
|
2009-06-04 09:36:54 +08:00
|
|
|
|
2009-07-16 18:41:54 +08:00
|
|
|
config ARCH_DAVINCI_DA850
|
2010-07-01 21:30:50 +08:00
|
|
|
bool "DA850/OMAP-L138/AM18x based system"
|
2009-07-16 18:41:54 +08:00
|
|
|
select ARCH_DAVINCI_DA8XX
|
2009-09-22 23:44:00 +08:00
|
|
|
select ARCH_HAS_CPUFREQ
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CP_INTC
|
2009-07-16 18:41:54 +08:00
|
|
|
|
2009-06-04 09:36:54 +08:00
|
|
|
config ARCH_DAVINCI_DA8XX
|
|
|
|
|
bool
|
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_ARM926T
|
2009-04-30 08:44:58 +08:00
|
|
|
|
2009-06-10 04:28:44 +08:00
|
|
|
config ARCH_DAVINCI_DM365
|
|
|
|
|
bool "DaVinci 365 based system"
|
|
|
|
|
select AINTC
|
|
|
|
|
select ARCH_DAVINCI_DMx
|
|
|
|
|
|
2007-05-01 02:37:19 +08:00
|
|
|
comment "DaVinci Board Type"
|
|
|
|
|
|
2012-08-28 17:57:52 +08:00
|
|
|
config MACH_DA8XX_DT
|
|
|
|
|
bool "Support DA8XX platforms using device tree"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_DAVINCI_DA8XX
|
2013-01-16 17:07:39 +08:00
|
|
|
select PINCTRL
|
2012-08-28 17:57:52 +08:00
|
|
|
help
|
|
|
|
|
Say y here to include support for TI DaVinci DA850 based using
|
|
|
|
|
Flattened Device Tree. More information at Documentation/devicetree
|
|
|
|
|
|
2007-05-01 02:37:19 +08:00
|
|
|
config MACH_DAVINCI_EVM
|
2009-04-15 00:30:11 +08:00
|
|
|
bool "TI DM644x EVM"
|
2009-06-04 05:54:27 +08:00
|
|
|
default ARCH_DAVINCI_DM644x
|
2009-04-15 00:30:11 +08:00
|
|
|
depends on ARCH_DAVINCI_DM644x
|
2010-11-19 23:25:30 +08:00
|
|
|
select EEPROM_AT24
|
2011-04-15 20:32:40 +08:00
|
|
|
select I2C
|
2007-05-01 02:37:19 +08:00
|
|
|
help
|
|
|
|
|
Configure this option to specify the whether the board used
|
2009-04-15 00:30:11 +08:00
|
|
|
for development is a DM644x EVM
|
2007-05-01 02:37:19 +08:00
|
|
|
|
2009-04-30 07:46:57 +08:00
|
|
|
config MACH_SFFSDR
|
|
|
|
|
bool "Lyrtech SFFSDR"
|
|
|
|
|
depends on ARCH_DAVINCI_DM644x
|
2010-11-19 23:25:30 +08:00
|
|
|
select EEPROM_AT24
|
2011-04-15 20:32:40 +08:00
|
|
|
select I2C
|
2009-04-30 07:46:57 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to select the Lyrtech Small Form Factor
|
|
|
|
|
Software Defined Radio (SFFSDR) board.
|
2009-04-14 22:50:37 +08:00
|
|
|
|
davinci: Initial support for Neuros OSD2 platform.
The Neuros OSD 2.0 is the hardware component of the Neuros Open
Internet Television Platform. Hardware is very close to Ti DM644X-EVM board.
It has: DM6446M02 module with 256MB NAND, 256MB RAM, TLV320AIC32 AIC,
USB, Ethernet, SD/MMC, UART, THS8200, TVP7000 for video.
Additionaly realtime clock, IR remote control receiver,
IR Blaster based on MSP430 (firmware although is different
from used in DM644X-EVM), internal ATA-6 3.5” HDD drive
with PATA interface, two muxed red-green leds.
For more information please refer to
http://wiki.neurostechnology.com/index.php/OSD_2.0_HD
Signed-off-by: Andrey Porodko <panda@chelcom.ru>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
2009-11-13 22:16:51 +08:00
|
|
|
config MACH_NEUROS_OSD2
|
|
|
|
|
bool "Neuros OSD2 Open Television Set Top Box"
|
|
|
|
|
depends on ARCH_DAVINCI_DM644x
|
|
|
|
|
help
|
|
|
|
|
Configure this option to specify the whether the board used
|
|
|
|
|
for development is a Neuros OSD2 Open Set Top Box.
|
|
|
|
|
|
2009-04-30 03:10:55 +08:00
|
|
|
config MACH_DAVINCI_DM355_EVM
|
|
|
|
|
bool "TI DM355 EVM"
|
2009-06-04 05:54:27 +08:00
|
|
|
default ARCH_DAVINCI_DM355
|
2009-04-30 03:10:55 +08:00
|
|
|
depends on ARCH_DAVINCI_DM355
|
|
|
|
|
help
|
|
|
|
|
Configure this option to specify the whether the board used
|
|
|
|
|
for development is a DM355 EVM
|
|
|
|
|
|
|
|
|
|
config MACH_DM355_LEOPARD
|
|
|
|
|
bool "DM355 Leopard board"
|
|
|
|
|
depends on ARCH_DAVINCI_DM355
|
|
|
|
|
help
|
|
|
|
|
Configure this option to specify the whether the board used
|
|
|
|
|
for development is a DM355 Leopard board.
|
|
|
|
|
|
2009-04-30 08:44:58 +08:00
|
|
|
config MACH_DAVINCI_DM6467_EVM
|
|
|
|
|
bool "TI DM6467 EVM"
|
2009-06-04 05:54:27 +08:00
|
|
|
default ARCH_DAVINCI_DM646x
|
2009-04-30 08:44:58 +08:00
|
|
|
depends on ARCH_DAVINCI_DM646x
|
2010-11-19 23:25:30 +08:00
|
|
|
select EEPROM_AT24
|
2011-04-15 20:32:40 +08:00
|
|
|
select I2C
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select MACH_DAVINCI_DM6467TEVM
|
2009-04-30 08:44:58 +08:00
|
|
|
help
|
|
|
|
|
Configure this option to specify the whether the board used
|
|
|
|
|
for development is a DM6467 EVM
|
|
|
|
|
|
2009-11-24 20:55:15 +08:00
|
|
|
config MACH_DAVINCI_DM6467TEVM
|
|
|
|
|
bool
|
|
|
|
|
|
2009-06-10 04:28:44 +08:00
|
|
|
config MACH_DAVINCI_DM365_EVM
|
|
|
|
|
bool "TI DM365 EVM"
|
|
|
|
|
default ARCH_DAVINCI_DM365
|
|
|
|
|
depends on ARCH_DAVINCI_DM365
|
2010-11-19 23:25:30 +08:00
|
|
|
select EEPROM_AT24
|
2011-04-15 20:32:40 +08:00
|
|
|
select I2C
|
2009-06-10 04:28:44 +08:00
|
|
|
help
|
|
|
|
|
Configure this option to specify whether the board used
|
|
|
|
|
for development is a DM365 EVM
|
|
|
|
|
|
2009-06-04 09:41:53 +08:00
|
|
|
config MACH_DAVINCI_DA830_EVM
|
2010-07-01 21:30:50 +08:00
|
|
|
bool "TI DA830/OMAP-L137/AM17x Reference Platform"
|
2009-06-04 09:41:53 +08:00
|
|
|
default ARCH_DAVINCI_DA830
|
|
|
|
|
depends on ARCH_DAVINCI_DA830
|
2010-11-19 23:25:30 +08:00
|
|
|
select EEPROM_AT24
|
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 GPIO_PCF857X
|
2011-04-15 20:32:40 +08:00
|
|
|
select I2C
|
2009-06-04 09:41:53 +08:00
|
|
|
help
|
2010-07-01 21:30:50 +08:00
|
|
|
Say Y here to select the TI DA830/OMAP-L137/AM17x Evaluation Module.
|
2009-04-30 08:44:58 +08:00
|
|
|
|
2009-09-16 09:15:06 +08:00
|
|
|
choice
|
2010-07-01 21:30:50 +08:00
|
|
|
prompt "Select DA830/OMAP-L137/AM17x UI board peripheral"
|
2009-10-21 23:48:20 +08:00
|
|
|
depends on MACH_DAVINCI_DA830_EVM
|
|
|
|
|
help
|
2010-07-01 21:30:50 +08:00
|
|
|
The presence of UI card on the DA830/OMAP-L137/AM17x EVM is
|
|
|
|
|
detected automatically based on successful probe of the I2C
|
|
|
|
|
based GPIO expander on that board. This option selected in this
|
|
|
|
|
menu has an effect only in case of a successful UI card detection.
|
2009-09-16 09:15:06 +08:00
|
|
|
|
|
|
|
|
config DA830_UI_LCD
|
|
|
|
|
bool "LCD"
|
|
|
|
|
help
|
|
|
|
|
Say Y here to use the LCD as a framebuffer or simple character
|
|
|
|
|
display.
|
|
|
|
|
|
2009-09-19 05:15:18 +08:00
|
|
|
config DA830_UI_NAND
|
|
|
|
|
bool "NAND flash"
|
|
|
|
|
help
|
2010-07-01 21:30:49 +08:00
|
|
|
Say Y here to use the NAND flash. Do not forget to setup
|
2009-09-19 05:15:18 +08:00
|
|
|
the switch correctly.
|
2009-09-16 09:15:06 +08:00
|
|
|
endchoice
|
|
|
|
|
|
2009-07-16 18:42:18 +08:00
|
|
|
config MACH_DAVINCI_DA850_EVM
|
2010-07-01 21:30:50 +08:00
|
|
|
bool "TI DA850/OMAP-L138/AM18x Reference Platform"
|
2009-07-16 18:42:18 +08:00
|
|
|
default ARCH_DAVINCI_DA850
|
|
|
|
|
depends on ARCH_DAVINCI_DA850
|
2009-10-01 05:00:53 +08:00
|
|
|
help
|
2010-07-01 21:30:50 +08:00
|
|
|
Say Y here to select the TI DA850/OMAP-L138/AM18x Evaluation Module.
|
2009-10-01 05:00:53 +08:00
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Select peripherals connected to expander on UI board"
|
2009-10-21 23:48:23 +08:00
|
|
|
depends on MACH_DAVINCI_DA850_EVM
|
|
|
|
|
help
|
2010-07-01 21:30:50 +08:00
|
|
|
The presence of User Interface (UI) card on the DA850/OMAP-L138/AM18x
|
2009-10-21 23:48:23 +08:00
|
|
|
EVM is detected automatically based on successful probe of the I2C
|
|
|
|
|
based GPIO expander on that card. This option selected in this
|
|
|
|
|
menu has an effect only in case of a successful UI card detection.
|
2009-10-01 05:00:53 +08:00
|
|
|
|
|
|
|
|
config DA850_UI_NONE
|
|
|
|
|
bool "No peripheral is enabled"
|
|
|
|
|
help
|
|
|
|
|
Say Y if you do not want to enable any of the peripherals connected
|
2010-07-01 21:30:50 +08:00
|
|
|
to TCA6416 expander on DA850/OMAP-L138/AM18x EVM UI card
|
2009-10-01 05:00:53 +08:00
|
|
|
|
|
|
|
|
config DA850_UI_RMII
|
|
|
|
|
bool "RMII Ethernet PHY"
|
|
|
|
|
help
|
2010-07-01 21:30:50 +08:00
|
|
|
Say Y if you want to use the RMII PHY on the DA850/OMAP-L138/AM18x
|
|
|
|
|
EVM. This PHY is found on the UI daughter card that is supplied with
|
2009-10-01 05:00:53 +08:00
|
|
|
the EVM.
|
|
|
|
|
NOTE: Please take care while choosing this option, MII PHY will
|
|
|
|
|
not be functional if RMII mode is selected.
|
|
|
|
|
|
2012-07-23 19:00:58 +08:00
|
|
|
config DA850_UI_SD_VIDEO_PORT
|
|
|
|
|
bool "Video Port Interface"
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to use Video Port Interface (VPIF) on the
|
|
|
|
|
DA850/OMAP-L138 EVM. The Video decoders/encoders are found on the
|
|
|
|
|
UI daughter card that is supplied with the EVM.
|
|
|
|
|
|
2009-10-01 05:00:53 +08:00
|
|
|
endchoice
|
|
|
|
|
|
2011-08-04 15:51:23 +08:00
|
|
|
config DA850_WL12XX
|
|
|
|
|
bool "AM18x wl1271 daughter board"
|
|
|
|
|
depends on MACH_DAVINCI_DA850_EVM
|
|
|
|
|
help
|
|
|
|
|
The wl1271 daughter card for AM18x EVMs is a combo wireless
|
|
|
|
|
connectivity add-on card, based on the LS Research TiWi module with
|
|
|
|
|
Texas Instruments' wl1271 solution.
|
|
|
|
|
Say Y if you want to use a wl1271 expansion card connected to the
|
|
|
|
|
AM18x EVM.
|
|
|
|
|
|
2010-12-10 05:51:07 +08:00
|
|
|
|
2010-09-03 01:58:07 +08:00
|
|
|
config MACH_MITYOMAPL138
|
|
|
|
|
bool "Critical Link MityDSP-L138/MityARM-1808 SoM"
|
|
|
|
|
depends on ARCH_DAVINCI_DA850
|
2010-11-19 23:25:30 +08:00
|
|
|
select EEPROM_AT24
|
2011-04-15 20:32:40 +08:00
|
|
|
select I2C
|
2010-09-03 01:58:07 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to select the Critical Link MityDSP-L138/MityARM-1808
|
|
|
|
|
System on Module. Information on this SoM may be found at
|
|
|
|
|
http://www.mitydsp.com
|
|
|
|
|
|
2010-09-24 00:28:40 +08:00
|
|
|
config MACH_OMAPL138_HAWKBOARD
|
|
|
|
|
bool "TI AM1808 / OMAPL-138 Hawkboard platform"
|
|
|
|
|
depends on ARCH_DAVINCI_DA850
|
|
|
|
|
help
|
|
|
|
|
Say Y here to select the TI AM1808 / OMAPL-138 Hawkboard platform .
|
|
|
|
|
Information of this board may be found at
|
|
|
|
|
http://www.hawkboard.org/
|
|
|
|
|
|
2009-04-14 22:50:37 +08:00
|
|
|
config DAVINCI_MUX
|
|
|
|
|
bool "DAVINCI multiplexing support"
|
|
|
|
|
depends on ARCH_DAVINCI
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Pin multiplexing support for DAVINCI boards. If your bootloader
|
|
|
|
|
sets the multiplexing correctly, say N. Otherwise, or if unsure,
|
|
|
|
|
say Y.
|
|
|
|
|
|
|
|
|
|
config DAVINCI_MUX_DEBUG
|
2010-07-01 21:30:49 +08:00
|
|
|
bool "Multiplexing debug output"
|
|
|
|
|
depends on DAVINCI_MUX
|
|
|
|
|
help
|
|
|
|
|
Makes the multiplexing functions print out a lot of debug info.
|
|
|
|
|
This is useful if you want to find out the correct values of the
|
|
|
|
|
multiplexing registers.
|
2009-04-14 22:50:37 +08:00
|
|
|
|
|
|
|
|
config DAVINCI_MUX_WARNINGS
|
2010-07-01 21:30:49 +08:00
|
|
|
bool "Warn about pins the bootloader didn't set up"
|
|
|
|
|
depends on DAVINCI_MUX
|
|
|
|
|
help
|
|
|
|
|
Choose Y here to warn whenever driver initialization logic needs
|
|
|
|
|
to change the pin multiplexing setup. When there are no warnings
|
|
|
|
|
printed, it's safe to deselect DAVINCI_MUX for your product.
|
2009-04-14 22:50:37 +08:00
|
|
|
|
2009-03-21 08:29:01 +08:00
|
|
|
config DAVINCI_RESET_CLOCKS
|
|
|
|
|
bool "Reset unused clocks during boot"
|
|
|
|
|
depends on ARCH_DAVINCI
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to reset unused clocks during boot.
|
|
|
|
|
This option saves power, but assumes all drivers are
|
|
|
|
|
using the clock framework. Broken drivers that do not
|
|
|
|
|
yet use clock framework may not work with this option.
|
|
|
|
|
If you are booting from another operating system, you
|
|
|
|
|
probably do not want this option enabled until your
|
|
|
|
|
device drivers work properly.
|
|
|
|
|
|
2007-05-01 02:37:19 +08:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
endif
|