2007-07-09 21:06:53 +00:00
|
|
|
if ARCH_MXC
|
|
|
|
|
|
2010-06-15 16:14:19 +00:00
|
|
|
source "arch/arm/plat-mxc/devices/Kconfig"
|
|
|
|
|
|
2007-07-09 21:06:53 +00:00
|
|
|
menu "Freescale MXC Implementations"
|
|
|
|
|
|
|
|
|
|
choice
|
2009-01-29 13:42:25 +00:00
|
|
|
prompt "Freescale CPU family:"
|
2011-09-27 05:48:02 +00:00
|
|
|
default ARCH_IMX_V6_V7
|
2007-07-09 21:06:53 +00:00
|
|
|
|
2011-08-23 07:39:35 +00:00
|
|
|
config ARCH_IMX_V4_V5
|
|
|
|
|
bool "i.MX1, i.MX21, i.MX25, i.MX27"
|
|
|
|
|
select ARM_PATCH_PHYS_VIRT
|
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 16:12:25 +00:00
|
|
|
select AUTO_ZRELADDR if !ZBOOT_ROM
|
2009-06-04 09:32:12 +00:00
|
|
|
help
|
2011-08-23 07:39:35 +00:00
|
|
|
This enables support for systems based on the Freescale i.MX ARMv4
|
|
|
|
|
and ARMv5 SoCs
|
2009-06-04 09:32:12 +00:00
|
|
|
|
2011-09-27 05:48:02 +00:00
|
|
|
config ARCH_IMX_V6_V7
|
2011-11-07 11:36:48 +00:00
|
|
|
bool "i.MX3, i.MX5, i.MX6"
|
2011-09-27 05:48:02 +00:00
|
|
|
select ARM_PATCH_PHYS_VIRT
|
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 16:12:25 +00:00
|
|
|
select AUTO_ZRELADDR if !ZBOOT_ROM
|
2011-11-29 15:56:19 +00:00
|
|
|
select MIGHT_HAVE_CACHE_L2X0
|
2007-07-09 21:06:53 +00:00
|
|
|
help
|
2011-11-07 11:36:48 +00:00
|
|
|
This enables support for systems based on the Freescale i.MX3, i.MX5
|
|
|
|
|
and i.MX6 family.
|
2011-04-08 09:06:43 +00:00
|
|
|
|
2007-07-09 21:06:53 +00:00
|
|
|
endchoice
|
|
|
|
|
|
2010-06-10 13:11:13 +00:00
|
|
|
source "arch/arm/mach-imx/Kconfig"
|
2007-07-09 21:06:53 +00:00
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2008-09-09 09:29:41 +00:00
|
|
|
config MXC_IRQ_PRIOR
|
|
|
|
|
bool "Use IRQ priority"
|
|
|
|
|
help
|
|
|
|
|
Select this if you want to use prioritized IRQ handling.
|
|
|
|
|
This feature prevents higher priority ISR to be interrupted
|
|
|
|
|
by lower priority IRQ even IRQF_DISABLED flag is not set.
|
|
|
|
|
This may be useful in embedded applications, where are strong
|
|
|
|
|
requirements for timing.
|
|
|
|
|
Say N here, unless you have a specialized requirement.
|
|
|
|
|
|
2009-12-03 20:36:41 +00:00
|
|
|
config MXC_TZIC
|
2010-11-05 08:47:21 +00:00
|
|
|
bool
|
2009-12-03 20:36:41 +00:00
|
|
|
|
2010-11-05 08:37:22 +00:00
|
|
|
config MXC_AVIC
|
|
|
|
|
bool
|
|
|
|
|
|
2010-06-24 13:11:28 +00:00
|
|
|
config MXC_DEBUG_BOARD
|
|
|
|
|
bool "Enable MXC debug board(for 3-stack)"
|
|
|
|
|
help
|
|
|
|
|
The debug board is an integral part of the MXC 3-stack(PDK)
|
|
|
|
|
platforms, it can be attached or removed from the peripheral
|
|
|
|
|
board. On debug board, several debug devices(ethernet, UART,
|
|
|
|
|
buttons, LEDs and JTAG) are implemented. Between the MCU and
|
|
|
|
|
these devices, a CPLD is added as a bridge which performs
|
|
|
|
|
data/address de-multiplexing and decode, signal level shift,
|
|
|
|
|
interrupt control and various board functions.
|
|
|
|
|
|
2010-08-19 12:08:04 +00:00
|
|
|
config HAVE_EPIT
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config MXC_USE_EPIT
|
|
|
|
|
bool "Use EPIT instead of GPT"
|
|
|
|
|
depends on HAVE_EPIT
|
|
|
|
|
help
|
|
|
|
|
Use EPIT as the system timer on systems that have it. Normally you
|
|
|
|
|
don't have a reason to do so as the EPIT has the same features and
|
|
|
|
|
uses the same clocks as the GPT. Anyway, on some systems the GPT
|
|
|
|
|
may be in use for other purposes.
|
|
|
|
|
|
2009-11-05 08:44:09 +00:00
|
|
|
config MXC_ULPI
|
|
|
|
|
bool
|
|
|
|
|
|
2009-04-02 15:38:41 +00:00
|
|
|
config ARCH_HAS_RNGA
|
|
|
|
|
bool
|
|
|
|
|
|
2010-02-15 08:42:59 +00:00
|
|
|
config IMX_HAVE_IOMUX_V1
|
|
|
|
|
bool
|
|
|
|
|
|
2009-04-01 09:11:48 +00:00
|
|
|
config ARCH_MXC_IOMUX_V3
|
|
|
|
|
bool
|
2009-10-29 16:12:39 +00:00
|
|
|
|
2010-10-12 16:29:01 +00:00
|
|
|
config IRAM_ALLOC
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_ALLOCATOR
|
|
|
|
|
|
2007-07-09 21:06:53 +00:00
|
|
|
endif
|
