2005-04-17 06:20:36 +08:00
|
|
|
comment "Processor Type"
|
|
|
|
|
|
|
|
|
|
# Select CPU types depending on the architecture selected. This selects
|
|
|
|
|
# which CPUs we support in the kernel image, and the compiler instruction
|
|
|
|
|
# optimiser behaviour.
|
|
|
|
|
|
2006-09-26 16:37:36 +08:00
|
|
|
# ARM7TDMI
|
|
|
|
|
config CPU_ARM7TDMI
|
|
|
|
|
bool "Support ARM7TDMI processor"
|
2006-09-28 00:44:39 +08:00
|
|
|
depends on !MMU
|
2006-09-26 16:37:36 +08:00
|
|
|
select CPU_32v4T
|
|
|
|
|
select CPU_ABRT_LV4T
|
|
|
|
|
select CPU_CACHE_V4
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-09-26 16:37:36 +08:00
|
|
|
help
|
|
|
|
|
A 32-bit RISC microprocessor based on the ARM7 processor core
|
|
|
|
|
which has no memory control unit and cache.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM7TDMI processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# ARM720T
|
|
|
|
|
config CPU_ARM720T
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM720T processor" if (ARCH_MULTI_V4T && ARCH_INTEGRATOR)
|
2006-08-28 19:51:20 +08:00
|
|
|
select CPU_32v4T
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_ABRT_LV4T
|
|
|
|
|
select CPU_CACHE_V4
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WT if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WT if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
A 32-bit RISC processor with 8kByte Cache, Write Buffer and
|
|
|
|
|
MMU built around an ARM7TDMI core.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM720T processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2006-09-26 16:37:50 +08:00
|
|
|
# ARM740T
|
|
|
|
|
config CPU_ARM740T
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM740T processor" if (ARCH_MULTI_V4T && ARCH_INTEGRATOR)
|
2006-09-28 00:44:39 +08:00
|
|
|
depends on !MMU
|
2006-09-26 16:37:50 +08:00
|
|
|
select CPU_32v4T
|
|
|
|
|
select CPU_ABRT_LV4T
|
2013-01-15 20:07:40 +08:00
|
|
|
select CPU_CACHE_V4
|
2006-09-26 16:37:50 +08:00
|
|
|
select CPU_CP15_MPU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-09-26 16:37:50 +08:00
|
|
|
help
|
|
|
|
|
A 32-bit RISC processor with 8KB cache or 4KB variants,
|
|
|
|
|
write buffer and MPU(Protection Unit) built around
|
|
|
|
|
an ARM7TDMI core.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM740T processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2006-09-26 16:38:05 +08:00
|
|
|
# ARM9TDMI
|
|
|
|
|
config CPU_ARM9TDMI
|
|
|
|
|
bool "Support ARM9TDMI processor"
|
2006-09-28 00:44:39 +08:00
|
|
|
depends on !MMU
|
2006-09-26 16:38:05 +08:00
|
|
|
select CPU_32v4T
|
2006-09-28 20:46:16 +08:00
|
|
|
select CPU_ABRT_NOMMU
|
2006-09-26 16:38:05 +08:00
|
|
|
select CPU_CACHE_V4
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-09-26 16:38:05 +08:00
|
|
|
help
|
|
|
|
|
A 32-bit RISC microprocessor based on the ARM9 processor core
|
|
|
|
|
which has no memory control unit and cache.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM9TDMI processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# ARM920T
|
|
|
|
|
config CPU_ARM920T
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM920T processor" if (ARCH_MULTI_V4T && ARCH_INTEGRATOR)
|
2006-08-28 19:51:20 +08:00
|
|
|
select CPU_32v4T
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_ABRT_EV4T
|
|
|
|
|
select CPU_CACHE_V4WT
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The ARM920T is licensed to be produced by numerous vendors,
|
2009-10-21 09:27:01 +08:00
|
|
|
and is used in the Cirrus EP93xx and the Samsung S3C2410.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM920T processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
|
|
|
|
# ARM922T
|
|
|
|
|
config CPU_ARM922T
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM922T processor" if (ARCH_MULTI_V4T && ARCH_INTEGRATOR)
|
2006-08-28 19:51:20 +08:00
|
|
|
select CPU_32v4T
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_ABRT_EV4T
|
|
|
|
|
select CPU_CACHE_V4WT
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The ARM922T is a version of the ARM920T, but with smaller
|
|
|
|
|
instruction and data caches. It is used in Altera's
|
2007-05-12 04:01:28 +08:00
|
|
|
Excalibur XA device family and Micrel's KS8695 Centaur.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM922T processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
|
|
|
|
# ARM925T
|
|
|
|
|
config CPU_ARM925T
|
2005-07-11 02:58:08 +08:00
|
|
|
bool "Support ARM925T processor" if ARCH_OMAP1
|
2006-08-28 19:51:20 +08:00
|
|
|
select CPU_32v4T
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_ABRT_EV4T
|
|
|
|
|
select CPU_CACHE_V4WT
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The ARM925T is a mix between the ARM920T and ARM926T, but with
|
|
|
|
|
different instruction and data caches. It is used in TI's OMAP
|
|
|
|
|
device family.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM925T processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
|
|
|
|
# ARM926T
|
|
|
|
|
config CPU_ARM926T
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM926T processor" if (!ARCH_MULTIPLATFORM || ARCH_MULTI_V5) && (ARCH_INTEGRATOR || MACH_REALVIEW_EB)
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV5TJ
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This is a variant of the ARM920. It has slightly different
|
|
|
|
|
instruction sequences for cache and TLB operations. Curiously,
|
|
|
|
|
there is no documentation on it at the ARM corporate website.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM926T processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2009-03-25 19:10:01 +08:00
|
|
|
# FA526
|
|
|
|
|
config CPU_FA526
|
|
|
|
|
bool
|
|
|
|
|
select CPU_32v4
|
|
|
|
|
select CPU_ABRT_EV4
|
|
|
|
|
select CPU_CACHE_FA
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CACHE_VIVT
|
2009-03-25 19:10:01 +08:00
|
|
|
select CPU_COPY_FA if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2009-03-25 19:10:01 +08:00
|
|
|
select CPU_TLB_FA if MMU
|
|
|
|
|
help
|
|
|
|
|
The FA526 is a version of the ARMv4 compatible processor with
|
|
|
|
|
Branch Target Buffer, Unified TLB and cache line size 16.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the FA526 processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2006-09-26 16:38:18 +08:00
|
|
|
# ARM940T
|
|
|
|
|
config CPU_ARM940T
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM940T processor" if (ARCH_MULTI_V4T && ARCH_INTEGRATOR)
|
2006-09-28 00:44:39 +08:00
|
|
|
depends on !MMU
|
2006-09-26 16:38:18 +08:00
|
|
|
select CPU_32v4T
|
2006-09-28 20:46:16 +08:00
|
|
|
select CPU_ABRT_NOMMU
|
2006-09-26 16:38:18 +08:00
|
|
|
select CPU_CACHE_VIVT
|
|
|
|
|
select CPU_CP15_MPU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-09-26 16:38:18 +08:00
|
|
|
help
|
|
|
|
|
ARM940T is a member of the ARM9TDMI family of general-
|
2006-11-30 12:22:59 +08:00
|
|
|
purpose microprocessors with MPU and separate 4KB
|
2006-09-26 16:38:18 +08:00
|
|
|
instruction and 4KB data cases, each with a 4-word line
|
|
|
|
|
length.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM940T processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2006-09-26 16:38:32 +08:00
|
|
|
# ARM946E-S
|
|
|
|
|
config CPU_ARM946E
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM946E-S processor" if (ARCH_MULTI_V5 && ARCH_INTEGRATOR)
|
2006-09-28 00:44:39 +08:00
|
|
|
depends on !MMU
|
2006-09-26 16:38:32 +08:00
|
|
|
select CPU_32v5
|
2006-09-28 20:46:16 +08:00
|
|
|
select CPU_ABRT_NOMMU
|
2006-09-26 16:38:32 +08:00
|
|
|
select CPU_CACHE_VIVT
|
|
|
|
|
select CPU_CP15_MPU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-09-26 16:38:32 +08:00
|
|
|
help
|
|
|
|
|
ARM946E-S is a member of the ARM9E-S family of high-
|
|
|
|
|
performance, 32-bit system-on-chip processor solutions.
|
|
|
|
|
The TCM and ARMv5TE 32-bit instruction set is supported.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM946E-S processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# ARM1020 - needs validating
|
|
|
|
|
config CPU_ARM1020
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM1020T (rev 0) processor" if (ARCH_MULTI_V5 && ARCH_INTEGRATOR)
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV4T
|
|
|
|
|
select CPU_CACHE_V4WT
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The ARM1020 is the 32K cached version of the ARM10 processor,
|
|
|
|
|
with an addition of a floating-point unit.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM1020 processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
|
|
|
|
# ARM1020E - needs validating
|
|
|
|
|
config CPU_ARM1020E
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM1020E processor" if (ARCH_MULTI_V5 && ARCH_INTEGRATOR)
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
depends on n
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV4T
|
|
|
|
|
select CPU_CACHE_V4WT
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# ARM1022E
|
|
|
|
|
config CPU_ARM1022
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM1022E processor" if (ARCH_MULTI_V5 && ARCH_INTEGRATOR)
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV4T
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU # can probably do better
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The ARM1022E is an implementation of the ARMv5TE architecture
|
|
|
|
|
based upon the ARM10 integer core with a 16KiB L1 Harvard cache,
|
|
|
|
|
embedded trace macrocell, and a floating-point unit.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM1022E processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
|
|
|
|
# ARM1026EJ-S
|
|
|
|
|
config CPU_ARM1026
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM1026EJ-S processor" if (ARCH_MULTI_V5 && ARCH_INTEGRATOR)
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV5T # But need Jazelle, but EV5TJ ignores bit 10
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU # can probably do better
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The ARM1026EJ-S is an implementation of the ARMv5TEJ architecture
|
|
|
|
|
based upon the ARM10 integer core.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the ARM1026EJ-S processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
|
|
|
|
# SA110
|
|
|
|
|
config CPU_SA110
|
2014-02-27 00:39:12 +08:00
|
|
|
bool
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_32v3 if ARCH_RPC
|
|
|
|
|
select CPU_32v4 if !ARCH_RPC
|
|
|
|
|
select CPU_ABRT_EV4
|
|
|
|
|
select CPU_CACHE_V4WB
|
|
|
|
|
select CPU_CACHE_VIVT
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WB if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
The Intel StrongARM(R) SA-110 is a 32-bit microprocessor and
|
|
|
|
|
is available at five speeds ranging from 100 MHz to 233 MHz.
|
|
|
|
|
More information is available at
|
|
|
|
|
<http://developer.intel.com/design/strong/sa110.htm>.
|
|
|
|
|
|
|
|
|
|
Say Y if you want support for the SA-110 processor.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
|
|
|
|
# SA1100
|
|
|
|
|
config CPU_SA1100
|
|
|
|
|
bool
|
|
|
|
|
select CPU_32v4
|
|
|
|
|
select CPU_ABRT_EV4
|
|
|
|
|
select CPU_CACHE_V4WB
|
|
|
|
|
select CPU_CACHE_VIVT
|
[ARM] nommu: defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU
By merging of uClinux/ARM, we need to treat various CPU cores which have
MMU, MPU or even none for memory management. The memory management
coprocessors are controlled by CP15 register set and the ARM core family
can be categorized by 5 groups by the register ;
G-a. CP15 is MMU : 610, 710, 720, 920, 922, 925, 926, 1020, 1020e, 1022,
v6 and the derivations sa1100, sa110, xscale, xsc3.
G-b. CP15 is MPU : 740, 940, 946, 996, 1156.
G-c. CP15 is MPU or MMU : 1026 (selectable by schematic design)
G-d. CP15 is exist, but nothing for memory managemnt : 966, 968.
G-e. no-CP15 : 7tdmi, 9tdmi, 9e, 9ej
This patch defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU. Thus the
family can be defined as :
- CPU_CP15 only : G-d
- CPU_CP15_MMU(implies CPU_CP15) : G-a, G-c(selectable)
- CPU_CP15_MPU(implies CPU_CP15) : G-b, G-c(selectable)
- !CPU_CP15 : G-e
Signed-off-by: Hyok S. Choi <hyok.choi@samsung.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2006-09-26 16:36:37 +08:00
|
|
|
select CPU_CP15_MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WB if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# XScale
|
|
|
|
|
config CPU_XSCALE
|
|
|
|
|
bool
|
|
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV5T
|
|
|
|
|
select CPU_CACHE_VIVT
|
[ARM] nommu: defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU
By merging of uClinux/ARM, we need to treat various CPU cores which have
MMU, MPU or even none for memory management. The memory management
coprocessors are controlled by CP15 register set and the ARM core family
can be categorized by 5 groups by the register ;
G-a. CP15 is MMU : 610, 710, 720, 920, 922, 925, 926, 1020, 1020e, 1022,
v6 and the derivations sa1100, sa110, xscale, xsc3.
G-b. CP15 is MPU : 740, 940, 946, 996, 1156.
G-c. CP15 is MPU or MMU : 1026 (selectable by schematic design)
G-d. CP15 is exist, but nothing for memory managemnt : 966, 968.
G-e. no-CP15 : 7tdmi, 9tdmi, 9e, 9ej
This patch defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU. Thus the
family can be defined as :
- CPU_CP15 only : G-d
- CPU_CP15_MMU(implies CPU_CP15) : G-a, G-c(selectable)
- CPU_CP15_MPU(implies CPU_CP15) : G-b, G-c(selectable)
- !CPU_CP15 : G-e
Signed-off-by: Hyok S. Choi <hyok.choi@samsung.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2006-09-26 16:36:37 +08:00
|
|
|
select CPU_CP15_MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-03-29 04:00:40 +08:00
|
|
|
# XScale Core Version 3
|
|
|
|
|
config CPU_XSC3
|
|
|
|
|
bool
|
|
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV5T
|
|
|
|
|
select CPU_CACHE_VIVT
|
[ARM] nommu: defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU
By merging of uClinux/ARM, we need to treat various CPU cores which have
MMU, MPU or even none for memory management. The memory management
coprocessors are controlled by CP15 register set and the ARM core family
can be categorized by 5 groups by the register ;
G-a. CP15 is MMU : 610, 710, 720, 920, 922, 925, 926, 1020, 1020e, 1022,
v6 and the derivations sa1100, sa110, xscale, xsc3.
G-b. CP15 is MPU : 740, 940, 946, 996, 1156.
G-c. CP15 is MPU or MMU : 1026 (selectable by schematic design)
G-d. CP15 is exist, but nothing for memory managemnt : 966, 968.
G-e. no-CP15 : 7tdmi, 9tdmi, 9e, 9ej
This patch defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU. Thus the
family can be defined as :
- CPU_CP15 only : G-d
- CPU_CP15_MMU(implies CPU_CP15) : G-a, G-c(selectable)
- CPU_CP15_MPU(implies CPU_CP15) : G-b, G-c(selectable)
- !CPU_CP15 : G-e
Signed-off-by: Hyok S. Choi <hyok.choi@samsung.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2006-09-26 16:36:37 +08:00
|
|
|
select CPU_CP15_MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
2006-03-29 04:00:40 +08:00
|
|
|
select IO_36
|
|
|
|
|
|
2009-01-20 14:15:18 +08:00
|
|
|
# Marvell PJ1 (Mohawk)
|
|
|
|
|
config CPU_MOHAWK
|
|
|
|
|
bool
|
|
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV5T
|
|
|
|
|
select CPU_CACHE_VIVT
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_COPY_V4WB if MMU
|
2009-01-20 14:15:18 +08:00
|
|
|
select CPU_CP15_MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_LEGACY
|
2009-01-20 14:15:18 +08:00
|
|
|
select CPU_TLB_V4WBI if MMU
|
|
|
|
|
|
2007-10-24 03:14:41 +08:00
|
|
|
# Feroceon
|
|
|
|
|
config CPU_FEROCEON
|
|
|
|
|
bool
|
|
|
|
|
select CPU_32v5
|
|
|
|
|
select CPU_ABRT_EV5T
|
|
|
|
|
select CPU_CACHE_VIVT
|
2008-04-24 13:31:45 +08:00
|
|
|
select CPU_COPY_FEROCEON if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_PABRT_LEGACY
|
2008-06-23 04:45:04 +08:00
|
|
|
select CPU_TLB_FEROCEON if MMU
|
2007-10-24 03:14:41 +08:00
|
|
|
|
2007-11-06 16:35:40 +08:00
|
|
|
config CPU_FEROCEON_OLD_ID
|
|
|
|
|
bool "Accept early Feroceon cores with an ARM926 ID"
|
|
|
|
|
depends on CPU_FEROCEON && !CPU_ARM926T
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This enables the usage of some old Feroceon cores
|
|
|
|
|
for which the CPU ID is equal to the ARM926 ID.
|
|
|
|
|
Relevant for Feroceon-1850 and early Feroceon-2850.
|
|
|
|
|
|
2010-11-24 11:54:19 +08:00
|
|
|
# Marvell PJ4
|
|
|
|
|
config CPU_PJ4
|
|
|
|
|
bool
|
|
|
|
|
select ARM_THUMBEE
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_V7
|
2010-11-24 11:54:19 +08:00
|
|
|
|
2012-10-03 17:58:07 +08:00
|
|
|
config CPU_PJ4B
|
|
|
|
|
bool
|
|
|
|
|
select CPU_V7
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# ARMv6
|
|
|
|
|
config CPU_V6
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM V6 processor" if (!ARCH_MULTIPLATFORM || ARCH_MULTI_V6) && (ARCH_INTEGRATOR || MACH_REALVIEW_EB || MACH_REALVIEW_PBX)
|
2005-04-17 06:20:36 +08:00
|
|
|
select CPU_32v6
|
|
|
|
|
select CPU_ABRT_EV6
|
|
|
|
|
select CPU_CACHE_V6
|
|
|
|
|
select CPU_CACHE_VIPT
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_COPY_V6 if MMU
|
[ARM] nommu: defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU
By merging of uClinux/ARM, we need to treat various CPU cores which have
MMU, MPU or even none for memory management. The memory management
coprocessors are controlled by CP15 register set and the ARM core family
can be categorized by 5 groups by the register ;
G-a. CP15 is MMU : 610, 710, 720, 920, 922, 925, 926, 1020, 1020e, 1022,
v6 and the derivations sa1100, sa110, xscale, xsc3.
G-b. CP15 is MPU : 740, 940, 946, 996, 1156.
G-c. CP15 is MPU or MMU : 1026 (selectable by schematic design)
G-d. CP15 is exist, but nothing for memory managemnt : 966, 968.
G-e. no-CP15 : 7tdmi, 9tdmi, 9e, 9ej
This patch defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU. Thus the
family can be defined as :
- CPU_CP15 only : G-d
- CPU_CP15_MMU(implies CPU_CP15) : G-a, G-c(selectable)
- CPU_CP15_MPU(implies CPU_CP15) : G-b, G-c(selectable)
- !CPU_CP15 : G-e
Signed-off-by: Hyok S. Choi <hyok.choi@samsung.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2006-09-26 16:36:37 +08:00
|
|
|
select CPU_CP15_MMU
|
2007-07-20 18:42:57 +08:00
|
|
|
select CPU_HAS_ASID if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_V6
|
2006-06-22 05:26:29 +08:00
|
|
|
select CPU_TLB_V6 if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2005-11-03 23:48:21 +08:00
|
|
|
# ARMv6k
|
2011-01-17 23:08:32 +08:00
|
|
|
config CPU_V6K
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM V6K processor" if (!ARCH_MULTIPLATFORM || ARCH_MULTI_V6) && (ARCH_INTEGRATOR || MACH_REALVIEW_EB || MACH_REALVIEW_PBX)
|
2011-01-17 23:08:32 +08:00
|
|
|
select CPU_32v6
|
2011-01-16 00:25:04 +08:00
|
|
|
select CPU_32v6K
|
2011-01-17 23:08:32 +08:00
|
|
|
select CPU_ABRT_EV6
|
|
|
|
|
select CPU_CACHE_V6
|
|
|
|
|
select CPU_CACHE_VIPT
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_COPY_V6 if MMU
|
2011-01-17 23:08:32 +08:00
|
|
|
select CPU_CP15_MMU
|
|
|
|
|
select CPU_HAS_ASID if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_V6
|
2011-01-17 23:08:32 +08:00
|
|
|
select CPU_TLB_V6 if MMU
|
2005-11-03 23:48:21 +08:00
|
|
|
|
2007-05-09 05:45:26 +08:00
|
|
|
# ARMv7
|
|
|
|
|
config CPU_V7
|
2014-11-11 01:52:31 +08:00
|
|
|
bool "Support ARM V7 processor" if (!ARCH_MULTIPLATFORM || ARCH_MULTI_V7) && (ARCH_INTEGRATOR || MACH_REALVIEW_EB || MACH_REALVIEW_PBX)
|
2011-02-10 00:33:46 +08:00
|
|
|
select CPU_32v6K
|
2007-05-09 05:45:26 +08:00
|
|
|
select CPU_32v7
|
|
|
|
|
select CPU_ABRT_EV7
|
|
|
|
|
select CPU_CACHE_V7
|
|
|
|
|
select CPU_CACHE_VIPT
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_COPY_V6 if MMU
|
2012-07-12 21:38:46 +08:00
|
|
|
select CPU_CP15_MMU if MMU
|
|
|
|
|
select CPU_CP15_MPU if !MMU
|
2007-07-20 18:43:02 +08:00
|
|
|
select CPU_HAS_ASID if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_PABRT_V7
|
2007-05-18 18:25:31 +08:00
|
|
|
select CPU_TLB_V7 if MMU
|
2007-05-09 05:45:26 +08:00
|
|
|
|
2013-03-22 04:02:37 +08:00
|
|
|
# ARMv7M
|
|
|
|
|
config CPU_V7M
|
|
|
|
|
bool
|
|
|
|
|
select CPU_32v7M
|
|
|
|
|
select CPU_ABRT_NOMMU
|
|
|
|
|
select CPU_CACHE_NOP
|
|
|
|
|
select CPU_PABRT_LEGACY
|
|
|
|
|
select CPU_THUMBONLY
|
|
|
|
|
|
2011-12-10 03:52:10 +08:00
|
|
|
config CPU_THUMBONLY
|
|
|
|
|
bool
|
|
|
|
|
# There are no CPUs available with MMU that don't implement an ARM ISA:
|
|
|
|
|
depends on !MMU
|
|
|
|
|
help
|
|
|
|
|
Select this if your CPU doesn't support the 32 bit ARM instructions.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# Figure out what processor architecture version we should be using.
|
|
|
|
|
# This defines the compiler instruction set which depends on the machine type.
|
|
|
|
|
config CPU_32v3
|
|
|
|
|
bool
|
2011-01-17 23:53:56 +08:00
|
|
|
select CPU_USE_DOMAINS if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
|
2013-07-24 01:37:00 +08:00
|
|
|
select NEED_KUSER_HELPERS
|
2014-04-23 05:26:27 +08:00
|
|
|
select TLS_REG_EMUL if SMP || !MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config CPU_32v4
|
|
|
|
|
bool
|
2011-01-17 23:53:56 +08:00
|
|
|
select CPU_USE_DOMAINS if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
|
2013-07-24 01:37:00 +08:00
|
|
|
select NEED_KUSER_HELPERS
|
2014-04-23 05:26:27 +08:00
|
|
|
select TLS_REG_EMUL if SMP || !MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-08-28 19:51:20 +08:00
|
|
|
config CPU_32v4T
|
|
|
|
|
bool
|
2011-01-17 23:53:56 +08:00
|
|
|
select CPU_USE_DOMAINS if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
|
2013-07-24 01:37:00 +08:00
|
|
|
select NEED_KUSER_HELPERS
|
2014-04-23 05:26:27 +08:00
|
|
|
select TLS_REG_EMUL if SMP || !MMU
|
2006-08-28 19:51:20 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_32v5
|
|
|
|
|
bool
|
2011-01-17 23:53:56 +08:00
|
|
|
select CPU_USE_DOMAINS if MMU
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
|
2013-07-24 01:37:00 +08:00
|
|
|
select NEED_KUSER_HELPERS
|
2014-04-23 05:26:27 +08:00
|
|
|
select TLS_REG_EMUL if SMP || !MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config CPU_32v6
|
|
|
|
|
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-07 00:12:25 +08:00
|
|
|
select TLS_REG_EMUL if !CPU_32v6K && !MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2011-01-17 23:08:32 +08:00
|
|
|
config CPU_32v6K
|
2011-01-16 00:25:04 +08:00
|
|
|
bool
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-05-09 05:45:26 +08:00
|
|
|
config CPU_32v7
|
|
|
|
|
bool
|
|
|
|
|
|
2013-03-22 04:02:37 +08:00
|
|
|
config CPU_32v7M
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# The abort model
|
2006-09-28 20:46:16 +08:00
|
|
|
config CPU_ABRT_NOMMU
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_ABRT_EV4
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_ABRT_EV4T
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_ABRT_LV4T
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_ABRT_EV5T
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_ABRT_EV5TJ
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_ABRT_EV6
|
|
|
|
|
bool
|
|
|
|
|
|
2007-05-09 05:45:26 +08:00
|
|
|
config CPU_ABRT_EV7
|
|
|
|
|
bool
|
|
|
|
|
|
2009-09-25 20:39:47 +08:00
|
|
|
config CPU_PABRT_LEGACY
|
2008-04-19 05:43:07 +08:00
|
|
|
bool
|
|
|
|
|
|
2009-09-25 20:39:47 +08:00
|
|
|
config CPU_PABRT_V6
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_PABRT_V7
|
2008-04-19 05:43:07 +08:00
|
|
|
bool
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# The cache model
|
|
|
|
|
config CPU_CACHE_V4
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_CACHE_V4WT
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_CACHE_V4WB
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_CACHE_V6
|
|
|
|
|
bool
|
|
|
|
|
|
2007-05-09 05:45:26 +08:00
|
|
|
config CPU_CACHE_V7
|
|
|
|
|
bool
|
|
|
|
|
|
2013-03-22 04:02:37 +08:00
|
|
|
config CPU_CACHE_NOP
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_CACHE_VIVT
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_CACHE_VIPT
|
|
|
|
|
bool
|
|
|
|
|
|
2009-03-25 19:10:01 +08:00
|
|
|
config CPU_CACHE_FA
|
|
|
|
|
bool
|
|
|
|
|
|
2006-06-22 05:26:29 +08:00
|
|
|
if MMU
|
2005-04-17 06:20:36 +08:00
|
|
|
# The copy-page model
|
|
|
|
|
config CPU_COPY_V4WT
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config CPU_COPY_V4WB
|
|
|
|
|
bool
|
|
|
|
|
|
2008-04-24 13:31:45 +08:00
|
|
|
config CPU_COPY_FEROCEON
|
|
|
|
|
bool
|
|
|
|
|
|
2009-03-25 19:10:01 +08:00
|
|
|
config CPU_COPY_FA
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_COPY_V6
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
# This selects the TLB model
|
|
|
|
|
config CPU_TLB_V4WT
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
ARM Architecture Version 4 TLB with writethrough cache.
|
|
|
|
|
|
|
|
|
|
config CPU_TLB_V4WB
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
ARM Architecture Version 4 TLB with writeback cache.
|
|
|
|
|
|
|
|
|
|
config CPU_TLB_V4WBI
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
ARM Architecture Version 4 TLB with writeback cache and invalidate
|
|
|
|
|
instruction cache entry.
|
|
|
|
|
|
2008-06-23 04:45:04 +08:00
|
|
|
config CPU_TLB_FEROCEON
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Feroceon TLB (v4wbi with non-outer-cachable page table walks).
|
|
|
|
|
|
2009-03-25 19:10:01 +08:00
|
|
|
config CPU_TLB_FA
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Faraday ARM FA526 architecture, unified TLB with writeback cache
|
|
|
|
|
and invalidate instruction cache entry. Branch target buffer is
|
|
|
|
|
also supported.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_TLB_V6
|
|
|
|
|
bool
|
|
|
|
|
|
2007-05-18 18:25:31 +08:00
|
|
|
config CPU_TLB_V7
|
|
|
|
|
bool
|
|
|
|
|
|
2009-08-12 05:58:49 +08:00
|
|
|
config VERIFY_PERMISSION_FAULT
|
|
|
|
|
bool
|
2006-06-22 05:26:29 +08:00
|
|
|
endif
|
|
|
|
|
|
2007-05-17 17:19:23 +08:00
|
|
|
config CPU_HAS_ASID
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This indicates whether the CPU has the ASID register; used to
|
|
|
|
|
tag TLB and possibly cache entries.
|
|
|
|
|
|
[ARM] nommu: defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU
By merging of uClinux/ARM, we need to treat various CPU cores which have
MMU, MPU or even none for memory management. The memory management
coprocessors are controlled by CP15 register set and the ARM core family
can be categorized by 5 groups by the register ;
G-a. CP15 is MMU : 610, 710, 720, 920, 922, 925, 926, 1020, 1020e, 1022,
v6 and the derivations sa1100, sa110, xscale, xsc3.
G-b. CP15 is MPU : 740, 940, 946, 996, 1156.
G-c. CP15 is MPU or MMU : 1026 (selectable by schematic design)
G-d. CP15 is exist, but nothing for memory managemnt : 966, 968.
G-e. no-CP15 : 7tdmi, 9tdmi, 9e, 9ej
This patch defines CPU_CP15, CPU_CP15_MMU and CPU_CP15_MPU. Thus the
family can be defined as :
- CPU_CP15 only : G-d
- CPU_CP15_MMU(implies CPU_CP15) : G-a, G-c(selectable)
- CPU_CP15_MPU(implies CPU_CP15) : G-b, G-c(selectable)
- !CPU_CP15 : G-e
Signed-off-by: Hyok S. Choi <hyok.choi@samsung.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2006-09-26 16:36:37 +08:00
|
|
|
config CPU_CP15
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Processor has the CP15 register.
|
|
|
|
|
|
|
|
|
|
config CPU_CP15_MMU
|
|
|
|
|
bool
|
|
|
|
|
select CPU_CP15
|
|
|
|
|
help
|
|
|
|
|
Processor has the CP15 register, which has MMU related registers.
|
|
|
|
|
|
|
|
|
|
config CPU_CP15_MPU
|
|
|
|
|
bool
|
|
|
|
|
select CPU_CP15
|
|
|
|
|
help
|
|
|
|
|
Processor has the CP15 register, which has MPU related registers.
|
|
|
|
|
|
2010-09-13 23:03:21 +08:00
|
|
|
config CPU_USE_DOMAINS
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option enables or disables the use of domain switching
|
|
|
|
|
via the set_fs() function.
|
|
|
|
|
|
2006-03-29 04:00:40 +08:00
|
|
|
#
|
|
|
|
|
# CPU supports 36-bit I/O
|
|
|
|
|
#
|
|
|
|
|
config IO_36
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
comment "Processor Features"
|
|
|
|
|
|
2011-11-23 01:30:32 +08:00
|
|
|
config ARM_LPAE
|
|
|
|
|
bool "Support for the Large Physical Address Extension"
|
2012-02-14 23:33:27 +08:00
|
|
|
depends on MMU && CPU_32v7 && !CPU_32v6 && !CPU_32v5 && \
|
|
|
|
|
!CPU_32v4 && !CPU_32v3
|
2011-11-23 01:30:32 +08:00
|
|
|
help
|
|
|
|
|
Say Y if you have an ARMv7 processor supporting the LPAE page
|
|
|
|
|
table format and you would like to access memory beyond the
|
|
|
|
|
4GB limit. The resulting kernel image will not run on
|
|
|
|
|
processors without the LPA extension.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config ARCH_PHYS_ADDR_T_64BIT
|
|
|
|
|
def_bool ARM_LPAE
|
|
|
|
|
|
|
|
|
|
config ARCH_DMA_ADDR_T_64BIT
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ARM_THUMB
|
2011-12-10 03:52:10 +08:00
|
|
|
bool "Support Thumb user binaries" if !CPU_THUMBONLY
|
2013-03-22 04:02:37 +08:00
|
|
|
depends on CPU_ARM720T || CPU_ARM740T || CPU_ARM920T || CPU_ARM922T || \
|
|
|
|
|
CPU_ARM925T || CPU_ARM926T || CPU_ARM940T || CPU_ARM946E || \
|
|
|
|
|
CPU_ARM1020 || CPU_ARM1020E || CPU_ARM1022 || CPU_ARM1026 || \
|
|
|
|
|
CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_V6 || CPU_V6K || \
|
|
|
|
|
CPU_V7 || CPU_FEROCEON || CPU_V7M
|
2005-04-17 06:20:36 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want to include kernel support for running user space
|
|
|
|
|
Thumb binaries.
|
|
|
|
|
|
|
|
|
|
The Thumb instruction set is a compressed form of the standard ARM
|
|
|
|
|
instruction set resulting in smaller binaries at the expense of
|
|
|
|
|
slightly less efficient code.
|
|
|
|
|
|
|
|
|
|
If you don't know what this all is, saying Y is a safe choice.
|
|
|
|
|
|
2008-04-19 05:43:06 +08:00
|
|
|
config ARM_THUMBEE
|
|
|
|
|
bool "Enable ThumbEE CPU extension"
|
|
|
|
|
depends on CPU_V7
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you have a CPU with the ThumbEE extension and code to
|
|
|
|
|
make use of it. Say N for code that can run on CPUs without ThumbEE.
|
|
|
|
|
|
2012-02-18 00:54:28 +08:00
|
|
|
config ARM_VIRT_EXT
|
2013-01-09 22:29:33 +08:00
|
|
|
bool
|
|
|
|
|
depends on MMU
|
|
|
|
|
default y if CPU_V7
|
2012-02-18 00:54:28 +08:00
|
|
|
help
|
|
|
|
|
Enable the kernel to make use of the ARM Virtualization
|
|
|
|
|
Extensions to install hypervisors without run-time firmware
|
|
|
|
|
assistance.
|
|
|
|
|
|
|
|
|
|
A compliant bootloader is required in order to make maximum
|
|
|
|
|
use of this feature. Refer to Documentation/arm/Booting for
|
|
|
|
|
details.
|
|
|
|
|
|
2010-09-17 01:00:47 +08:00
|
|
|
config SWP_EMULATE
|
2014-07-04 21:44:36 +08:00
|
|
|
bool "Emulate SWP/SWPB instructions" if !SMP
|
2014-02-08 02:12:27 +08:00
|
|
|
depends on CPU_V7
|
2010-09-17 01:00:47 +08:00
|
|
|
default y if SMP
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select HAVE_PROC_CPU if PROC_FS
|
2010-09-17 01:00:47 +08:00
|
|
|
help
|
|
|
|
|
ARMv6 architecture deprecates use of the SWP/SWPB instructions.
|
|
|
|
|
ARMv7 multiprocessing extensions introduce the ability to disable
|
|
|
|
|
these instructions, triggering an undefined instruction exception
|
|
|
|
|
when executed. Say Y here to enable software emulation of these
|
|
|
|
|
instructions for userspace (not kernel) using LDREX/STREX.
|
|
|
|
|
Also creates /proc/cpu/swp_emulation for statistics.
|
|
|
|
|
|
|
|
|
|
In some older versions of glibc [<=2.8] SWP is used during futex
|
|
|
|
|
trylock() operations with the assumption that the code will not
|
|
|
|
|
be preempted. This invalid assumption may be more likely to fail
|
|
|
|
|
with SWP emulation enabled, leading to deadlock of the user
|
|
|
|
|
application.
|
|
|
|
|
|
|
|
|
|
NOTE: when accessing uncached shared regions, LDREX/STREX rely
|
|
|
|
|
on an external transaction monitoring block called a global
|
|
|
|
|
monitor to maintain update atomicity. If your system does not
|
|
|
|
|
implement a global monitor, this option can cause programs that
|
|
|
|
|
perform SWP operations to uncached memory to deadlock.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_BIG_ENDIAN
|
|
|
|
|
bool "Build big-endian kernel"
|
|
|
|
|
depends on ARCH_SUPPORTS_BIG_ENDIAN
|
|
|
|
|
help
|
|
|
|
|
Say Y if you plan on running a kernel in big-endian mode.
|
|
|
|
|
Note that your board must be properly built and your board
|
|
|
|
|
port must properly enable any big-endian related features
|
|
|
|
|
of your chipset/board/processor.
|
|
|
|
|
|
2009-05-30 21:00:18 +08:00
|
|
|
config CPU_ENDIAN_BE8
|
|
|
|
|
bool
|
|
|
|
|
depends on CPU_BIG_ENDIAN
|
2011-01-17 23:08:32 +08:00
|
|
|
default CPU_V6 || CPU_V6K || CPU_V7
|
2009-05-30 21:00:18 +08:00
|
|
|
help
|
|
|
|
|
Support for the BE-8 (big-endian) mode on ARMv6 and ARMv7 processors.
|
|
|
|
|
|
|
|
|
|
config CPU_ENDIAN_BE32
|
|
|
|
|
bool
|
|
|
|
|
depends on CPU_BIG_ENDIAN
|
|
|
|
|
default !CPU_ENDIAN_BE8
|
|
|
|
|
help
|
|
|
|
|
Support for the BE-32 (big-endian) mode on pre-ARMv6 processors.
|
|
|
|
|
|
2006-09-28 20:46:34 +08:00
|
|
|
config CPU_HIGH_VECTOR
|
2007-02-18 02:05:24 +08:00
|
|
|
depends on !MMU && CPU_CP15 && !CPU_ARM740T
|
2006-09-28 20:46:34 +08:00
|
|
|
bool "Select the High exception vector"
|
|
|
|
|
help
|
|
|
|
|
Say Y here to select high exception vector(0xFFFF0000~).
|
2012-04-13 00:12:37 +08:00
|
|
|
The exception vector can vary depending on the platform
|
2006-09-28 20:46:34 +08:00
|
|
|
design in nommu mode. If your platform needs to select
|
|
|
|
|
high exception vector, say Y.
|
|
|
|
|
Otherwise or if you are unsure, say N, and the low exception
|
|
|
|
|
vector (0x00000000~) will be used.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_ICACHE_DISABLE
|
2006-09-26 16:36:37 +08:00
|
|
|
bool "Disable I-Cache (I-bit)"
|
2012-05-04 19:04:26 +08:00
|
|
|
depends on CPU_CP15 && !(CPU_ARM720T || CPU_ARM740T || CPU_XSCALE || CPU_XSC3)
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to disable the processor instruction cache. Unless
|
|
|
|
|
you have a reason not to or are unsure, say N.
|
|
|
|
|
|
|
|
|
|
config CPU_DCACHE_DISABLE
|
2006-09-26 16:36:37 +08:00
|
|
|
bool "Disable D-Cache (C-bit)"
|
|
|
|
|
depends on CPU_CP15
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to disable the processor data cache. Unless
|
|
|
|
|
you have a reason not to or are unsure, say N.
|
|
|
|
|
|
2006-09-26 16:38:32 +08:00
|
|
|
config CPU_DCACHE_SIZE
|
|
|
|
|
hex
|
|
|
|
|
depends on CPU_ARM740T || CPU_ARM946E
|
|
|
|
|
default 0x00001000 if CPU_ARM740T
|
|
|
|
|
default 0x00002000 # default size for ARM946E-S
|
|
|
|
|
help
|
|
|
|
|
Some cores are synthesizable to have various sized cache. For
|
|
|
|
|
ARM946E-S case, it can vary from 0KB to 1MB.
|
|
|
|
|
To support such cache operations, it is efficient to know the size
|
|
|
|
|
before compile time.
|
|
|
|
|
If your SoC is configured to have a different size, define the value
|
|
|
|
|
here with proper conditions.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_DCACHE_WRITETHROUGH
|
|
|
|
|
bool "Force write through D-cache"
|
2009-03-25 19:10:01 +08:00
|
|
|
depends on (CPU_ARM740T || CPU_ARM920T || CPU_ARM922T || CPU_ARM925T || CPU_ARM926T || CPU_ARM940T || CPU_ARM946E || CPU_ARM1020 || CPU_FA526) && !CPU_DCACHE_DISABLE
|
2005-04-17 06:20:36 +08:00
|
|
|
default y if CPU_ARM925T
|
|
|
|
|
help
|
|
|
|
|
Say Y here to use the data cache in writethrough mode. Unless you
|
|
|
|
|
specifically require this or are unsure, say N.
|
|
|
|
|
|
|
|
|
|
config CPU_CACHE_ROUND_ROBIN
|
|
|
|
|
bool "Round robin I and D cache replacement algorithm"
|
2006-09-26 16:38:32 +08:00
|
|
|
depends on (CPU_ARM926T || CPU_ARM946E || CPU_ARM1020) && (!CPU_ICACHE_DISABLE || !CPU_DCACHE_DISABLE)
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to use the predictable round-robin cache replacement
|
|
|
|
|
policy. Unless you specifically require this or are unsure, say N.
|
|
|
|
|
|
|
|
|
|
config CPU_BPREDICT_DISABLE
|
|
|
|
|
bool "Disable branch prediction"
|
2011-01-17 23:08:32 +08:00
|
|
|
depends on CPU_ARM1020 || CPU_V6 || CPU_V6K || CPU_MOHAWK || CPU_XSC3 || CPU_V7 || CPU_FA526
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to disable branch prediction. If unsure, say N.
|
2005-04-30 05:08:33 +08:00
|
|
|
|
2005-05-06 06:24:45 +08:00
|
|
|
config TLS_REG_EMUL
|
|
|
|
|
bool
|
2013-07-24 01:37:00 +08:00
|
|
|
select NEED_KUSER_HELPERS
|
2005-05-06 06:24:45 +08:00
|
|
|
help
|
2005-05-13 02:27:12 +08:00
|
|
|
An SMP system using a pre-ARMv6 processor (there are apparently
|
|
|
|
|
a few prototypes like that in existence) and therefore access to
|
|
|
|
|
that required register must be emulated.
|
2005-05-06 06:24:45 +08:00
|
|
|
|
2005-06-09 02:00:47 +08:00
|
|
|
config NEEDS_SYSCALL_FOR_CMPXCHG
|
|
|
|
|
bool
|
2013-07-24 01:37:00 +08:00
|
|
|
select NEED_KUSER_HELPERS
|
2005-06-09 02:00:47 +08:00
|
|
|
help
|
|
|
|
|
SMP on a pre-ARMv6 processor? Well OK then.
|
|
|
|
|
Forget about fast user space cmpxchg support.
|
|
|
|
|
It is just not possible.
|
|
|
|
|
|
2013-07-24 01:37:00 +08:00
|
|
|
config NEED_KUSER_HELPERS
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config KUSER_HELPERS
|
|
|
|
|
bool "Enable kuser helpers in vector page" if !NEED_KUSER_HELPERS
|
2014-11-11 06:46:27 +08:00
|
|
|
depends on MMU
|
2013-07-24 01:37:00 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Warning: disabling this option may break user programs.
|
|
|
|
|
|
|
|
|
|
Provide kuser helpers in the vector page. The kernel provides
|
|
|
|
|
helper code to userspace in read only form at a fixed location
|
|
|
|
|
in the high vector page to allow userspace to be independent of
|
|
|
|
|
the CPU type fitted to the system. This permits binaries to be
|
|
|
|
|
run on ARMv4 through to ARMv7 without modification.
|
|
|
|
|
|
2013-08-15 05:36:32 +08:00
|
|
|
See Documentation/arm/kernel_user_helpers.txt for details.
|
|
|
|
|
|
2013-07-24 01:37:00 +08:00
|
|
|
However, the fixed address nature of these helpers can be used
|
|
|
|
|
by ROP (return orientated programming) authors when creating
|
|
|
|
|
exploits.
|
|
|
|
|
|
|
|
|
|
If all of the binaries and libraries which run on your platform
|
|
|
|
|
are built specifically for your platform, and make no use of
|
2013-08-15 05:36:32 +08:00
|
|
|
these helpers, then you can turn this option off to hinder
|
|
|
|
|
such exploits. However, in that case, if a binary or library
|
|
|
|
|
relying on those helpers is run, it will receive a SIGILL signal,
|
|
|
|
|
which will terminate the program.
|
2013-07-24 01:37:00 +08:00
|
|
|
|
|
|
|
|
Say N here only if you are absolutely certain that you do not
|
|
|
|
|
need these helpers; otherwise, the safe option is to say Y.
|
|
|
|
|
|
2010-06-21 22:10:07 +08:00
|
|
|
config DMA_CACHE_RWFO
|
|
|
|
|
bool "Enable read/write for ownership DMA cache maintenance"
|
2011-01-18 21:30:33 +08:00
|
|
|
depends on CPU_V6K && SMP
|
2010-06-21 22:10:07 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
The Snoop Control Unit on ARM11MPCore does not detect the
|
|
|
|
|
cache maintenance operations and the dma_{map,unmap}_area()
|
|
|
|
|
functions may leave stale cache entries on other CPUs. By
|
|
|
|
|
enabling this option, Read or Write For Ownership in the ARMv6
|
|
|
|
|
DMA cache maintenance functions is performed. These LDR/STR
|
|
|
|
|
instructions change the cache line state to shared or modified
|
|
|
|
|
so that the cache operation has the desired effect.
|
|
|
|
|
|
|
|
|
|
Note that the workaround is only valid on processors that do
|
|
|
|
|
not perform speculative loads into the D-cache. For such
|
|
|
|
|
processors, if cache maintenance operations are not broadcast
|
|
|
|
|
in hardware, other workarounds are needed (e.g. cache
|
|
|
|
|
maintenance broadcasting in software via FIQ).
|
|
|
|
|
|
2007-02-05 21:48:08 +08:00
|
|
|
config OUTER_CACHE
|
|
|
|
|
bool
|
2007-02-05 21:48:19 +08:00
|
|
|
|
2010-03-24 23:47:53 +08:00
|
|
|
config OUTER_CACHE_SYNC
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
The outer cache has a outer_cache_fns.sync function pointer
|
|
|
|
|
that can be used to drain the write buffer of the outer cache.
|
|
|
|
|
|
2008-06-23 04:45:04 +08:00
|
|
|
config CACHE_FEROCEON_L2
|
|
|
|
|
bool "Enable the Feroceon L2 cache controller"
|
2014-07-11 05:36:21 +08:00
|
|
|
depends on ARCH_MV78XX0 || ARCH_MVEBU
|
2008-06-23 04:45:04 +08:00
|
|
|
default y
|
|
|
|
|
select OUTER_CACHE
|
|
|
|
|
help
|
|
|
|
|
This option enables the Feroceon L2 cache controller.
|
|
|
|
|
|
2008-09-23 20:28:10 +08:00
|
|
|
config CACHE_FEROCEON_L2_WRITETHROUGH
|
|
|
|
|
bool "Force Feroceon L2 cache write through"
|
|
|
|
|
depends on CACHE_FEROCEON_L2
|
|
|
|
|
help
|
|
|
|
|
Say Y here to use the Feroceon L2 cache in writethrough mode.
|
|
|
|
|
Unless you specifically require this, say N for writeback mode.
|
|
|
|
|
|
2011-11-29 23:56:19 +08:00
|
|
|
config MIGHT_HAVE_CACHE_L2X0
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option should be selected by machines which have a L2x0
|
|
|
|
|
or PL310 cache controller, but where its use is optional.
|
|
|
|
|
|
|
|
|
|
The only effect of this option is to make CACHE_L2X0 and
|
|
|
|
|
related options available to the user for configuration.
|
|
|
|
|
|
|
|
|
|
Boards or SoCs which always require the cache controller
|
|
|
|
|
support to be present should select CACHE_L2X0 directly
|
|
|
|
|
instead of this option, thus preventing the user from
|
|
|
|
|
inadvertently configuring a broken kernel.
|
|
|
|
|
|
2007-02-05 21:48:19 +08:00
|
|
|
config CACHE_L2X0
|
2011-11-29 23:56:19 +08:00
|
|
|
bool "Enable the L2x0 outer cache controller" if MIGHT_HAVE_CACHE_L2X0
|
|
|
|
|
default MIGHT_HAVE_CACHE_L2X0
|
2007-02-05 21:48:19 +08:00
|
|
|
select OUTER_CACHE
|
2010-03-24 23:48:53 +08:00
|
|
|
select OUTER_CACHE_SYNC
|
2008-04-19 05:43:17 +08:00
|
|
|
help
|
|
|
|
|
This option enables the L2x0 PrimeCell.
|
2008-06-06 16:34:03 +08:00
|
|
|
|
2014-06-19 17:19:10 +08:00
|
|
|
if CACHE_L2X0
|
|
|
|
|
|
2014-03-16 20:12:11 +08:00
|
|
|
config PL310_ERRATA_588369
|
|
|
|
|
bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
|
|
|
|
|
help
|
|
|
|
|
The PL310 L2 cache controller implements three types of Clean &
|
|
|
|
|
Invalidate maintenance operations: by Physical Address
|
|
|
|
|
(offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
|
|
|
|
|
They are architecturally defined to behave as the execution of a
|
|
|
|
|
clean operation followed immediately by an invalidate operation,
|
|
|
|
|
both performing to the same memory location. This functionality
|
2014-07-08 09:59:42 +08:00
|
|
|
is not correctly implemented in PL310 prior to r2p0 (fixed in r2p0)
|
|
|
|
|
as clean lines are not invalidated as a result of these operations.
|
2014-03-16 20:12:11 +08:00
|
|
|
|
|
|
|
|
config PL310_ERRATA_727915
|
|
|
|
|
bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
|
|
|
|
|
help
|
|
|
|
|
PL310 implements the Clean & Invalidate by Way L2 cache maintenance
|
|
|
|
|
operation (offset 0x7FC). This operation runs in background so that
|
|
|
|
|
PL310 can handle normal accesses while it is in progress. Under very
|
|
|
|
|
rare circumstances, due to this erratum, write data can be lost when
|
|
|
|
|
PL310 treats a cacheable write transaction during a Clean &
|
2014-07-08 09:59:42 +08:00
|
|
|
Invalidate by Way operation. Revisions prior to r3p1 are affected by
|
|
|
|
|
this errata (fixed in r3p1).
|
2014-03-16 20:12:11 +08:00
|
|
|
|
|
|
|
|
config PL310_ERRATA_753970
|
|
|
|
|
bool "PL310 errata: cache sync operation may be faulty"
|
|
|
|
|
help
|
|
|
|
|
This option enables the workaround for the 753970 PL310 (r3p0) erratum.
|
|
|
|
|
|
|
|
|
|
Under some condition the effect of cache sync operation on
|
|
|
|
|
the store buffer still remains when the operation completes.
|
|
|
|
|
This means that the store buffer is always asked to drain and
|
|
|
|
|
this prevents it from merging any further writes. The workaround
|
|
|
|
|
is to replace the normal offset of cache sync operation (0x730)
|
|
|
|
|
by another offset targeting an unmapped PL310 register 0x740.
|
|
|
|
|
This has the same effect as the cache sync operation: store buffer
|
|
|
|
|
drain and waiting for all buffers empty.
|
|
|
|
|
|
|
|
|
|
config PL310_ERRATA_769419
|
|
|
|
|
bool "PL310 errata: no automatic Store Buffer drain"
|
|
|
|
|
help
|
|
|
|
|
On revisions of the PL310 prior to r3p2, the Store Buffer does
|
|
|
|
|
not automatically drain. This can cause normal, non-cacheable
|
|
|
|
|
writes to be retained when the memory system is idle, leading
|
|
|
|
|
to suboptimal I/O performance for drivers using coherent DMA.
|
|
|
|
|
This option adds a write barrier to the cpu_idle loop so that,
|
|
|
|
|
on systems with an outer cache, the store buffer is drained
|
|
|
|
|
explicitly.
|
|
|
|
|
|
2014-06-19 17:19:10 +08:00
|
|
|
endif
|
|
|
|
|
|
2009-11-25 01:33:52 +08:00
|
|
|
config CACHE_TAUROS2
|
|
|
|
|
bool "Enable the Tauros2 L2 cache controller"
|
2010-11-24 11:54:21 +08:00
|
|
|
depends on (ARCH_DOVE || ARCH_MMP || CPU_PJ4)
|
2009-11-25 01:33:52 +08:00
|
|
|
default y
|
|
|
|
|
select OUTER_CACHE
|
|
|
|
|
help
|
|
|
|
|
This option enables the Tauros2 L2 cache controller (as
|
|
|
|
|
found on PJ1/PJ4).
|
|
|
|
|
|
2008-06-06 16:34:03 +08:00
|
|
|
config CACHE_XSC3L2
|
|
|
|
|
bool "Enable the L2 cache on XScale3"
|
|
|
|
|
depends on CPU_XSC3
|
|
|
|
|
default y
|
|
|
|
|
select OUTER_CACHE
|
|
|
|
|
help
|
|
|
|
|
This option enables the L2 cache on XScale3.
|
2009-09-15 17:23:53 +08:00
|
|
|
|
2011-02-14 23:55:45 +08:00
|
|
|
config ARM_L1_CACHE_SHIFT_6
|
|
|
|
|
bool
|
2012-01-20 19:01:10 +08:00
|
|
|
default y if CPU_V7
|
2011-02-14 23:55:45 +08:00
|
|
|
help
|
|
|
|
|
Setting ARM L1 cache line size to 64 Bytes.
|
|
|
|
|
|
2009-09-15 17:23:53 +08:00
|
|
|
config ARM_L1_CACHE_SHIFT
|
|
|
|
|
int
|
2010-02-22 07:02:59 +08:00
|
|
|
default 6 if ARM_L1_CACHE_SHIFT_6
|
2009-09-15 17:23:53 +08:00
|
|
|
default 5
|
2010-05-15 18:02:43 +08:00
|
|
|
|
|
|
|
|
config ARM_DMA_MEM_BUFFERABLE
|
2011-01-17 23:08:32 +08:00
|
|
|
bool "Use non-cacheable memory for DMA" if (CPU_V6 || CPU_V6K) && !CPU_V7
|
2010-07-01 20:22:48 +08:00
|
|
|
depends on !(MACH_REALVIEW_PB1176 || REALVIEW_EB_ARM11MP || \
|
|
|
|
|
MACH_REALVIEW_PB11MP)
|
2011-01-17 23:08:32 +08:00
|
|
|
default y if CPU_V6 || CPU_V6K || CPU_V7
|
2010-05-15 18:02:43 +08:00
|
|
|
help
|
|
|
|
|
Historically, the kernel has used strongly ordered mappings to
|
|
|
|
|
provide DMA coherent memory. With the advent of ARMv7, mapping
|
|
|
|
|
memory with differing types results in unpredictable behaviour,
|
|
|
|
|
so on these CPUs, this option is forced on.
|
|
|
|
|
|
|
|
|
|
Multiple mappings with differing attributes is also unpredictable
|
|
|
|
|
on ARMv6 CPUs, but since they do not have aggressive speculative
|
|
|
|
|
prefetch, no harm appears to occur.
|
|
|
|
|
|
|
|
|
|
However, drivers may be missing the necessary barriers for ARMv6,
|
|
|
|
|
and therefore turning this on may result in unpredictable driver
|
|
|
|
|
behaviour. Therefore, we offer this as an option.
|
|
|
|
|
|
|
|
|
|
You are recommended say 'Y' here and debug any affected drivers.
|
2010-05-18 00:24:04 +08:00
|
|
|
|
2010-03-24 23:49:54 +08:00
|
|
|
config ARCH_HAS_BARRIERS
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option allows the use of custom mandatory barriers
|
|
|
|
|
included via the mach/barriers.h file.
|
2013-02-01 17:41:37 +08:00
|
|
|
|
|
|
|
|
config ARCH_SUPPORTS_BIG_ENDIAN
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option specifies the architecture can support big endian
|
|
|
|
|
operation.
|
2014-04-04 08:28:11 +08:00
|
|
|
|
|
|
|
|
config ARM_KERNMEM_PERMS
|
|
|
|
|
bool "Restrict kernel memory permissions"
|
2015-01-29 00:58:33 +08:00
|
|
|
depends on MMU
|
2014-04-04 08:28:11 +08:00
|
|
|
help
|
|
|
|
|
If this is set, kernel memory other than kernel text (and rodata)
|
|
|
|
|
will be made non-executable. The tradeoff is that each region is
|
|
|
|
|
padded to section-size (1MiB) boundaries (because their permissions
|
|
|
|
|
are different and splitting the 1M pages into 4K ones causes TLB
|
|
|
|
|
performance problems), wasting memory.
|
2014-04-04 04:29:50 +08:00
|
|
|
|
|
|
|
|
config DEBUG_RODATA
|
|
|
|
|
bool "Make kernel text and rodata read-only"
|
|
|
|
|
depends on ARM_KERNMEM_PERMS
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
If this is set, kernel text and rodata will be made read-only. This
|
|
|
|
|
is to help catch accidental or malicious attempts to change the
|
|
|
|
|
kernel's executable code. Additionally splits rodata from kernel
|
|
|
|
|
text so it can be made explicitly non-executable. This creates
|
|
|
|
|
another section-size padded region, so it can waste more memory
|
|
|
|
|
space while gaining the read-only protections.
|