2014-06-10 21:06:10 +07:00
|
|
|
menuconfig ARCH_MXC
|
2012-10-19 01:04:30 +07:00
|
|
|
bool "Freescale i.MX family" if ARCH_MULTI_V4_V5 || ARCH_MULTI_V6_V7
|
2014-01-14 21:36:47 +07:00
|
|
|
select ARCH_HAS_OPP
|
2012-09-17 08:38:39 +07:00
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
2013-07-26 10:17:35 +07:00
|
|
|
select ARM_CPU_SUSPEND if PM
|
2012-09-17 08:38:39 +07:00
|
|
|
select CLKSRC_MMIO
|
|
|
|
select GENERIC_IRQ_CHIP
|
2013-11-16 21:25:02 +07:00
|
|
|
select PINCTRL
|
2014-01-14 21:36:47 +07:00
|
|
|
select PM_OPP if PM
|
2013-08-13 15:59:28 +07:00
|
|
|
select SOC_BUS
|
2014-02-18 00:04:17 +07:00
|
|
|
select SRAM
|
2012-09-17 08:38:39 +07:00
|
|
|
help
|
|
|
|
Support for Freescale MXC/iMX-based family of processors
|
|
|
|
|
2014-06-10 21:06:10 +07:00
|
|
|
if ARCH_MXC
|
2012-09-13 18:48:07 +07:00
|
|
|
|
|
|
|
config MXC_TZIC
|
|
|
|
bool
|
|
|
|
|
|
|
|
config MXC_AVIC
|
|
|
|
bool
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
config ARCH_HAS_RNGA
|
|
|
|
bool
|
|
|
|
|
2013-03-21 06:39:42 +07:00
|
|
|
config HAVE_IMX_ANATOP
|
|
|
|
bool
|
|
|
|
|
2011-09-06 13:39:44 +07:00
|
|
|
config HAVE_IMX_GPC
|
|
|
|
bool
|
|
|
|
|
|
|
|
config HAVE_IMX_MMDC
|
|
|
|
bool
|
|
|
|
|
|
|
|
config HAVE_IMX_SRC
|
2012-10-23 14:23:59 +07:00
|
|
|
def_bool y if SMP
|
2013-03-28 23:35:19 +07:00
|
|
|
select ARCH_HAS_RESET_CONTROLLER
|
2011-09-06 13:39:44 +07:00
|
|
|
|
2012-09-13 12:26:00 +07:00
|
|
|
config IMX_HAVE_IOMUX_V1
|
|
|
|
bool
|
|
|
|
|
|
|
|
config ARCH_MXC_IOMUX_V3
|
|
|
|
bool
|
|
|
|
|
2010-06-14 22:39:21 +07:00
|
|
|
config SOC_IMX1
|
2010-11-12 00:06:17 +07:00
|
|
|
bool
|
2010-06-14 22:39:21 +07:00
|
|
|
select CPU_ARM920T
|
|
|
|
select IMX_HAVE_IOMUX_V1
|
2010-11-05 15:37:22 +07:00
|
|
|
select MXC_AVIC
|
2010-11-12 00:06:17 +07:00
|
|
|
|
|
|
|
config SOC_IMX21
|
|
|
|
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-06 23:12:25 +07:00
|
|
|
select CPU_ARM926T
|
2010-11-12 00:06:17 +07:00
|
|
|
select IMX_HAVE_IOMUX_V1
|
2010-11-05 15:37:22 +07:00
|
|
|
select MXC_AVIC
|
2010-11-12 00:06:17 +07:00
|
|
|
|
|
|
|
config SOC_IMX25
|
2010-06-14 22:39:21 +07:00
|
|
|
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-06 23:12:25 +07:00
|
|
|
select ARCH_MXC_IOMUX_V3
|
2010-11-12 00:06:17 +07:00
|
|
|
select CPU_ARM926T
|
2010-11-05 15:37:22 +07:00
|
|
|
select MXC_AVIC
|
2013-11-06 15:52:18 +07:00
|
|
|
select PINCTRL_IMX25
|
2010-11-12 00:06:17 +07:00
|
|
|
|
|
|
|
config SOC_IMX27
|
|
|
|
bool
|
2013-03-27 20:01:31 +07:00
|
|
|
select ARCH_HAS_OPP
|
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 23:12:25 +07:00
|
|
|
select CPU_ARM926T
|
2010-11-12 00:06:17 +07:00
|
|
|
select IMX_HAVE_IOMUX_V1
|
2010-11-05 15:37:22 +07:00
|
|
|
select MXC_AVIC
|
2013-11-12 15:50:10 +07:00
|
|
|
select PINCTRL_IMX27
|
2010-11-12 00:06:17 +07:00
|
|
|
|
2011-03-17 15:40:29 +07:00
|
|
|
config SOC_IMX31
|
|
|
|
bool
|
|
|
|
select CPU_V6
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_RNGA
|
|
|
|
select MXC_AVIC
|
2011-09-27 12:48:02 +07:00
|
|
|
select SMP_ON_UP if SMP
|
2011-03-17 15:40:29 +07:00
|
|
|
|
|
|
|
config SOC_IMX35
|
|
|
|
bool
|
|
|
|
select ARCH_MXC_IOMUX_V3
|
|
|
|
select HAVE_EPIT
|
|
|
|
select MXC_AVIC
|
2014-01-10 22:40:39 +07:00
|
|
|
select PINCTRL_IMX35
|
2011-09-27 12:48:02 +07:00
|
|
|
select SMP_ON_UP if SMP
|
2011-03-17 15:40:29 +07:00
|
|
|
|
2012-09-17 08:38:39 +07:00
|
|
|
if ARCH_MULTI_V4T
|
2010-06-14 22:39:21 +07:00
|
|
|
|
2010-06-14 20:56:58 +07:00
|
|
|
comment "MX1 platforms:"
|
|
|
|
config MACH_MXLADS
|
|
|
|
bool
|
|
|
|
|
|
|
|
config ARCH_MX1ADS
|
|
|
|
bool "MX1ADS platform"
|
2010-06-16 20:26:07 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-06-22 19:50:59 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
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 23:12:25 +07:00
|
|
|
select MACH_MXLADS
|
|
|
|
select SOC_IMX1
|
2010-06-14 20:56:58 +07:00
|
|
|
help
|
|
|
|
Say Y here if you are using Motorola MX1ADS/MXLADS boards
|
|
|
|
|
|
|
|
config MACH_SCB9328
|
|
|
|
bool "Synertronixx scb9328"
|
2010-06-22 19:50:59 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2013-06-03 20:46:53 +07:00
|
|
|
select SOC_IMX1
|
2010-06-14 20:56:58 +07:00
|
|
|
help
|
|
|
|
Say Y here if you are using a Synertronixx scb9328 board
|
|
|
|
|
2011-04-29 12:21:39 +07:00
|
|
|
config MACH_APF9328
|
|
|
|
bool "APF9328"
|
2011-10-08 22:19:49 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2011-04-29 12:21:39 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX1
|
2011-04-29 12:21:39 +07:00
|
|
|
help
|
|
|
|
Say Yes here if you are using the Armadeus APF9328 development board
|
|
|
|
|
2012-09-17 08:38:39 +07:00
|
|
|
endif
|
|
|
|
|
|
|
|
if ARCH_MULTI_V5
|
|
|
|
|
2010-06-14 21:56:46 +07:00
|
|
|
comment "MX21 platforms:"
|
2008-07-05 15:03:00 +07:00
|
|
|
|
2009-04-15 20:39:27 +07:00
|
|
|
config MACH_MX21ADS
|
|
|
|
bool "MX21ADS platform"
|
2010-11-04 23:07:48 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2010-06-22 22:59:58 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2010-06-16 16:17:45 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX21
|
2009-04-15 20:39:27 +07:00
|
|
|
help
|
|
|
|
Include support for MX21ADS platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
2010-11-12 00:06:17 +07:00
|
|
|
comment "MX25 platforms:"
|
|
|
|
|
|
|
|
config MACH_MX25_3DS
|
|
|
|
bool "Support MX25PDK (3DS) Platform"
|
2011-07-09 00:59:50 +07:00
|
|
|
select IMX_HAVE_PLATFORM_FLEXCAN
|
2010-12-22 21:25:32 +07:00
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
2010-11-12 00:06:17 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
|
|
|
select IMX_HAVE_PLATFORM_IMXDI_RTC
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
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 23:12:25 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-11-12 00:06:17 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_KEYPAD
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2010-11-20 03:03:33 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SDHCI_ESDHC_IMX
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX25
|
2010-11-12 00:06:17 +07:00
|
|
|
|
2011-12-13 13:31:35 +07:00
|
|
|
config MACH_EUKREA_CPUIMX25SD
|
2010-11-12 00:06:17 +07:00
|
|
|
bool "Support Eukrea CPUIMX25 Platform"
|
|
|
|
select IMX_HAVE_PLATFORM_FLEXCAN
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
2012-05-08 14:20:18 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
2010-11-12 00:06:17 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMXDI_RTC
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2010-11-20 03:03:33 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SDHCI_ESDHC_IMX
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX25
|
2010-11-12 00:06:17 +07:00
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Baseboard"
|
2011-12-13 13:31:35 +07:00
|
|
|
depends on MACH_EUKREA_CPUIMX25SD
|
2010-11-12 00:06:17 +07:00
|
|
|
default MACH_EUKREA_MBIMXSD25_BASEBOARD
|
|
|
|
|
|
|
|
config MACH_EUKREA_MBIMXSD25_BASEBOARD
|
|
|
|
bool "Eukrea MBIMXSD development board"
|
2011-03-01 00:04:33 +07:00
|
|
|
select IMX_HAVE_PLATFORM_GPIO_KEYS
|
2010-11-12 00:06:17 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
2012-05-08 14:20:17 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2011-05-29 02:05:01 +07:00
|
|
|
select LEDS_GPIO_REGISTER
|
2010-11-12 00:06:17 +07:00
|
|
|
help
|
|
|
|
This adds board specific devices that can be found on Eukrea's
|
|
|
|
MBIMXSD evaluation board.
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2012-09-20 19:59:36 +07:00
|
|
|
config MACH_IMX25_DT
|
|
|
|
bool "Support i.MX25 platforms from device tree"
|
|
|
|
select SOC_IMX25
|
|
|
|
help
|
|
|
|
Include support for Freescale i.MX25 based platforms
|
|
|
|
using the device tree for discovery
|
|
|
|
|
2010-06-14 21:56:46 +07:00
|
|
|
comment "MX27 platforms:"
|
|
|
|
|
2008-07-05 15:03:00 +07:00
|
|
|
config MACH_MX27ADS
|
|
|
|
bool "MX27ADS platform"
|
2010-11-04 23:07:48 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2010-06-16 22:25:40 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-06-23 14:36:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2010-06-16 12:35:31 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2010-10-29 15:56:07 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_W1
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX27
|
2008-07-05 15:03:00 +07:00
|
|
|
help
|
|
|
|
Include support for MX27ADS platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
2008-07-05 15:03:00 +07:00
|
|
|
|
|
|
|
config MACH_PCM038
|
|
|
|
bool "Phytec phyCORE-i.MX27 CPU module (pcm038)"
|
2010-11-04 16:09:10 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
2010-06-16 22:25:40 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-06-23 14:36:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2010-11-06 00:52:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
2010-06-16 12:35:31 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2010-10-29 15:56:07 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_W1
|
2010-06-22 14:00:22 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX27
|
2008-07-05 15:03:00 +07:00
|
|
|
help
|
|
|
|
Include support for phyCORE-i.MX27 (aka pcm038) platform. This
|
|
|
|
includes specific configurations for the module and its peripherals.
|
2008-07-05 15:03:01 +07:00
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Baseboard"
|
|
|
|
depends on MACH_PCM038
|
|
|
|
default MACH_PCM970_BASEBOARD
|
|
|
|
|
|
|
|
config MACH_PCM970_BASEBOARD
|
2010-11-04 23:07:48 +07:00
|
|
|
bool "PHYTEC PCM970 development board"
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2008-07-05 15:03:01 +07:00
|
|
|
help
|
|
|
|
This adds board specific devices that can be found on Phytec's
|
|
|
|
PCM970 evaluation board.
|
|
|
|
|
|
|
|
endchoice
|
2009-01-29 20:42:25 +07:00
|
|
|
|
2009-12-10 16:19:43 +07:00
|
|
|
config MACH_CPUIMX27
|
2009-07-16 21:26:33 +07:00
|
|
|
bool "Eukrea CPUIMX27 module"
|
2010-11-09 23:52:14 +07:00
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
2010-11-04 16:09:10 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
2010-06-16 22:25:40 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-06-23 14:36:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2010-11-06 00:52:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
2010-06-16 12:35:31 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2010-10-29 15:56:07 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_W1
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX27
|
2009-07-16 21:26:33 +07:00
|
|
|
help
|
|
|
|
Include support for Eukrea CPUIMX27 platform. This includes
|
|
|
|
specific configurations for the module and its peripherals.
|
|
|
|
|
|
|
|
config MACH_EUKREA_CPUIMX27_USESDHC2
|
|
|
|
bool "CPUIMX27 integrates SDHC2 module"
|
2009-12-10 16:19:43 +07:00
|
|
|
depends on MACH_CPUIMX27
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2009-07-16 21:26:33 +07:00
|
|
|
help
|
2010-05-19 23:45:59 +07:00
|
|
|
This adds support for the internal SDHC2 used on CPUIMX27
|
2009-07-16 21:26:33 +07:00
|
|
|
for wifi or eMMC.
|
|
|
|
|
2010-05-19 23:45:59 +07:00
|
|
|
config MACH_EUKREA_CPUIMX27_USEUART4
|
|
|
|
bool "CPUIMX27 integrates UART4 module"
|
|
|
|
depends on MACH_CPUIMX27
|
|
|
|
help
|
|
|
|
This adds support for the internal UART4 used on CPUIMX27
|
|
|
|
for bluetooth.
|
|
|
|
|
2009-07-16 21:26:34 +07:00
|
|
|
choice
|
|
|
|
prompt "Baseboard"
|
2009-12-10 16:19:43 +07:00
|
|
|
depends on MACH_CPUIMX27
|
2009-07-16 21:26:34 +07:00
|
|
|
default MACH_EUKREA_MBIMX27_BASEBOARD
|
|
|
|
|
|
|
|
config MACH_EUKREA_MBIMX27_BASEBOARD
|
2010-08-25 22:37:45 +07:00
|
|
|
bool "Eukrea MBIMX27 development board"
|
2010-11-04 23:07:48 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2010-11-10 15:58:56 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_KEYPAD
|
2010-08-25 22:37:45 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
2010-06-23 14:36:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2010-06-22 14:00:22 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2011-05-29 02:05:01 +07:00
|
|
|
select LEDS_GPIO_REGISTER
|
2009-07-16 21:26:34 +07:00
|
|
|
help
|
|
|
|
This adds board specific devices that can be found on Eukrea's
|
|
|
|
MBIMX27 evaluation board.
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2009-04-17 02:45:01 +07:00
|
|
|
config MACH_MX27_3DS
|
|
|
|
bool "MX27PDK platform"
|
2010-12-22 21:25:31 +07:00
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
2010-12-08 02:14:45 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
2011-06-22 19:25:25 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2011-03-02 02:59:46 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-11-10 15:58:56 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_KEYPAD
|
2012-07-04 01:44:57 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
2010-06-23 14:36:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2012-02-16 04:36:10 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MX2_CAMERA
|
2010-12-22 21:25:31 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2011-01-03 20:16:39 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2011-01-11 03:17:37 +07:00
|
|
|
select MXC_DEBUG_BOARD
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX27
|
2009-04-17 02:45:01 +07:00
|
|
|
help
|
|
|
|
Include support for MX27PDK platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
2009-06-04 04:23:54 +07:00
|
|
|
|
2010-07-30 15:06:01 +07:00
|
|
|
config MACH_IMX27_VISSTRIM_M10
|
|
|
|
bool "Vista Silicon i.MX27 Visstrim_m10"
|
2011-03-01 00:04:33 +07:00
|
|
|
select IMX_HAVE_PLATFORM_GPIO_KEYS
|
2010-07-30 15:06:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2011-03-18 18:24:08 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
2010-07-30 15:06:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2012-02-28 23:31:51 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MX2_CAMERA
|
2012-09-05 18:06:15 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MX2_EMMA
|
2010-11-06 00:52:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
2012-02-28 23:31:48 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2012-02-29 19:17:33 +07:00
|
|
|
select LEDS_GPIO_REGISTER
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX27
|
2010-07-30 15:06:01 +07:00
|
|
|
help
|
|
|
|
Include support for Visstrim_m10 platform and its different variants.
|
|
|
|
This includes specific configurations for the board and its
|
|
|
|
peripherals.
|
|
|
|
|
2009-08-06 16:19:39 +07:00
|
|
|
config MACH_PCA100
|
|
|
|
bool "Phytec phyCARD-s (pca100)"
|
2010-11-09 23:52:14 +07:00
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
2010-11-04 16:09:10 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
2010-11-04 23:07:48 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2010-06-16 22:25:40 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-08-25 22:37:45 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
2010-06-23 14:36:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2010-11-06 00:52:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2010-06-16 12:35:31 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2010-10-29 15:56:07 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_W1
|
2010-06-22 14:00:22 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX27
|
2009-08-06 16:19:39 +07:00
|
|
|
help
|
|
|
|
Include support for phyCARD-s (aka pca100) platform. This
|
|
|
|
includes specific configurations for the module and its peripherals.
|
|
|
|
|
2009-11-26 00:24:50 +07:00
|
|
|
config MACH_MXT_TD60
|
|
|
|
bool "Maxtrack i-MXT TD60"
|
2010-11-04 23:07:48 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2010-06-16 22:25:40 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2010-06-23 14:36:01 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2010-11-05 23:26:09 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2010-06-16 12:35:31 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX27
|
2009-11-26 00:24:50 +07:00
|
|
|
help
|
|
|
|
Include support for i-MXT (aka td60) platform. This
|
|
|
|
includes specific configurations for the module and its peripherals.
|
|
|
|
|
2012-02-29 03:57:50 +07:00
|
|
|
config MACH_IMX27_DT
|
|
|
|
bool "Support i.MX27 platforms from device tree"
|
|
|
|
select SOC_IMX27
|
|
|
|
help
|
|
|
|
Include support for Freescale i.MX27 based platforms
|
|
|
|
using the device tree for discovery
|
|
|
|
|
2009-01-29 20:42:25 +07:00
|
|
|
endif
|
2011-03-17 15:40:29 +07:00
|
|
|
|
2012-09-17 08:38:39 +07:00
|
|
|
if ARCH_MULTI_V6
|
2011-03-17 15:40:29 +07:00
|
|
|
|
|
|
|
comment "MX31 platforms:"
|
|
|
|
|
|
|
|
config MACH_MX31ADS
|
|
|
|
bool "Support MX31ADS platforms"
|
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 23:12:25 +07:00
|
|
|
default y
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for MX31ADS platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_MX31ADS_WM1133_EV1
|
|
|
|
bool "Support Wolfson Microelectronics 1133-EV1 module"
|
|
|
|
depends on MACH_MX31ADS
|
|
|
|
depends on MFD_WM8350_I2C
|
2013-02-14 23:45:58 +07:00
|
|
|
depends on REGULATOR_WM8350 = y
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for the Wolfson Microelectronics 1133-EV1 PMU
|
|
|
|
and audio module for the MX31ADS platform.
|
|
|
|
|
|
|
|
config MACH_MX31LILLY
|
|
|
|
bool "Support MX31 LILLY-1131 platforms (INCO startec)"
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for mx31 based LILLY1131 modules. This includes
|
|
|
|
specific configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_MX31LITE
|
|
|
|
bool "Support MX31 LITEKIT (LogicPD)"
|
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_RTC
|
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2011-05-29 02:05:01 +07:00
|
|
|
select LEDS_GPIO_REGISTER
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for MX31 LITEKIT platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_PCM037
|
|
|
|
bool "Support Phytec pcm037 (i.MX31) platforms"
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_W1
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for Phytec pcm037 platform. This includes
|
|
|
|
specific configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_PCM037_EET
|
|
|
|
bool "Support pcm037 EET board extensions"
|
|
|
|
depends on MACH_PCM037
|
|
|
|
select IMX_HAVE_PLATFORM_GPIO_KEYS
|
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
|
|
|
help
|
|
|
|
Add support for PCM037 EET baseboard extensions. If you are using the
|
|
|
|
OLED display with EET, use "video=mx3fb:CMEL-OLED" kernel
|
|
|
|
command-line parameter.
|
|
|
|
|
|
|
|
config MACH_MX31_3DS
|
|
|
|
bool "Support MX31PDK (3DS)"
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_KEYPAD
|
2012-05-22 02:09:06 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
2011-09-15 00:04:38 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
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 23:12:25 +07:00
|
|
|
select MXC_DEBUG_BOARD
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for MX31PDK (3DS) platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_MX31_3DS_MXC_NAND_USE_BBT
|
|
|
|
bool "Make the MXC NAND driver use the in flash Bad Block Table"
|
|
|
|
depends on MACH_MX31_3DS
|
|
|
|
depends on MTD_NAND_MXC
|
|
|
|
help
|
|
|
|
Enable this if you want that the MXC NAND driver uses the in flash
|
|
|
|
Bad Block Table to know what blocks are bad instead of scanning the
|
|
|
|
entire flash looking for bad block markers.
|
|
|
|
|
|
|
|
config MACH_MX31MOBOARD
|
|
|
|
bool "Support mx31moboard platforms (EPFL Mobots group)"
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
2012-01-21 00:58:23 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
2012-05-15 18:53:52 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2011-05-29 02:05:01 +07:00
|
|
|
select LEDS_GPIO_REGISTER
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for mx31moboard platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_QONG
|
|
|
|
bool "Support Dave/DENX QongEVB-LITE platform"
|
2011-09-19 20:59:46 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
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 23:12:25 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for Dave/DENX QongEVB-LITE platform. This includes
|
|
|
|
specific configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_ARMADILLO5X0
|
|
|
|
bool "Support Atmark Armadillo-500 Development Base Board"
|
|
|
|
select IMX_HAVE_PLATFORM_GPIO_KEYS
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_MMC
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for Atmark Armadillo-500 platform. This includes
|
|
|
|
specific configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_KZM_ARM11_01
|
|
|
|
bool "Support KZM-ARM11-01(Kyoto Microcomputer)"
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for KZM-ARM11-01. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_BUG
|
|
|
|
bool "Support Buglabs BUGBase platform"
|
|
|
|
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-06 23:12:25 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select SOC_IMX31
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for BUGBase 1.3 platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
2012-07-10 02:39:12 +07:00
|
|
|
config MACH_IMX31_DT
|
|
|
|
bool "Support i.MX31 platforms from device tree"
|
|
|
|
select SOC_IMX31
|
|
|
|
help
|
|
|
|
Include support for Freescale i.MX31 based platforms
|
|
|
|
using the device tree for discovery.
|
|
|
|
|
2011-03-17 15:40:29 +07:00
|
|
|
comment "MX35 platforms:"
|
|
|
|
|
2013-12-18 21:10:25 +07:00
|
|
|
config MACH_IMX35_DT
|
|
|
|
bool "Support i.MX35 platforms from device tree"
|
|
|
|
select SOC_IMX35
|
|
|
|
help
|
|
|
|
Include support for Freescale i.MX35 based platforms
|
|
|
|
using the device tree for discovery.
|
|
|
|
|
2011-03-17 15:40:29 +07:00
|
|
|
config MACH_PCM043
|
|
|
|
bool "Support Phytec pcm043 (i.MX35) platforms"
|
|
|
|
select IMX_HAVE_PLATFORM_FLEXCAN
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
|
|
|
select IMX_HAVE_PLATFORM_SDHCI_ESDHC_IMX
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX35
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for Phytec pcm043 platform. This includes
|
|
|
|
specific configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
config MACH_MX35_3DS
|
|
|
|
bool "Support MX35PDK platform"
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
2012-04-24 22:48:18 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_FB
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2012-04-24 22:48:18 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
2012-07-04 21:36:28 +07:00
|
|
|
select IMX_HAVE_PLATFORM_MXC_RTC
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SDHCI_ESDHC_IMX
|
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 23:12:25 +07:00
|
|
|
select MXC_DEBUG_BOARD
|
|
|
|
select SOC_IMX35
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for MX35PDK platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
2011-12-13 13:31:43 +07:00
|
|
|
config MACH_EUKREA_CPUIMX35SD
|
2011-03-17 15:40:29 +07:00
|
|
|
bool "Support Eukrea CPUIMX35 Platform"
|
|
|
|
select IMX_HAVE_PLATFORM_FLEXCAN
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_I2C
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
|
|
|
select IMX_HAVE_PLATFORM_SDHCI_ESDHC_IMX
|
2013-06-06 19:41:57 +07:00
|
|
|
select USB_ULPI_VIEWPORT if USB_ULPI
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX35
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for Eukrea CPUIMX35 platform. This includes
|
|
|
|
specific configurations for the board and its peripherals.
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Baseboard"
|
2011-12-13 13:31:43 +07:00
|
|
|
depends on MACH_EUKREA_CPUIMX35SD
|
2011-03-17 15:40:29 +07:00
|
|
|
default MACH_EUKREA_MBIMXSD35_BASEBOARD
|
|
|
|
|
|
|
|
config MACH_EUKREA_MBIMXSD35_BASEBOARD
|
|
|
|
bool "Eukrea MBIMXSD development board"
|
|
|
|
select IMX_HAVE_PLATFORM_GPIO_KEYS
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_SSI
|
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
2012-05-08 14:20:19 +07:00
|
|
|
select IMX_HAVE_PLATFORM_SPI_IMX
|
2011-05-29 02:05:01 +07:00
|
|
|
select LEDS_GPIO_REGISTER
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
This adds board specific devices that can be found on Eukrea's
|
|
|
|
MBIMXSD evaluation board.
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
config MACH_VPR200
|
|
|
|
bool "Support VPR200 platform"
|
|
|
|
select IMX_HAVE_PLATFORM_FSL_USB2_UDC
|
|
|
|
select IMX_HAVE_PLATFORM_GPIO_KEYS
|
|
|
|
select IMX_HAVE_PLATFORM_IMX2_WDT
|
|
|
|
select IMX_HAVE_PLATFORM_IMX_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-06 23:12:25 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IMX_UART
|
2011-03-17 15:40:29 +07:00
|
|
|
select IMX_HAVE_PLATFORM_IPU_CORE
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_EHCI
|
|
|
|
select IMX_HAVE_PLATFORM_MXC_NAND
|
|
|
|
select IMX_HAVE_PLATFORM_SDHCI_ESDHC_IMX
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX35
|
2011-03-17 15:40:29 +07:00
|
|
|
help
|
|
|
|
Include support for VPR200 platform. This includes specific
|
|
|
|
configurations for the board and its peripherals.
|
|
|
|
|
2012-09-17 08:38:39 +07:00
|
|
|
endif
|
|
|
|
|
|
|
|
if ARCH_MULTI_V7
|
|
|
|
|
2012-08-12 22:21:39 +07:00
|
|
|
comment "Device tree only"
|
2011-11-07 18:36:48 +07:00
|
|
|
|
2014-05-19 12:37:50 +07:00
|
|
|
config SOC_IMX5
|
|
|
|
bool
|
|
|
|
select ARCH_HAS_OPP
|
|
|
|
select HAVE_IMX_SRC
|
|
|
|
select MXC_TZIC
|
|
|
|
|
2013-10-29 12:15:54 +07:00
|
|
|
config SOC_IMX50
|
|
|
|
bool "i.MX50 support"
|
2013-11-16 21:25:02 +07:00
|
|
|
select PINCTRL_IMX50
|
2013-10-29 12:15:54 +07:00
|
|
|
select SOC_IMX5
|
|
|
|
|
|
|
|
help
|
|
|
|
This enables support for Freescale i.MX50 processor.
|
|
|
|
|
2014-05-19 12:47:43 +07:00
|
|
|
config SOC_IMX51
|
2014-05-10 22:47:36 +07:00
|
|
|
bool "i.MX51 support"
|
2014-05-19 12:47:43 +07:00
|
|
|
select PINCTRL_IMX51
|
|
|
|
select SOC_IMX5
|
2014-05-10 22:47:36 +07:00
|
|
|
help
|
|
|
|
This enables support for Freescale i.MX51 processor
|
|
|
|
|
2012-08-12 22:21:39 +07:00
|
|
|
config SOC_IMX53
|
|
|
|
bool "i.MX53 support"
|
|
|
|
select PINCTRL_IMX53
|
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 23:12:25 +07:00
|
|
|
select SOC_IMX5
|
2011-11-07 18:36:48 +07:00
|
|
|
|
|
|
|
help
|
2012-08-12 22:21:39 +07:00
|
|
|
This enables support for Freescale i.MX53 processor.
|
2011-10-02 14:09:11 +07:00
|
|
|
|
2014-02-27 14:22:49 +07:00
|
|
|
config SOC_IMX6
|
|
|
|
bool
|
2012-10-23 18:44:34 +07:00
|
|
|
select ARM_ERRATA_754322
|
|
|
|
select ARM_ERRATA_775420
|
2011-10-02 14:09:11 +07:00
|
|
|
select ARM_GIC
|
2013-03-21 06:39:42 +07:00
|
|
|
select HAVE_IMX_ANATOP
|
2011-09-06 13:39:44 +07:00
|
|
|
select HAVE_IMX_GPC
|
|
|
|
select HAVE_IMX_MMDC
|
2013-01-11 21:08:27 +07:00
|
|
|
select HAVE_IMX_SRC
|
2012-09-05 09:57:15 +07:00
|
|
|
select MFD_SYSCON
|
2014-06-19 16:19:10 +07:00
|
|
|
select PL310_ERRATA_769419 if CACHE_L2X0
|
2011-10-02 14:09:11 +07:00
|
|
|
|
2014-02-27 14:22:49 +07:00
|
|
|
config SOC_IMX6Q
|
|
|
|
bool "i.MX6 Quad/DualLite support"
|
|
|
|
select ARM_ERRATA_764369 if SMP
|
|
|
|
select HAVE_ARM_SCU if SMP
|
|
|
|
select HAVE_ARM_TWD if SMP
|
|
|
|
select PCI_DOMAINS if PCI
|
|
|
|
select PINCTRL_IMX6Q
|
|
|
|
select SOC_IMX6
|
|
|
|
|
2011-10-02 14:09:11 +07:00
|
|
|
help
|
|
|
|
This enables support for Freescale i.MX6 Quad processor.
|
|
|
|
|
2013-05-03 10:24:47 +07:00
|
|
|
config SOC_IMX6SL
|
|
|
|
bool "i.MX6 SoloLite support"
|
|
|
|
select PINCTRL_IMX6SL
|
2014-02-27 14:22:49 +07:00
|
|
|
select SOC_IMX6
|
2013-05-03 10:24:47 +07:00
|
|
|
|
|
|
|
help
|
|
|
|
This enables support for Freescale i.MX6 SoloLite processor.
|
|
|
|
|
2014-05-13 20:46:16 +07:00
|
|
|
config SOC_IMX6SX
|
|
|
|
bool "i.MX6 SoloX support"
|
|
|
|
select PINCTRL_IMX6SX
|
|
|
|
select SOC_IMX6
|
|
|
|
|
|
|
|
help
|
|
|
|
This enables support for Freescale i.MX6 SoloX processor.
|
|
|
|
|
2013-05-28 16:12:21 +07:00
|
|
|
config SOC_VF610
|
|
|
|
bool "Vybrid Family VF610 support"
|
|
|
|
select ARM_GIC
|
|
|
|
select PINCTRL_VF610
|
|
|
|
select VF_PIT_TIMER
|
2014-06-19 16:19:10 +07:00
|
|
|
select PL310_ERRATA_769419 if CACHE_L2X0
|
2013-05-28 16:12:21 +07:00
|
|
|
|
|
|
|
help
|
|
|
|
This enable support for Freescale Vybrid VF610 processor.
|
|
|
|
|
2011-03-17 15:40:29 +07:00
|
|
|
endif
|
2012-09-13 14:51:15 +07:00
|
|
|
|
|
|
|
source "arch/arm/mach-imx/devices/Kconfig"
|
2012-09-13 18:48:07 +07:00
|
|
|
|
2014-06-10 21:06:10 +07:00
|
|
|
endif
|