2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2010-07-05 21:31:47 +08:00
|
|
|
if ARCH_OMAP1
|
|
|
|
|
|
|
|
|
|
menu "TI OMAP1 specific features"
|
|
|
|
|
|
2005-07-11 02:58:08 +08:00
|
|
|
comment "OMAP Core Type"
|
|
|
|
|
|
|
|
|
|
config ARCH_OMAP730
|
|
|
|
|
bool "OMAP730 Based System"
|
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_OMAP_OTG
|
2008-10-26 18:55:14 +08:00
|
|
|
select CPU_ARM926T
|
2011-01-19 04:42:23 +08:00
|
|
|
select OMAP_MPU_TIMER
|
2005-07-11 02:58:08 +08:00
|
|
|
|
2009-03-24 09:07:46 +08:00
|
|
|
config ARCH_OMAP850
|
|
|
|
|
bool "OMAP850 Based System"
|
2009-11-23 02:10:52 +08:00
|
|
|
select ARCH_OMAP_OTG
|
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-03-24 09:07:46 +08:00
|
|
|
|
2005-11-10 22:26:48 +08:00
|
|
|
config ARCH_OMAP15XX
|
2005-07-11 02:58:08 +08:00
|
|
|
default y
|
2005-11-10 22:26:48 +08:00
|
|
|
bool "OMAP15xx Based System"
|
2008-10-26 18:55:14 +08:00
|
|
|
select CPU_ARM925T
|
2011-01-19 04:42:23 +08:00
|
|
|
select OMAP_MPU_TIMER
|
2005-07-11 02:58:08 +08:00
|
|
|
|
|
|
|
|
config ARCH_OMAP16XX
|
|
|
|
|
bool "OMAP16xx Based System"
|
|
|
|
|
select ARCH_OMAP_OTG
|
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
|
2018-02-15 14:01:46 +08:00
|
|
|
select OMAP_DM_TIMER
|
2005-07-11 02:58:08 +08:00
|
|
|
|
2016-10-20 21:42:19 +08:00
|
|
|
config OMAP_MUX
|
|
|
|
|
bool "OMAP multiplexing support"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Pin multiplexing support for OMAP boards. If your bootloader
|
|
|
|
|
sets the multiplexing correctly, say N. Otherwise, or if unsure,
|
|
|
|
|
say Y.
|
|
|
|
|
|
|
|
|
|
config OMAP_MUX_DEBUG
|
|
|
|
|
bool "Multiplexing debug output"
|
|
|
|
|
depends on OMAP_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.
|
|
|
|
|
|
|
|
|
|
config OMAP_MUX_WARNINGS
|
|
|
|
|
bool "Warn about pins the bootloader didn't set up"
|
|
|
|
|
depends on OMAP_MUX
|
|
|
|
|
default y
|
|
|
|
|
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 OMAP_MUX for your product.
|
|
|
|
|
|
2005-07-11 02:58:08 +08:00
|
|
|
comment "OMAP Board Type"
|
|
|
|
|
|
|
|
|
|
config MACH_OMAP_INNOVATOR
|
|
|
|
|
bool "TI Innovator"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP15XX || ARCH_OMAP16XX
|
2005-07-11 02:58:08 +08:00
|
|
|
help
|
|
|
|
|
TI OMAP 1510 or 1610 Innovator board support. Say Y here if you
|
|
|
|
|
have such a board.
|
|
|
|
|
|
|
|
|
|
config MACH_OMAP_H2
|
|
|
|
|
bool "TI H2 Support"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP16XX
|
2005-07-11 02:58:08 +08:00
|
|
|
help
|
|
|
|
|
TI OMAP 1610/1611B H2 board support. Say Y here if you have such
|
|
|
|
|
a board.
|
|
|
|
|
|
|
|
|
|
config MACH_OMAP_H3
|
|
|
|
|
bool "TI H3 Support"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP16XX
|
2005-07-11 02:58:08 +08:00
|
|
|
help
|
|
|
|
|
TI OMAP 1710 H3 board support. Say Y here if you have such
|
|
|
|
|
a board.
|
|
|
|
|
|
2009-11-23 02:11:34 +08:00
|
|
|
config MACH_HERALD
|
|
|
|
|
bool "HTC Herald"
|
|
|
|
|
depends on ARCH_OMAP850
|
|
|
|
|
help
|
|
|
|
|
HTC Herald smartphone support (AKA T-Mobile Wing, ...)
|
|
|
|
|
|
2005-07-11 02:58:08 +08:00
|
|
|
config MACH_OMAP_OSK
|
|
|
|
|
bool "TI OSK Support"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP16XX
|
2005-07-11 02:58:08 +08:00
|
|
|
help
|
|
|
|
|
TI OMAP 5912 OSK (OMAP Starter Kit) board support. Say Y here
|
|
|
|
|
if you have such a board.
|
|
|
|
|
|
2005-09-09 06:07:38 +08:00
|
|
|
config OMAP_OSK_MISTRAL
|
|
|
|
|
bool "Mistral QVGA board Support"
|
|
|
|
|
depends on MACH_OMAP_OSK
|
|
|
|
|
help
|
|
|
|
|
The OSK supports an optional add-on board with a Quarter-VGA
|
|
|
|
|
touchscreen, PDA-ish buttons, a resume button, bicolor LED,
|
|
|
|
|
and camera connector. Say Y here if you have this board.
|
|
|
|
|
|
2005-07-11 02:58:08 +08:00
|
|
|
config MACH_OMAP_PERSEUS2
|
|
|
|
|
bool "TI Perseus2"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP730
|
2005-07-11 02:58:08 +08:00
|
|
|
help
|
|
|
|
|
Support for TI OMAP 730 Perseus2 board. Say Y here if you have such
|
|
|
|
|
a board.
|
|
|
|
|
|
2006-06-27 07:16:03 +08:00
|
|
|
config MACH_OMAP_FSAMPLE
|
|
|
|
|
bool "TI F-Sample"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP730
|
2006-06-27 07:16:03 +08:00
|
|
|
help
|
|
|
|
|
Support for TI OMAP 850 F-Sample board. Say Y here if you have such
|
|
|
|
|
a board.
|
|
|
|
|
|
2005-11-10 22:26:48 +08:00
|
|
|
config MACH_OMAP_PALMTE
|
|
|
|
|
bool "Palm Tungsten E"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP15XX
|
2005-11-10 22:26:48 +08:00
|
|
|
help
|
2006-12-07 09:13:51 +08:00
|
|
|
Support for the Palm Tungsten E PDA. To boot the kernel, you'll
|
|
|
|
|
need a PalmOS compatible bootloader; check out
|
|
|
|
|
http://palmtelinux.sourceforge.net/ for more information.
|
|
|
|
|
Say Y here if you have this PDA model, say N otherwise.
|
2005-11-10 22:26:48 +08:00
|
|
|
|
2006-12-07 09:13:57 +08:00
|
|
|
config MACH_OMAP_PALMZ71
|
|
|
|
|
bool "Palm Zire71"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP15XX
|
2006-12-07 09:13:57 +08:00
|
|
|
help
|
|
|
|
|
Support for the Palm Zire71 PDA. To boot the kernel,
|
|
|
|
|
you'll need a PalmOS compatible bootloader; check out
|
2009-01-26 18:12:25 +08:00
|
|
|
http://hackndev.com/palm/z71 for more information.
|
2006-12-07 09:13:57 +08:00
|
|
|
Say Y here if you have such a PDA, say N otherwise.
|
|
|
|
|
|
2006-12-07 09:14:07 +08:00
|
|
|
config MACH_OMAP_PALMTT
|
|
|
|
|
bool "Palm Tungsten|T"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP15XX
|
2006-12-07 09:14:07 +08:00
|
|
|
help
|
|
|
|
|
Support for the Palm Tungsten|T PDA. To boot the kernel, you'll
|
|
|
|
|
need a PalmOS compatible bootloader (Garux); check out
|
2010-10-17 01:36:23 +08:00
|
|
|
http://garux.sourceforge.net/ for more information.
|
2006-12-07 09:14:07 +08:00
|
|
|
Say Y here if you have this PDA model, say N otherwise.
|
|
|
|
|
|
2006-12-07 09:14:08 +08:00
|
|
|
config MACH_SX1
|
|
|
|
|
bool "Siemens SX1"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP15XX
|
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 I2C
|
2006-12-07 09:14:08 +08:00
|
|
|
help
|
|
|
|
|
Support for the Siemens SX1 phone. To boot the kernel,
|
|
|
|
|
you'll need a SX1 compatible bootloader; check out
|
|
|
|
|
http://forum.oslik.ru and
|
2020-07-13 14:48:50 +08:00
|
|
|
https://www.handhelds.org/moin/moin.cgi/SiemensSX1
|
2006-12-07 09:14:08 +08:00
|
|
|
for more information.
|
|
|
|
|
Say Y here if you have such a phone, say NO otherwise.
|
|
|
|
|
|
2006-04-03 00:46:30 +08:00
|
|
|
config MACH_NOKIA770
|
|
|
|
|
bool "Nokia 770"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP16XX
|
2006-04-03 00:46:30 +08:00
|
|
|
help
|
|
|
|
|
Support for the Nokia 770 Internet Tablet. Say Y here if you
|
|
|
|
|
have such a device.
|
|
|
|
|
|
|
|
|
|
config MACH_AMS_DELTA
|
|
|
|
|
bool "Amstrad E3 (Delta)"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP15XX
|
2010-11-17 06:26:57 +08:00
|
|
|
select FIQ
|
ARM: OMAP1: ams-delta: convert latches to basic_mmio_gpio
Once ready, ams-delta specific device drivers currently calling custom
ams_delta_latch[12]_write() functions can be updated to call generic
gpio_set_value() instead, which will make them less platform dependent.
Even more, some custom ams-delta only drivers can perhaps be dropped
from the tree after converting selected ams-delta platform devices to
follow generic GPIO based device models.
The latch_gpios[] table is initially filled with all latch1 and latch2
GPIO pins in order to register and initialize them from the board file
until those are handled by respective existing device drivers (leds,
nand, lcd, serio, asoc, serial). That table will get almost empty after
the transision process is completed, holding only pins not used by any
drivers / connected to unused devices, in order to initialize them from
the board file for power saving purposes.
The new ams_delta_latch_write() function is a unified replacement for
those removed ams_delta_latch[12]_write(), and serves as a temporary
wrapper over gpio_set_value(), providing the old API for those not yet
updated device drivers, and will be removed after all custom drivers are
converted or replaced.
Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Signed-off-by: Tony Lindgren <tony@atomide.com>
2011-12-20 10:24:21 +08:00
|
|
|
select GPIO_GENERIC_PLATFORM
|
2011-12-20 07:08:53 +08:00
|
|
|
select LEDS_GPIO_REGISTER
|
ARM: OMAP1: ams-delta: set up regulator over modem reset GPIO pin
The Amstrad Delta on-board latch2 bit named MODEM_NRESET, now available
as a GPIO pin AMS_DELTA_GPIO_PIN_NMODEM_RESET, is used to power up/down
(bring into/out of a reset state) two distinct on-board devices
simultaneously: the modem, and the voice codec. As a consequence, that
bit is, or can be, manipulated concurrently by two drivers, or their
platform provided hooks.
Instead of updating those drivers to use the gpiolib API as a new method
of controlling the MODEM_NRESET pin state, like it was done to other
drivers accessing latch2 pins, and still being vulnerable to potential
concurrency conflicts, or trying to solve that sharing issue with a
custom piece of code, set up a fixed regulator device on top of that
GPIO pin, with the intention of updating both drivers to manipulate that
regulator, not the GPIO pin directly.
Before the ASoC driver is updated and the modem platform data expanded
with a power management callback for switching its power, the
ams_delta_latch_write() function, which still provides the old API for
accessing latch2 functionality from not updated drivers, is modified to
toggle the regulator instead of the MODEM_NRESET GPIO pin. A helper
function provided for balancing the regulator enable/disable operations,
together with the consumer data needed for tracking the regulator state,
will be removed once the drivers are updated.
Depends on patch series "ARM: OMAP1: ams-delta: replace custom I/O with
GPIO".
Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Signed-off-by: Tony Lindgren <tony@atomide.com>
2012-03-06 00:05:10 +08:00
|
|
|
select REGULATOR
|
|
|
|
|
select REGULATOR_FIXED_VOLTAGE
|
2006-04-03 00:46:30 +08:00
|
|
|
help
|
|
|
|
|
Support for the Amstrad E3 (codename Delta) videophone. Say Y here
|
|
|
|
|
if you have such a device.
|
|
|
|
|
|
2005-07-11 02:58:08 +08:00
|
|
|
config MACH_OMAP_GENERIC
|
|
|
|
|
bool "Generic OMAP board"
|
2019-11-12 01:10:34 +08:00
|
|
|
depends on ARCH_OMAP15XX || ARCH_OMAP16XX
|
2005-07-11 02:58:08 +08:00
|
|
|
help
|
|
|
|
|
Support for generic OMAP-1510, 1610 or 1710 board with
|
|
|
|
|
no FPGA. Can be used as template for porting Linux to
|
|
|
|
|
custom OMAP boards. Say Y here if you have a custom
|
|
|
|
|
board.
|
|
|
|
|
|
2010-07-05 21:31:47 +08:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
endif
|