License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
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
|
2015-05-26 22:40:16 +08:00
|
|
|
bool
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-05-26 22:40:16 +08:00
|
|
|
bool
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2015-11-26 00:32:21 +08:00
|
|
|
bool
|
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
|
2018-05-14 18:56:36 +08:00
|
|
|
select CPU_SPECTRE if MMU
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
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
|
2016-08-31 00:31:22 +08:00
|
|
|
select CPU_CACHE_V7M
|
2013-03-22 04:02:37 +08:00
|
|
|
select CPU_CACHE_NOP
|
|
|
|
select CPU_PABRT_LEGACY
|
|
|
|
select CPU_THUMBONLY
|
|
|
|
|
2011-12-10 03:52:10 +08:00
|
|
|
config CPU_THUMBONLY
|
|
|
|
bool
|
2017-02-09 20:00:16 +08:00
|
|
|
select CPU_THUMB_CAPABLE
|
2011-12-10 03:52:10 +08:00
|
|
|
# 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.
|
|
|
|
|
2017-02-09 20:00:16 +08:00
|
|
|
config CPU_THUMB_CAPABLE
|
|
|
|
bool
|
|
|
|
help
|
|
|
|
Select this if your CPU can support Thumb mode.
|
|
|
|
|
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
|
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
|
lib/GCD.c: use binary GCD algorithm instead of Euclidean
The binary GCD algorithm is based on the following facts:
1. If a and b are all evens, then gcd(a,b) = 2 * gcd(a/2, b/2)
2. If a is even and b is odd, then gcd(a,b) = gcd(a/2, b)
3. If a and b are all odds, then gcd(a,b) = gcd((a-b)/2, b) = gcd((a+b)/2, b)
Even on x86 machines with reasonable division hardware, the binary
algorithm runs about 25% faster (80% the execution time) than the
division-based Euclidian algorithm.
On platforms like Alpha and ARMv6 where division is a function call to
emulation code, it's even more significant.
There are two variants of the code here, depending on whether a fast
__ffs (find least significant set bit) instruction is available. This
allows the unpredictable branches in the bit-at-a-time shifting loop to
be eliminated.
If fast __ffs is not available, the "even/odd" GCD variant is used.
I use the following code to benchmark:
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <string.h>
#include <time.h>
#include <unistd.h>
#define swap(a, b) \
do { \
a ^= b; \
b ^= a; \
a ^= b; \
} while (0)
unsigned long gcd0(unsigned long a, unsigned long b)
{
unsigned long r;
if (a < b) {
swap(a, b);
}
if (b == 0)
return a;
while ((r = a % b) != 0) {
a = b;
b = r;
}
return b;
}
unsigned long gcd1(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
b >>= __builtin_ctzl(b);
for (;;) {
a >>= __builtin_ctzl(a);
if (a == b)
return a << __builtin_ctzl(r);
if (a < b)
swap(a, b);
a -= b;
}
}
unsigned long gcd2(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
r &= -r;
while (!(b & r))
b >>= 1;
for (;;) {
while (!(a & r))
a >>= 1;
if (a == b)
return a;
if (a < b)
swap(a, b);
a -= b;
a >>= 1;
if (a & r)
a += b;
a >>= 1;
}
}
unsigned long gcd3(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
b >>= __builtin_ctzl(b);
if (b == 1)
return r & -r;
for (;;) {
a >>= __builtin_ctzl(a);
if (a == 1)
return r & -r;
if (a == b)
return a << __builtin_ctzl(r);
if (a < b)
swap(a, b);
a -= b;
}
}
unsigned long gcd4(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
r &= -r;
while (!(b & r))
b >>= 1;
if (b == r)
return r;
for (;;) {
while (!(a & r))
a >>= 1;
if (a == r)
return r;
if (a == b)
return a;
if (a < b)
swap(a, b);
a -= b;
a >>= 1;
if (a & r)
a += b;
a >>= 1;
}
}
static unsigned long (*gcd_func[])(unsigned long a, unsigned long b) = {
gcd0, gcd1, gcd2, gcd3, gcd4,
};
#define TEST_ENTRIES (sizeof(gcd_func) / sizeof(gcd_func[0]))
#if defined(__x86_64__)
#define rdtscll(val) do { \
unsigned long __a,__d; \
__asm__ __volatile__("rdtsc" : "=a" (__a), "=d" (__d)); \
(val) = ((unsigned long long)__a) | (((unsigned long long)__d)<<32); \
} while(0)
static unsigned long long benchmark_gcd_func(unsigned long (*gcd)(unsigned long, unsigned long),
unsigned long a, unsigned long b, unsigned long *res)
{
unsigned long long start, end;
unsigned long long ret;
unsigned long gcd_res;
rdtscll(start);
gcd_res = gcd(a, b);
rdtscll(end);
if (end >= start)
ret = end - start;
else
ret = ~0ULL - start + 1 + end;
*res = gcd_res;
return ret;
}
#else
static inline struct timespec read_time(void)
{
struct timespec time;
clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &time);
return time;
}
static inline unsigned long long diff_time(struct timespec start, struct timespec end)
{
struct timespec temp;
if ((end.tv_nsec - start.tv_nsec) < 0) {
temp.tv_sec = end.tv_sec - start.tv_sec - 1;
temp.tv_nsec = 1000000000ULL + end.tv_nsec - start.tv_nsec;
} else {
temp.tv_sec = end.tv_sec - start.tv_sec;
temp.tv_nsec = end.tv_nsec - start.tv_nsec;
}
return temp.tv_sec * 1000000000ULL + temp.tv_nsec;
}
static unsigned long long benchmark_gcd_func(unsigned long (*gcd)(unsigned long, unsigned long),
unsigned long a, unsigned long b, unsigned long *res)
{
struct timespec start, end;
unsigned long gcd_res;
start = read_time();
gcd_res = gcd(a, b);
end = read_time();
*res = gcd_res;
return diff_time(start, end);
}
#endif
static inline unsigned long get_rand()
{
if (sizeof(long) == 8)
return (unsigned long)rand() << 32 | rand();
else
return rand();
}
int main(int argc, char **argv)
{
unsigned int seed = time(0);
int loops = 100;
int repeats = 1000;
unsigned long (*res)[TEST_ENTRIES];
unsigned long long elapsed[TEST_ENTRIES];
int i, j, k;
for (;;) {
int opt = getopt(argc, argv, "n:r:s:");
/* End condition always first */
if (opt == -1)
break;
switch (opt) {
case 'n':
loops = atoi(optarg);
break;
case 'r':
repeats = atoi(optarg);
break;
case 's':
seed = strtoul(optarg, NULL, 10);
break;
default:
/* You won't actually get here. */
break;
}
}
res = malloc(sizeof(unsigned long) * TEST_ENTRIES * loops);
memset(elapsed, 0, sizeof(elapsed));
srand(seed);
for (j = 0; j < loops; j++) {
unsigned long a = get_rand();
/* Do we have args? */
unsigned long b = argc > optind ? strtoul(argv[optind], NULL, 10) : get_rand();
unsigned long long min_elapsed[TEST_ENTRIES];
for (k = 0; k < repeats; k++) {
for (i = 0; i < TEST_ENTRIES; i++) {
unsigned long long tmp = benchmark_gcd_func(gcd_func[i], a, b, &res[j][i]);
if (k == 0 || min_elapsed[i] > tmp)
min_elapsed[i] = tmp;
}
}
for (i = 0; i < TEST_ENTRIES; i++)
elapsed[i] += min_elapsed[i];
}
for (i = 0; i < TEST_ENTRIES; i++)
printf("gcd%d: elapsed %llu\n", i, elapsed[i]);
k = 0;
srand(seed);
for (j = 0; j < loops; j++) {
unsigned long a = get_rand();
unsigned long b = argc > optind ? strtoul(argv[optind], NULL, 10) : get_rand();
for (i = 1; i < TEST_ENTRIES; i++) {
if (res[j][i] != res[j][0])
break;
}
if (i < TEST_ENTRIES) {
if (k == 0) {
k = 1;
fprintf(stderr, "Error:\n");
}
fprintf(stderr, "gcd(%lu, %lu): ", a, b);
for (i = 0; i < TEST_ENTRIES; i++)
fprintf(stderr, "%ld%s", res[j][i], i < TEST_ENTRIES - 1 ? ", " : "\n");
}
}
if (k == 0)
fprintf(stderr, "PASS\n");
free(res);
return 0;
}
Compiled with "-O2", on "VirtualBox 4.4.0-22-generic #38-Ubuntu x86_64" got:
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 10174
gcd1: elapsed 2120
gcd2: elapsed 2902
gcd3: elapsed 2039
gcd4: elapsed 2812
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9309
gcd1: elapsed 2280
gcd2: elapsed 2822
gcd3: elapsed 2217
gcd4: elapsed 2710
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9589
gcd1: elapsed 2098
gcd2: elapsed 2815
gcd3: elapsed 2030
gcd4: elapsed 2718
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9914
gcd1: elapsed 2309
gcd2: elapsed 2779
gcd3: elapsed 2228
gcd4: elapsed 2709
PASS
[akpm@linux-foundation.org: avoid #defining a CONFIG_ variable]
Signed-off-by: Zhaoxiu Zeng <zhaoxiu.zeng@gmail.com>
Signed-off-by: George Spelvin <linux@horizon.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-05-21 08:03:57 +08:00
|
|
|
select CPU_NO_EFFICIENT_FFS
|
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
|
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
|
lib/GCD.c: use binary GCD algorithm instead of Euclidean
The binary GCD algorithm is based on the following facts:
1. If a and b are all evens, then gcd(a,b) = 2 * gcd(a/2, b/2)
2. If a is even and b is odd, then gcd(a,b) = gcd(a/2, b)
3. If a and b are all odds, then gcd(a,b) = gcd((a-b)/2, b) = gcd((a+b)/2, b)
Even on x86 machines with reasonable division hardware, the binary
algorithm runs about 25% faster (80% the execution time) than the
division-based Euclidian algorithm.
On platforms like Alpha and ARMv6 where division is a function call to
emulation code, it's even more significant.
There are two variants of the code here, depending on whether a fast
__ffs (find least significant set bit) instruction is available. This
allows the unpredictable branches in the bit-at-a-time shifting loop to
be eliminated.
If fast __ffs is not available, the "even/odd" GCD variant is used.
I use the following code to benchmark:
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <string.h>
#include <time.h>
#include <unistd.h>
#define swap(a, b) \
do { \
a ^= b; \
b ^= a; \
a ^= b; \
} while (0)
unsigned long gcd0(unsigned long a, unsigned long b)
{
unsigned long r;
if (a < b) {
swap(a, b);
}
if (b == 0)
return a;
while ((r = a % b) != 0) {
a = b;
b = r;
}
return b;
}
unsigned long gcd1(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
b >>= __builtin_ctzl(b);
for (;;) {
a >>= __builtin_ctzl(a);
if (a == b)
return a << __builtin_ctzl(r);
if (a < b)
swap(a, b);
a -= b;
}
}
unsigned long gcd2(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
r &= -r;
while (!(b & r))
b >>= 1;
for (;;) {
while (!(a & r))
a >>= 1;
if (a == b)
return a;
if (a < b)
swap(a, b);
a -= b;
a >>= 1;
if (a & r)
a += b;
a >>= 1;
}
}
unsigned long gcd3(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
b >>= __builtin_ctzl(b);
if (b == 1)
return r & -r;
for (;;) {
a >>= __builtin_ctzl(a);
if (a == 1)
return r & -r;
if (a == b)
return a << __builtin_ctzl(r);
if (a < b)
swap(a, b);
a -= b;
}
}
unsigned long gcd4(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
r &= -r;
while (!(b & r))
b >>= 1;
if (b == r)
return r;
for (;;) {
while (!(a & r))
a >>= 1;
if (a == r)
return r;
if (a == b)
return a;
if (a < b)
swap(a, b);
a -= b;
a >>= 1;
if (a & r)
a += b;
a >>= 1;
}
}
static unsigned long (*gcd_func[])(unsigned long a, unsigned long b) = {
gcd0, gcd1, gcd2, gcd3, gcd4,
};
#define TEST_ENTRIES (sizeof(gcd_func) / sizeof(gcd_func[0]))
#if defined(__x86_64__)
#define rdtscll(val) do { \
unsigned long __a,__d; \
__asm__ __volatile__("rdtsc" : "=a" (__a), "=d" (__d)); \
(val) = ((unsigned long long)__a) | (((unsigned long long)__d)<<32); \
} while(0)
static unsigned long long benchmark_gcd_func(unsigned long (*gcd)(unsigned long, unsigned long),
unsigned long a, unsigned long b, unsigned long *res)
{
unsigned long long start, end;
unsigned long long ret;
unsigned long gcd_res;
rdtscll(start);
gcd_res = gcd(a, b);
rdtscll(end);
if (end >= start)
ret = end - start;
else
ret = ~0ULL - start + 1 + end;
*res = gcd_res;
return ret;
}
#else
static inline struct timespec read_time(void)
{
struct timespec time;
clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &time);
return time;
}
static inline unsigned long long diff_time(struct timespec start, struct timespec end)
{
struct timespec temp;
if ((end.tv_nsec - start.tv_nsec) < 0) {
temp.tv_sec = end.tv_sec - start.tv_sec - 1;
temp.tv_nsec = 1000000000ULL + end.tv_nsec - start.tv_nsec;
} else {
temp.tv_sec = end.tv_sec - start.tv_sec;
temp.tv_nsec = end.tv_nsec - start.tv_nsec;
}
return temp.tv_sec * 1000000000ULL + temp.tv_nsec;
}
static unsigned long long benchmark_gcd_func(unsigned long (*gcd)(unsigned long, unsigned long),
unsigned long a, unsigned long b, unsigned long *res)
{
struct timespec start, end;
unsigned long gcd_res;
start = read_time();
gcd_res = gcd(a, b);
end = read_time();
*res = gcd_res;
return diff_time(start, end);
}
#endif
static inline unsigned long get_rand()
{
if (sizeof(long) == 8)
return (unsigned long)rand() << 32 | rand();
else
return rand();
}
int main(int argc, char **argv)
{
unsigned int seed = time(0);
int loops = 100;
int repeats = 1000;
unsigned long (*res)[TEST_ENTRIES];
unsigned long long elapsed[TEST_ENTRIES];
int i, j, k;
for (;;) {
int opt = getopt(argc, argv, "n:r:s:");
/* End condition always first */
if (opt == -1)
break;
switch (opt) {
case 'n':
loops = atoi(optarg);
break;
case 'r':
repeats = atoi(optarg);
break;
case 's':
seed = strtoul(optarg, NULL, 10);
break;
default:
/* You won't actually get here. */
break;
}
}
res = malloc(sizeof(unsigned long) * TEST_ENTRIES * loops);
memset(elapsed, 0, sizeof(elapsed));
srand(seed);
for (j = 0; j < loops; j++) {
unsigned long a = get_rand();
/* Do we have args? */
unsigned long b = argc > optind ? strtoul(argv[optind], NULL, 10) : get_rand();
unsigned long long min_elapsed[TEST_ENTRIES];
for (k = 0; k < repeats; k++) {
for (i = 0; i < TEST_ENTRIES; i++) {
unsigned long long tmp = benchmark_gcd_func(gcd_func[i], a, b, &res[j][i]);
if (k == 0 || min_elapsed[i] > tmp)
min_elapsed[i] = tmp;
}
}
for (i = 0; i < TEST_ENTRIES; i++)
elapsed[i] += min_elapsed[i];
}
for (i = 0; i < TEST_ENTRIES; i++)
printf("gcd%d: elapsed %llu\n", i, elapsed[i]);
k = 0;
srand(seed);
for (j = 0; j < loops; j++) {
unsigned long a = get_rand();
unsigned long b = argc > optind ? strtoul(argv[optind], NULL, 10) : get_rand();
for (i = 1; i < TEST_ENTRIES; i++) {
if (res[j][i] != res[j][0])
break;
}
if (i < TEST_ENTRIES) {
if (k == 0) {
k = 1;
fprintf(stderr, "Error:\n");
}
fprintf(stderr, "gcd(%lu, %lu): ", a, b);
for (i = 0; i < TEST_ENTRIES; i++)
fprintf(stderr, "%ld%s", res[j][i], i < TEST_ENTRIES - 1 ? ", " : "\n");
}
}
if (k == 0)
fprintf(stderr, "PASS\n");
free(res);
return 0;
}
Compiled with "-O2", on "VirtualBox 4.4.0-22-generic #38-Ubuntu x86_64" got:
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 10174
gcd1: elapsed 2120
gcd2: elapsed 2902
gcd3: elapsed 2039
gcd4: elapsed 2812
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9309
gcd1: elapsed 2280
gcd2: elapsed 2822
gcd3: elapsed 2217
gcd4: elapsed 2710
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9589
gcd1: elapsed 2098
gcd2: elapsed 2815
gcd3: elapsed 2030
gcd4: elapsed 2718
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9914
gcd1: elapsed 2309
gcd2: elapsed 2779
gcd3: elapsed 2228
gcd4: elapsed 2709
PASS
[akpm@linux-foundation.org: avoid #defining a CONFIG_ variable]
Signed-off-by: Zhaoxiu Zeng <zhaoxiu.zeng@gmail.com>
Signed-off-by: George Spelvin <linux@horizon.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-05-21 08:03:57 +08:00
|
|
|
select CPU_NO_EFFICIENT_FFS
|
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
|
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
|
lib/GCD.c: use binary GCD algorithm instead of Euclidean
The binary GCD algorithm is based on the following facts:
1. If a and b are all evens, then gcd(a,b) = 2 * gcd(a/2, b/2)
2. If a is even and b is odd, then gcd(a,b) = gcd(a/2, b)
3. If a and b are all odds, then gcd(a,b) = gcd((a-b)/2, b) = gcd((a+b)/2, b)
Even on x86 machines with reasonable division hardware, the binary
algorithm runs about 25% faster (80% the execution time) than the
division-based Euclidian algorithm.
On platforms like Alpha and ARMv6 where division is a function call to
emulation code, it's even more significant.
There are two variants of the code here, depending on whether a fast
__ffs (find least significant set bit) instruction is available. This
allows the unpredictable branches in the bit-at-a-time shifting loop to
be eliminated.
If fast __ffs is not available, the "even/odd" GCD variant is used.
I use the following code to benchmark:
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <string.h>
#include <time.h>
#include <unistd.h>
#define swap(a, b) \
do { \
a ^= b; \
b ^= a; \
a ^= b; \
} while (0)
unsigned long gcd0(unsigned long a, unsigned long b)
{
unsigned long r;
if (a < b) {
swap(a, b);
}
if (b == 0)
return a;
while ((r = a % b) != 0) {
a = b;
b = r;
}
return b;
}
unsigned long gcd1(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
b >>= __builtin_ctzl(b);
for (;;) {
a >>= __builtin_ctzl(a);
if (a == b)
return a << __builtin_ctzl(r);
if (a < b)
swap(a, b);
a -= b;
}
}
unsigned long gcd2(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
r &= -r;
while (!(b & r))
b >>= 1;
for (;;) {
while (!(a & r))
a >>= 1;
if (a == b)
return a;
if (a < b)
swap(a, b);
a -= b;
a >>= 1;
if (a & r)
a += b;
a >>= 1;
}
}
unsigned long gcd3(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
b >>= __builtin_ctzl(b);
if (b == 1)
return r & -r;
for (;;) {
a >>= __builtin_ctzl(a);
if (a == 1)
return r & -r;
if (a == b)
return a << __builtin_ctzl(r);
if (a < b)
swap(a, b);
a -= b;
}
}
unsigned long gcd4(unsigned long a, unsigned long b)
{
unsigned long r = a | b;
if (!a || !b)
return r;
r &= -r;
while (!(b & r))
b >>= 1;
if (b == r)
return r;
for (;;) {
while (!(a & r))
a >>= 1;
if (a == r)
return r;
if (a == b)
return a;
if (a < b)
swap(a, b);
a -= b;
a >>= 1;
if (a & r)
a += b;
a >>= 1;
}
}
static unsigned long (*gcd_func[])(unsigned long a, unsigned long b) = {
gcd0, gcd1, gcd2, gcd3, gcd4,
};
#define TEST_ENTRIES (sizeof(gcd_func) / sizeof(gcd_func[0]))
#if defined(__x86_64__)
#define rdtscll(val) do { \
unsigned long __a,__d; \
__asm__ __volatile__("rdtsc" : "=a" (__a), "=d" (__d)); \
(val) = ((unsigned long long)__a) | (((unsigned long long)__d)<<32); \
} while(0)
static unsigned long long benchmark_gcd_func(unsigned long (*gcd)(unsigned long, unsigned long),
unsigned long a, unsigned long b, unsigned long *res)
{
unsigned long long start, end;
unsigned long long ret;
unsigned long gcd_res;
rdtscll(start);
gcd_res = gcd(a, b);
rdtscll(end);
if (end >= start)
ret = end - start;
else
ret = ~0ULL - start + 1 + end;
*res = gcd_res;
return ret;
}
#else
static inline struct timespec read_time(void)
{
struct timespec time;
clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &time);
return time;
}
static inline unsigned long long diff_time(struct timespec start, struct timespec end)
{
struct timespec temp;
if ((end.tv_nsec - start.tv_nsec) < 0) {
temp.tv_sec = end.tv_sec - start.tv_sec - 1;
temp.tv_nsec = 1000000000ULL + end.tv_nsec - start.tv_nsec;
} else {
temp.tv_sec = end.tv_sec - start.tv_sec;
temp.tv_nsec = end.tv_nsec - start.tv_nsec;
}
return temp.tv_sec * 1000000000ULL + temp.tv_nsec;
}
static unsigned long long benchmark_gcd_func(unsigned long (*gcd)(unsigned long, unsigned long),
unsigned long a, unsigned long b, unsigned long *res)
{
struct timespec start, end;
unsigned long gcd_res;
start = read_time();
gcd_res = gcd(a, b);
end = read_time();
*res = gcd_res;
return diff_time(start, end);
}
#endif
static inline unsigned long get_rand()
{
if (sizeof(long) == 8)
return (unsigned long)rand() << 32 | rand();
else
return rand();
}
int main(int argc, char **argv)
{
unsigned int seed = time(0);
int loops = 100;
int repeats = 1000;
unsigned long (*res)[TEST_ENTRIES];
unsigned long long elapsed[TEST_ENTRIES];
int i, j, k;
for (;;) {
int opt = getopt(argc, argv, "n:r:s:");
/* End condition always first */
if (opt == -1)
break;
switch (opt) {
case 'n':
loops = atoi(optarg);
break;
case 'r':
repeats = atoi(optarg);
break;
case 's':
seed = strtoul(optarg, NULL, 10);
break;
default:
/* You won't actually get here. */
break;
}
}
res = malloc(sizeof(unsigned long) * TEST_ENTRIES * loops);
memset(elapsed, 0, sizeof(elapsed));
srand(seed);
for (j = 0; j < loops; j++) {
unsigned long a = get_rand();
/* Do we have args? */
unsigned long b = argc > optind ? strtoul(argv[optind], NULL, 10) : get_rand();
unsigned long long min_elapsed[TEST_ENTRIES];
for (k = 0; k < repeats; k++) {
for (i = 0; i < TEST_ENTRIES; i++) {
unsigned long long tmp = benchmark_gcd_func(gcd_func[i], a, b, &res[j][i]);
if (k == 0 || min_elapsed[i] > tmp)
min_elapsed[i] = tmp;
}
}
for (i = 0; i < TEST_ENTRIES; i++)
elapsed[i] += min_elapsed[i];
}
for (i = 0; i < TEST_ENTRIES; i++)
printf("gcd%d: elapsed %llu\n", i, elapsed[i]);
k = 0;
srand(seed);
for (j = 0; j < loops; j++) {
unsigned long a = get_rand();
unsigned long b = argc > optind ? strtoul(argv[optind], NULL, 10) : get_rand();
for (i = 1; i < TEST_ENTRIES; i++) {
if (res[j][i] != res[j][0])
break;
}
if (i < TEST_ENTRIES) {
if (k == 0) {
k = 1;
fprintf(stderr, "Error:\n");
}
fprintf(stderr, "gcd(%lu, %lu): ", a, b);
for (i = 0; i < TEST_ENTRIES; i++)
fprintf(stderr, "%ld%s", res[j][i], i < TEST_ENTRIES - 1 ? ", " : "\n");
}
}
if (k == 0)
fprintf(stderr, "PASS\n");
free(res);
return 0;
}
Compiled with "-O2", on "VirtualBox 4.4.0-22-generic #38-Ubuntu x86_64" got:
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 10174
gcd1: elapsed 2120
gcd2: elapsed 2902
gcd3: elapsed 2039
gcd4: elapsed 2812
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9309
gcd1: elapsed 2280
gcd2: elapsed 2822
gcd3: elapsed 2217
gcd4: elapsed 2710
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9589
gcd1: elapsed 2098
gcd2: elapsed 2815
gcd3: elapsed 2030
gcd4: elapsed 2718
PASS
zhaoxiuzeng@zhaoxiuzeng-VirtualBox:~/develop$ ./gcd -r 500000 -n 10
gcd0: elapsed 9914
gcd1: elapsed 2309
gcd2: elapsed 2779
gcd3: elapsed 2228
gcd4: elapsed 2709
PASS
[akpm@linux-foundation.org: avoid #defining a CONFIG_ variable]
Signed-off-by: Zhaoxiu Zeng <zhaoxiu.zeng@gmail.com>
Signed-off-by: George Spelvin <linux@horizon.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-05-21 08:03:57 +08:00
|
|
|
select CPU_NO_EFFICIENT_FFS
|
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
|
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
|
|
|
|
|
2016-08-31 00:31:22 +08:00
|
|
|
config CPU_CACHE_V7M
|
|
|
|
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.
|
|
|
|
|
2015-04-10 16:46:46 +08:00
|
|
|
config CPU_V7M_NUM_IRQ
|
|
|
|
int "Number of external interrupts connected to the NVIC"
|
|
|
|
depends on CPU_V7M
|
|
|
|
default 90 if ARCH_STM32
|
|
|
|
default 38 if ARCH_EFM32
|
2015-05-20 07:16:46 +08:00
|
|
|
default 112 if SOC_VF610
|
2015-04-10 16:46:46 +08:00
|
|
|
default 240
|
|
|
|
help
|
|
|
|
This option indicates the number of interrupts connected to the NVIC.
|
|
|
|
The value can be larger than the real number of interrupts supported
|
|
|
|
by the system, but must not be lower.
|
|
|
|
The default value is 240, corresponding to the maximum number of
|
|
|
|
interrupts supported by the NVIC on Cortex-M family.
|
|
|
|
|
|
|
|
If unsure, keep default value.
|
|
|
|
|
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.
|
|
|
|
|
2015-04-04 23:58:38 +08:00
|
|
|
config ARM_PV_FIXUP
|
|
|
|
def_bool y
|
|
|
|
depends on ARM_LPAE && ARM_PATCH_PHYS_VIRT && ARCH_KEYSTONE
|
|
|
|
|
2011-11-23 01:30:32 +08:00
|
|
|
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
|
2017-05-19 23:35:56 +08:00
|
|
|
bool "Support Thumb user binaries" if !CPU_THUMBONLY && EXPERT
|
2017-02-09 20:00:16 +08:00
|
|
|
depends on CPU_THUMB_CAPABLE
|
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.
|
|
|
|
|
2017-05-19 23:35:56 +08:00
|
|
|
If this option is disabled, and you run userspace that switches to
|
|
|
|
Thumb mode, signal handling will not work correctly, resulting in
|
|
|
|
segmentation faults or illegal instruction aborts.
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
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)"
|
2016-08-31 00:31:22 +08:00
|
|
|
depends on (CPU_CP15 && !(CPU_ARM720T || CPU_ARM740T || CPU_XSCALE || CPU_XSC3)) || CPU_V7M
|
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)"
|
2016-08-31 00:31:22 +08:00
|
|
|
depends on (CPU_CP15 && !SMP) || CPU_V7M
|
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"
|
2016-08-31 00:31:22 +08:00
|
|
|
depends on CPU_ARM1020 || CPU_V6 || CPU_V6K || CPU_MOHAWK || CPU_XSC3 || CPU_V7 || CPU_FA526 || CPU_V7M
|
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
|
|
|
|
2018-05-14 18:56:36 +08:00
|
|
|
config CPU_SPECTRE
|
|
|
|
bool
|
|
|
|
|
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
|
|
|
|
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.
|
|
|
|
|
2015-03-26 02:16:05 +08:00
|
|
|
config VDSO
|
|
|
|
bool "Enable VDSO for acceleration of some system calls"
|
2015-04-18 04:51:38 +08:00
|
|
|
depends on AEABI && MMU && CPU_V7
|
2015-03-26 02:16:05 +08:00
|
|
|
default y if ARM_ARCH_TIMER
|
|
|
|
select GENERIC_TIME_VSYSCALL
|
|
|
|
help
|
|
|
|
Place in the process address space an ELF shared object
|
|
|
|
providing fast implementations of gettimeofday and
|
|
|
|
clock_gettime. Systems that implement the ARM architected
|
|
|
|
timer will receive maximum benefit.
|
|
|
|
|
|
|
|
You must have glibc 2.22 or later for programs to seamlessly
|
|
|
|
take advantage of this.
|
|
|
|
|
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
|
ARM: move heavy barrier support out of line
The existing memory barrier macro causes a significant amount of code
to be inserted inline at every call site. For example, in
gpio_set_irq_type(), we have this for mb():
c0344c08: f57ff04e dsb st
c0344c0c: e59f8190 ldr r8, [pc, #400] ; c0344da4 <gpio_set_irq_type+0x230>
c0344c10: e3590004 cmp r9, #4
c0344c14: e5983014 ldr r3, [r8, #20]
c0344c18: 0a000054 beq c0344d70 <gpio_set_irq_type+0x1fc>
c0344c1c: e3530000 cmp r3, #0
c0344c20: 0a000004 beq c0344c38 <gpio_set_irq_type+0xc4>
c0344c24: e50b2030 str r2, [fp, #-48] ; 0xffffffd0
c0344c28: e50bc034 str ip, [fp, #-52] ; 0xffffffcc
c0344c2c: e12fff33 blx r3
c0344c30: e51bc034 ldr ip, [fp, #-52] ; 0xffffffcc
c0344c34: e51b2030 ldr r2, [fp, #-48] ; 0xffffffd0
c0344c38: e5963004 ldr r3, [r6, #4]
Moving the outer_cache_sync() call out of line reduces the impact of
the barrier:
c0344968: f57ff04e dsb st
c034496c: e35a0004 cmp sl, #4
c0344970: e50b2030 str r2, [fp, #-48] ; 0xffffffd0
c0344974: 0a000044 beq c0344a8c <gpio_set_irq_type+0x1b8>
c0344978: ebf363dd bl c001d8f4 <arm_heavy_mb>
c034497c: e5953004 ldr r3, [r5, #4]
This should reduce the cache footprint of this code. Overall, this
results in a reduction of around 20K in the kernel size:
text data bss dec hex filename
10773970 667392 10369656 21811018 14ccf4a ../build/imx6/vmlinux-old
10754219 667392 10369656 21791267 14c8223 ../build/imx6/vmlinux-new
Another advantage to this approach is that we can finally resolve the
issue of SoCs which have their own memory barrier requirements within
multiplatform kernels (such as OMAP.) Here, the bus interconnects
need additional handling to ensure that writes become visible in the
correct order (eg, between dma_map() operations, writes to DMA
coherent memory, and MMIO accesses.)
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Richard Woodruff <r-woodruff2@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2015-06-02 06:44:46 +08:00
|
|
|
select ARM_HEAVY_MB
|
2010-03-24 23:47:53 +08:00
|
|
|
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.
|
|
|
|
|
2017-12-01 08:10:09 +08:00
|
|
|
config CACHE_B15_RAC
|
|
|
|
bool "Enable the Broadcom Brahma-B15 read-ahead cache controller"
|
|
|
|
depends on ARCH_BRCMSTB
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
This option enables the Broadcom Brahma-B15 read-ahead cache
|
|
|
|
controller. If disabled, the read-ahead cache remains off.
|
|
|
|
|
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
|
|
|
|
2016-09-02 17:35:18 +08:00
|
|
|
config CACHE_L2X0_PMU
|
|
|
|
bool "L2x0 performance monitor support" if CACHE_L2X0
|
|
|
|
depends on PERF_EVENTS
|
|
|
|
help
|
|
|
|
This option enables support for the performance monitoring features
|
|
|
|
of the L220 and PL310 outer cache controllers.
|
|
|
|
|
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).
|
|
|
|
|
2015-10-02 12:42:19 +08:00
|
|
|
config CACHE_UNIPHIER
|
|
|
|
bool "Enable the UniPhier outer cache controller"
|
|
|
|
depends on ARCH_UNIPHIER
|
2016-10-31 21:37:13 +08:00
|
|
|
select ARM_L1_CACHE_SHIFT_7
|
2015-10-02 12:42:19 +08:00
|
|
|
select OUTER_CACHE
|
|
|
|
select OUTER_CACHE_SYNC
|
|
|
|
help
|
|
|
|
This option enables the UniPhier outer cache (system cache)
|
|
|
|
controller.
|
|
|
|
|
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.
|
|
|
|
|
2016-10-31 21:37:13 +08:00
|
|
|
config ARM_L1_CACHE_SHIFT_7
|
|
|
|
bool
|
|
|
|
help
|
|
|
|
Setting ARM L1 cache line size to 128 Bytes.
|
|
|
|
|
2009-09-15 17:23:53 +08:00
|
|
|
config ARM_L1_CACHE_SHIFT
|
|
|
|
int
|
2016-10-31 21:37:13 +08:00
|
|
|
default 7 if ARM_L1_CACHE_SHIFT_7
|
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
|
2017-05-24 18:24:31 +08:00
|
|
|
bool "Use non-cacheable memory for DMA" if (CPU_V6 || CPU_V6K || CPU_V7M) && !CPU_V7
|
|
|
|
default y if CPU_V6 || CPU_V6K || CPU_V7 || CPU_V7M
|
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.
|
|
|
|
|
2017-05-24 18:24:31 +08:00
|
|
|
On some of the beefier ARMv7-M machines (with DMA and write
|
|
|
|
buffers) you likely want this enabled, while those that
|
|
|
|
didn't need it until now also won't need it in the future.
|
|
|
|
|
2010-05-15 18:02:43 +08:00
|
|
|
You are recommended say 'Y' here and debug any affected drivers.
|
2010-05-18 00:24:04 +08:00
|
|
|
|
ARM: move heavy barrier support out of line
The existing memory barrier macro causes a significant amount of code
to be inserted inline at every call site. For example, in
gpio_set_irq_type(), we have this for mb():
c0344c08: f57ff04e dsb st
c0344c0c: e59f8190 ldr r8, [pc, #400] ; c0344da4 <gpio_set_irq_type+0x230>
c0344c10: e3590004 cmp r9, #4
c0344c14: e5983014 ldr r3, [r8, #20]
c0344c18: 0a000054 beq c0344d70 <gpio_set_irq_type+0x1fc>
c0344c1c: e3530000 cmp r3, #0
c0344c20: 0a000004 beq c0344c38 <gpio_set_irq_type+0xc4>
c0344c24: e50b2030 str r2, [fp, #-48] ; 0xffffffd0
c0344c28: e50bc034 str ip, [fp, #-52] ; 0xffffffcc
c0344c2c: e12fff33 blx r3
c0344c30: e51bc034 ldr ip, [fp, #-52] ; 0xffffffcc
c0344c34: e51b2030 ldr r2, [fp, #-48] ; 0xffffffd0
c0344c38: e5963004 ldr r3, [r6, #4]
Moving the outer_cache_sync() call out of line reduces the impact of
the barrier:
c0344968: f57ff04e dsb st
c034496c: e35a0004 cmp sl, #4
c0344970: e50b2030 str r2, [fp, #-48] ; 0xffffffd0
c0344974: 0a000044 beq c0344a8c <gpio_set_irq_type+0x1b8>
c0344978: ebf363dd bl c001d8f4 <arm_heavy_mb>
c034497c: e5953004 ldr r3, [r5, #4]
This should reduce the cache footprint of this code. Overall, this
results in a reduction of around 20K in the kernel size:
text data bss dec hex filename
10773970 667392 10369656 21811018 14ccf4a ../build/imx6/vmlinux-old
10754219 667392 10369656 21791267 14c8223 ../build/imx6/vmlinux-new
Another advantage to this approach is that we can finally resolve the
issue of SoCs which have their own memory barrier requirements within
multiplatform kernels (such as OMAP.) Here, the bus interconnects
need additional handling to ensure that writes become visible in the
correct order (eg, between dma_map() operations, writes to DMA
coherent memory, and MMIO accesses.)
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Richard Woodruff <r-woodruff2@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2015-06-02 06:44:46 +08:00
|
|
|
config ARM_HEAVY_MB
|
|
|
|
bool
|
|
|
|
|
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
|
|
|
|
2016-01-26 08:19:36 +08:00
|
|
|
config DEBUG_ALIGN_RODATA
|
|
|
|
bool "Make rodata strictly non-executable"
|
2017-02-07 08:31:58 +08:00
|
|
|
depends on STRICT_KERNEL_RWX
|
2014-04-04 04:29:50 +08:00
|
|
|
default y
|
|
|
|
help
|
2016-01-26 08:19:36 +08:00
|
|
|
If this is set, rodata will be made explicitly non-executable. This
|
|
|
|
provides protection on the rare chance that attackers might find and
|
|
|
|
use ROP gadgets that exist in the rodata section. This adds an
|
|
|
|
additional section-aligned split of rodata from kernel text so it
|
|
|
|
can be made explicitly non-executable. This padding may waste memory
|
|
|
|
space to gain the additional protection.
|