2019-05-19 05:07:45 -07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2022-05-30 05:46:17 -07:00
|
|
|
menuconfig ARCH_OMAP1
|
|
|
|
|
bool "TI OMAP1"
|
|
|
|
|
depends on ARCH_MULTI_V4T || ARCH_MULTI_V5
|
|
|
|
|
depends on CPU_LITTLE_ENDIAN
|
ARM: add ATAGS dependencies to non-DT platforms
There are a total of eight platforms that only suppor ATAGS based boot
with board files but no devicetree booting.
For dove, the DT support is part of the mvebu platform, which shares
driver but no code in arch/arm.
Most of these will never get converted to DT, and the majority of the
board files appear to be entirely unused already. There are still known
users on a few machines, and there may be interest in converting some
omap1, ep93xx or footbridge machines over in the future.
For the moment, just add a Kconfig dependency to hide these platforms
completely when CONFIG_ATAGS is disabled, and reorder the priority
of the options: Rather than offering to turn ATAGS off for platforms
that have DT support, make it a top-level setting that determines
which platforms are visible.
The s3c24xx platform supports one machine with DT support, but it
cannot be built without also including ATAGS support, and the
entire platform is scheduled for removal, so leaving the entire
platform behind a dependency seems good enough.
All defconfig files should keep working, as the option remains default
enabled.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2022-07-05 05:10:34 -07:00
|
|
|
depends on ATAGS
|
2022-05-30 05:46:17 -07:00
|
|
|
select ARCH_HAS_HOLES_MEMORYMODEL
|
|
|
|
|
select ARCH_OMAP
|
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
|
select FORCE_PCI if PCCARD
|
|
|
|
|
select GPIOLIB
|
|
|
|
|
help
|
|
|
|
|
Support for older TI OMAP1 (omap7xx, omap15xx or omap16xx)
|
|
|
|
|
|
2010-07-05 06:31:47 -07:00
|
|
|
if ARCH_OMAP1
|
|
|
|
|
|
|
|
|
|
menu "TI OMAP1 specific features"
|
|
|
|
|
|
2005-07-10 11:58:08 -07:00
|
|
|
comment "OMAP Core Type"
|
|
|
|
|
|
2005-11-10 07:26:48 -07:00
|
|
|
config ARCH_OMAP15XX
|
2022-05-30 05:46:17 -07:00
|
|
|
depends on ARCH_MULTI_V4T
|
2005-07-10 11:58:08 -07:00
|
|
|
default y
|
2005-11-10 07:26:48 -07:00
|
|
|
bool "OMAP15xx Based System"
|
2008-10-26 03:55:14 -07:00
|
|
|
select CPU_ARM925T
|
2011-01-18 13:42:23 -07:00
|
|
|
select OMAP_MPU_TIMER
|
2005-07-10 11:58:08 -07:00
|
|
|
|
|
|
|
|
config ARCH_OMAP16XX
|
2022-05-30 05:46:17 -07:00
|
|
|
depends on ARCH_MULTI_V5
|
2005-07-10 11:58:08 -07:00
|
|
|
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-06 09:12:25 -07:00
|
|
|
select CPU_ARM926T
|
2018-02-14 23:01:46 -07:00
|
|
|
select OMAP_DM_TIMER
|
2005-07-10 11:58:08 -07:00
|
|
|
|
2019-09-20 08:44:32 -07:00
|
|
|
config ARCH_OMAP
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
comment "OMAP Feature Selections"
|
|
|
|
|
|
2016-10-20 06:42:19 -07: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.
|
|
|
|
|
|
2019-09-20 04:57:31 -07:00
|
|
|
config OMAP_32K_TIMER
|
|
|
|
|
bool "Use 32KHz timer"
|
|
|
|
|
depends on ARCH_OMAP16XX
|
|
|
|
|
default ARCH_OMAP16XX
|
|
|
|
|
help
|
|
|
|
|
Select this option if you want to enable the OMAP 32KHz timer.
|
|
|
|
|
This timer saves power compared to the OMAP_MPU_TIMER, and has
|
|
|
|
|
support for no tick during idle. The 32KHz timer provides less
|
|
|
|
|
intra-tick resolution than OMAP_MPU_TIMER. The 32KHz timer is
|
|
|
|
|
currently only available for OMAP16XX, 24XX, 34XX, OMAP4/5 and DRA7XX.
|
|
|
|
|
|
|
|
|
|
On OMAP2PLUS this value is only used for CONFIG_HZ and
|
|
|
|
|
CLOCK_TICK_RATE compile time calculation.
|
|
|
|
|
The actual timer selection is done in the board file
|
|
|
|
|
through the (DT_)MACHINE_START structure.
|
|
|
|
|
|
2019-09-20 08:44:32 -07:00
|
|
|
config OMAP_MPU_TIMER
|
|
|
|
|
bool "Use mpu timer"
|
|
|
|
|
depends on ARCH_OMAP1
|
|
|
|
|
help
|
|
|
|
|
Select this option if you want to use the OMAP mpu timer. This
|
|
|
|
|
timer provides more intra-tick resolution than the 32KHz timer,
|
|
|
|
|
but consumes more power.
|
|
|
|
|
|
|
|
|
|
config OMAP_SERIAL_WAKE
|
|
|
|
|
bool "Enable wake-up events for serial ports"
|
|
|
|
|
depends on ARCH_OMAP1 && OMAP_MUX
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Select this option if you want to have your system wake up
|
|
|
|
|
to data on the serial RX line. This allows you to wake the
|
|
|
|
|
system from serial console.
|
|
|
|
|
|
|
|
|
|
config OMAP_RESET_CLOCKS
|
|
|
|
|
bool "Reset unused clocks during boot"
|
|
|
|
|
depends on ARCH_OMAP
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config ARCH_OMAP_OTG
|
|
|
|
|
bool
|
|
|
|
|
|
2005-07-10 11:58:08 -07:00
|
|
|
comment "OMAP Board Type"
|
|
|
|
|
|
|
|
|
|
config MACH_OMAP_OSK
|
|
|
|
|
bool "TI OSK Support"
|
2019-11-11 10:10:34 -07:00
|
|
|
depends on ARCH_OMAP16XX
|
2021-05-17 02:58:09 -07:00
|
|
|
help
|
2005-07-10 11:58:08 -07:00
|
|
|
TI OMAP 5912 OSK (OMAP Starter Kit) board support. Say Y here
|
2023-03-15 02:11:52 -07:00
|
|
|
if you have such a board.
|
2005-07-10 11:58:08 -07:00
|
|
|
|
2005-11-10 07:26:48 -07:00
|
|
|
config MACH_OMAP_PALMTE
|
|
|
|
|
bool "Palm Tungsten E"
|
2019-11-11 10:10:34 -07:00
|
|
|
depends on ARCH_OMAP15XX
|
2005-11-10 07:26:48 -07:00
|
|
|
help
|
2006-12-06 18:13:51 -07: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 07:26:48 -07:00
|
|
|
|
2006-12-06 18:14:08 -07:00
|
|
|
config MACH_SX1
|
|
|
|
|
bool "Siemens SX1"
|
2019-11-11 10:10:34 -07: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-06 09:12:25 -07:00
|
|
|
select I2C
|
2006-12-06 18:14:08 -07: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-12 23:48:50 -07:00
|
|
|
https://www.handhelds.org/moin/moin.cgi/SiemensSX1
|
2006-12-06 18:14:08 -07:00
|
|
|
for more information.
|
|
|
|
|
Say Y here if you have such a phone, say NO otherwise.
|
|
|
|
|
|
2006-04-02 09:46:30 -07:00
|
|
|
config MACH_NOKIA770
|
|
|
|
|
bool "Nokia 770"
|
2019-11-11 10:10:34 -07:00
|
|
|
depends on ARCH_OMAP16XX
|
2006-04-02 09:46:30 -07: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-11 10:10:34 -07:00
|
|
|
depends on ARCH_OMAP15XX
|
2010-11-16 15:26:57 -07: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-19 19:24:21 -07:00
|
|
|
select GPIO_GENERIC_PLATFORM
|
2011-12-19 16:08:53 -07: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-05 09:05:10 -07:00
|
|
|
select REGULATOR
|
|
|
|
|
select REGULATOR_FIXED_VOLTAGE
|
2006-04-02 09:46:30 -07:00
|
|
|
help
|
|
|
|
|
Support for the Amstrad E3 (codename Delta) videophone. Say Y here
|
|
|
|
|
if you have such a device.
|
|
|
|
|
|
2010-07-05 06:31:47 -07:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
endif
|