License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2015-12-09 04:44:18 +08:00
|
|
|
config ARCH_VERSATILE
|
|
|
|
|
bool "ARM Ltd. Versatile family"
|
|
|
|
|
depends on ARCH_MULTI_V5
|
ARM: rework endianess selection
Choosing big-endian vs little-endian kernels in Kconfig has not worked
correctly since the introduction of CONFIG_ARCH_MULTIPLATFORM a long
time ago.
The problems is that CONFIG_BIG_ENDIAN depends on
ARCH_SUPPORTS_BIG_ENDIAN, which can set by any one platform
in the config, but would actually have to be supported by all
of them.
This was mostly ok for ARMv6/ARMv7 builds, since these are BE8 and
tend to just work aside from problems in nonportable device drivers.
For ARMv4/v5 machines, CONFIG_BIG_ENDIAN and CONFIG_ARCH_MULTIPLATFORM
were never set together, so this was disabled on all those machines
except for IXP4xx.
As IXP4xx can now become part of ARCH_MULTIPLATFORM, it seems better to
formalize this logic: all ARMv4/v5 platforms get an explicit dependency
on being either big-endian (ixp4xx) or little-endian (the rest). We may
want to fix ixp4xx in the future to support both, but it does not work
in LE mode at the moment.
For the ARMv6/v7 platforms, there are two ways this could be handled
a) allow both modes only for platforms selecting
'ARCH_SUPPORTS_BIG_ENDIAN' today, but only LE mode for the
others, given that these were added intentionally at some
point.
b) allow both modes everwhere, given that it was already possible
to build that way by e.g. selecting ARCH_VIRT, and that the
list is not an accurate reflection of which platforms may or
may not work.
Out of these, I picked b) because it seemed slighly more logical
to me.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2022-04-04 17:52:31 +08:00
|
|
|
depends on CPU_LITTLE_ENDIAN
|
2015-12-09 04:44:18 +08:00
|
|
|
select ARM_AMBA
|
|
|
|
|
select ARM_TIMER_SP804
|
|
|
|
|
select ARM_VIC
|
|
|
|
|
select CLKSRC_VERSATILE
|
|
|
|
|
select CPU_ARM926T
|
2021-09-02 00:08:33 +08:00
|
|
|
select CLK_ICST
|
2016-01-25 16:23:02 +08:00
|
|
|
select MFD_SYSCON
|
2015-12-09 04:44:18 +08:00
|
|
|
select PLAT_VERSATILE
|
2016-01-25 16:23:02 +08:00
|
|
|
select POWER_RESET
|
|
|
|
|
select POWER_RESET_VERSATILE
|
2015-12-09 04:44:18 +08:00
|
|
|
select VERSATILE_FPGA_IRQ
|
|
|
|
|
help
|
|
|
|
|
This enables support for ARM Ltd Versatile board.
|
|
|
|
|
|
2022-04-01 20:35:42 +08:00
|
|
|
menuconfig ARCH_INTEGRATOR
|
|
|
|
|
bool "ARM Ltd. Integrator family"
|
|
|
|
|
depends on ARCH_MULTI_V4T || ARCH_MULTI_V5 || ARCH_MULTI_V6
|
ARM: rework endianess selection
Choosing big-endian vs little-endian kernels in Kconfig has not worked
correctly since the introduction of CONFIG_ARCH_MULTIPLATFORM a long
time ago.
The problems is that CONFIG_BIG_ENDIAN depends on
ARCH_SUPPORTS_BIG_ENDIAN, which can set by any one platform
in the config, but would actually have to be supported by all
of them.
This was mostly ok for ARMv6/ARMv7 builds, since these are BE8 and
tend to just work aside from problems in nonportable device drivers.
For ARMv4/v5 machines, CONFIG_BIG_ENDIAN and CONFIG_ARCH_MULTIPLATFORM
were never set together, so this was disabled on all those machines
except for IXP4xx.
As IXP4xx can now become part of ARCH_MULTIPLATFORM, it seems better to
formalize this logic: all ARMv4/v5 platforms get an explicit dependency
on being either big-endian (ixp4xx) or little-endian (the rest). We may
want to fix ixp4xx in the future to support both, but it does not work
in LE mode at the moment.
For the ARMv6/v7 platforms, there are two ways this could be handled
a) allow both modes only for platforms selecting
'ARCH_SUPPORTS_BIG_ENDIAN' today, but only LE mode for the
others, given that these were added intentionally at some
point.
b) allow both modes everwhere, given that it was already possible
to build that way by e.g. selecting ARCH_VIRT, and that the
list is not an accurate reflection of which platforms may or
may not work.
Out of these, I picked b) because it seemed slighly more logical
to me.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2022-04-04 17:52:31 +08:00
|
|
|
depends on CPU_LITTLE_ENDIAN || ARCH_MULTI_V6
|
2022-04-01 20:35:42 +08:00
|
|
|
select ARM_AMBA
|
|
|
|
|
select CMA
|
|
|
|
|
select DMA_CMA
|
|
|
|
|
select HAVE_TCM
|
|
|
|
|
select CLK_ICST
|
|
|
|
|
select MFD_SYSCON
|
|
|
|
|
select PLAT_VERSATILE
|
|
|
|
|
select POWER_RESET
|
|
|
|
|
select POWER_RESET_VERSATILE
|
|
|
|
|
select POWER_SUPPLY
|
|
|
|
|
select SOC_INTEGRATOR_CM
|
|
|
|
|
select VERSATILE_FPGA_IRQ
|
|
|
|
|
help
|
|
|
|
|
Support for ARM's Integrator platform.
|
|
|
|
|
|
|
|
|
|
if ARCH_INTEGRATOR
|
|
|
|
|
|
|
|
|
|
config ARCH_INTEGRATOR_AP
|
|
|
|
|
bool "Support Integrator/AP and Integrator/PP2 platforms"
|
|
|
|
|
select INTEGRATOR_AP_TIMER
|
|
|
|
|
select SERIAL_AMBA_PL010 if TTY
|
|
|
|
|
select SERIAL_AMBA_PL010_CONSOLE if TTY
|
|
|
|
|
select SOC_BUS
|
|
|
|
|
help
|
|
|
|
|
Include support for the ARM(R) Integrator/AP and
|
|
|
|
|
Integrator/PP2 platforms.
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_IMPD1
|
|
|
|
|
bool "Include support for Integrator/IM-PD1"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
select ARM_VIC
|
|
|
|
|
select GPIO_PL061
|
|
|
|
|
select GPIOLIB
|
|
|
|
|
select REGULATOR
|
|
|
|
|
select REGULATOR_FIXED_VOLTAGE
|
|
|
|
|
help
|
|
|
|
|
The IM-PD1 is an add-on logic module for the Integrator which
|
|
|
|
|
allows ARM(R) Ltd PrimeCells to be developed and evaluated.
|
|
|
|
|
The IM-PD1 can be found on the Integrator/PP2 platform.
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM720T
|
|
|
|
|
bool "Integrator/CM720T core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
depends on ARCH_MULTI_V4T
|
|
|
|
|
select CPU_ARM720T
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM920T
|
|
|
|
|
bool "Integrator/CM920T core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
depends on ARCH_MULTI_V4T
|
|
|
|
|
select CPU_ARM920T
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM922T_XA10
|
|
|
|
|
bool "Integrator/CM922T-XA10 core module"
|
|
|
|
|
depends on ARCH_MULTI_V4T
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
select CPU_ARM922T
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM926EJS
|
|
|
|
|
bool "Integrator/CM926EJ-S core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
depends on ARCH_MULTI_V5
|
|
|
|
|
select CPU_ARM926T
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM10200E_REV0
|
|
|
|
|
bool "Integrator/CM10200E rev.0 core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP && n
|
|
|
|
|
depends on ARCH_MULTI_V5
|
|
|
|
|
select CPU_ARM1020
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM10200E
|
|
|
|
|
bool "Integrator/CM10200E core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP && n
|
|
|
|
|
depends on ARCH_MULTI_V5
|
|
|
|
|
select CPU_ARM1020E
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM10220E
|
|
|
|
|
bool "Integrator/CM10220E core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
depends on ARCH_MULTI_V5
|
|
|
|
|
select CPU_ARM1022
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM1026EJS
|
|
|
|
|
bool "Integrator/CM1026EJ-S core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
depends on ARCH_MULTI_V5
|
|
|
|
|
select CPU_ARM1026
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CM1136JFS
|
|
|
|
|
bool "Integrator/CM1136JF-S core module"
|
|
|
|
|
depends on ARCH_INTEGRATOR_AP
|
|
|
|
|
depends on ARCH_MULTI_V6
|
|
|
|
|
select CPU_V6
|
|
|
|
|
|
|
|
|
|
config ARCH_INTEGRATOR_CP
|
|
|
|
|
bool "Support Integrator/CP platform"
|
|
|
|
|
depends on ARCH_MULTI_V5 || ARCH_MULTI_V6
|
|
|
|
|
select ARM_TIMER_SP804
|
|
|
|
|
select SERIAL_AMBA_PL011 if TTY
|
|
|
|
|
select SERIAL_AMBA_PL011_CONSOLE if TTY
|
|
|
|
|
select SOC_BUS
|
|
|
|
|
help
|
|
|
|
|
Include support for the ARM(R) Integrator CP platform.
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CT926
|
|
|
|
|
bool "Integrator/CT926 (ARM926EJ-S) core tile"
|
|
|
|
|
depends on ARCH_INTEGRATOR_CP
|
|
|
|
|
depends on ARCH_MULTI_V5
|
|
|
|
|
select CPU_ARM926T
|
|
|
|
|
|
|
|
|
|
config INTEGRATOR_CTB36
|
|
|
|
|
bool "Integrator/CTB36 (ARM1136JF-S) core tile"
|
|
|
|
|
depends on ARCH_INTEGRATOR_CP
|
|
|
|
|
depends on ARCH_MULTI_V6
|
|
|
|
|
select CPU_V6
|
|
|
|
|
|
|
|
|
|
config ARCH_CINTEGRATOR
|
|
|
|
|
depends on ARCH_INTEGRATOR_CP
|
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
menuconfig ARCH_REALVIEW
|
|
|
|
|
bool "ARM Ltd. RealView family"
|
ARM: rework endianess selection
Choosing big-endian vs little-endian kernels in Kconfig has not worked
correctly since the introduction of CONFIG_ARCH_MULTIPLATFORM a long
time ago.
The problems is that CONFIG_BIG_ENDIAN depends on
ARCH_SUPPORTS_BIG_ENDIAN, which can set by any one platform
in the config, but would actually have to be supported by all
of them.
This was mostly ok for ARMv6/ARMv7 builds, since these are BE8 and
tend to just work aside from problems in nonportable device drivers.
For ARMv4/v5 machines, CONFIG_BIG_ENDIAN and CONFIG_ARCH_MULTIPLATFORM
were never set together, so this was disabled on all those machines
except for IXP4xx.
As IXP4xx can now become part of ARCH_MULTIPLATFORM, it seems better to
formalize this logic: all ARMv4/v5 platforms get an explicit dependency
on being either big-endian (ixp4xx) or little-endian (the rest). We may
want to fix ixp4xx in the future to support both, but it does not work
in LE mode at the moment.
For the ARMv6/v7 platforms, there are two ways this could be handled
a) allow both modes only for platforms selecting
'ARCH_SUPPORTS_BIG_ENDIAN' today, but only LE mode for the
others, given that these were added intentionally at some
point.
b) allow both modes everwhere, given that it was already possible
to build that way by e.g. selecting ARCH_VIRT, and that the
list is not an accurate reflection of which platforms may or
may not work.
Out of these, I picked b) because it seemed slighly more logical
to me.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2022-04-04 17:52:31 +08:00
|
|
|
depends on (CPU_LITTLE_ENDIAN && ARCH_MULTI_V5) || ARCH_MULTI_V6 || ARCH_MULTI_V7
|
2022-04-01 20:35:42 +08:00
|
|
|
select ARM_AMBA
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select ARM_TIMER_SP804
|
|
|
|
|
select CLK_SP810
|
|
|
|
|
select GPIO_PL061 if GPIOLIB
|
|
|
|
|
select HAVE_ARM_SCU if SMP
|
|
|
|
|
select HAVE_ARM_TWD if SMP
|
|
|
|
|
select HAVE_PATA_PLATFORM
|
|
|
|
|
select HAVE_TCM
|
|
|
|
|
select CLK_ICST
|
|
|
|
|
select MACH_REALVIEW_EB if ARCH_MULTI_V5
|
|
|
|
|
select MFD_SYSCON
|
|
|
|
|
select PLAT_VERSATILE
|
|
|
|
|
select POWER_RESET
|
|
|
|
|
select POWER_RESET_VERSATILE
|
|
|
|
|
select POWER_SUPPLY
|
|
|
|
|
select SOC_REALVIEW
|
|
|
|
|
help
|
|
|
|
|
This enables support for ARM Ltd RealView boards.
|
|
|
|
|
|
|
|
|
|
if ARCH_REALVIEW
|
|
|
|
|
|
|
|
|
|
config MACH_REALVIEW_EB
|
|
|
|
|
bool "Support RealView(R) Emulation Baseboard"
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select CPU_ARM926T if ARCH_MULTI_V5
|
|
|
|
|
help
|
|
|
|
|
Include support for the ARM(R) RealView(R) Emulation Baseboard
|
|
|
|
|
platform. On an ARMv5 kernel, this will include support for
|
|
|
|
|
the ARM926EJ-S core tile, while on an ARMv6/v7 kernel, at least
|
|
|
|
|
one of the ARM1136, ARM1176, ARM11MPCore or Cortex-A9MPCore
|
|
|
|
|
core tile options should be enabled.
|
|
|
|
|
|
|
|
|
|
config REALVIEW_EB_ARM1136
|
|
|
|
|
bool "Support ARM1136J(F)-S Tile"
|
|
|
|
|
depends on MACH_REALVIEW_EB && ARCH_MULTI_V6
|
|
|
|
|
select CPU_V6
|
|
|
|
|
help
|
|
|
|
|
Enable support for the ARM1136 tile fitted to the
|
|
|
|
|
Realview(R) Emulation Baseboard platform.
|
|
|
|
|
|
|
|
|
|
config REALVIEW_EB_ARM1176
|
|
|
|
|
bool "Support ARM1176JZ(F)-S Tile"
|
|
|
|
|
depends on MACH_REALVIEW_EB && ARCH_MULTI_V6
|
|
|
|
|
help
|
|
|
|
|
Enable support for the ARM1176 tile fitted to the
|
|
|
|
|
Realview(R) Emulation Baseboard platform.
|
|
|
|
|
|
|
|
|
|
config REALVIEW_EB_A9MP
|
|
|
|
|
bool "Support Multicore Cortex-A9 Tile"
|
|
|
|
|
depends on MACH_REALVIEW_EB && ARCH_MULTI_V7
|
|
|
|
|
help
|
|
|
|
|
Enable support for the Cortex-A9MPCore tile fitted to the
|
|
|
|
|
Realview(R) Emulation Baseboard platform.
|
|
|
|
|
|
|
|
|
|
config REALVIEW_EB_ARM11MP
|
|
|
|
|
bool "Support ARM11MPCore Tile"
|
|
|
|
|
depends on MACH_REALVIEW_EB && ARCH_MULTI_V6
|
|
|
|
|
select HAVE_SMP
|
|
|
|
|
help
|
|
|
|
|
Enable support for the ARM11MPCore tile fitted to the Realview(R)
|
|
|
|
|
Emulation Baseboard platform.
|
|
|
|
|
|
|
|
|
|
config MACH_REALVIEW_PB11MP
|
|
|
|
|
bool "Support RealView(R) Platform Baseboard for ARM11MPCore"
|
|
|
|
|
depends on ARCH_MULTI_V6
|
|
|
|
|
select HAVE_SMP
|
|
|
|
|
help
|
|
|
|
|
Include support for the ARM(R) RealView(R) Platform Baseboard for
|
|
|
|
|
the ARM11MPCore. This platform has an on-board ARM11MPCore and has
|
|
|
|
|
support for PCI-E and Compact Flash.
|
|
|
|
|
|
|
|
|
|
# ARMv6 CPU without K extensions, but does have the new exclusive ops
|
|
|
|
|
config MACH_REALVIEW_PB1176
|
|
|
|
|
bool "Support RealView(R) Platform Baseboard for ARM1176JZF-S"
|
|
|
|
|
depends on ARCH_MULTI_V6
|
|
|
|
|
select CPU_V6
|
|
|
|
|
select HAVE_TCM
|
|
|
|
|
help
|
|
|
|
|
Include support for the ARM(R) RealView(R) Platform Baseboard for
|
|
|
|
|
ARM1176JZF-S.
|
|
|
|
|
|
|
|
|
|
config MACH_REALVIEW_PBA8
|
|
|
|
|
bool "Support RealView(R) Platform Baseboard for Cortex(tm)-A8 platform"
|
|
|
|
|
depends on ARCH_MULTI_V7
|
|
|
|
|
help
|
|
|
|
|
Include support for the ARM(R) RealView Platform Baseboard for
|
|
|
|
|
Cortex(tm)-A8. This platform has an on-board Cortex-A8 and has
|
|
|
|
|
support for PCI-E and Compact Flash.
|
|
|
|
|
|
|
|
|
|
config MACH_REALVIEW_PBX
|
|
|
|
|
bool "Support RealView(R) Platform Baseboard Explore for Cortex-A9"
|
|
|
|
|
depends on ARCH_MULTI_V7
|
|
|
|
|
select ZONE_DMA
|
|
|
|
|
help
|
|
|
|
|
Include support for the ARM(R) RealView(R) Platform Baseboard
|
|
|
|
|
Explore.
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
menuconfig ARCH_VEXPRESS
|
|
|
|
|
bool "ARM Ltd. Versatile Express family"
|
|
|
|
|
depends on ARCH_MULTI_V7
|
|
|
|
|
select ARM_AMBA
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select ARM_GLOBAL_TIMER
|
|
|
|
|
select ARM_TIMER_SP804
|
|
|
|
|
select GPIOLIB
|
|
|
|
|
select HAVE_ARM_SCU if SMP
|
|
|
|
|
select HAVE_ARM_TWD if SMP
|
|
|
|
|
select HAVE_PATA_PLATFORM
|
|
|
|
|
select CLK_ICST
|
|
|
|
|
select NO_IOPORT_MAP
|
|
|
|
|
select PLAT_VERSATILE
|
|
|
|
|
select POWER_RESET
|
|
|
|
|
select POWER_RESET_VEXPRESS
|
|
|
|
|
select POWER_SUPPLY
|
|
|
|
|
select REGULATOR if MMC_ARMMMCI
|
|
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
|
|
|
|
select VEXPRESS_CONFIG
|
|
|
|
|
help
|
|
|
|
|
This option enables support for systems using Cortex processor based
|
|
|
|
|
ARM core and logic (FPGA) tiles on the Versatile Express motherboard,
|
|
|
|
|
for example:
|
|
|
|
|
|
|
|
|
|
- CoreTile Express A5x2 (V2P-CA5s)
|
|
|
|
|
- CoreTile Express A9x4 (V2P-CA9)
|
|
|
|
|
- CoreTile Express A15x2 (V2P-CA15)
|
|
|
|
|
- LogicTile Express 13MG (V2F-2XV6) with A5, A7, A9 or A15 SMMs
|
|
|
|
|
(Soft Macrocell Models)
|
|
|
|
|
- Versatile Express RTSMs (Models)
|
|
|
|
|
|
|
|
|
|
You must boot using a Flattened Device Tree in order to use these
|
|
|
|
|
platforms. The traditional (ATAGs) boot method is not usable on
|
|
|
|
|
these boards with this option.
|
|
|
|
|
|
|
|
|
|
if ARCH_VEXPRESS
|
|
|
|
|
|
|
|
|
|
config ARCH_VEXPRESS_CORTEX_A5_A9_ERRATA
|
|
|
|
|
bool "Enable A5 and A9 only errata work-arounds"
|
|
|
|
|
default y
|
|
|
|
|
select ARM_ERRATA_643719 if SMP
|
|
|
|
|
select ARM_ERRATA_720789
|
|
|
|
|
select PL310_ERRATA_753970 if CACHE_L2X0
|
|
|
|
|
help
|
|
|
|
|
Provides common dependencies for Versatile Express platforms
|
|
|
|
|
based on Cortex-A5 and Cortex-A9 processors. In order to
|
|
|
|
|
build a working kernel, you must also enable relevant core
|
|
|
|
|
tile support or Flattened Device Tree based support options.
|
|
|
|
|
|
|
|
|
|
config ARCH_VEXPRESS_DCSCB
|
|
|
|
|
bool "Dual Cluster System Control Block (DCSCB) support"
|
|
|
|
|
depends on MCPM
|
|
|
|
|
select ARM_CCI400_PORT_CTRL
|
|
|
|
|
help
|
|
|
|
|
Support for the Dual Cluster System Configuration Block (DCSCB).
|
|
|
|
|
This is needed to provide CPU and cluster power management
|
|
|
|
|
on RTSM implementing big.LITTLE.
|
|
|
|
|
|
|
|
|
|
config ARCH_VEXPRESS_SPC
|
|
|
|
|
bool "Versatile Express Serial Power Controller (SPC)"
|
|
|
|
|
select PM_OPP
|
|
|
|
|
help
|
|
|
|
|
The TC2 (A15x2 A7x3) versatile express core tile integrates a logic
|
|
|
|
|
block called Serial Power Controller (SPC) that provides the interface
|
|
|
|
|
between the dual cluster test-chip and the M3 microcontroller that
|
|
|
|
|
carries out power management.
|
|
|
|
|
|
|
|
|
|
config ARCH_VEXPRESS_TC2_PM
|
|
|
|
|
bool "Versatile Express TC2 power management"
|
|
|
|
|
depends on MCPM
|
|
|
|
|
select ARM_CCI400_PORT_CTRL
|
|
|
|
|
select ARCH_VEXPRESS_SPC
|
|
|
|
|
select ARM_CPU_SUSPEND
|
|
|
|
|
help
|
|
|
|
|
Support for CPU and cluster power management on Versatile Express
|
|
|
|
|
with a TC2 (A15x2 A7x3) big.LITTLE core tile.
|
|
|
|
|
|
|
|
|
|
endif
|