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 15:07:57 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
32-bit userspace ABI: introduce ARCH_32BIT_OFF_T config option
All new 32-bit architectures should have 64-bit userspace off_t type, but
existing architectures has 32-bit ones.
To enforce the rule, new config option is added to arch/Kconfig that defaults
ARCH_32BIT_OFF_T to be disabled for new 32-bit architectures. All existing
32-bit architectures enable it explicitly.
New option affects force_o_largefile() behaviour. Namely, if userspace
off_t is 64-bits long, we have no reason to reject user to open big files.
Note that even if architectures has only 64-bit off_t in the kernel
(arc, c6x, h8300, hexagon, nios2, openrisc, and unicore32),
a libc may use 32-bit off_t, and therefore want to limit the file size
to 4GB unless specified differently in the open flags.
Signed-off-by: Yury Norov <ynorov@caviumnetworks.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Yury Norov <ynorov@marvell.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2018-05-16 11:18:49 +03:00
|
|
|
|
2018-11-07 23:14:09 +00:00
|
|
|
|
2026-01-09 11:08:49 +01:00
|
|
|
|
2024-02-15 09:46:32 -05:00
|
|
|
|
2023-06-14 01:39:32 +02:00
|
|
|
|
2025-08-21 14:15:42 -07:00
|
|
|
|
2021-03-30 20:22:07 -07:00
|
|
|
|
2024-08-28 09:02:47 +03:00
|
|
|
|
2020-01-22 13:58:51 +03:00
|
|
|
|
|
|
|
|
|
MIPS/bpf: Enable bpf_probe_read{, str}() on MIPS again
After commit 0ebeea8ca8a4 ("bpf: Restrict bpf_probe_read{, str}() only to
archs where they work"), bpf_probe_read{, str}() functions were no longer
available on MIPS, so there exist some errors when running bpf program:
root@linux:/home/loongson/bcc# python examples/tracing/task_switch.py
bpf: Failed to load program: Invalid argument
[...]
11: (85) call bpf_probe_read#4
unknown func bpf_probe_read#4
[...]
Exception: Failed to load BPF program count_sched: Invalid argument
ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE should be restricted to archs
with non-overlapping address ranges, but they can overlap in EVA mode
on MIPS, so select ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE if !EVA in
arch/mips/Kconfig, otherwise the bpf old helper bpf_probe_read() will
not be available.
This is similar with the commit d195b1d1d119 ("powerpc/bpf: Enable
bpf_probe_read{, str}() on powerpc again").
Fixes: 0ebeea8ca8a4 ("bpf: Restrict bpf_probe_read{, str}() only to archs where they work")
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2021-03-25 20:50:01 +08:00
|
|
|
|
2020-01-22 13:58:51 +03:00
|
|
|
|
2021-05-17 09:22:34 +02:00
|
|
|
|
|
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2024-01-28 10:45:29 -08:00
|
|
|
|
2020-12-03 15:22:51 +08:00
|
|
|
|
2021-04-07 10:35:43 -07:00
|
|
|
|
2015-09-29 12:19:48 +02:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2021-04-29 22:55:15 -07:00
|
|
|
|
2017-06-09 17:26:42 -07:00
|
|
|
|
2017-06-09 17:26:43 -07:00
|
|
|
|
2021-05-04 18:38:13 -07:00
|
|
|
|
2019-09-23 15:39:18 -07:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2021-01-10 11:57:01 +00:00
|
|
|
|
2019-12-04 08:46:31 +08:00
|
|
|
|
2024-12-22 09:04:13 +09:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2018-11-08 23:44:55 +00:00
|
|
|
|
2024-05-07 16:22:00 +01:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2024-12-22 09:04:13 +09:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
|
|
|
|
|
2019-06-21 10:52:46 +01:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
|
|
|
|
|
2018-11-15 20:05:37 +01:00
|
|
|
|
2018-04-11 08:50:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-11 11:48:49 +01:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
|
|
|
|
|
2023-05-21 23:31:23 +01:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2022-10-21 14:51:44 +02:00
|
|
|
|
2023-03-23 17:33:52 +01:00
|
|
|
|
MIPS: Workaround GCC __builtin_unreachable reordering bug
Some versions of GCC for the MIPS architecture suffer from a bug which
can lead to instructions from beyond an unreachable statement being
incorrectly reordered into earlier branch delay slots if the unreachable
statement is the only content of a case in a switch statement. This can
lead to seemingly random behaviour, such as invalid memory accesses from
incorrectly reordered loads or stores, and link failures on microMIPS
builds.
See this potential GCC fix for details:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00360.html
Runtime problems resulting from this bug were initially observed using a
maltasmvp_defconfig v4.4 kernel built using GCC 4.9.2 (from a Codescape
SDK 2015.06-05 toolchain), with the result being an address exception
taken after log messages about the L1 caches (during probe of the L2
cache):
Initmem setup node 0 [mem 0x0000000080000000-0x000000009fffffff]
VPE topology {2,2} total 4
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 64kB, 4-way, PIPT, no aliases, linesize 32 bytes
<AdEL exception here>
This is early enough that the kernel exception vectors are not in use,
so any further output depends upon the bootloader. This is reproducible
in QEMU where no further output occurs - ie. the system hangs here.
Given the nature of the bug it may potentially be hit with differing
symptoms. The bug is known to affect GCC versions as recent as 7.3, and
it is unclear whether GCC 8 fixed it or just happens not to encounter
the bug in the testcase found at the link above due to differing
optimizations.
This bug can be worked around by placing a volatile asm statement, which
GCC is prevented from reordering past, prior to the
__builtin_unreachable call.
That was actually done already for other reasons by commit 173a3efd3edb
("bug.h: work around GCC PR82365 in BUG()"), but creates problems for
microMIPS builds due to the lack of a .insn directive. The microMIPS ISA
allows for interlinking with regular MIPS32 code by repurposing bit 0 of
the program counter as an ISA mode bit. To switch modes one changes the
value of this bit in the PC. However typical branch instructions encode
their offsets as multiples of 2-byte instruction halfwords, which means
they cannot change ISA mode - this must be done using either an indirect
branch (a jump-register in MIPS terminology) or a dedicated jalx
instruction. In order to ensure that regular branches don't attempt to
target code in a different ISA which they can't actually switch to, the
linker will check that branch targets are code in the same ISA as the
branch.
Unfortunately our empty asm volatile statements don't qualify as code,
and the link for microMIPS builds fails with errors such as:
arch/mips/mm/dma-default.s:3265: Error: branch to a symbol in another ISA mode
arch/mips/mm/dma-default.s:5027: Error: branch to a symbol in another ISA mode
Resolve this by adding a .insn directive within the asm statement which
declares that what comes next is code. This may or may not be true,
since we don't really know what comes next, but as this code is in an
unreachable path anyway that doesn't matter since we won't execute it.
We do this in asm/compiler.h & select CONFIG_HAVE_ARCH_COMPILER_H in
order to have this included by linux/compiler_types.h after
linux/compiler-gcc.h. This will result in asm/compiler.h being included
in all C compilations via the -include linux/compiler_types.h argument
in c_flags, which should be harmless.
Signed-off-by: Paul Burton <paul.burton@mips.com>
Fixes: 173a3efd3edb ("bug.h: work around GCC PR82365 in BUG()")
Patchwork: https://patchwork.linux-mips.org/patch/20270/
Cc: James Hogan <jhogan@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: linux-mips@linux-mips.org
2018-08-20 15:36:18 -07:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2021-01-22 12:02:51 +01:00
|
|
|
|
2016-11-24 17:32:45 +00:00
|
|
|
|
|
|
|
|
|
2014-01-22 14:40:04 +00:00
|
|
|
|
2012-08-17 08:22:04 +02:00
|
|
|
|
2019-07-15 17:40:01 -04:00
|
|
|
|
2019-08-19 14:54:20 +09:00
|
|
|
|
2022-06-08 16:40:24 +02:00
|
|
|
|
2020-01-27 16:41:52 +01:00
|
|
|
|
2010-10-27 18:59:09 +08:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-28 11:33:05 +00:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2024-04-02 14:55:15 +02:00
|
|
|
|
MIPS: Tracing: Add function graph tracer support for MIPS
The implementation of function graph tracer for MIPS is a little
different from X86.
in MIPS, gcc(with -pg) only transfer the caller's return address(at) and
the _mcount's return address(ra) to us.
For the kernel part without -mlong-calls:
move at, ra
jal _mcount
For the module part with -mlong-calls:
lui v1, hi16bit_of_mcount
addiu v1, v1, low16bit_of_mcount
move at, ra
jal _mcount
Without -mlong-calls,
if the function is a leaf, it will not save the return address(ra):
ffffffff80101298 <au1k_wait>:
ffffffff80101298: 67bdfff0 daddiu sp,sp,-16
ffffffff8010129c: ffbe0008 sd s8,8(sp)
ffffffff801012a0: 03a0f02d move s8,sp
ffffffff801012a4: 03e0082d move at,ra
ffffffff801012a8: 0c042930 jal ffffffff8010a4c0 <_mcount>
ffffffff801012ac: 00020021 nop
so, we can hijack it directly in _mcount, but if the function is non-leaf, the
return address is saved in the stack.
ffffffff80133030 <copy_process>:
ffffffff80133030: 67bdff50 daddiu sp,sp,-176
ffffffff80133034: ffbe00a0 sd s8,160(sp)
ffffffff80133038: 03a0f02d move s8,sp
ffffffff8013303c: ffbf00a8 sd ra,168(sp)
ffffffff80133040: ffb70098 sd s7,152(sp)
ffffffff80133044: ffb60090 sd s6,144(sp)
ffffffff80133048: ffb50088 sd s5,136(sp)
ffffffff8013304c: ffb40080 sd s4,128(sp)
ffffffff80133050: ffb30078 sd s3,120(sp)
ffffffff80133054: ffb20070 sd s2,112(sp)
ffffffff80133058: ffb10068 sd s1,104(sp)
ffffffff8013305c: ffb00060 sd s0,96(sp)
ffffffff80133060: 03e0082d move at,ra
ffffffff80133064: 0c042930 jal ffffffff8010a4c0 <_mcount>
ffffffff80133068: 00020021 nop
but we can not get the exact stack address(which saved ra) directly in
_mcount, we need to search the content of at register in the stack space
or search the "s{d,w} ra, offset(sp)" instruction in the text. 'Cause we
can not prove there is only a match in the stack space, so, we search
the text instead.
as we can see, if the first instruction above "move at, ra" is not a
store instruction, there should be a leaf function, so we hijack the at
register directly via putting &return_to_handler into it, otherwise, we
search the "s{d,w} ra, offset(sp)" instruction to get the stack offset,
and then the stack address. we use the above copy_process() as an
example, we at last find "ffbf00a8", 0xa8 is the stack offset, we plus
it with s8(fp), that is the stack address, we hijack the content via
writing the &return_to_handler in.
If with -mlong-calls, since there are two more instructions above "move
at, ra", so, we can move the pointer to the position above "lui v1,
hi16bit_of_mcount".
Signed-off-by: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Nicholas Mc Guire <der.herr@hofr.at>
Cc: zhangfx@lemote.com
Cc: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org
Cc: linux-mips@linux-mips.org
Patchwork: http://patchwork.linux-mips.org/patch/677/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2009-11-20 20:34:34 +08:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2020-01-22 13:58:51 +03:00
|
|
|
|
|
|
|
|
|
2018-10-29 18:27:41 -07:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
|
|
|
|
|
2010-08-03 11:22:20 -07:00
|
|
|
|
|
|
|
|
|
2018-11-21 21:56:36 +00:00
|
|
|
|
2012-09-28 14:31:03 +09:30
|
|
|
|
2016-05-20 17:00:33 -07:00
|
|
|
|
2024-02-23 23:18:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2021-02-04 11:35:22 +08:00
|
|
|
|
|
|
|
|
|
2016-09-02 10:13:21 +02:00
|
|
|
|
2018-06-14 10:13:53 -07:00
|
|
|
|
2019-11-15 23:44:49 +00:00
|
|
|
|
2018-06-14 19:36:45 +09:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2017-10-04 03:46:14 +01:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2018-11-15 20:05:37 +01:00
|
|
|
|
2023-06-22 18:47:40 +02:00
|
|
|
|
2026-01-27 20:12:57 +08:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2020-01-22 13:58:51 +03:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2020-09-28 12:13:07 +02:00
|
|
|
|
2018-08-28 16:26:30 +02:00
|
|
|
|
2017-05-15 10:46:35 +01:00
|
|
|
|
2021-07-31 14:22:32 +09:00
|
|
|
|
2020-06-14 00:18:12 -04:00
|
|
|
|
2022-01-31 11:17:09 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2020-04-16 17:00:07 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-06 21:29:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 18:42:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-06 21:29:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2020-09-06 21:29:25 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2020-09-06 21:29:25 +02:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
2020-09-06 21:29:25 +02:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-22 13:58:51 +03:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
2021-02-10 10:56:41 +01:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
2024-02-16 18:42:21 +01:00
|
|
|
|
2018-07-27 18:23:21 -07:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-23 14:08:13 +00:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
|
|
|
|
|
2023-05-29 14:52:45 +01:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-29 14:52:45 +01:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-22 13:58:51 +03:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-06 21:29:29 +02:00
|
|
|
|
2020-01-22 13:58:51 +03:00
|
|
|
|
2018-01-17 19:56:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-07-15 21:45:04 +02:00
|
|
|
|
2007-05-11 20:44:30 +09:00
|
|
|
|
2018-04-03 16:24:20 +02:00
|
|
|
|
2012-11-30 17:27:27 +01:00
|
|
|
|
2012-11-14 23:34:17 -06:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2021-02-10 10:56:40 +01:00
|
|
|
|
2020-04-16 17:00:07 +02:00
|
|
|
|
2010-07-15 21:45:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2009-10-14 18:12:16 +08:00
|
|
|
|
2014-07-23 16:36:48 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2014-10-29 03:18:38 +04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2014-10-29 03:18:41 +04:00
|
|
|
|
2014-10-29 03:18:38 +04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-29 03:18:42 +04:00
|
|
|
|
2014-10-29 03:18:38 +04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-04 21:28:14 +01:00
|
|
|
|
|
|
|
|
|
2015-08-03 19:23:52 +02:00
|
|
|
|
2011-01-04 21:28:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2018-07-20 13:58:20 +02:00
|
|
|
|
2015-04-19 14:30:04 +02:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2011-01-04 21:28:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-29 01:49:24 +02:00
|
|
|
|
2016-01-26 09:38:29 +01:00
|
|
|
|
2015-05-31 01:52:25 +02:00
|
|
|
|
2018-03-24 23:47:22 +01:00
|
|
|
|
2011-01-04 21:28:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-25 09:49:00 -08:00
|
|
|
|
|
|
|
|
|
2020-06-17 12:50:33 +02:00
|
|
|
|
2018-06-15 13:08:52 +02:00
|
|
|
|
2014-10-20 21:28:05 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-22 14:30:14 +00:00
|
|
|
|
2014-12-25 09:49:17 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2014-12-25 09:49:17 -08:00
|
|
|
|
2014-10-20 21:28:05 -07:00
|
|
|
|
2014-12-25 09:49:17 -08:00
|
|
|
|
2014-10-20 21:28:05 -07:00
|
|
|
|
|
|
|
|
|
2014-12-25 09:49:17 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-20 21:28:05 -07:00
|
|
|
|
|
|
|
|
|
2014-12-25 09:49:17 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-24 10:55:16 -07:00
|
|
|
|
2021-11-08 11:24:31 -08:00
|
|
|
|
|
|
|
|
|
2022-07-15 14:37:47 -07:00
|
|
|
|
2014-10-20 21:28:05 -07:00
|
|
|
|
2014-12-25 09:49:00 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-20 21:28:05 -07:00
|
|
|
|
2007-09-25 15:40:12 +02:00
|
|
|
|
2010-03-25 11:42:41 +01:00
|
|
|
|
2012-12-26 20:06:17 +00:00
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
2007-11-24 22:33:28 +00:00
|
|
|
|
2007-09-25 15:40:12 +02:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2013-07-23 15:40:37 +01:00
|
|
|
|
2012-12-26 20:06:18 +00:00
|
|
|
|
2007-09-25 15:40:12 +02:00
|
|
|
|
|
|
|
|
|
2014-04-29 01:49:24 +02:00
|
|
|
|
2018-01-17 00:21:44 +02:00
|
|
|
|
2007-09-25 15:41:24 +02:00
|
|
|
|
2014-03-26 21:40:25 +01:00
|
|
|
|
2014-06-17 16:36:50 +02:00
|
|
|
|
|
|
|
|
|
2015-06-10 23:05:08 +02:00
|
|
|
|
2016-01-25 09:50:29 +01:00
|
|
|
|
2017-11-14 17:16:27 +00:00
|
|
|
|
2007-09-25 15:40:12 +02:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2007-09-25 15:40:12 +02:00
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
|
|
|
|
|
2013-06-18 16:55:39 +00:00
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
|
|
|
|
|
2014-07-08 16:26:13 +02:00
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-06 08:49:11 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2014-01-14 09:54:40 -08:00
|
|
|
|
2020-04-08 23:44:13 -07:00
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-05-09 23:34:53 +02:00
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
2007-11-24 22:33:28 +00:00
|
|
|
|
2007-10-22 19:43:15 +09:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2007-10-11 23:46:10 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2007-09-13 23:51:26 +09:00
|
|
|
|
2007-03-14 21:51:26 +09:00
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2007-03-02 12:42:33 +09:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
2008-01-15 19:42:57 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2014-03-26 21:40:25 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2006-05-09 23:34:53 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2008-04-25 12:11:44 +09:00
|
|
|
|
2014-04-06 21:46:05 +01:00
|
|
|
|
2008-04-24 09:48:40 +09:00
|
|
|
|
2014-04-06 21:46:05 +01:00
|
|
|
|
2007-10-23 12:43:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2014-04-07 15:39:19 -07:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
2013-01-16 18:53:19 -08:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-14 09:54:38 -08:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-08-29 14:21:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-07 13:44:57 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-21 21:33:33 +00:00
|
|
|
|
2025-05-07 13:44:57 +00:00
|
|
|
|
|
|
|
|
|
2025-05-21 21:33:33 +00:00
|
|
|
|
2025-05-07 13:44:57 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2006-05-09 23:34:53 +02:00
|
|
|
|
2019-10-09 15:27:14 +02:00
|
|
|
|
|
|
|
|
|
2018-02-05 15:37:43 +01:00
|
|
|
|
2018-02-05 16:40:00 +01:00
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
2007-11-24 22:33:28 +00:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2011-06-01 19:05:10 +01:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2007-10-11 23:46:10 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2013-01-16 18:53:19 -08:00
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
2021-01-22 12:02:50 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2020-09-06 21:29:31 +02:00
|
|
|
|
2015-05-24 16:11:13 +01:00
|
|
|
|
2020-09-06 21:29:31 +02:00
|
|
|
|
|
|
|
|
|
2024-02-16 18:42:21 +01:00
|
|
|
|
2012-03-30 16:48:05 +02:00
|
|
|
|
2021-05-30 18:17:59 +01:00
|
|
|
|
|
|
|
|
|
2010-06-19 04:08:19 +00:00
|
|
|
|
2011-03-30 09:27:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2011-03-30 09:27:47 +02:00
|
|
|
|
|
|
|
|
|
2023-01-15 13:19:22 +01:00
|
|
|
|
2011-03-30 09:27:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-29 01:49:24 +02:00
|
|
|
|
2011-03-30 09:27:47 +02:00
|
|
|
|
2018-01-15 20:54:35 +00:00
|
|
|
|
2011-03-30 09:27:47 +02:00
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2011-03-30 09:27:47 +02:00
|
|
|
|
|
|
|
|
|
2020-04-08 23:44:13 -07:00
|
|
|
|
2012-04-13 20:56:13 +02:00
|
|
|
|
2012-08-28 12:44:59 +02:00
|
|
|
|
|
|
|
|
|
2013-09-03 13:18:12 +02:00
|
|
|
|
|
|
|
|
|
2011-03-30 09:27:47 +02:00
|
|
|
|
2015-04-21 10:00:35 +08:00
|
|
|
|
MIPS: Loongson: Unify LOONGSON3/LOONGSON64 Kconfig usage
There are mixed LOONGSON3/LOONGSON64 usages in recently changes, let's
establish some rules:
1, In Kconfig symbols, we only use CPU_LOONGSON64, MACH_LOONGSON64 and
SYS_HAS_CPU_LOONGSON64, all other derived symbols use "LOONGSON3" since
they all not widely-used symbols and sometimes not suitable for all
64-bit Loongson processors. E.g., we use symbols LOONGSON3_ENHANCEMENT,
CPU_LOONGSON3_WORKAROUNDS, etc.
2, Hide GSx64/GSx64E in Kconfig title since it is not useful for
general users. However, in the full description we use a more detailed
manner. E.g., GS264/GS464/GS464E/GS464V.
All Kconfig titles and descriptions of Loongson processors and machines
have also been updated in this patch for consistency.
Signed-off-by: Huacai Chen <chenhc@lemote.com>
Signed-off-by: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: James Hogan <jhogan@kernel.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org
Cc: linux-mips@vger.kernel.org
Cc: Fuxin Zhang <zhangfx@lemote.com>
Cc: Zhangjin Wu <wuzhangjin@gmail.com>
Cc: Huacai Chen <chenhuacai@gmail.com>
2019-11-04 14:11:21 +08:00
|
|
|
|
2025-07-16 19:25:16 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-01-04 17:16:46 +08:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
2015-04-21 10:00:35 +08:00
|
|
|
|
2009-07-02 23:26:45 +08:00
|
|
|
|
2015-04-21 10:00:35 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
2019-10-20 22:43:14 +08:00
|
|
|
|
|
|
|
|
|
2012-07-25 16:17:24 +02:00
|
|
|
|
|
|
|
|
|
2019-10-20 22:43:14 +08:00
|
|
|
|
2012-07-25 16:17:24 +02:00
|
|
|
|
2019-10-20 22:43:14 +08:00
|
|
|
|
MIPS: Loongson: Unify LOONGSON3/LOONGSON64 Kconfig usage
There are mixed LOONGSON3/LOONGSON64 usages in recently changes, let's
establish some rules:
1, In Kconfig symbols, we only use CPU_LOONGSON64, MACH_LOONGSON64 and
SYS_HAS_CPU_LOONGSON64, all other derived symbols use "LOONGSON3" since
they all not widely-used symbols and sometimes not suitable for all
64-bit Loongson processors. E.g., we use symbols LOONGSON3_ENHANCEMENT,
CPU_LOONGSON3_WORKAROUNDS, etc.
2, Hide GSx64/GSx64E in Kconfig title since it is not useful for
general users. However, in the full description we use a more detailed
manner. E.g., GS264/GS464/GS464E/GS464V.
All Kconfig titles and descriptions of Loongson processors and machines
have also been updated in this patch for consistency.
Signed-off-by: Huacai Chen <chenhc@lemote.com>
Signed-off-by: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: James Hogan <jhogan@kernel.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org
Cc: linux-mips@vger.kernel.org
Cc: Fuxin Zhang <zhangfx@lemote.com>
Cc: Zhangjin Wu <wuzhangjin@gmail.com>
Cc: Huacai Chen <chenhuacai@gmail.com>
2019-11-04 14:11:21 +08:00
|
|
|
|
2023-11-07 11:15:19 +00:00
|
|
|
|
2019-10-20 23:01:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-14 10:41:05 +08:00
|
|
|
|
2019-10-20 23:01:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-27 14:34:34 +08:00
|
|
|
|
2020-03-31 15:00:06 +08:00
|
|
|
|
2019-10-20 23:01:36 +08:00
|
|
|
|
2020-05-26 17:21:16 +08:00
|
|
|
|
2019-10-20 23:01:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-20 22:43:14 +08:00
|
|
|
|
2020-11-25 18:07:46 +08:00
|
|
|
|
2019-10-20 23:01:36 +08:00
|
|
|
|
2020-03-25 11:55:02 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-29 14:58:37 +08:00
|
|
|
|
2019-10-20 22:43:14 +08:00
|
|
|
|
MIPS: Loongson: Unify LOONGSON3/LOONGSON64 Kconfig usage
There are mixed LOONGSON3/LOONGSON64 usages in recently changes, let's
establish some rules:
1, In Kconfig symbols, we only use CPU_LOONGSON64, MACH_LOONGSON64 and
SYS_HAS_CPU_LOONGSON64, all other derived symbols use "LOONGSON3" since
they all not widely-used symbols and sometimes not suitable for all
64-bit Loongson processors. E.g., we use symbols LOONGSON3_ENHANCEMENT,
CPU_LOONGSON3_WORKAROUNDS, etc.
2, Hide GSx64/GSx64E in Kconfig title since it is not useful for
general users. However, in the full description we use a more detailed
manner. E.g., GS264/GS464/GS464E/GS464V.
All Kconfig titles and descriptions of Loongson processors and machines
have also been updated in this patch for consistency.
Signed-off-by: Huacai Chen <chenhc@lemote.com>
Signed-off-by: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: James Hogan <jhogan@kernel.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org
Cc: linux-mips@vger.kernel.org
Cc: Fuxin Zhang <zhangfx@lemote.com>
Cc: Zhangjin Wu <wuzhangjin@gmail.com>
Cc: Huacai Chen <chenhuacai@gmail.com>
2019-11-04 14:11:21 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-25 16:17:24 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-05-09 23:34:53 +02:00
|
|
|
|
2005-09-15 08:52:34 +00:00
|
|
|
|
2018-02-05 15:37:43 +01:00
|
|
|
|
2018-02-05 16:40:00 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2008-01-29 10:15:00 +00:00
|
|
|
|
2015-05-22 16:51:02 +01:00
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
2014-10-20 12:03:58 -07:00
|
|
|
|
2015-08-22 02:40:41 -07:00
|
|
|
|
2018-11-12 19:00:59 +02:00
|
|
|
|
2021-02-10 10:56:40 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2011-06-01 19:05:10 +01:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2007-10-11 23:46:10 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2018-11-12 19:00:59 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2006-06-20 17:15:20 +01:00
|
|
|
|
2018-11-12 19:00:59 +02:00
|
|
|
|
2014-10-20 21:27:57 -07:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2018-11-12 19:00:59 +02:00
|
|
|
|
2025-07-13 12:04:34 +02:00
|
|
|
|
2015-09-22 11:58:43 -07:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
2014-01-16 13:12:36 +00:00
|
|
|
|
2015-02-26 18:16:38 -06:00
|
|
|
|
2014-11-19 11:31:56 +00:00
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2012-07-19 09:11:15 +02:00
|
|
|
|
2014-11-19 11:31:56 +00:00
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2015-02-26 18:16:38 -06:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2014-11-15 22:07:07 +00:00
|
|
|
|
2018-11-12 19:00:59 +02:00
|
|
|
|
2014-01-15 10:31:56 +00:00
|
|
|
|
2006-06-05 17:24:46 +01:00
|
|
|
|
2018-11-12 19:00:59 +02:00
|
|
|
|
2007-02-02 17:41:47 +01:00
|
|
|
|
2018-01-15 20:54:35 +00:00
|
|
|
|
2009-10-14 18:12:16 +08:00
|
|
|
|
2015-05-22 16:51:02 +01:00
|
|
|
|
2020-08-24 18:32:48 +02:00
|
|
|
|
2015-04-27 15:07:19 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2005-02-02 22:23:46 +00:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2016-01-13 18:15:39 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MIPS: mobileye: Add EyeQ6H support
EyeQ6H (or “High”) is an other SoC from Mobileye still based on the
MIPS I6500 architecture as the EyeQ5. The 2 clusters of this SoC
contains 4 cores which are capable of running 4 threads. Besides this,
it features multiple controllers such as the classic UART, high speed
I2C, SPI, as well as CAN-FD, PCIe Gen4, Octal/Quad SPI Flash
interface, Gigabit Ethernet, MIPI CSI-2, MIPI DSI, and eMMC 5.1. It
also includes a Hardware Security Module, Functional Safety Hardware,
and video encoders and more.
This commit provides the infrastructure to build a kernel running on
EyeQ6H SoC. For now the support is limited and only one CPU core is
running.
Reviewed-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2024-05-13 20:34:17 +02:00
|
|
|
|
|
|
|
|
|
2024-02-16 18:42:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-10-27 17:15:35 +01:00
|
|
|
|
2024-02-16 18:42:22 +01:00
|
|
|
|
MIPS: mobileye: Add EyeQ6H support
EyeQ6H (or “High”) is an other SoC from Mobileye still based on the
MIPS I6500 architecture as the EyeQ5. The 2 clusters of this SoC
contains 4 cores which are capable of running 4 threads. Besides this,
it features multiple controllers such as the classic UART, high speed
I2C, SPI, as well as CAN-FD, PCIe Gen4, Octal/Quad SPI Flash
interface, Gigabit Ethernet, MIPI CSI-2, MIPI DSI, and eMMC 5.1. It
also includes a Hardware Security Module, Functional Safety Hardware,
and video encoders and more.
This commit provides the infrastructure to build a kernel running on
EyeQ6H SoC. For now the support is limited and only one CPU core is
running.
Reviewed-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2024-05-13 20:34:17 +02:00
|
|
|
|
2024-02-16 18:42:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-13 17:11:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-20 22:05:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-31 13:51:18 +02:00
|
|
|
|
2013-01-20 22:05:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2013-01-20 22:05:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-29 01:49:24 +02:00
|
|
|
|
2020-10-13 10:05:47 +08:00
|
|
|
|
2013-01-20 22:05:30 +01:00
|
|
|
|
2013-09-04 00:16:59 +02:00
|
|
|
|
|
|
|
|
|
2013-01-20 22:05:30 +01:00
|
|
|
|
2021-01-19 10:21:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 18:42:21 +01:00
|
|
|
|
2021-01-19 10:21:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-10 16:35:22 +12:00
|
|
|
|
2021-01-19 10:21:07 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-05-09 23:34:53 +02:00
|
|
|
|
2019-10-09 15:27:17 +02:00
|
|
|
|
2019-10-09 15:27:14 +02:00
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
|
|
|
|
|
2018-02-05 16:40:00 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
2007-11-24 22:33:28 +00:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2018-11-15 20:05:37 +01:00
|
|
|
|
2007-10-11 23:46:10 +01:00
|
|
|
|
2007-11-23 20:34:16 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2006-11-30 01:14:51 +00:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
2008-07-16 14:06:15 +02:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
2019-10-09 15:27:17 +02:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2020-08-24 18:32:43 +02:00
|
|
|
|
2020-08-24 18:32:44 +02:00
|
|
|
|
2020-08-24 18:32:45 +02:00
|
|
|
|
2014-01-14 09:54:38 -08:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-05-09 23:34:53 +02:00
|
|
|
|
2018-06-15 13:08:44 +02:00
|
|
|
|
2019-09-16 14:13:10 +03:00
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
|
|
|
|
|
2019-10-22 18:13:15 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
2021-03-01 08:38:32 +01:00
|
|
|
|
2007-03-01 11:56:43 +00:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2019-02-19 16:57:20 +01:00
|
|
|
|
2019-05-07 23:09:15 +02:00
|
|
|
|
2007-02-06 16:53:15 +00:00
|
|
|
|
2019-05-07 23:09:13 +02:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2006-06-11 23:03:08 +01:00
|
|
|
|
2006-11-02 17:23:33 +00:00
|
|
|
|
2020-08-24 18:32:49 +02:00
|
|
|
|
2014-01-14 09:54:38 -08:00
|
|
|
|
MIPS: SGI-IP27: always enable NUMA in Kconfig
When a configuration has NUMA disabled and SGI_IP27 enabled, the build
fails:
CC kernel/bounds.s
CC arch/mips/kernel/asm-offsets.s
In file included from arch/mips/include/asm/topology.h:11,
from include/linux/topology.h:36,
from include/linux/gfp.h:9,
from include/linux/slab.h:15,
from include/linux/crypto.h:19,
from include/crypto/hash.h:11,
from include/linux/uio.h:10,
from include/linux/socket.h:8,
from include/linux/compat.h:15,
from arch/mips/kernel/asm-offsets.c:12:
include/linux/topology.h: In function 'numa_node_id':
arch/mips/include/asm/mach-ip27/topology.h:16:27: error: implicit declaration of function 'cputonasid'; did you mean 'cpu_vpe_id'? [-Werror=implicit-function-declaration]
#define cpu_to_node(cpu) (cputonasid(cpu))
^~~~~~~~~~
include/linux/topology.h:119:9: note: in expansion of macro 'cpu_to_node'
return cpu_to_node(raw_smp_processor_id());
^~~~~~~~~~~
include/linux/topology.h: In function 'cpu_cpu_mask':
arch/mips/include/asm/mach-ip27/topology.h:19:7: error: implicit declaration of function 'hub_data' [-Werror=implicit-function-declaration]
&hub_data(node)->h_cpus)
^~~~~~~~
include/linux/topology.h:210:9: note: in expansion of macro 'cpumask_of_node'
return cpumask_of_node(cpu_to_node(cpu));
^~~~~~~~~~~~~~~
arch/mips/include/asm/mach-ip27/topology.h:19:21: error: invalid type argument of '->' (have 'int')
&hub_data(node)->h_cpus)
^~
include/linux/topology.h:210:9: note: in expansion of macro 'cpumask_of_node'
return cpumask_of_node(cpu_to_node(cpu));
^~~~~~~~~~~~~~~
Before switch from discontigmem to sparsemem, there always was
CONFIG_NEED_MULTIPLE_NODES=y because it was selected by DISCONTIGMEM.
Without DISCONTIGMEM it is possible to have SPARSEMEM without NUMA for
SGI_IP27 and as many things there rely on custom node definition, the
build breaks.
As Thomas noted "... there are right now too many places in IP27 code,
which assumes NUMA enabled", the simplest solution would be to always
enable NUMA for SGI-IP27 builds.
Reported-by: kernel test robot <lkp@intel.com>
Fixes: 397dc00e249e ("mips: sgi-ip27: switch from DISCONTIGMEM to SPARSEMEM")
Cc: stable@vger.kernel.org
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-08-05 15:51:41 +03:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
2013-01-16 18:53:19 -08:00
|
|
|
|
2019-10-09 15:27:17 +02:00
|
|
|
|
2019-10-09 15:27:14 +02:00
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
|
|
|
|
|
2018-02-05 16:40:00 +01:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2018-11-15 20:05:37 +01:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-10 20:29:55 +02:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-09 15:27:17 +02:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:49 +02:00
|
|
|
|
2014-08-19 22:00:07 +02:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
2019-10-24 12:18:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-03-01 08:38:32 +01:00
|
|
|
|
2019-10-24 12:18:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:49 +02:00
|
|
|
|
2019-10-24 12:18:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2007-07-10 17:33:00 +01:00
|
|
|
|
2019-10-09 15:27:14 +02:00
|
|
|
|
|
|
|
|
|
2018-06-15 13:08:48 +02:00
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
2007-11-24 22:33:28 +00:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-19 14:55:42 +00:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2020-08-24 18:32:48 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2006-05-09 23:34:53 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 15:21:24 +01:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-04-18 15:26:36 +02:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-03 02:05:43 +00:00
|
|
|
|
MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur
The Broadcom SiByte BCM1250, BCM1125, and BCM1125H SOCs have an onchip
DRAM controller that supports memory amounts of up to 16GiB, and due to
how the address decoder has been wired in the SOC any memory beyond 1GiB
is actually mapped starting from 4GiB physical up, that is beyond the
32-bit addressable limit[1]. Consequently if the maximum amount of
memory has been installed, then it will span up to 19GiB.
Many of the evaluation boards we support that are based on one of these
SOCs have their memory soldered and the amount present fits in the
32-bit address range. The BCM91250A SWARM board however has actual DIMM
slots and accepts, depending on the peripherals revision of the SOC, up
to 4GiB or 8GiB of memory in commercially available JEDEC modules[2].
I believe this is also the case with the BCM91250C2 LittleSur board.
This means that up to either 3GiB or 7GiB of memory requires 64-bit
addressing to access.
I believe the BCM91480B BigSur board, which has the BCM1480 SOC instead,
accepts at least as much memory, although I have no documentation or
actual hardware available to verify that.
Both systems have PCI slots installed for use by any PCI option boards,
including ones that only support 32-bit addressing (additionally the
32-bit PCI host bridge of the BCM1250, BCM1125, and BCM1125H SOCs limits
addressing to 32-bits), and there is no IOMMU available. Therefore for
PCI DMA to work in the presence of memory beyond enable swiotlb for the
affected systems.
All the other SOC onchip DMA devices use 40-bit addressing and therefore
can address the whole memory, so only enable swiotlb if PCI support and
support for DMA beyond 4GiB have been both enabled in the configuration
of the kernel.
This shows up as follows:
Broadcom SiByte BCM1250 B2 @ 800 MHz (SB1 rev 2)
Board type: SiByte BCM91250A (SWARM)
Determined physical RAM map:
memory: 000000000fe7fe00 @ 0000000000000000 (usable)
memory: 000000001ffffe00 @ 0000000080000000 (usable)
memory: 000000000ffffe00 @ 00000000c0000000 (usable)
memory: 0000000087fffe00 @ 0000000100000000 (usable)
software IO TLB: mapped [mem 0xcbffc000-0xcfffc000] (64MB)
in the bootstrap log and removes failures like these:
defxx 0000:02:00.0: dma_direct_map_page: overflow 0x0000000185bc6080+4608 of device mask ffffffff bus mask 0
fddi0: Receive buffer allocation failed
fddi0: Adapter open failed!
IP-Config: Failed to open fddi0
defxx 0000:09:08.0: dma_direct_map_page: overflow 0x0000000185bc6080+4608 of device mask ffffffff bus mask 0
fddi1: Receive buffer allocation failed
fddi1: Adapter open failed!
IP-Config: Failed to open fddi1
when memory beyond 4GiB is handed out to devices that can only do 32-bit
addressing.
This updates commit cce335ae47e2 ("[MIPS] 64-bit Sibyte kernels need
DMA32.").
References:
[1] "BCM1250/BCM1125/BCM1125H User Manual", Revision 1250_1125-UM100-R,
Broadcom Corporation, 21 Oct 2002, Section 3: "System Overview",
"Memory Map", pp. 34-38
[2] "BCM91250A User Manual", Revision 91250A-UM100-R, Broadcom
Corporation, 18 May 2004, Section 3: "Physical Description",
"Supported DRAM", p. 23
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
[paul.burton@mips.com: Remove GPL text from dma.c; SPDX tag covers it]
Signed-off-by: Paul Burton <paul.burton@mips.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Patchwork: https://patchwork.linux-mips.org/patch/21108/
References: cce335ae47e2 ("[MIPS] 64-bit Sibyte kernels need DMA32.")
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
2018-11-13 22:42:44 +00:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-04-18 15:26:36 +02:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-13 22:42:37 +00:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur
The Broadcom SiByte BCM1250, BCM1125, and BCM1125H SOCs have an onchip
DRAM controller that supports memory amounts of up to 16GiB, and due to
how the address decoder has been wired in the SOC any memory beyond 1GiB
is actually mapped starting from 4GiB physical up, that is beyond the
32-bit addressable limit[1]. Consequently if the maximum amount of
memory has been installed, then it will span up to 19GiB.
Many of the evaluation boards we support that are based on one of these
SOCs have their memory soldered and the amount present fits in the
32-bit address range. The BCM91250A SWARM board however has actual DIMM
slots and accepts, depending on the peripherals revision of the SOC, up
to 4GiB or 8GiB of memory in commercially available JEDEC modules[2].
I believe this is also the case with the BCM91250C2 LittleSur board.
This means that up to either 3GiB or 7GiB of memory requires 64-bit
addressing to access.
I believe the BCM91480B BigSur board, which has the BCM1480 SOC instead,
accepts at least as much memory, although I have no documentation or
actual hardware available to verify that.
Both systems have PCI slots installed for use by any PCI option boards,
including ones that only support 32-bit addressing (additionally the
32-bit PCI host bridge of the BCM1250, BCM1125, and BCM1125H SOCs limits
addressing to 32-bits), and there is no IOMMU available. Therefore for
PCI DMA to work in the presence of memory beyond enable swiotlb for the
affected systems.
All the other SOC onchip DMA devices use 40-bit addressing and therefore
can address the whole memory, so only enable swiotlb if PCI support and
support for DMA beyond 4GiB have been both enabled in the configuration
of the kernel.
This shows up as follows:
Broadcom SiByte BCM1250 B2 @ 800 MHz (SB1 rev 2)
Board type: SiByte BCM91250A (SWARM)
Determined physical RAM map:
memory: 000000000fe7fe00 @ 0000000000000000 (usable)
memory: 000000001ffffe00 @ 0000000080000000 (usable)
memory: 000000000ffffe00 @ 00000000c0000000 (usable)
memory: 0000000087fffe00 @ 0000000100000000 (usable)
software IO TLB: mapped [mem 0xcbffc000-0xcfffc000] (64MB)
in the bootstrap log and removes failures like these:
defxx 0000:02:00.0: dma_direct_map_page: overflow 0x0000000185bc6080+4608 of device mask ffffffff bus mask 0
fddi0: Receive buffer allocation failed
fddi0: Adapter open failed!
IP-Config: Failed to open fddi0
defxx 0000:09:08.0: dma_direct_map_page: overflow 0x0000000185bc6080+4608 of device mask ffffffff bus mask 0
fddi1: Receive buffer allocation failed
fddi1: Adapter open failed!
IP-Config: Failed to open fddi1
when memory beyond 4GiB is handed out to devices that can only do 32-bit
addressing.
This updates commit cce335ae47e2 ("[MIPS] 64-bit Sibyte kernels need
DMA32.").
References:
[1] "BCM1250/BCM1125/BCM1125H User Manual", Revision 1250_1125-UM100-R,
Broadcom Corporation, 21 Oct 2002, Section 3: "System Overview",
"Memory Map", pp. 34-38
[2] "BCM91250A User Manual", Revision 91250A-UM100-R, Broadcom
Corporation, 18 May 2004, Section 3: "Physical Description",
"Supported DRAM", p. 23
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
[paul.burton@mips.com: Remove GPL text from dma.c; SPDX tag covers it]
Signed-off-by: Paul Burton <paul.burton@mips.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Patchwork: https://patchwork.linux-mips.org/patch/21108/
References: cce335ae47e2 ("[MIPS] 64-bit Sibyte kernels need DMA32.")
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
2018-11-13 22:42:44 +00:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-01 21:55:39 +00:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
2007-11-03 02:05:43 +00:00
|
|
|
|
MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur
The Broadcom SiByte BCM1250, BCM1125, and BCM1125H SOCs have an onchip
DRAM controller that supports memory amounts of up to 16GiB, and due to
how the address decoder has been wired in the SOC any memory beyond 1GiB
is actually mapped starting from 4GiB physical up, that is beyond the
32-bit addressable limit[1]. Consequently if the maximum amount of
memory has been installed, then it will span up to 19GiB.
Many of the evaluation boards we support that are based on one of these
SOCs have their memory soldered and the amount present fits in the
32-bit address range. The BCM91250A SWARM board however has actual DIMM
slots and accepts, depending on the peripherals revision of the SOC, up
to 4GiB or 8GiB of memory in commercially available JEDEC modules[2].
I believe this is also the case with the BCM91250C2 LittleSur board.
This means that up to either 3GiB or 7GiB of memory requires 64-bit
addressing to access.
I believe the BCM91480B BigSur board, which has the BCM1480 SOC instead,
accepts at least as much memory, although I have no documentation or
actual hardware available to verify that.
Both systems have PCI slots installed for use by any PCI option boards,
including ones that only support 32-bit addressing (additionally the
32-bit PCI host bridge of the BCM1250, BCM1125, and BCM1125H SOCs limits
addressing to 32-bits), and there is no IOMMU available. Therefore for
PCI DMA to work in the presence of memory beyond enable swiotlb for the
affected systems.
All the other SOC onchip DMA devices use 40-bit addressing and therefore
can address the whole memory, so only enable swiotlb if PCI support and
support for DMA beyond 4GiB have been both enabled in the configuration
of the kernel.
This shows up as follows:
Broadcom SiByte BCM1250 B2 @ 800 MHz (SB1 rev 2)
Board type: SiByte BCM91250A (SWARM)
Determined physical RAM map:
memory: 000000000fe7fe00 @ 0000000000000000 (usable)
memory: 000000001ffffe00 @ 0000000080000000 (usable)
memory: 000000000ffffe00 @ 00000000c0000000 (usable)
memory: 0000000087fffe00 @ 0000000100000000 (usable)
software IO TLB: mapped [mem 0xcbffc000-0xcfffc000] (64MB)
in the bootstrap log and removes failures like these:
defxx 0000:02:00.0: dma_direct_map_page: overflow 0x0000000185bc6080+4608 of device mask ffffffff bus mask 0
fddi0: Receive buffer allocation failed
fddi0: Adapter open failed!
IP-Config: Failed to open fddi0
defxx 0000:09:08.0: dma_direct_map_page: overflow 0x0000000185bc6080+4608 of device mask ffffffff bus mask 0
fddi1: Receive buffer allocation failed
fddi1: Adapter open failed!
IP-Config: Failed to open fddi1
when memory beyond 4GiB is handed out to devices that can only do 32-bit
addressing.
This updates commit cce335ae47e2 ("[MIPS] 64-bit Sibyte kernels need
DMA32.").
References:
[1] "BCM1250/BCM1125/BCM1125H User Manual", Revision 1250_1125-UM100-R,
Broadcom Corporation, 21 Oct 2002, Section 3: "System Overview",
"Memory Map", pp. 34-38
[2] "BCM91250A User Manual", Revision 91250A-UM100-R, Broadcom
Corporation, 18 May 2004, Section 3: "Physical Description",
"Supported DRAM", p. 23
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
[paul.burton@mips.com: Remove GPL text from dma.c; SPDX tag covers it]
Signed-off-by: Paul Burton <paul.burton@mips.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Patchwork: https://patchwork.linux-mips.org/patch/21108/
References: cce335ae47e2 ("[MIPS] 64-bit Sibyte kernels need DMA32.")
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
2018-11-13 22:42:44 +00:00
|
|
|
|
2007-07-27 15:25:43 +09:00
|
|
|
|
2006-12-05 17:05:44 +01:00
|
|
|
|
|
|
|
|
|
2019-10-09 15:27:14 +02:00
|
|
|
|
|
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
|
|
|
|
|
2013-03-25 09:39:54 +00:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2018-02-05 15:37:43 +01:00
|
|
|
|
2018-02-05 16:40:00 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
2007-11-24 22:33:28 +00:00
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2018-11-15 20:05:37 +01:00
|
|
|
|
2011-06-01 19:05:10 +01:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2007-10-11 23:46:10 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2020-09-14 18:05:00 +02:00
|
|
|
|
2006-06-13 13:59:01 +02:00
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2006-06-13 13:59:01 +02:00
|
|
|
|
2006-12-28 18:22:32 +01:00
|
|
|
|
2006-06-13 13:59:01 +02:00
|
|
|
|
2007-03-01 11:56:43 +00:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
2013-01-16 18:53:19 -08:00
|
|
|
|
2006-06-13 13:59:01 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:45 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-12-05 17:05:44 +01:00
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2008-07-11 23:27:54 +09:00
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:47 +02:00
|
|
|
|
2005-07-25 22:45:45 +00:00
|
|
|
|
2008-07-16 16:12:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2008-07-16 16:12:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2014-01-14 09:54:38 -08:00
|
|
|
|
2008-07-16 16:12:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-05-22 15:10:46 +00:00
|
|
|
|
|
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
2018-01-10 16:21:13 +01:00
|
|
|
|
2018-11-15 20:05:36 +01:00
|
|
|
|
2018-04-03 16:24:20 +02:00
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
|
|
|
|
|
2012-10-17 00:39:09 +02:00
|
|
|
|
2015-05-21 19:59:31 +02:00
|
|
|
|
2015-03-20 19:11:58 +03:00
|
|
|
|
|
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
2009-02-02 11:30:59 -08:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2020-03-25 16:45:29 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-01 13:27:30 -07:00
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2014-05-28 23:52:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-28 12:34:04 -05:00
|
|
|
|
|
|
|
|
|
2014-08-21 13:04:22 -07:00
|
|
|
|
2021-03-26 01:34:56 -04:00
|
|
|
|
2015-03-05 17:31:30 +03:00
|
|
|
|
2018-04-24 09:00:54 +02:00
|
|
|
|
2016-12-13 14:25:37 -06:00
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2024-03-23 17:51:00 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-16 19:12:16 +02:00
|
|
|
|
2014-10-29 03:18:39 +04:00
|
|
|
|
2011-01-04 21:28:14 +01:00
|
|
|
|
2011-07-23 01:20:13 +02:00
|
|
|
|
2009-08-18 13:23:37 +01:00
|
|
|
|
2014-12-25 09:49:20 -08:00
|
|
|
|
2025-05-07 13:44:57 +00:00
|
|
|
|
2016-10-05 18:18:20 +01:00
|
|
|
|
2020-09-06 21:29:33 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2011-03-30 09:27:48 +02:00
|
|
|
|
MIPS: mobileye: Add EyeQ6H support
EyeQ6H (or “High”) is an other SoC from Mobileye still based on the
MIPS I6500 architecture as the EyeQ5. The 2 clusters of this SoC
contains 4 cores which are capable of running 4 threads. Besides this,
it features multiple controllers such as the classic UART, high speed
I2C, SPI, as well as CAN-FD, PCIe Gen4, Octal/Quad SPI Flash
interface, Gigabit Ethernet, MIPI CSI-2, MIPI DSI, and eMMC 5.1. It
also includes a Hardware Security Module, Functional Safety Hardware,
and video encoders and more.
This commit provides the infrastructure to build a kernel running on
EyeQ6H SoC. For now the support is limited and only one CPU core is
running.
Reviewed-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2024-05-13 20:34:17 +02:00
|
|
|
|
2016-01-13 18:15:39 -07:00
|
|
|
|
2013-01-20 22:05:30 +01:00
|
|
|
|
2005-02-07 01:27:14 +00:00
|
|
|
|
2005-02-03 14:28:23 +00:00
|
|
|
|
2008-07-11 00:31:36 +09:00
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
2019-10-20 22:43:14 +08:00
|
|
|
|
2015-04-21 10:00:35 +08:00
|
|
|
|
|
|
|
|
|
2005-02-03 14:28:23 +00:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
[PATCH] bitops: mips: use generic bitops
- remove __{,test_and_}{set,clear,change}_bit() and test_bit()
- unless defined(CONFIG_CPU_MIPS32) or defined(CONFIG_CPU_MIPS64)
- remove __ffs()
- remove ffs()
- remove ffz()
- remove fls()
- remove fls64()
- remove find_{next,first}{,_zero}_bit()
- remove sched_find_first_bit()
- remove generic_hweight64()
- remove generic_hweight{32,16,8}()
- remove ext2_{set,clear,test,find_first_zero,find_next_zero}_bit()
- remove ext2_{set,clear}_bit_atomic()
- remove minix_{test,set,test_and_clear,test,find_first_zero}_bit()
Signed-off-by: Akinobu Mita <mita@miraclelinux.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-26 01:39:30 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-11 09:05:16 +01:00
|
|
|
|
2006-04-04 13:11:45 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2005-09-15 08:52:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-06-14 15:55:31 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-01 01:57:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-04-25 12:11:44 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-10-22 19:43:15 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-10-18 17:48:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-01 01:57:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-10-25 01:34:09 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-01 01:57:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-04-24 09:48:40 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-24 22:33:28 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-01 01:57:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MIPS: VDSO: Add implementations of gettimeofday() and clock_gettime()
Add user-mode implementations of gettimeofday() and clock_gettime() to
the VDSO. This is currently usable with 2 clocksources: the CP0 count
register, which is accessible to user-mode via RDHWR on R2 and later
cores, or the MIPS Global Interrupt Controller (GIC) timer, which
provides a "user-mode visible" section containing a mirror of its
counter registers. This section must be mapped into user memory, which
is done below the VDSO data page.
When a supported clocksource is not in use, the VDSO functions will
return -ENOSYS, which causes libc to fall back on the standard syscall
path.
When support for neither of these clocksources is compiled into the
kernel at all, the VDSO still provides clock_gettime(), as the coarse
realtime/monotonic clocks can still be implemented. However,
gettimeofday() is not provided in this case as nothing can be done
without a suitable clocksource. This causes the symbol lookup to fail
in libc and it will then always use the standard syscall path.
This patch includes a workaround for a bug in QEMU which results in
RDHWR on the CP0 count register always returning a constant (incorrect)
value. A fix for this has been submitted, and the workaround can be
removed after the fix has been in stable releases for a reasonable
amount of time.
A simple performance test which calls gettimeofday() 1000 times in a
loop and calculates the average execution time gives the following
results on a Malta + I6400 (running at 20MHz):
- Syscall: ~31000 ns
- VDSO (GIC): ~15000 ns
- VDSO (CP0): ~9500 ns
[markos.chandras@imgtec.com:
- Minor code re-arrangements in order for mappings to be made
in the order they appear to the process' address space.
- Move do_{monotonic, realtime} outside of the MIPS_CLOCK_VSYSCALL ifdef
- Use gic_get_usm_range so we can do the GIC mapping in the
arch/mips/kernel/vdso instead of the GIC irqchip driver]
Signed-off-by: Alex Smith <alex.smith@imgtec.com>
Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
Cc: linux-kernel@vger.kernel.org
Cc: linux-mips@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/11338/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2015-10-21 09:57:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-04-05 00:55:41 +09:00
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2008-04-05 00:55:41 +09:00
|
|
|
|
|
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
2007-09-05 08:58:26 +02:00
|
|
|
|
|
|
|
|
|
2015-07-29 22:44:53 +02:00
|
|
|
|
2023-04-11 15:17:47 +08:00
|
|
|
|
2015-07-29 22:44:53 +02:00
|
|
|
|
2005-09-03 15:56:19 -07:00
|
|
|
|
|
|
|
|
|
2019-08-26 09:22:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-22 13:24:23 +00:00
|
|
|
|
2019-08-26 09:03:44 +02:00
|
|
|
|
2020-02-21 15:55:43 -08:00
|
|
|
|
2023-02-22 13:24:24 +00:00
|
|
|
|
2018-06-15 13:08:46 +02:00
|
|
|
|
2020-02-21 15:55:43 -08:00
|
|
|
|
2019-10-29 11:01:37 +01:00
|
|
|
|
|
|
|
|
|
2005-09-03 15:56:19 -07:00
|
|
|
|
2007-03-01 11:56:43 +00:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2009-06-23 10:00:31 +01:00
|
|
|
|
2007-08-07 14:52:17 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-04-28 17:14:26 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-07 15:39:19 -07:00
|
|
|
|
2007-05-29 15:08:07 +01:00
|
|
|
|
|
|
|
|
|
2014-11-13 11:25:27 +00:00
|
|
|
|
2020-01-22 13:58:50 +03:00
|
|
|
|
2014-11-13 11:25:27 +00:00
|
|
|
|
2007-08-24 16:48:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-18 12:55:21 +09:00
|
|
|
|
2007-08-24 16:48:30 +01:00
|
|
|
|
2006-11-30 01:14:51 +00:00
|
|
|
|
|
|
|
|
|
2007-08-24 16:48:30 +01:00
|
|
|
|
2006-11-30 01:14:51 +00:00
|
|
|
|
2020-03-25 16:45:29 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-18 12:55:21 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 10:05:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 10:05:39 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2012-04-14 00:14:11 +09:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-14 00:14:11 +09:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2006-11-30 05:22:59 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2007-05-09 07:12:20 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-07-23 18:41:43 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-02-09 17:08:58 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2012-10-17 00:48:10 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-08-02 23:35:53 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-09-13 23:51:26 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-03-14 21:51:26 +09:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2019-05-07 23:09:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-06-14 15:55:31 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-13 13:32:03 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-10 20:29:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2013-03-25 09:39:54 +00:00
|
|
|
|
2008-01-04 23:31:07 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-14 09:54:38 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2014-01-14 09:54:39 -08:00
|
|
|
|
2014-12-25 09:49:09 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2019-10-22 18:13:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2007-12-02 13:00:32 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-15 20:48:50 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-20 22:43:13 +08:00
|
|
|
|
MIPS: Loongson: Unify LOONGSON3/LOONGSON64 Kconfig usage
There are mixed LOONGSON3/LOONGSON64 usages in recently changes, let's
establish some rules:
1, In Kconfig symbols, we only use CPU_LOONGSON64, MACH_LOONGSON64 and
SYS_HAS_CPU_LOONGSON64, all other derived symbols use "LOONGSON3" since
they all not widely-used symbols and sometimes not suitable for all
64-bit Loongson processors. E.g., we use symbols LOONGSON3_ENHANCEMENT,
CPU_LOONGSON3_WORKAROUNDS, etc.
2, Hide GSx64/GSx64E in Kconfig title since it is not useful for
general users. However, in the full description we use a more detailed
manner. E.g., GS264/GS464/GS464E/GS464V.
All Kconfig titles and descriptions of Loongson processors and machines
have also been updated in this patch for consistency.
Signed-off-by: Huacai Chen <chenhc@lemote.com>
Signed-off-by: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: James Hogan <jhogan@kernel.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org
Cc: linux-mips@vger.kernel.org
Cc: Fuxin Zhang <zhangfx@lemote.com>
Cc: Zhangjin Wu <wuzhangjin@gmail.com>
Cc: Huacai Chen <chenhuacai@gmail.com>
2019-11-04 14:11:21 +08:00
|
|
|
|
2019-10-20 22:43:13 +08:00
|
|
|
|
2018-06-15 13:08:41 +02:00
|
|
|
|
2020-01-13 18:15:00 +08:00
|
|
|
|
|
|
|
|
|
2014-03-21 18:44:07 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MIPS: Loongson: Add Loongson-3A R4 basic support
All Loongson-3 CPU family:
Code-name Brand-name PRId
Loongson-3A R1 Loongson-3A1000 0x6305
Loongson-3A R2 Loongson-3A2000 0x6308
Loongson-3A R2.1 Loongson-3A2000 0x630c
Loongson-3A R3 Loongson-3A3000 0x6309
Loongson-3A R3.1 Loongson-3A3000 0x630d
Loongson-3A R4 Loongson-3A4000 0xc000
Loongson-3B R1 Loongson-3B1000 0x6306
Loongson-3B R2 Loongson-3B1500 0x6307
Features of R4 revision of Loongson-3A:
- All R2/R3 features, including SFB, V-Cache, FTLB, RIXI, DSP, etc.
- Support variable ASID bits.
- Support MSA and VZ extensions.
- Support CPUCFG (CPU config) and CSR (Control and Status Register)
extensions.
- 64 entries of VTLB (classic TLB), 2048 entries of FTLB (8-way
set-associative).
Now 64-bit Loongson processors has three types of PRID.IMP: 0x6300 is
the classic one so we call it PRID_IMP_LOONGSON_64C (e.g., Loongson-2E/
2F/3A1000/3B1000/3B1500/3A2000/3A3000), 0x6100 is for some processors
which has reduced capabilities so we call it PRID_IMP_LOONGSON_64R
(e.g., Loongson-2K), 0xc000 is supposed to cover all new processors in
general (e.g., Loongson-3A4000+) so we call it PRID_IMP_LOONGSON_64G.
Signed-off-by: Huacai Chen <chenhc@lemote.com>
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Paul Burton <paul.burton@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: James Hogan <jhogan@kernel.org>
Cc: linux-mips@linux-mips.org
Cc: linux-mips@vger.kernel.org
Cc: Fuxin Zhang <zhangfx@lemote.com>
Cc: Zhangjin Wu <wuzhangjin@gmail.com>
Cc: Huacai Chen <chenhuacai@gmail.com>
2019-09-21 21:50:27 +08:00
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
2020-01-13 18:15:00 +08:00
|
|
|
|
|
|
|
|
|
2023-11-07 11:15:19 +00:00
|
|
|
|
2014-03-21 18:44:07 +08:00
|
|
|
|
|
|
|
|
|
MIPS: Loongson: Add Loongson-3A R4 basic support
All Loongson-3 CPU family:
Code-name Brand-name PRId
Loongson-3A R1 Loongson-3A1000 0x6305
Loongson-3A R2 Loongson-3A2000 0x6308
Loongson-3A R2.1 Loongson-3A2000 0x630c
Loongson-3A R3 Loongson-3A3000 0x6309
Loongson-3A R3.1 Loongson-3A3000 0x630d
Loongson-3A R4 Loongson-3A4000 0xc000
Loongson-3B R1 Loongson-3B1000 0x6306
Loongson-3B R2 Loongson-3B1500 0x6307
Features of R4 revision of Loongson-3A:
- All R2/R3 features, including SFB, V-Cache, FTLB, RIXI, DSP, etc.
- Support variable ASID bits.
- Support MSA and VZ extensions.
- Support CPUCFG (CPU config) and CSR (Control and Status Register)
extensions.
- 64 entries of VTLB (classic TLB), 2048 entries of FTLB (8-way
set-associative).
Now 64-bit Loongson processors has three types of PRID.IMP: 0x6300 is
the classic one so we call it PRID_IMP_LOONGSON_64C (e.g., Loongson-2E/
2F/3A1000/3B1000/3B1500/3A2000/3A3000), 0x6100 is for some processors
which has reduced capabilities so we call it PRID_IMP_LOONGSON_64R
(e.g., Loongson-2K), 0xc000 is supposed to cover all new processors in
general (e.g., Loongson-3A4000+) so we call it PRID_IMP_LOONGSON_64G.
Signed-off-by: Huacai Chen <chenhc@lemote.com>
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Paul Burton <paul.burton@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: James Hogan <jhogan@kernel.org>
Cc: linux-mips@linux-mips.org
Cc: linux-mips@vger.kernel.org
Cc: Fuxin Zhang <zhangfx@lemote.com>
Cc: Zhangjin Wu <wuzhangjin@gmail.com>
Cc: Huacai Chen <chenhuacai@gmail.com>
2019-09-21 21:50:27 +08:00
|
|
|
|
2016-03-03 09:45:09 +08:00
|
|
|
|
2017-03-16 21:00:28 +08:00
|
|
|
|
2021-09-13 14:19:08 +08:00
|
|
|
|
2016-04-19 11:23:22 +02:00
|
|
|
|
2018-04-24 09:00:54 +02:00
|
|
|
|
2014-03-21 18:44:07 +08:00
|
|
|
|
2022-05-24 10:03:11 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-21 18:44:07 +08:00
|
|
|
|
2009-07-02 23:27:41 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-20 22:43:13 +08:00
|
|
|
|
2007-06-06 14:52:43 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-30 22:57:33 -03:00
|
|
|
|
2009-11-06 18:45:05 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-20 22:43:13 +08:00
|
|
|
|
2009-11-06 18:45:05 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-16 19:25:16 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-06 20:34:54 +08:00
|
|
|
|
2012-07-25 16:17:24 +02:00
|
|
|
|
2025-07-16 19:25:16 +08:00
|
|
|
|
|
|
|
|
|
2016-05-19 12:29:30 +08:00
|
|
|
|
2005-07-06 12:08:11 +00:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-07-06 12:08:11 +00:00
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2006-03-05 00:45:33 +00:00
|
|
|
|
2005-07-12 14:51:22 +00:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2005-07-12 14:51:22 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-07-12 14:51:22 +00:00
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2006-03-05 00:45:33 +00:00
|
|
|
|
2014-01-27 15:23:10 +00:00
|
|
|
|
2005-07-06 12:08:11 +00:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2005-07-06 12:08:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
2015-07-16 13:24:46 +01:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
2020-01-22 13:58:50 +03:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-07-06 12:08:11 +00:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2006-03-05 00:45:33 +00:00
|
|
|
|
2009-05-27 17:47:46 -07:00
|
|
|
|
2005-07-06 12:08:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-07-12 14:51:22 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2005-07-12 14:51:22 +00:00
|
|
|
|
|
|
|
|
|
2006-03-05 00:45:33 +00:00
|
|
|
|
2009-05-27 17:47:46 -07:00
|
|
|
|
2014-01-27 15:23:10 +00:00
|
|
|
|
2005-07-12 14:51:22 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
2015-07-16 13:24:46 +01:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
2020-01-22 13:58:50 +03:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-02 02:21:53 +00:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
2017-02-16 12:39:01 +00:00
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mips: Add MIPS Warrior P5600 support
This is a MIPS32 Release 5 based IP core with XPA, EVA, dual/quad issue
exec pipes, MMU with two-levels TLB, UCA, MSA, MDU core level features
and system level features like up to six P5600 calculation cores, CM2
with L2 cache, IOCU/IOMMU (though might be unused depending on the
system-specific IP core configuration), GIC, CPC, virtualisation module,
eJTAG and PDtrace.
As being MIPS32 Release 5 based core it provides all the features
available by the CPU_MIPS32_R5 config, while adding a few more like
UCA attribute support, availability of CPU-freq (by means of L2/CM
clock ratio setting), EI/VI GIC modes detection at runtime.
In addition to this if P5600 architecture is enabled modern GNU GCC
provides a specific tuning for P5600 processors with respect to the
classic MIPS32 Release 5. First of all branch-likely avoidance is
activated only when the code is compiled with the speed optimization
(avoidance is always enabled for the pure MIPS32 Release 5
architecture). Secondly the madd/msub avoidance is enabled since
madd/msub utilization isn't profitable due to overhead of getting the
result out of the HI/LO registers. Multiply-accumulate instructions are
activated and utilized together with the necessary code reorder when
multiply-add/multiply-subtract statements are met. Finally load/store
bonding is activated by default. All of these optimizations may make
the code relatively faster than if just MIP32 release 5 architecture
was requested.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
mips: Add MIPS Warrior P5600 support
This is a MIPS32 Release 5 based IP core with XPA, EVA, dual/quad issue
exec pipes, MMU with two-levels TLB, UCA, MSA, MDU core level features
and system level features like up to six P5600 calculation cores, CM2
with L2 cache, IOCU/IOMMU (though might be unused depending on the
system-specific IP core configuration), GIC, CPC, virtualisation module,
eJTAG and PDtrace.
As being MIPS32 Release 5 based core it provides all the features
available by the CPU_MIPS32_R5 config, while adding a few more like
UCA attribute support, availability of CPU-freq (by means of L2/CM
clock ratio setting), EI/VI GIC modes detection at runtime.
In addition to this if P5600 architecture is enabled modern GNU GCC
provides a specific tuning for P5600 processors with respect to the
classic MIPS32 Release 5. First of all branch-likely avoidance is
activated only when the code is compiled with the speed optimization
(avoidance is always enabled for the pure MIPS32 Release 5
architecture). Secondly the madd/msub avoidance is enabled since
madd/msub utilization isn't profitable due to overhead of getting the
result out of the HI/LO registers. Multiply-accumulate instructions are
activated and utilized together with the necessary code reorder when
multiply-add/multiply-subtract statements are met. Finally load/store
bonding is activated by default. All of these optimizations may make
the code relatively faster than if just MIP32 release 5 architecture
was requested.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2006-04-24 14:58:53 +01:00
|
|
|
|
2019-08-31 15:40:43 +00:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-13 17:10:07 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2006-03-17 12:59:22 +09:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-24 01:27:57 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-05-27 17:47:46 -07:00
|
|
|
|
2008-10-24 01:27:57 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
2005-09-03 15:56:21 -07:00
|
|
|
|
|
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2006-10-31 03:45:07 +00:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
|
|
|
|
|
2009-02-02 11:30:59 -08:00
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
|
|
|
|
|
2024-02-23 23:18:37 +01:00
|
|
|
|
|
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
|
|
|
|
|
2009-05-27 17:47:46 -07:00
|
|
|
|
2015-05-25 20:27:29 +01:00
|
|
|
|
|
|
|
|
|
2014-01-14 09:54:38 -08:00
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-18 14:12:05 +01:00
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-26 18:20:06 +02:00
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
|
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
2013-12-18 14:12:04 +01:00
|
|
|
|
2017-02-07 13:58:54 -08:00
|
|
|
|
|
|
|
|
|
2021-10-20 11:48:47 -07:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
2013-12-18 14:12:05 +01:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2024-01-28 01:23:09 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-03 10:22:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mips: Add MIPS Warrior P5600 support
This is a MIPS32 Release 5 based IP core with XPA, EVA, dual/quad issue
exec pipes, MMU with two-levels TLB, UCA, MSA, MDU core level features
and system level features like up to six P5600 calculation cores, CM2
with L2 cache, IOCU/IOMMU (though might be unused depending on the
system-specific IP core configuration), GIC, CPC, virtualisation module,
eJTAG and PDtrace.
As being MIPS32 Release 5 based core it provides all the features
available by the CPU_MIPS32_R5 config, while adding a few more like
UCA attribute support, availability of CPU-freq (by means of L2/CM
clock ratio setting), EI/VI GIC modes detection at runtime.
In addition to this if P5600 architecture is enabled modern GNU GCC
provides a specific tuning for P5600 processors with respect to the
classic MIPS32 Release 5. First of all branch-likely avoidance is
activated only when the code is compiled with the speed optimization
(avoidance is always enabled for the pure MIPS32 Release 5
architecture). Secondly the madd/msub avoidance is enabled since
madd/msub utilization isn't profitable due to overhead of getting the
result out of the HI/LO registers. Multiply-accumulate instructions are
activated and utilized together with the necessary code reorder when
multiply-add/multiply-subtract statements are met. Finally load/store
bonding is activated by default. All of these optimizations may make
the code relatively faster than if just MIP32 release 5 architecture
was requested.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:15 +03:00
|
|
|
|
|
|
|
|
|
2013-12-03 10:22:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-26 18:16:38 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mips: Add MIPS Warrior P5600 support
This is a MIPS32 Release 5 based IP core with XPA, EVA, dual/quad issue
exec pipes, MMU with two-levels TLB, UCA, MSA, MDU core level features
and system level features like up to six P5600 calculation cores, CM2
with L2 cache, IOCU/IOMMU (though might be unused depending on the
system-specific IP core configuration), GIC, CPC, virtualisation module,
eJTAG and PDtrace.
As being MIPS32 Release 5 based core it provides all the features
available by the CPU_MIPS32_R5 config, while adding a few more like
UCA attribute support, availability of CPU-freq (by means of L2/CM
clock ratio setting), EI/VI GIC modes detection at runtime.
In addition to this if P5600 architecture is enabled modern GNU GCC
provides a specific tuning for P5600 processors with respect to the
classic MIPS32 Release 5. First of all branch-likely avoidance is
activated only when the code is compiled with the speed optimization
(avoidance is always enabled for the pure MIPS32 Release 5
architecture). Secondly the madd/msub avoidance is enabled since
madd/msub utilization isn't profitable due to overhead of getting the
result out of the HI/LO registers. Multiply-accumulate instructions are
activated and utilized together with the necessary code reorder when
multiply-add/multiply-subtract statements are met. Finally load/store
bonding is activated by default. All of these optimizations may make
the code relatively faster than if just MIP32 release 5 architecture
was requested.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:15 +03:00
|
|
|
|
2015-02-26 18:16:38 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-03 16:24:20 +02:00
|
|
|
|
2015-02-26 18:16:38 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-04-10 20:04:42 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-10-14 18:12:16 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-09-16 16:55:20 +01:00
|
|
|
|
2009-10-14 18:12:16 +08:00
|
|
|
|
2010-01-15 20:34:46 +08:00
|
|
|
|
2013-09-11 11:51:41 +01:00
|
|
|
|
2020-09-01 16:26:51 +02:00
|
|
|
|
2009-10-14 18:12:16 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-10 10:57:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-20 22:43:13 +08:00
|
|
|
|
2009-07-02 23:27:41 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-18 13:54:15 +02:00
|
|
|
|
2025-07-13 12:04:34 +02:00
|
|
|
|
2009-07-02 23:27:41 +08:00
|
|
|
|
2013-12-18 14:12:05 +01:00
|
|
|
|
2013-12-18 14:12:06 +01:00
|
|
|
|
2011-11-10 22:30:24 -08:00
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-20 21:27:58 -07:00
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
|
|
|
|
|
2016-02-09 12:55:53 -08:00
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-20 21:27:58 -07:00
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
|
|
|
|
|
2016-02-09 12:55:53 -08:00
|
|
|
|
2011-11-10 22:30:24 -08:00
|
|
|
|
2019-10-20 22:43:13 +08:00
|
|
|
|
2014-03-21 18:44:07 +08:00
|
|
|
|
|
|
|
|
|
2016-03-03 09:45:09 +08:00
|
|
|
|
2014-03-21 18:44:07 +08:00
|
|
|
|
2009-07-02 23:27:41 +08:00
|
|
|
|
2007-06-06 14:52:43 +08:00
|
|
|
|
|
|
|
|
|
2009-11-06 18:45:05 +08:00
|
|
|
|
|
|
|
|
|
2009-11-11 13:39:12 +08:00
|
|
|
|
|
|
|
|
|
2009-11-06 18:45:05 +08:00
|
|
|
|
2025-07-16 19:25:16 +08:00
|
|
|
|
2016-05-19 12:29:30 +08:00
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-03 10:22:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-26 18:16:38 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-13 12:16:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mips: Add MIPS Warrior P5600 support
This is a MIPS32 Release 5 based IP core with XPA, EVA, dual/quad issue
exec pipes, MMU with two-levels TLB, UCA, MSA, MDU core level features
and system level features like up to six P5600 calculation cores, CM2
with L2 cache, IOCU/IOMMU (though might be unused depending on the
system-specific IP core configuration), GIC, CPC, virtualisation module,
eJTAG and PDtrace.
As being MIPS32 Release 5 based core it provides all the features
available by the CPU_MIPS32_R5 config, while adding a few more like
UCA attribute support, availability of CPU-freq (by means of L2/CM
clock ratio setting), EI/VI GIC modes detection at runtime.
In addition to this if P5600 architecture is enabled modern GNU GCC
provides a specific tuning for P5600 processors with respect to the
classic MIPS32 Release 5. First of all branch-likely avoidance is
activated only when the code is compiled with the speed optimization
(avoidance is always enabled for the pure MIPS32 Release 5
architecture). Secondly the madd/msub avoidance is enabled since
madd/msub utilization isn't profitable due to overhead of getting the
result out of the HI/LO registers. Multiply-accumulate instructions are
activated and utilized together with the necessary code reorder when
multiply-add/multiply-subtract statements are met. Finally load/store
bonding is activated by default. All of these optimizations may make
the code relatively faster than if just MIP32 release 5 architecture
was requested.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-13 17:10:07 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-24 01:27:57 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-20 22:33:09 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-02 11:30:59 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
|
|
|
|
|
2013-12-18 14:12:05 +01:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-18 14:12:02 +01:00
|
|
|
|
2010-10-17 10:56:53 -07:00
|
|
|
|
2007-07-14 13:24:05 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-10-31 03:45:07 +00:00
|
|
|
|
|
|
|
|
|
2007-07-14 13:24:05 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-20 17:15:20 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
mips: Add MIPS Warrior P5600 support
This is a MIPS32 Release 5 based IP core with XPA, EVA, dual/quad issue
exec pipes, MMU with two-levels TLB, UCA, MSA, MDU core level features
and system level features like up to six P5600 calculation cores, CM2
with L2 cache, IOCU/IOMMU (though might be unused depending on the
system-specific IP core configuration), GIC, CPC, virtualisation module,
eJTAG and PDtrace.
As being MIPS32 Release 5 based core it provides all the features
available by the CPU_MIPS32_R5 config, while adding a few more like
UCA attribute support, availability of CPU-freq (by means of L2/CM
clock ratio setting), EI/VI GIC modes detection at runtime.
In addition to this if P5600 architecture is enabled modern GNU GCC
provides a specific tuning for P5600 processors with respect to the
classic MIPS32 Release 5. First of all branch-likely avoidance is
activated only when the code is compiled with the speed optimization
(avoidance is always enabled for the pure MIPS32 Release 5
architecture). Secondly the madd/msub avoidance is enabled since
madd/msub utilization isn't profitable due to overhead of getting the
result out of the HI/LO registers. Multiply-accumulate instructions are
activated and utilized together with the necessary code reorder when
multiply-add/multiply-subtract statements are met. Finally load/store
bonding is activated by default. All of these optimizations may make
the code relatively faster than if just MIP32 release 5 architecture
was requested.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:15 +03:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
2021-02-28 00:02:36 +01:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2018-11-08 23:44:55 +00:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-11 15:33:38 -08:00
|
|
|
|
2016-02-09 12:55:51 -08:00
|
|
|
|
2020-01-13 18:14:59 +08:00
|
|
|
|
2014-11-13 13:32:03 +00:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
|
|
|
|
|
mips: Add MIPS Warrior P5600 support
This is a MIPS32 Release 5 based IP core with XPA, EVA, dual/quad issue
exec pipes, MMU with two-levels TLB, UCA, MSA, MDU core level features
and system level features like up to six P5600 calculation cores, CM2
with L2 cache, IOCU/IOMMU (though might be unused depending on the
system-specific IP core configuration), GIC, CPC, virtualisation module,
eJTAG and PDtrace.
As being MIPS32 Release 5 based core it provides all the features
available by the CPU_MIPS32_R5 config, while adding a few more like
UCA attribute support, availability of CPU-freq (by means of L2/CM
clock ratio setting), EI/VI GIC modes detection at runtime.
In addition to this if P5600 architecture is enabled modern GNU GCC
provides a specific tuning for P5600 processors with respect to the
classic MIPS32 Release 5. First of all branch-likely avoidance is
activated only when the code is compiled with the speed optimization
(avoidance is always enabled for the pure MIPS32 Release 5
architecture). Secondly the madd/msub avoidance is enabled since
madd/msub utilization isn't profitable due to overhead of getting the
result out of the HI/LO registers. Multiply-accumulate instructions are
activated and utilized together with the necessary code reorder when
multiply-add/multiply-subtract statements are met. Finally load/store
bonding is activated by default. All of these optimizations may make
the code relatively faster than if just MIP32 release 5 architecture
was requested.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:15 +03:00
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-09 12:55:51 -08:00
|
|
|
|
2020-01-13 18:14:59 +08:00
|
|
|
|
2016-05-06 13:35:03 +01:00
|
|
|
|
2016-05-06 14:36:24 +01:00
|
|
|
|
2014-11-13 13:32:03 +00:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2018-11-08 23:44:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
2018-11-08 23:44:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-03 10:22:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-26 18:16:38 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-11 13:39:12 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-05-27 17:47:46 -07:00
|
|
|
|
|
|
|
|
|
2021-12-13 12:16:42 +01:00
|
|
|
|
2024-01-04 11:00:36 -05:00
|
|
|
|
|
|
|
|
|
2009-10-14 12:16:56 -07:00
|
|
|
|
|
|
|
|
|
MIPS: clean up CONFIG_MIPS_PGD_C0_CONTEXT handling
+. LOONGSON64 use 0x98xx_xxxx_xxxx_xxxx as xphys cached, instread of
0xa8xx_xxxx_xxxx_xxxx
+. let CONFIG_MIPS_PGD_C0_CONTEXT depend on 64bit
+. cast CAC_BASE into u64 to silence warning on MIPS32
CP0 Context has enough room for wraping pgd into its 41-bit PTEBase field.
+. For XPHYS, the trick is that pgd is 4kB aligned, and the PABITS <= 53,
only save 53 - 12 = 41 bits, aka :
bit[63:59] | 0000 00 | bit[53:12] | 0000 0000 0000
+. for CKSEG0, only save 29 - 12 = 17 bits
when switching pgd, only need to save bit[53:12] or bit[28:12] into
CP0 Context's bit[63:23], see folling asm generated at run time
tlbmiss_handler_setup_pgd:
.set push
.set noreorder
dsra a2, a0, 29
move a3, a0
dins a0, zero, 29, 35
daddiu a2, a2, 4 //for CKSEG0, a2 from 0xfffffffffffffffc
//into 0
movn a0, a3, a2
dsll a0, a0, 11
jr ra
dmtc0 a0, CP0_CONTEXT
.set pop
when using it on page walking
dmfc0 k0, CP0_CONTEXT
dins k0, zero, 0, 23 // zero badv2
ori k0, k0, (CAC_BASE >> 53) // *prefix* with bit[63:59]
drotr k0, k0, 11 // kick it in the right place
Signed-off-by: Huang Pei <huangpei@loongson.cn>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2021-03-13 09:39:27 +08:00
|
|
|
|
2021-10-20 14:49:13 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
2008-09-23 00:04:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
|
|
|
|
|
2008-09-23 00:04:26 -07:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-07-23 12:02:09 +02:00
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-14 18:34:43 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-16 17:27:34 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-05-14 18:34:43 -07:00
|
|
|
|
|
|
|
|
|
2021-12-22 13:43:46 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-15 10:39:59 -04:00
|
|
|
|
2010-10-11 14:52:45 -07:00
|
|
|
|
2023-03-15 14:31:33 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-11 14:52:45 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-20 17:15:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-08-05 14:28:54 +00:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2012-01-31 18:18:43 +01:00
|
|
|
|
|
|
|
|
|
2022-02-22 10:04:28 +01:00
|
|
|
|
2012-01-31 18:18:43 +01:00
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2018-11-07 23:14:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
|
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2022-02-22 10:04:28 +01:00
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2019-08-31 15:40:43 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-01-31 18:18:44 +01:00
|
|
|
|
|
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2012-01-31 18:18:44 +01:00
|
|
|
|
2012-01-31 18:18:45 +01:00
|
|
|
|
|
|
|
|
|
2019-08-31 15:40:43 +00:00
|
|
|
|
2012-01-31 18:18:45 +01:00
|
|
|
|
2006-10-06 17:36:20 +01:00
|
|
|
|
2014-04-08 11:59:10 +01:00
|
|
|
|
2017-08-07 16:01:16 -07:00
|
|
|
|
2024-02-02 18:21:45 +00:00
|
|
|
|
|
|
|
|
|
2006-10-06 17:36:20 +01:00
|
|
|
|
2007-05-08 14:05:39 +01:00
|
|
|
|
2013-10-04 16:23:28 -05:00
|
|
|
|
2006-10-06 17:36:20 +01:00
|
|
|
|
|
|
|
|
|
2007-11-19 12:23:51 +00:00
|
|
|
|
2013-10-04 16:23:28 -05:00
|
|
|
|
2025-08-26 11:08:57 +02:00
|
|
|
|
2012-07-13 16:44:53 -04:00
|
|
|
|
2006-10-06 17:36:20 +01:00
|
|
|
|
2013-10-04 16:23:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-10-06 17:36:20 +01:00
|
|
|
|
2007-07-27 19:31:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-23 16:29:44 +02:00
|
|
|
|
2007-07-27 19:31:10 +01:00
|
|
|
|
2014-12-03 15:47:03 +00:00
|
|
|
|
|
|
|
|
|
2016-10-17 15:34:37 +01:00
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2014-12-03 15:47:03 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-10 12:30:56 +00:00
|
|
|
|
2014-12-03 15:47:03 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-15 20:54:35 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
|
|
|
|
|
2018-01-15 20:54:35 +00:00
|
|
|
|
2007-05-08 14:05:39 +01:00
|
|
|
|
|
|
|
|
|
2006-06-05 17:24:46 +01:00
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 15:52:06 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-05 20:51:27 +02:00
|
|
|
|
2013-10-30 15:52:06 -05:00
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
2014-01-01 16:26:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-05 20:51:27 +02:00
|
|
|
|
2014-01-15 10:32:00 +00:00
|
|
|
|
2014-01-15 10:31:53 +00:00
|
|
|
|
|
|
|
|
|
2016-02-03 03:15:33 +00:00
|
|
|
|
2014-01-15 10:31:53 +00:00
|
|
|
|
2014-04-14 14:13:57 +01:00
|
|
|
|
2014-01-15 10:31:53 +00:00
|
|
|
|
2025-04-13 21:12:32 +02:00
|
|
|
|
2023-05-12 23:07:37 +02:00
|
|
|
|
2014-01-15 10:31:53 +00:00
|
|
|
|
2014-04-14 14:13:57 +01:00
|
|
|
|
2025-08-26 11:08:57 +02:00
|
|
|
|
2014-01-15 10:31:53 +00:00
|
|
|
|
|
|
|
|
|
2020-12-03 14:54:43 +08:00
|
|
|
|
2014-01-15 10:31:53 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-14 11:00:56 +01:00
|
|
|
|
2014-09-18 16:09:49 +01:00
|
|
|
|
2014-04-14 11:00:56 +01:00
|
|
|
|
|
|
|
|
|
2014-01-15 10:31:51 +00:00
|
|
|
|
|
|
|
|
|
2017-08-12 19:49:42 -07:00
|
|
|
|
2014-01-15 10:31:51 +00:00
|
|
|
|
2014-01-15 10:31:52 +00:00
|
|
|
|
|
|
|
|
|
2008-10-04 00:06:29 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 08:46:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-02-02 17:41:47 +01:00
|
|
|
|
|
|
|
|
|
2014-07-21 08:46:14 +01:00
|
|
|
|
2007-02-02 17:41:47 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-25 13:27:11 -05:00
|
|
|
|
2014-10-27 10:34:11 +00:00
|
|
|
|
2014-07-21 08:46:14 +01:00
|
|
|
|
2013-03-25 13:27:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 08:46:14 +01:00
|
|
|
|
|
|
|
|
|
2014-01-27 15:23:10 +00:00
|
|
|
|
2015-07-27 12:58:27 -07:00
|
|
|
|
2014-01-27 15:23:10 +00:00
|
|
|
|
2018-11-07 23:14:02 +00:00
|
|
|
|
2014-07-11 16:47:14 +01:00
|
|
|
|
2014-01-27 15:23:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-27 15:23:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-27 15:23:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-04-24 14:58:53 +01:00
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
2011-11-16 01:25:45 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-13 18:14:59 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-09 12:55:51 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-22 13:58:50 +03:00
|
|
|
|
MIPS: Add Kconfig variable for CPUs with unaligned load/store instructions
MIPSR6 CPUs do not support unaligned load/store instructions
(LWL, LWR, SWL, SWR and LDL, LDR, SDL, SDR for 64bit).
Currently the MIPS tree has some special cases to avoid these
instructions, and the code is testing for !CONFIG_CPU_MIPSR6.
This patch declares a new Kconfig variable:
CONFIG_CPU_HAS_LOAD_STORE_LR.
This variable indicates that the CPU supports these instructions.
Then, the patch does the following:
- Carefully selects this option on all CPUs except MIPSR6.
- Switches all the special cases to test for the new variable,
and inverts the logic:
'#ifndef CONFIG_CPU_MIPSR6' turns into
'#ifdef CONFIG_CPU_HAS_LOAD_STORE_LR'
and vice-versa.
Also, when this variable is NOT selected (e.g. MIPSR6),
CONFIG_GENERIC_CSUM will default to 'y', to compile generic
C checksum code (instead of special assembly code that uses the
unsupported instructions).
This commit should not affect any existing CPU, and is required
for future Lexra CPU support, that misses these instructions too.
Signed-off-by: Yasha Cherikovsky <yasha.che3@gmail.com>
Signed-off-by: Paul Burton <paul.burton@mips.com>
Patchwork: https://patchwork.linux-mips.org/patch/20808/
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: James Hogan <jhogan@kernel.org>
Cc: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
2018-09-26 14:16:15 +03:00
|
|
|
|
|
|
|
|
|
2020-01-22 13:58:50 +03:00
|
|
|
|
MIPS: Add Kconfig variable for CPUs with unaligned load/store instructions
MIPSR6 CPUs do not support unaligned load/store instructions
(LWL, LWR, SWL, SWR and LDL, LDR, SDL, SDR for 64bit).
Currently the MIPS tree has some special cases to avoid these
instructions, and the code is testing for !CONFIG_CPU_MIPSR6.
This patch declares a new Kconfig variable:
CONFIG_CPU_HAS_LOAD_STORE_LR.
This variable indicates that the CPU supports these instructions.
Then, the patch does the following:
- Carefully selects this option on all CPUs except MIPSR6.
- Switches all the special cases to test for the new variable,
and inverts the logic:
'#ifndef CONFIG_CPU_MIPSR6' turns into
'#ifdef CONFIG_CPU_HAS_LOAD_STORE_LR'
and vice-versa.
Also, when this variable is NOT selected (e.g. MIPSR6),
CONFIG_GENERIC_CSUM will default to 'y', to compile generic
C checksum code (instead of special assembly code that uses the
unsupported instructions).
This commit should not affect any existing CPU, and is required
for future Lexra CPU support, that misses these instructions too.
Signed-off-by: Yasha Cherikovsky <yasha.che3@gmail.com>
Signed-off-by: Paul Burton <paul.burton@mips.com>
Patchwork: https://patchwork.linux-mips.org/patch/20808/
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: James Hogan <jhogan@kernel.org>
Cc: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
2018-09-26 14:16:15 +03:00
|
|
|
|
2020-01-22 13:58:50 +03:00
|
|
|
|
|
|
|
|
|
MIPS: Add Kconfig variable for CPUs with unaligned load/store instructions
MIPSR6 CPUs do not support unaligned load/store instructions
(LWL, LWR, SWL, SWR and LDL, LDR, SDL, SDR for 64bit).
Currently the MIPS tree has some special cases to avoid these
instructions, and the code is testing for !CONFIG_CPU_MIPSR6.
This patch declares a new Kconfig variable:
CONFIG_CPU_HAS_LOAD_STORE_LR.
This variable indicates that the CPU supports these instructions.
Then, the patch does the following:
- Carefully selects this option on all CPUs except MIPSR6.
- Switches all the special cases to test for the new variable,
and inverts the logic:
'#ifndef CONFIG_CPU_MIPSR6' turns into
'#ifdef CONFIG_CPU_HAS_LOAD_STORE_LR'
and vice-versa.
Also, when this variable is NOT selected (e.g. MIPSR6),
CONFIG_GENERIC_CSUM will default to 'y', to compile generic
C checksum code (instead of special assembly code that uses the
unsupported instructions).
This commit should not affect any existing CPU, and is required
for future Lexra CPU support, that misses these instructions too.
Signed-off-by: Yasha Cherikovsky <yasha.che3@gmail.com>
Signed-off-by: Paul Burton <paul.burton@mips.com>
Patchwork: https://patchwork.linux-mips.org/patch/20808/
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: James Hogan <jhogan@kernel.org>
Cc: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
2018-09-26 14:16:15 +03:00
|
|
|
|
2006-06-05 17:24:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
2006-06-05 17:24:46 +01:00
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
2006-06-05 17:24:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
2006-06-05 17:24:46 +01:00
|
|
|
|
2005-07-14 15:57:16 +00:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-10-23 12:43:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-18 11:04:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-10-23 12:43:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-18 11:04:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-10-23 12:43:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-18 11:04:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-10-23 12:43:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-01 23:04:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-06 14:36:23 +01:00
|
|
|
|
|
|
|
|
|
2022-02-22 10:04:28 +01:00
|
|
|
|
2016-05-06 14:36:23 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-06 14:36:24 +01:00
|
|
|
|
2022-02-22 10:04:28 +01:00
|
|
|
|
2016-05-06 14:36:23 +01:00
|
|
|
|
|
|
|
|
|
2016-05-06 14:36:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-10-27 18:34:30 +00:00
|
|
|
|
2020-08-24 18:32:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:49 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 18:32:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-03 10:22:26 +00:00
|
|
|
|
2020-11-03 10:27:25 +01:00
|
|
|
|
2005-08-10 15:17:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2007-02-02 17:41:47 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-05 16:52:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-29 01:49:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-27 15:23:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-06-25 14:54:31 -07:00
|
|
|
|
|
|
|
|
|
2019-10-20 22:43:13 +08:00
|
|
|
|
2005-06-25 14:54:31 -07:00
|
|
|
|
2006-07-03 00:09:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-11 23:03:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-12-03 20:32:52 +08:00
|
|
|
|
mm: percpu: generalize percpu related config
Patch series "mm: percpu: Cleanup percpu first chunk function".
When supporting page mapping percpu first chunk allocator on arm64, we
found there are lots of duplicated codes in percpu embed/page first chunk
allocator. This patchset is aimed to cleanup them and should no function
change.
The currently supported status about 'embed' and 'page' in Archs shows
below,
embed: NEED_PER_CPU_PAGE_FIRST_CHUNK
page: NEED_PER_CPU_EMBED_FIRST_CHUNK
embed page
------------------------
arm64 Y Y
mips Y N
powerpc Y Y
riscv Y N
sparc Y Y
x86 Y Y
------------------------
There are two interfaces about percpu first chunk allocator,
extern int __init pcpu_embed_first_chunk(size_t reserved_size, size_t dyn_size,
size_t atom_size,
pcpu_fc_cpu_distance_fn_t cpu_distance_fn,
- pcpu_fc_alloc_fn_t alloc_fn,
- pcpu_fc_free_fn_t free_fn);
+ pcpu_fc_cpu_to_node_fn_t cpu_to_nd_fn);
extern int __init pcpu_page_first_chunk(size_t reserved_size,
- pcpu_fc_alloc_fn_t alloc_fn,
- pcpu_fc_free_fn_t free_fn,
- pcpu_fc_populate_pte_fn_t populate_pte_fn);
+ pcpu_fc_cpu_to_node_fn_t cpu_to_nd_fn);
The pcpu_fc_alloc_fn_t/pcpu_fc_free_fn_t is killed, we provide generic
pcpu_fc_alloc() and pcpu_fc_free() function, which are called in the
pcpu_embed/page_first_chunk().
1) For pcpu_embed_first_chunk(), pcpu_fc_cpu_to_node_fn_t is needed to be
provided when archs supported NUMA.
2) For pcpu_page_first_chunk(), the pcpu_fc_populate_pte_fn_t is killed too,
a generic pcpu_populate_pte() which marked '__weak' is provided, if you
need a different function to populate pte on the arch(like x86), please
provide its own implementation.
[1] https://github.com/kevin78/linux.git percpu-cleanup
This patch (of 4):
The HAVE_SETUP_PER_CPU_AREA/NEED_PER_CPU_EMBED_FIRST_CHUNK/
NEED_PER_CPU_PAGE_FIRST_CHUNK/USE_PERCPU_NUMA_NODE_ID configs, which have
duplicate definitions on platforms that subscribe it.
Move them into mm, drop these redundant definitions and instead just
select it on applicable platforms.
Link: https://lkml.kernel.org/r/20211216112359.103822-1-wangkefeng.wang@huawei.com
Link: https://lkml.kernel.org/r/20211216112359.103822-2-wangkefeng.wang@huawei.com
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com> [arm64]
Cc: Will Deacon <will@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: Dennis Zhou <dennis@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2022-01-19 18:07:41 -08:00
|
|
|
|
|
|
|
|
|
2006-06-11 23:03:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-31 17:55:43 -08:00
|
|
|
|
2006-06-11 23:03:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 10:05:39 +01:00
|
|
|
|
|
|
|
|
|
mips: Add MIPS Release 5 support
There are five MIPS32/64 architecture releases currently available:
from 1 to 6 except fourth one, which was intentionally skipped.
Three of them can be called as major: 1st, 2nd and 6th, that not only
have some system level alterations, but also introduced significant
core/ISA level updates. The rest of the MIPS architecture releases are
minor.
Even though they don't have as much ISA/system/core level changes
as the major ones with respect to the previous releases, they still
provide a set of updates (I'd say they were intended to be the
intermediate releases before a major one) that might be useful for the
kernel and user-level code, when activated by the kernel or compiler.
In particular the following features were introduced or ended up being
available at/after MIPS32/64 Release 5 architecture:
+ the last release of the misaligned memory access instructions,
+ virtualisation - VZ ASE - is optional component of the arch,
+ SIMD - MSA ASE - is optional component of the arch,
+ DSP ASE is optional component of the arch,
+ CP0.Status.FR=1 for CP1.FIR.F64=1 (pure 64-bit FPU general registers)
must be available if FPU is implemented,
+ CP1.FIR.Has2008 support is required so CP1.FCSR.{ABS2008,NAN2008} bits
are available.
+ UFR/UNFR aliases to access CP0.Status.FR from user-space by means of
ctc1/cfc1 instructions (enabled by CP0.Config5.UFR),
+ CP0.COnfig5.LLB=1 and eretnc instruction are implemented to without
accidentally clearing LL-bit when returning from an interrupt,
exception, or error trap,
+ XPA feature together with extended versions of CPx registers is
introduced, which needs to have mfhc0/mthc0 instructions available.
So due to these changes GNU GCC provides an extended instructions set
support for MIPS32/64 Release 5 by default like eretnc/mfhc0/mthc0. Even
though the architecture alteration isn't that big, it still worth to be
taken into account by the kernel software. Finally we can't deny that
some optimization/limitations might be found in future and implemented
on some level in kernel or compiler. In this case having even
intermediate MIPS architecture releases support would be more than
useful.
So the most of the changes provided by this commit can be split into
either compile- or runtime configs related. The compile-time related
changes are caused by adding the new CONFIG_CPU_MIPS32_R5/CONFIG_CPU_MIPSR5
configs and concern the code activating MIPSR2 or MIPSR6 already
implemented features (like eretnc/LLbit, mthc0/mfhc0). In addition
CPU_HAS_MSA can be now freely enabled for MIPS32/64 release 5 based
platforms as this is done for CPU_MIPS32_R6 CPUs. The runtime changes
concerns the features which are handled with respect to the MIPS ISA
revision detected at run-time by means of CP0.Config.{AT,AR} bits. Alas
these fields can be used to detect either r1 or r2 or r6 releases.
But since we know which CPUs in fact support the R5 arch, we can manually
set MIPS_CPU_ISA_M32R5/MIPS_CPU_ISA_M64R5 bit of c->isa_level and then
use cpu_has_mips32r5/cpu_has_mips64r5 where it's appropriate.
Since XPA/EVA provide too complex alterationss and to have them used with
MIPS32 Release 2 charged kernels (for compatibility with current platform
configs) they are left to be setup as a separate kernel configs.
Co-developed-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
2020-05-21 17:07:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-25 18:07:46 +08:00
|
|
|
|
|
|
|
|
|
2025-03-11 12:06:19 +01:00
|
|
|
|
2016-03-31 10:05:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 10:05:34 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-25 18:07:46 +08:00
|
|
|
|
2016-03-31 10:05:34 +01:00
|
|
|
|
2020-06-14 01:50:22 +09:00
|
|
|
|
2016-03-31 10:05:34 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 10:05:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-06-14 01:50:22 +09:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 10:05:41 +01:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2016-03-31 10:05:41 +01:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2016-03-31 10:05:41 +01:00
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2016-03-31 10:05:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-06-14 01:50:22 +09:00
|
|
|
|
2016-03-31 10:05:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-04-10 22:53:53 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-28 19:43:01 -07:00
|
|
|
|
2006-04-10 22:53:53 -07:00
|
|
|
|
2010-10-12 19:37:22 +08:00
|
|
|
|
|
|
|
|
|
2021-10-20 14:49:13 +02:00
|
|
|
|
2010-10-12 19:37:22 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-05 12:08:33 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2006-06-04 11:51:46 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2014-01-23 15:55:29 -08:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2014-01-23 15:55:29 -08:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2014-01-23 15:55:29 -08:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-03 15:50:21 +02:00
|
|
|
|
2020-07-14 21:12:26 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-07 08:50:40 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-19 12:23:51 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-15 10:31:53 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-04 11:51:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-02-06 16:53:15 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2014-04-29 20:07:40 +05:30
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2007-02-06 16:53:15 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-03-18 01:01:39 +09:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2007-03-18 01:01:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2012-07-13 16:44:53 -04:00
|
|
|
|
|
|
|
|
|
2017-09-28 12:34:04 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-13 16:44:53 -04:00
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
2015-09-22 10:16:39 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
2008-02-25 16:55:29 +00:00
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-22 10:16:39 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-22 10:16:39 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-22 10:16:39 -07:00
|
|
|
|
2006-06-20 00:19:13 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-07 10:30:19 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-12 12:15:39 -04:00
|
|
|
|
|
|
|
|
|
2007-01-16 23:29:11 +09:00
|
|
|
|
2023-07-12 12:15:39 -04:00
|
|
|
|
|
|
|
|
|
2012-10-11 18:14:58 +02:00
|
|
|
|
2024-09-17 12:37:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-11 18:14:58 +02:00
|
|
|
|
2016-12-02 09:58:29 +01:00
|
|
|
|
2018-03-26 19:11:51 +01:00
|
|
|
|
2016-12-02 09:58:29 +01:00
|
|
|
|
|
|
|
|
|
2012-10-11 18:14:58 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-22 13:12:07 +00:00
|
|
|
|
2018-11-07 23:13:58 +00:00
|
|
|
|
2013-11-22 13:12:07 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-14 17:55:18 +00:00
|
|
|
|
|
|
|
|
|
2020-10-27 18:34:30 +00:00
|
|
|
|
2014-02-14 17:55:18 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-22 13:12:07 +00:00
|
|
|
|
2010-10-13 00:52:46 -06:00
|
|
|
|
2012-09-18 11:28:54 +02:00
|
|
|
|
2010-10-13 00:52:46 -06:00
|
|
|
|
2010-11-18 15:54:56 -08:00
|
|
|
|
2012-02-24 08:07:06 -07:00
|
|
|
|
2010-10-13 00:52:46 -06:00
|
|
|
|
2018-09-11 14:49:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-21 13:04:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-12 12:24:58 +02:00
|
|
|
|
treewide: change conditional prompt for choices to 'depends on'
While Documentation/kbuild/kconfig-language.rst provides a brief
explanation, there are recurring confusions regarding the usage of a
prompt followed by 'if <expr>'. This conditional controls _only_ the
prompt.
A typical usage is as follows:
menuconfig BLOCK
bool "Enable the block layer" if EXPERT
default y
When EXPERT=n, the prompt is hidden, but this config entry is still
active, and BLOCK is set to its default value 'y'. This is reasonable
because you are likely want to enable the block device support. When
EXPERT=y, the prompt is shown, allowing you to toggle BLOCK.
Please note that it is different from 'depends on EXPERT', which would
enable and disable the entire config entry.
However, this conditional prompt has never worked in a choice block.
The following two work in the same way: when EXPERT is disabled, the
choice block is entirely disabled.
[Test Code 1]
choice
prompt "choose" if EXPERT
config A
bool "A"
config B
bool "B"
endchoice
[Test Code 2]
choice
prompt "choose"
depends on EXPERT
config A
bool "A"
config B
bool "B"
endchoice
I believe the first case should hide only the prompt, producing the
default:
CONFIG_A=y
# CONFIG_B is not set
The next commit will change (fix) the behavior of the conditional prompt
in choice blocks.
I see several choice blocks wrongly using a conditional prompt, where
'depends on' makes more sense.
To preserve the current behavior, this commit converts such misuses.
I did not touch the following entry in arch/x86/Kconfig:
choice
prompt "Memory split" if EXPERT
default VMSPLIT_3G
This is truly the correct use of the conditional prompt; when EXPERT=n,
this choice block should silently select the reasonable VMSPLIT_3G,
although the resulting PAGE_OFFSET will not be affected anyway.
Presumably, the one in fs/jffs2/Kconfig is also correct, but I converted
it to 'depends on' to avoid any potential behavioral change.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2024-06-27 03:22:00 +09:00
|
|
|
|
|
|
|
|
|
2015-04-12 12:24:58 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-11 17:46:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-10-27 18:34:30 +00:00
|
|
|
|
2015-09-11 17:46:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-12 12:24:58 +02:00
|
|
|
|
2016-06-20 11:27:36 +02:00
|
|
|
|
2015-04-12 12:24:58 +02:00
|
|
|
|
|
|
|
|
|
2016-06-20 11:27:36 +02:00
|
|
|
|
2015-04-12 12:24:58 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-12 13:13:02 +02:00
|
|
|
|
treewide: change conditional prompt for choices to 'depends on'
While Documentation/kbuild/kconfig-language.rst provides a brief
explanation, there are recurring confusions regarding the usage of a
prompt followed by 'if <expr>'. This conditional controls _only_ the
prompt.
A typical usage is as follows:
menuconfig BLOCK
bool "Enable the block layer" if EXPERT
default y
When EXPERT=n, the prompt is hidden, but this config entry is still
active, and BLOCK is set to its default value 'y'. This is reasonable
because you are likely want to enable the block device support. When
EXPERT=y, the prompt is shown, allowing you to toggle BLOCK.
Please note that it is different from 'depends on EXPERT', which would
enable and disable the entire config entry.
However, this conditional prompt has never worked in a choice block.
The following two work in the same way: when EXPERT is disabled, the
choice block is entirely disabled.
[Test Code 1]
choice
prompt "choose" if EXPERT
config A
bool "A"
config B
bool "B"
endchoice
[Test Code 2]
choice
prompt "choose"
depends on EXPERT
config A
bool "A"
config B
bool "B"
endchoice
I believe the first case should hide only the prompt, producing the
default:
CONFIG_A=y
# CONFIG_B is not set
The next commit will change (fix) the behavior of the conditional prompt
in choice blocks.
I see several choice blocks wrongly using a conditional prompt, where
'depends on' makes more sense.
To preserve the current behavior, this commit converts such misuses.
I did not touch the following entry in arch/x86/Kconfig:
choice
prompt "Memory split" if EXPERT
default VMSPLIT_3G
This is truly the correct use of the conditional prompt; when EXPERT=n,
this choice block should silently select the reasonable VMSPLIT_3G,
although the resulting PAGE_OFFSET will not be affected anyway.
Presumably, the one in fs/jffs2/Kconfig is also correct, but I converted
it to 'depends on' to avoid any potential behavioral change.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2024-06-27 03:22:00 +09:00
|
|
|
|
|
|
|
|
|
2015-10-12 13:13:03 +02:00
|
|
|
|
2025-07-16 19:25:16 +08:00
|
|
|
|
|
|
|
|
|
2015-10-12 13:13:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-28 11:03:09 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-12 13:13:02 +02:00
|
|
|
|
|
|
|
|
|
2005-10-29 19:32:41 +01:00
|
|
|
|
|
|
|
|
|
2006-09-26 23:44:01 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-14 15:45:51 -07:00
|
|
|
|
|
|
|
|
|
2017-02-16 17:27:34 -08:00
|
|
|
|
2021-11-25 18:59:48 +08:00
|
|
|
|
2015-04-14 15:45:51 -07:00
|
|
|
|
|
|
|
|
|
2018-07-27 18:23:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2016-10-05 18:18:12 +01:00
|
|
|
|
2018-11-15 20:05:33 +01:00
|
|
|
|
2016-10-05 18:18:12 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-15 20:05:33 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-16 10:36:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-24 17:32:45 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2016-11-24 17:32:45 +00:00
|
|
|
|
|
|
|
|
|
2019-03-11 16:54:27 +01:00
|
|
|
|
2016-11-24 17:32:45 +00:00
|
|
|
|
2007-10-11 23:46:10 +01:00
|
|
|
|
|
|
|
|
|
2011-05-08 19:03:03 +01:00
|
|
|
|
2011-06-09 13:08:27 +00:00
|
|
|
|
2009-11-17 01:32:58 +08:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MIPS: Compat: Fix build error if CONFIG_MIPS32_COMPAT but no compat ABI.
In that case nor __NR_seccomp_*_32 symbols will be defined in
<asm/unistd.h> so the attempt to use it in kernel.seccomp.c will fail
with:
kernel/seccomp.c:565:2: error: '__NR_seccomp_read_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:24: error: '__NR_seccomp_write_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:47: error: '__NR_seccomp_exit_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:69: error: '__NR_seccomp_sigreturn_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
Solved by changing the compat ABIs in kconfig to select MIPS32_COMPAT
directly. This also means the user no longer has to select MIPS32_COMPAT
before being able to see the ABI options.
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2014-12-19 01:18:03 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MIPS: Compat: Fix build error if CONFIG_MIPS32_COMPAT but no compat ABI.
In that case nor __NR_seccomp_*_32 symbols will be defined in
<asm/unistd.h> so the attempt to use it in kernel.seccomp.c will fail
with:
kernel/seccomp.c:565:2: error: '__NR_seccomp_read_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:24: error: '__NR_seccomp_write_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:47: error: '__NR_seccomp_exit_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:69: error: '__NR_seccomp_sigreturn_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
Solved by changing the compat ABIs in kconfig to select MIPS32_COMPAT
directly. This also means the user no longer has to select MIPS32_COMPAT
before being able to see the ABI options.
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2014-12-19 01:18:03 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-03 12:10:23 +01:00
|
|
|
|
2019-01-10 17:24:31 +01:00
|
|
|
|
MIPS: Compat: Fix build error if CONFIG_MIPS32_COMPAT but no compat ABI.
In that case nor __NR_seccomp_*_32 symbols will be defined in
<asm/unistd.h> so the attempt to use it in kernel.seccomp.c will fail
with:
kernel/seccomp.c:565:2: error: '__NR_seccomp_read_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:24: error: '__NR_seccomp_write_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:47: error: '__NR_seccomp_exit_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
^
kernel/seccomp.c:565:69: error: '__NR_seccomp_sigreturn_32' undeclared here (not in a function)
__NR_seccomp_read_32, __NR_seccomp_write_32, __NR_seccomp_exit_32, __NR_seccomp_sigreturn_32,
Solved by changing the compat ABIs in kconfig to select MIPS32_COMPAT
directly. This also means the user no longer has to select MIPS32_COMPAT
before being able to see the ABI options.
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2014-12-19 01:18:03 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-01-25 15:19:25 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-28 19:34:59 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-09 11:08:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-02-09 17:08:58 +00:00
|
|
|
|
2006-06-05 17:43:10 +02:00
|
|
|
|
2009-06-04 20:27:10 +08:00
|
|
|
|
|
|
|
|
|
2009-07-02 11:48:07 +01:00
|
|
|
|
2009-06-04 20:27:10 +08:00
|
|
|
|
2007-12-08 02:14:00 +01:00
|
|
|
|
|
|
|
|
|
2009-07-02 11:48:07 +01:00
|
|
|
|
2007-12-08 02:14:00 +01:00
|
|
|
|
2007-02-09 17:08:58 +00:00
|
|
|
|
2006-06-05 17:43:10 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 12:54:21 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-14 16:24:22 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 12:54:21 +00:00
|
|
|
|
2022-05-24 10:03:11 +02:00
|
|
|
|
2009-11-17 01:32:58 +08:00
|
|
|
|
2014-04-14 16:24:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-21 18:33:59 -08:00
|
|
|
|
2020-04-28 15:14:16 -07:00
|
|
|
|
|
|
|
|
|