2005-04-17 05:20:36 +07:00
|
|
|
if ARCH_PXA
|
|
|
|
|
|
2007-09-12 09:13:17 +07:00
|
|
|
menu "Intel PXA2xx/PXA3xx Implementations"
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
comment "Intel/Marvell Dev Platforms (sorted by hardware release time)"
|
2009-05-17 01:20:39 +07:00
|
|
|
|
2014-09-28 19:13:21 +07:00
|
|
|
config MACH_PXA27X_DT
|
|
|
|
|
bool "Support PXA27x platforms from device tree"
|
|
|
|
|
select POWER_SUPPLY
|
|
|
|
|
select PXA27x
|
|
|
|
|
select USE_OF
|
|
|
|
|
help
|
|
|
|
|
Include support for Marvell PXA27x based platforms using
|
|
|
|
|
the device tree. Needn't select any other machine while
|
|
|
|
|
MACH_PXA27X_DT is enabled.
|
|
|
|
|
|
2012-07-25 22:54:41 +07:00
|
|
|
config MACH_PXA3XX_DT
|
|
|
|
|
bool "Support PXA3xx platforms from device tree"
|
|
|
|
|
select CPU_PXA300
|
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 POWER_SUPPLY
|
|
|
|
|
select PXA3xx
|
2012-07-25 22:54:41 +07:00
|
|
|
select USE_OF
|
|
|
|
|
help
|
|
|
|
|
Include support for Marvell PXA3xx based platforms using
|
|
|
|
|
the device tree. Needn't select any other machine while
|
|
|
|
|
MACH_PXA3XX_DT is enabled.
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config ARCH_LUBBOCK
|
2009-10-12 08:32:07 +07:00
|
|
|
bool "Intel DBPXA250 Development Platform (aka Lubbock)"
|
2005-04-17 05:20:36 +07:00
|
|
|
select PXA25x
|
|
|
|
|
select SA1111
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_MAINSTONE
|
|
|
|
|
bool "Intel HCDDBBVA0 Development Platform (aka Mainstone)"
|
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 PXA27x
|
2006-03-29 03:08:13 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_ZYLONITE
|
2009-11-09 13:25:52 +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 PXA3xx
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2009-11-09 13:25:52 +07:00
|
|
|
config MACH_ZYLONITE300
|
|
|
|
|
bool "PXA3xx Development Platform (aka Zylonite) PXA300/310"
|
|
|
|
|
select CPU_PXA300
|
|
|
|
|
select CPU_PXA310
|
|
|
|
|
select MACH_ZYLONITE
|
|
|
|
|
|
|
|
|
|
config MACH_ZYLONITE320
|
|
|
|
|
bool "PXA3xx Development Platform (aka Zylonite) PXA320"
|
|
|
|
|
select CPU_PXA320
|
|
|
|
|
select MACH_ZYLONITE
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_LITTLETON
|
|
|
|
|
bool "PXA3xx Form Factor Platform (aka Littleton)"
|
2009-12-28 00:14:25 +07:00
|
|
|
select CPU_PXA300
|
|
|
|
|
select CPU_PXA310
|
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 PXA3xx
|
2009-10-12 08:32:07 +07:00
|
|
|
|
|
|
|
|
config MACH_TAVOREVB
|
|
|
|
|
bool "PXA930 Evaluation Board (aka TavorEVB)"
|
|
|
|
|
select CPU_PXA930
|
2013-04-10 08:25:44 +07:00
|
|
|
select CPU_PXA935
|
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 PXA3xx
|
2014-03-13 22:45:00 +07:00
|
|
|
select FB
|
|
|
|
|
select FB_PXA
|
2009-10-12 08:32:07 +07:00
|
|
|
|
|
|
|
|
config MACH_SAAR
|
|
|
|
|
bool "PXA930 Handheld Platform (aka SAAR)"
|
|
|
|
|
select CPU_PXA930
|
2013-04-10 08:25:44 +07:00
|
|
|
select CPU_PXA935
|
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 PXA3xx
|
2014-03-13 22:45:00 +07:00
|
|
|
select FB
|
|
|
|
|
select FB_PXA
|
2009-10-12 08:32:07 +07:00
|
|
|
|
|
|
|
|
comment "Third Party Dev Platforms (sorted by vendor name)"
|
|
|
|
|
|
|
|
|
|
config ARCH_PXA_IDP
|
|
|
|
|
bool "Accelent Xscale IDP"
|
2008-10-03 02:15:35 +07:00
|
|
|
select PXA25x
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config ARCH_VIPER
|
|
|
|
|
bool "Arcom/Eurotech VIPER SBC"
|
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 ARCOM_PCMCIA
|
2014-03-13 22:47:35 +07:00
|
|
|
select I2C_GPIO if I2C=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 ISA
|
|
|
|
|
select PXA25x
|
2009-10-12 08:32:07 +07:00
|
|
|
|
2009-11-14 19:47:03 +07:00
|
|
|
config MACH_ARCOM_ZEUS
|
|
|
|
|
bool "Arcom/Eurotech ZEUS SBC"
|
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 ARCOM_PCMCIA
|
2009-11-14 19:47:03 +07:00
|
|
|
select ISA
|
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 PXA27x
|
2009-11-14 19:47:03 +07:00
|
|
|
|
2009-07-04 20:43:56 +07:00
|
|
|
config MACH_BALLOON3
|
|
|
|
|
bool "Balloon 3 board"
|
|
|
|
|
select IWMMXT
|
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 PXA27x
|
2009-07-04 20:43:56 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_CSB726
|
|
|
|
|
bool "Enable Cogent CSB726 System On a Module"
|
|
|
|
|
select IWMMXT
|
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 PXA27x
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
2009-10-12 08:32:07 +07:00
|
|
|
Say Y here if you intend to run this kernel on a Cogent
|
|
|
|
|
CSB726 System On Module.
|
2009-03-28 22:18:51 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config CSB726_CSB701
|
|
|
|
|
bool "Enable support for CSB701 baseboard"
|
|
|
|
|
depends on MACH_CSB726
|
2008-10-21 10:36:19 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_ARMCORE
|
|
|
|
|
bool "CompuLab CM-X255/CM-X270 modules"
|
2012-03-21 02:33:01 +07:00
|
|
|
select ARCH_HAS_DMA_SET_COHERENT_MASK if PCI
|
2009-10-12 08:32:07 +07:00
|
|
|
select IWMMXT
|
2010-12-02 18:32:15 +07:00
|
|
|
select MIGHT_HAVE_PCI
|
2012-04-05 05:48:04 +07:00
|
|
|
select NEED_MACH_IO_H if PCI
|
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 PXA25x
|
|
|
|
|
select PXA27x
|
2008-07-01 21:45:10 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_EM_X270
|
|
|
|
|
bool "CompuLab EM-x270 platform"
|
2008-07-01 21:45:10 +07:00
|
|
|
select PXA27x
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_EXEDA
|
|
|
|
|
bool "CompuLab eXeda platform"
|
2008-07-01 21:45:10 +07:00
|
|
|
select PXA27x
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_CM_X300
|
|
|
|
|
bool "CompuLab CM-X300 modules"
|
|
|
|
|
select CPU_PXA300
|
2009-11-10 19:18:41 +07:00
|
|
|
select CPU_PXA310
|
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 PXA3xx
|
2008-07-01 21:45:10 +07:00
|
|
|
|
2010-02-05 23:31:48 +07:00
|
|
|
config MACH_CAPC7117
|
|
|
|
|
bool "Embedian CAPC-7117 evaluation kit based on the MXM-8x10 CoM"
|
|
|
|
|
select CPU_PXA320
|
|
|
|
|
select PXA3xx
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config ARCH_GUMSTIX
|
|
|
|
|
bool "Gumstix XScale 255 boards"
|
2008-08-14 22:20:31 +07:00
|
|
|
select PXA25x
|
2009-10-12 08:32:07 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on
|
|
|
|
|
Basix, Connex, ws-200ax, ws-400ax systems
|
2008-07-01 21:45:10 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
choice
|
|
|
|
|
prompt "Gumstix Carrier/Expansion Board"
|
|
|
|
|
depends on ARCH_GUMSTIX
|
2007-11-19 19:16:56 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config GUMSTIX_AM200EPD
|
|
|
|
|
bool "Enable AM200EPD board support"
|
2007-11-19 19:16:56 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config GUMSTIX_AM300EPD
|
|
|
|
|
bool "Enable AM300EPD board support"
|
2008-06-26 04:39:31 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
endchoice
|
2007-11-19 19:16:56 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_INTELMOTE2
|
|
|
|
|
bool "Intel Mote 2 Platform"
|
|
|
|
|
select IWMMXT
|
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 PXA27x
|
2007-11-19 19:16:56 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_STARGATE2
|
|
|
|
|
bool "Intel Stargate 2 Platform"
|
|
|
|
|
select IWMMXT
|
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 PXA27x
|
2007-11-19 19:16:56 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_XCEP
|
|
|
|
|
bool "Iskratel Electronics XCEP"
|
|
|
|
|
select MTD
|
|
|
|
|
select MTD_CFI
|
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 MTD_CFI_INTELEXT
|
|
|
|
|
select MTD_PHYSMAP
|
|
|
|
|
select PXA25x
|
2007-11-19 19:16:56 +07:00
|
|
|
help
|
2009-10-12 08:32:07 +07:00
|
|
|
PXA255 based Single Board Computer with SMC 91C111 ethernet chip and 64 MB of flash.
|
|
|
|
|
Tuned for usage in Libera instruments for particle accelerators.
|
2007-11-19 19:16:56 +07:00
|
|
|
|
2008-08-19 03:45:03 +07:00
|
|
|
config TRIZEPS_PXA
|
|
|
|
|
bool "PXA based Keith und Koep Trizeps DIMM-Modules"
|
|
|
|
|
|
2006-06-29 22:01:43 +07:00
|
|
|
config MACH_TRIZEPS4
|
|
|
|
|
bool "Keith und Koep Trizeps4 DIMM-Module"
|
2008-08-19 03:45:03 +07:00
|
|
|
depends on TRIZEPS_PXA
|
2006-06-29 22:01:43 +07:00
|
|
|
select PXA27x
|
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 TRIZEPS_PCMCIA
|
2006-06-29 22:01:43 +07:00
|
|
|
|
2008-08-19 03:45:03 +07:00
|
|
|
config MACH_TRIZEPS4WL
|
|
|
|
|
bool "Keith und Koep Trizeps4-WL DIMM-Module"
|
|
|
|
|
depends on TRIZEPS_PXA
|
2014-03-13 22:54:26 +07:00
|
|
|
select MACH_TRIZEPS4
|
2006-06-29 22:01:43 +07:00
|
|
|
select PXA27x
|
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 TRIZEPS_PCMCIA
|
2008-08-19 03:45:03 +07:00
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Select base board for Trizeps module"
|
|
|
|
|
depends on TRIZEPS_PXA
|
2006-06-29 22:01:43 +07:00
|
|
|
|
2008-08-19 03:45:03 +07:00
|
|
|
config MACH_TRIZEPS_CONXS
|
2008-07-02 19:50:09 +07:00
|
|
|
bool "ConXS Eval Board"
|
2008-08-19 03:45:03 +07:00
|
|
|
|
|
|
|
|
config MACH_TRIZEPS_UCONXS
|
|
|
|
|
bool "uConXS Eval Board"
|
|
|
|
|
|
|
|
|
|
config MACH_TRIZEPS_ANY
|
|
|
|
|
bool "another Board"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2009-11-14 19:39:13 +07:00
|
|
|
config ARCOM_PCMCIA
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Generic option for Arcom Viper/Zeus PCMCIA
|
|
|
|
|
|
2008-08-19 03:45:03 +07:00
|
|
|
config TRIZEPS_PCMCIA
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Enable PCMCIA support for Trizeps modules
|
2008-07-02 19:50:09 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_LOGICPD_PXA270
|
|
|
|
|
bool "LogicPD PXA270 Card Engine Development Platform"
|
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 PXA27x
|
2009-02-02 13:57:55 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_PCM027
|
|
|
|
|
bool "Phytec phyCORE-PXA270 CPU module (PCM-027)"
|
|
|
|
|
select IWMMXT
|
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 PXA27x
|
2008-01-23 20:54:50 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_PCM990_BASEBOARD
|
|
|
|
|
bool "PHYTEC PCM-990 development board"
|
|
|
|
|
depends on MACH_PCM027
|
2009-03-13 22:37:09 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
choice
|
|
|
|
|
prompt "display on pcm990"
|
|
|
|
|
depends on MACH_PCM990_BASEBOARD
|
2009-03-23 08:04:18 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config PCM990_DISPLAY_SHARP
|
|
|
|
|
bool "sharp lq084v1dg21 stn display"
|
2007-09-12 09:13:17 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config PCM990_DISPLAY_NEC
|
|
|
|
|
bool "nec nl6448bc20_18d tft display"
|
2007-12-13 09:41:43 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config PCM990_DISPLAY_NONE
|
|
|
|
|
bool "no display"
|
2008-07-11 11:59:38 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
endchoice
|
2008-07-11 13:02:20 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_COLIBRI
|
|
|
|
|
bool "Toradex Colibri PXA270"
|
2007-09-23 21:59:26 +07:00
|
|
|
select PXA27x
|
|
|
|
|
|
2010-05-22 05:29:39 +07:00
|
|
|
config MACH_COLIBRI_PXA270_INCOME
|
|
|
|
|
bool "Income s.r.o. PXA270 SBC"
|
|
|
|
|
depends on MACH_COLIBRI
|
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 PXA27x
|
2010-05-22 05:29:39 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_COLIBRI300
|
|
|
|
|
bool "Toradex Colibri PXA300/310"
|
2008-08-26 20:03:44 +07:00
|
|
|
select CPU_PXA300
|
2009-11-09 13:40:47 +07:00
|
|
|
select CPU_PXA310
|
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 PXA3xx
|
2007-09-23 21:59:26 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_COLIBRI320
|
|
|
|
|
bool "Toradex Colibri PXA320"
|
|
|
|
|
select CPU_PXA320
|
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 PXA3xx
|
2009-10-12 08:32:07 +07:00
|
|
|
|
2010-08-12 06:45:05 +07:00
|
|
|
config MACH_COLIBRI_EVALBOARD
|
2010-08-12 06:18:38 +07:00
|
|
|
bool "Toradex Colibri Evaluation Carrier Board support"
|
|
|
|
|
depends on MACH_COLIBRI || MACH_COLIBRI300 || MACH_COLIBRI320
|
|
|
|
|
|
2010-03-09 10:04:12 +07:00
|
|
|
config MACH_VPAC270
|
|
|
|
|
bool "Voipac PXA270"
|
2010-04-27 02:46:07 +07:00
|
|
|
select HAVE_PATA_PLATFORM
|
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 PXA27x
|
2010-03-09 10:04:12 +07:00
|
|
|
help
|
|
|
|
|
PXA270 based Single Board Computer.
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
comment "End-user Products (sorted by vendor name)"
|
|
|
|
|
|
[ARM] pxa: add basic support for HP iPAQ hx4700 PDAs
This includes
- IrDA (pxafixp_ir),
- Buttons (gpio-keys),
- ASIC3 IRQ/GPIOs (asic3),
- EGPIOs (htc-egpio),
- ATI Imageon w3220 framebuffer (w100fb),
- Backlight (pwm-backlight),
- StrataFlash (physmap),
- Battery monitor (ds1wm,w1_ds2760,ds2760_battery)
- USB gadget support (pxa27x_udc,gpio_vbus).
- bq24022 battery charger (pda_power,bq24022)
- TSC2046 touchscreen (ads7846)
Signed-off-by: Philipp Zabel <philipp.zabel@gmail.com>
Signed-off-by: Eric Miao <eric.miao@marvell.com>
2009-05-28 12:05:18 +07:00
|
|
|
config MACH_H4700
|
|
|
|
|
bool "HP iPAQ hx4700"
|
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 IWMMXT
|
|
|
|
|
select PXA27x
|
[ARM] pxa: add basic support for HP iPAQ hx4700 PDAs
This includes
- IrDA (pxafixp_ir),
- Buttons (gpio-keys),
- ASIC3 IRQ/GPIOs (asic3),
- EGPIOs (htc-egpio),
- ATI Imageon w3220 framebuffer (w100fb),
- Backlight (pwm-backlight),
- StrataFlash (physmap),
- Battery monitor (ds1wm,w1_ds2760,ds2760_battery)
- USB gadget support (pxa27x_udc,gpio_vbus).
- bq24022 battery charger (pda_power,bq24022)
- TSC2046 touchscreen (ads7846)
Signed-off-by: Philipp Zabel <philipp.zabel@gmail.com>
Signed-off-by: Eric Miao <eric.miao@marvell.com>
2009-05-28 12:05:18 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_H5000
|
|
|
|
|
bool "HP iPAQ h5000"
|
|
|
|
|
select PXA25x
|
|
|
|
|
|
|
|
|
|
config MACH_HIMALAYA
|
|
|
|
|
bool "HTC Himalaya Support"
|
|
|
|
|
select CPU_PXA26x
|
|
|
|
|
|
2007-11-22 23:59:11 +07:00
|
|
|
config MACH_MAGICIAN
|
|
|
|
|
bool "Enable HTC Magician Support"
|
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 IWMMXT
|
|
|
|
|
select PXA27x
|
2007-11-22 23:59:11 +07:00
|
|
|
|
2008-08-17 15:34:30 +07:00
|
|
|
config MACH_MIOA701
|
|
|
|
|
bool "Mitac Mio A701 Support"
|
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 IWMMXT
|
|
|
|
|
select PXA27x
|
2008-08-17 15:34:30 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a
|
|
|
|
|
MIO A701. Currently there is only basic support
|
|
|
|
|
for this PDA.
|
2007-11-22 23:59:11 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config PXA_EZX
|
|
|
|
|
bool "Motorola EZX Platform"
|
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 IWMMXT
|
|
|
|
|
select PXA27x
|
2008-01-08 14:44:23 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_EZX_A780
|
|
|
|
|
bool "Motorola EZX A780"
|
|
|
|
|
default y
|
|
|
|
|
depends on PXA_EZX
|
|
|
|
|
|
|
|
|
|
config MACH_EZX_E680
|
|
|
|
|
bool "Motorola EZX E680"
|
|
|
|
|
default y
|
|
|
|
|
depends on PXA_EZX
|
|
|
|
|
|
|
|
|
|
config MACH_EZX_A1200
|
|
|
|
|
bool "Motorola EZX A1200"
|
|
|
|
|
default y
|
|
|
|
|
depends on PXA_EZX
|
|
|
|
|
|
|
|
|
|
config MACH_EZX_A910
|
|
|
|
|
bool "Motorola EZX A910"
|
|
|
|
|
default y
|
|
|
|
|
depends on PXA_EZX
|
|
|
|
|
|
|
|
|
|
config MACH_EZX_E6
|
|
|
|
|
bool "Motorola EZX E6"
|
|
|
|
|
default y
|
|
|
|
|
depends on PXA_EZX
|
|
|
|
|
|
|
|
|
|
config MACH_EZX_E2
|
|
|
|
|
bool "Motorola EZX E2"
|
|
|
|
|
default y
|
|
|
|
|
depends on PXA_EZX
|
|
|
|
|
|
|
|
|
|
config MACH_MP900C
|
|
|
|
|
bool "Nec Mobilepro 900/c"
|
|
|
|
|
select PXA25x
|
|
|
|
|
|
[ARM] 5153/1: Add support for PalmTX handheld computer
PalmTX is PXA27x based device with wifi, bluetooth,
touchscreen, sdio slot, irda, keypad, nand flash,
pxa framebuffer, serial and usb gadget interface.
Supported by this patch is pxafb, touchscreen, irda,
keypad and sdio slot.
Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2008-07-07 23:25:46 +07:00
|
|
|
config ARCH_PXA_PALM
|
|
|
|
|
bool "PXA based Palm PDAs"
|
|
|
|
|
|
2010-07-13 19:08:57 +07:00
|
|
|
config MACH_PALM27X
|
|
|
|
|
bool
|
|
|
|
|
|
2009-03-24 06:29:29 +07:00
|
|
|
config MACH_PALMTE2
|
|
|
|
|
bool "Palm Tungsten|E2"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select PXA25x
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Palm Tungsten|E2
|
|
|
|
|
handheld computer.
|
|
|
|
|
|
2009-07-16 18:26:48 +07:00
|
|
|
config MACH_PALMTC
|
|
|
|
|
bool "Palm Tungsten|C"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select PXA25x
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Palm Tungsten|C
|
|
|
|
|
handheld computer.
|
|
|
|
|
|
2008-11-20 06:58:38 +07:00
|
|
|
config MACH_PALMT5
|
|
|
|
|
bool "Palm Tungsten|T5"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select IWMMXT
|
2010-07-13 13:16:45 +07:00
|
|
|
select MACH_PALM27X
|
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 PXA27x
|
2008-11-20 06:58:38 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Palm Tungsten|T5
|
|
|
|
|
handheld computer.
|
|
|
|
|
|
[ARM] 5153/1: Add support for PalmTX handheld computer
PalmTX is PXA27x based device with wifi, bluetooth,
touchscreen, sdio slot, irda, keypad, nand flash,
pxa framebuffer, serial and usb gadget interface.
Supported by this patch is pxafb, touchscreen, irda,
keypad and sdio slot.
Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2008-07-07 23:25:46 +07:00
|
|
|
config MACH_PALMTX
|
|
|
|
|
bool "Palm T|X"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select IWMMXT
|
2010-07-13 13:16:45 +07:00
|
|
|
select MACH_PALM27X
|
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 PXA27x
|
[ARM] 5153/1: Add support for PalmTX handheld computer
PalmTX is PXA27x based device with wifi, bluetooth,
touchscreen, sdio slot, irda, keypad, nand flash,
pxa framebuffer, serial and usb gadget interface.
Supported by this patch is pxafb, touchscreen, irda,
keypad and sdio slot.
Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2008-07-07 23:25:46 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Palm T|X
|
|
|
|
|
handheld computer.
|
|
|
|
|
|
2008-08-29 21:47:52 +07:00
|
|
|
config MACH_PALMZ72
|
|
|
|
|
bool "Palm Zire 72"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select IWMMXT
|
2010-07-13 13:16:45 +07:00
|
|
|
select MACH_PALM27X
|
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 PXA27x
|
2008-08-29 21:47:52 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on Palm Zire 72
|
|
|
|
|
handheld computer.
|
2008-11-21 04:50:46 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_PALMLD
|
|
|
|
|
bool "Palm LifeDrive"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select IWMMXT
|
2010-07-13 13:16:45 +07:00
|
|
|
select MACH_PALM27X
|
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 PXA27x
|
2009-10-12 08:32:07 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Palm LifeDrive
|
|
|
|
|
handheld computer.
|
|
|
|
|
|
2009-09-11 18:57:01 +07:00
|
|
|
config PALM_TREO
|
|
|
|
|
bool
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
|
2009-09-11 18:57:02 +07:00
|
|
|
config MACH_CENTRO
|
|
|
|
|
bool "Palm Centro 685 (GSM)"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select IWMMXT
|
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_PALM27X
|
2009-09-11 18:57:02 +07:00
|
|
|
select PALM_TREO
|
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 PXA27x
|
2009-09-11 18:57:02 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on Palm Centro 685 (GSM)
|
|
|
|
|
smartphone.
|
|
|
|
|
|
2009-05-18 20:24:14 +07:00
|
|
|
config MACH_TREO680
|
|
|
|
|
bool "Palm Treo 680"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_PALM
|
|
|
|
|
select IWMMXT
|
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_PALM27X
|
2009-09-11 18:57:01 +07:00
|
|
|
select PALM_TREO
|
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 PXA27x
|
2009-05-18 20:24:14 +07:00
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on Palm Treo 680
|
|
|
|
|
smartphone.
|
|
|
|
|
|
2009-11-27 19:47:09 +07:00
|
|
|
config MACH_RAUMFELD_RC
|
|
|
|
|
bool "Raumfeld Controller"
|
|
|
|
|
select CPU_PXA300
|
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 POWER_SUPPLY
|
|
|
|
|
select PXA3xx
|
2009-11-27 19:47:09 +07:00
|
|
|
|
|
|
|
|
config MACH_RAUMFELD_CONNECTOR
|
|
|
|
|
bool "Raumfeld Connector"
|
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_PXA300
|
2011-10-02 03:03:53 +07:00
|
|
|
select POWER_SUPPLY
|
2009-11-27 19:47:09 +07:00
|
|
|
select PXA3xx
|
|
|
|
|
|
|
|
|
|
config MACH_RAUMFELD_SPEAKER
|
|
|
|
|
bool "Raumfeld Speaker"
|
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_PXA300
|
2011-10-02 03:03:53 +07:00
|
|
|
select POWER_SUPPLY
|
2009-11-27 19:47:09 +07:00
|
|
|
select PXA3xx
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config PXA_SHARPSL
|
|
|
|
|
bool "SHARP Zaurus SL-5600, SL-C7xx and SL-Cxx00 Models"
|
|
|
|
|
select SHARP_PARAM
|
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 SHARP_SCOOP
|
2008-11-21 04:50:46 +07:00
|
|
|
help
|
2009-10-12 08:32:07 +07:00
|
|
|
Say Y here if you intend to run this kernel on a
|
|
|
|
|
Sharp Zaurus SL-5600 (Poodle), SL-C700 (Corgi),
|
|
|
|
|
SL-C750 (Shepherd), SL-C760 (Husky), SL-C1000 (Akita),
|
|
|
|
|
SL-C3000 (Spitz), SL-C3100 (Borzoi) or SL-C6000x (Tosa)
|
2008-11-21 04:50:46 +07:00
|
|
|
handheld computer.
|
2008-08-29 21:47:52 +07:00
|
|
|
|
2010-06-23 08:27:32 +07:00
|
|
|
config PXA_SHARPSL_DETECT_MACH_ID
|
|
|
|
|
bool "Detect machine ID at run-time in the decompressor"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want the zImage decompressor to detect
|
|
|
|
|
the Zaurus machine ID at run-time. For latest kexec-based
|
|
|
|
|
boot loader, this is not necessary.
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_POODLE
|
|
|
|
|
bool "Enable Sharp SL-5600 (Poodle) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
select PXA25x
|
|
|
|
|
select SHARP_LOCOMO
|
2005-09-13 15:25:34 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_CORGI
|
|
|
|
|
bool "Enable Sharp SL-C700 (Corgi) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
select PXA25x
|
|
|
|
|
select PXA_SHARP_C7xx
|
2005-09-13 15:25:34 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_SHEPHERD
|
|
|
|
|
bool "Enable Sharp SL-C750 (Shepherd) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
select PXA25x
|
|
|
|
|
select PXA_SHARP_C7xx
|
2005-09-13 15:25:34 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_HUSKY
|
|
|
|
|
bool "Enable Sharp SL-C760 (Husky) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
select PXA25x
|
|
|
|
|
select PXA_SHARP_C7xx
|
2005-09-13 15:25:34 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_AKITA
|
|
|
|
|
bool "Enable Sharp SL-1000 (Akita) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
select I2C
|
|
|
|
|
select I2C_PXA
|
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_SPITZ
|
|
|
|
|
select PXA27x
|
|
|
|
|
select PXA_SHARP_Cxx00
|
2009-02-17 00:40:55 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_SPITZ
|
|
|
|
|
bool "Enable Sharp Zaurus SL-3000 (Spitz) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
select PXA27x
|
|
|
|
|
select PXA_SHARP_Cxx00
|
2009-02-17 00:40:57 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_BORZOI
|
|
|
|
|
bool "Enable Sharp Zaurus SL-3100 (Borzoi) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
2008-07-09 14:08:17 +07:00
|
|
|
select PXA27x
|
2009-10-12 08:32:07 +07:00
|
|
|
select PXA_SHARP_Cxx00
|
|
|
|
|
|
|
|
|
|
config MACH_TOSA
|
|
|
|
|
bool "Enable Sharp SL-6000x (Tosa) Support"
|
|
|
|
|
depends on PXA_SHARPSL
|
|
|
|
|
select PXA25x
|
2008-07-09 14:08:17 +07:00
|
|
|
|
2010-06-22 16:15:32 +07:00
|
|
|
config TOSA_BT
|
|
|
|
|
tristate "Control the state of built-in bluetooth chip on Sharp SL-6000"
|
2016-01-29 21:06:32 +07:00
|
|
|
depends on MACH_TOSA && NET
|
2010-06-22 16:15:32 +07:00
|
|
|
select RFKILL
|
|
|
|
|
help
|
|
|
|
|
This is a simple driver that is able to control
|
|
|
|
|
the state of built in bluetooth chip on tosa.
|
|
|
|
|
|
|
|
|
|
config TOSA_USE_EXT_KEYCODES
|
|
|
|
|
bool "Tosa keyboard: use extended keycodes"
|
|
|
|
|
depends on MACH_TOSA
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Say Y here to enable the tosa keyboard driver to generate extended
|
|
|
|
|
(>= 127) keycodes. Be aware, that they can't be correctly interpreted
|
|
|
|
|
by either console keyboard driver or by Kdrive keybd driver.
|
|
|
|
|
|
|
|
|
|
Say Y only if you know, what you are doing!
|
|
|
|
|
|
2010-02-05 23:31:48 +07:00
|
|
|
config MACH_ICONTROL
|
|
|
|
|
bool "TMT iControl/SafeTCam based on the MXM-8x10 CoM"
|
|
|
|
|
select CPU_PXA320
|
|
|
|
|
select PXA3xx
|
|
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config ARCH_PXA_ESERIES
|
|
|
|
|
bool "PXA based Toshiba e-series PDAs"
|
2010-12-15 06:20:16 +07:00
|
|
|
select FB_W100
|
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 PXA25x
|
2008-07-09 14:08:17 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_E330
|
|
|
|
|
bool "Toshiba e330"
|
2008-07-09 14:08:17 +07:00
|
|
|
default y
|
2009-10-12 08:32:07 +07:00
|
|
|
depends on ARCH_PXA_ESERIES
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Toshiba
|
|
|
|
|
e330 family PDA.
|
2008-07-09 14:08:17 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_E350
|
|
|
|
|
bool "Toshiba e350"
|
2008-07-09 14:08:17 +07:00
|
|
|
default y
|
2009-10-12 08:32:07 +07:00
|
|
|
depends on ARCH_PXA_ESERIES
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Toshiba
|
|
|
|
|
e350 family PDA.
|
2008-07-09 14:08:17 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_E740
|
|
|
|
|
bool "Toshiba e740"
|
2008-07-09 14:08:17 +07:00
|
|
|
default y
|
2009-10-12 08:32:07 +07:00
|
|
|
depends on ARCH_PXA_ESERIES
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Toshiba
|
|
|
|
|
e740 family PDA.
|
2008-07-09 14:08:17 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_E750
|
|
|
|
|
bool "Toshiba e750"
|
2008-07-09 14:08:17 +07:00
|
|
|
default y
|
2009-10-12 08:32:07 +07:00
|
|
|
depends on ARCH_PXA_ESERIES
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Toshiba
|
|
|
|
|
e750 family PDA.
|
2008-07-09 14:08:17 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_E400
|
|
|
|
|
bool "Toshiba e400"
|
2008-07-09 14:08:17 +07:00
|
|
|
default y
|
2009-10-12 08:32:07 +07:00
|
|
|
depends on ARCH_PXA_ESERIES
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you intend to run this kernel on a Toshiba
|
|
|
|
|
e400 family PDA.
|
2008-07-09 14:08:17 +07:00
|
|
|
|
2009-10-12 08:32:07 +07:00
|
|
|
config MACH_E800
|
|
|
|
|
bool "Toshiba e800"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARCH_PXA_ESERIES
|
2009-09-07 13:08:34 +07:00
|
|
|
help
|
2009-10-12 08:32:07 +07:00
|
|
|
Say Y here if you intend to run this kernel on a Toshiba
|
|
|
|
|
e800 family PDA.
|
2009-09-07 13:08:34 +07:00
|
|
|
|
2010-02-28 18:41:23 +07:00
|
|
|
config MACH_ZIPIT2
|
|
|
|
|
bool "Zipit Z2 Handheld"
|
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 PXA27x
|
2005-04-17 05:20:36 +07:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
config PXA25x
|
|
|
|
|
bool
|
2008-10-26 17:55:14 +07:00
|
|
|
select CPU_XSCALE
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
|
Select code specific to PXA21x/25x/26x variants
|
|
|
|
|
|
|
|
|
|
config PXA27x
|
|
|
|
|
bool
|
2008-10-26 17:55:14 +07:00
|
|
|
select CPU_XSCALE
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
|
Select code specific to PXA27x variants
|
|
|
|
|
|
2008-11-26 17:12:04 +07:00
|
|
|
config CPU_PXA26x
|
|
|
|
|
bool
|
|
|
|
|
select PXA25x
|
|
|
|
|
help
|
|
|
|
|
Select code specific to PXA26x (codename Dalhart)
|
|
|
|
|
|
2007-09-12 09:13:17 +07:00
|
|
|
config PXA3xx
|
|
|
|
|
bool
|
2008-10-26 17:55:14 +07:00
|
|
|
select CPU_XSC3
|
2007-09-12 09:13:17 +07:00
|
|
|
help
|
|
|
|
|
Select code specific to PXA3xx variants
|
|
|
|
|
|
2009-11-09 13:37:59 +07:00
|
|
|
config CPU_PXA300
|
|
|
|
|
bool
|
|
|
|
|
select PXA3xx
|
|
|
|
|
help
|
|
|
|
|
PXA300 (codename Monahans-L)
|
|
|
|
|
|
|
|
|
|
config CPU_PXA310
|
|
|
|
|
bool
|
|
|
|
|
select CPU_PXA300
|
2010-07-27 19:06:58 +07:00
|
|
|
select PXA310_ULPI if USB_ULPI
|
2009-11-09 13:37:59 +07:00
|
|
|
help
|
|
|
|
|
PXA310 (codename Monahans-LV)
|
|
|
|
|
|
|
|
|
|
config CPU_PXA320
|
|
|
|
|
bool
|
|
|
|
|
select PXA3xx
|
|
|
|
|
help
|
|
|
|
|
PXA320 (codename Monahans-P)
|
|
|
|
|
|
|
|
|
|
config CPU_PXA930
|
|
|
|
|
bool
|
|
|
|
|
select PXA3xx
|
|
|
|
|
help
|
|
|
|
|
PXA930 (codename Tavor-P)
|
|
|
|
|
|
|
|
|
|
config CPU_PXA935
|
|
|
|
|
bool
|
|
|
|
|
select CPU_PXA930
|
|
|
|
|
help
|
|
|
|
|
PXA935 (codename Tavor-P65)
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config PXA_SHARP_C7xx
|
|
|
|
|
bool
|
2006-01-06 03:44:55 +07:00
|
|
|
select SHARPSL_PM
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
|
Enable support for all Sharp C7xx models
|
|
|
|
|
|
2005-09-13 15:25:34 +07:00
|
|
|
config PXA_SHARP_Cxx00
|
|
|
|
|
bool
|
2006-01-06 03:44:55 +07:00
|
|
|
select SHARPSL_PM
|
2005-09-13 15:25:34 +07:00
|
|
|
help
|
|
|
|
|
Enable common support for Sharp Cxx00 models
|
|
|
|
|
|
2010-06-22 16:15:32 +07:00
|
|
|
config SHARPSL_PM
|
|
|
|
|
bool
|
|
|
|
|
select APM_EMULATION
|
|
|
|
|
select SHARPSL_PM_MAX1111
|
2010-04-27 13:43:03 +07:00
|
|
|
|
2010-06-22 16:15:32 +07:00
|
|
|
config SHARPSL_PM_MAX1111
|
|
|
|
|
bool
|
|
|
|
|
select HWMON
|
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 SENSORS_MAX1111
|
2011-10-02 03:03:58 +07:00
|
|
|
select SPI
|
|
|
|
|
select SPI_MASTER
|
2010-04-27 13:43:03 +07:00
|
|
|
|
2010-07-27 19:06:58 +07:00
|
|
|
config PXA310_ULPI
|
|
|
|
|
bool
|
|
|
|
|
|
2015-04-25 03:22:19 +07:00
|
|
|
config PXA_SYSTEMS_CPLDS
|
|
|
|
|
tristate "Motherboard cplds"
|
|
|
|
|
default ARCH_LUBBOCK || MACH_MAINSTONE
|
|
|
|
|
help
|
|
|
|
|
This driver supports the Lubbock and Mainstone multifunction chip
|
|
|
|
|
found on the pxa25x development platform system (Lubbock) and pxa27x
|
|
|
|
|
development platform system (Mainstone). This IO board supports the
|
|
|
|
|
interrupts handling, ethernet controller, flash chips, etc ...
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
endif
|