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 17:07:57 +03:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2008-02-08 15:19:31 +03:00
|
|
|
config MN10300
|
|
|
|
def_bool y
|
2016-05-21 03:00:16 +03:00
|
|
|
select HAVE_EXIT_THREAD
|
2009-02-21 02:38:38 +03:00
|
|
|
select HAVE_OPROFILE
|
2015-11-28 19:52:04 +03:00
|
|
|
select HAVE_UID16
|
2011-03-24 20:54:24 +03:00
|
|
|
select GENERIC_IRQ_SHOW
|
2012-07-31 01:42:46 +04:00
|
|
|
select ARCH_WANT_IPC_PARSE_VERSION
|
2011-03-18 19:54:31 +03:00
|
|
|
select HAVE_ARCH_TRACEHOOK
|
|
|
|
select HAVE_ARCH_KGDB
|
2013-01-12 02:31:54 +04:00
|
|
|
select GENERIC_ATOMIC64
|
2012-03-24 02:01:51 +04:00
|
|
|
select HAVE_NMI_WATCHDOG if MN10300_WD_TIMER
|
2013-03-07 08:48:16 +04:00
|
|
|
select VIRT_TO_BUS
|
2012-05-18 20:45:50 +04:00
|
|
|
select GENERIC_CLOCKEVENTS
|
2012-09-28 09:01:03 +04:00
|
|
|
select MODULES_USE_ELF_RELA
|
2012-12-26 01:24:21 +04:00
|
|
|
select OLD_SIGSUSPEND3
|
2012-12-26 04:28:15 +04:00
|
|
|
select OLD_SIGACTION
|
2013-07-02 00:04:42 +04:00
|
|
|
select HAVE_DEBUG_STACKOVERFLOW
|
2016-01-21 02:01:50 +03:00
|
|
|
select ARCH_NO_COHERENT_DMA_MMAP
|
2008-02-08 15:19:31 +03:00
|
|
|
|
2010-10-27 20:28:38 +04:00
|
|
|
config AM33_2
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
config AM33_3
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
config AM34_2
|
|
|
|
def_bool n
|
2010-10-27 20:28:40 +04:00
|
|
|
select MN10300_HAS_ATOMIC_OPS_UNIT
|
2010-10-27 20:28:46 +04:00
|
|
|
select MN10300_HAS_CACHE_SNOOP
|
2008-02-08 15:19:31 +03:00
|
|
|
|
2010-10-27 20:28:48 +04:00
|
|
|
config ERRATUM_NEED_TO_RELOAD_MMUCTR
|
|
|
|
def_bool y if AM33_3 || AM34_2
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
config MMU
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config HIGHMEM
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
config NUMA
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
config RWSEM_GENERIC_SPINLOCK
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config RWSEM_XCHGADD_ALGORITHM
|
|
|
|
bool
|
|
|
|
|
|
|
|
config GENERIC_CALIBRATE_DELAY
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config GENERIC_HWEIGHT
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config GENERIC_BUG
|
|
|
|
def_bool y
|
2016-03-18 00:21:06 +03:00
|
|
|
depends on BUG
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
config QUICKLIST
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config ARCH_HAS_ILOG2_U32
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config HOTPLUG_CPU
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
source "init/Kconfig"
|
|
|
|
|
2008-10-19 07:27:21 +04:00
|
|
|
source "kernel/Kconfig.freezer"
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
|
2010-10-27 20:29:00 +04:00
|
|
|
menu "Panasonic MN10300 system setup"
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Unit type"
|
|
|
|
default MN10300_UNIT_ASB2303
|
|
|
|
help
|
|
|
|
This option specifies board for which the kernel will be
|
|
|
|
compiled. It affects the external peripherals catered for.
|
|
|
|
|
|
|
|
config MN10300_UNIT_ASB2303
|
|
|
|
bool "ASB2303"
|
|
|
|
|
|
|
|
config MN10300_UNIT_ASB2305
|
|
|
|
bool "ASB2305"
|
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
config MN10300_UNIT_ASB2364
|
|
|
|
bool "ASB2364"
|
2010-10-27 20:28:58 +04:00
|
|
|
select SMSC911X_ARCH_HOOKS if SMSC911X
|
2010-10-27 20:28:55 +04:00
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Processor support"
|
|
|
|
default MN10300_PROC_MN103E010
|
|
|
|
help
|
|
|
|
This option specifies the processor for which the kernel will be
|
|
|
|
compiled. It affects the on-chip peripherals catered for.
|
|
|
|
|
|
|
|
config MN10300_PROC_MN103E010
|
|
|
|
bool "MN103E010"
|
|
|
|
depends on MN10300_UNIT_ASB2303 || MN10300_UNIT_ASB2305
|
2010-10-27 20:28:38 +04:00
|
|
|
select AM33_2
|
2008-02-08 15:19:31 +03:00
|
|
|
select MN10300_PROC_HAS_TTYSM0
|
|
|
|
select MN10300_PROC_HAS_TTYSM1
|
|
|
|
select MN10300_PROC_HAS_TTYSM2
|
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
config MN10300_PROC_MN2WS0050
|
|
|
|
bool "MN2WS0050"
|
|
|
|
depends on MN10300_UNIT_ASB2364
|
|
|
|
select AM34_2
|
|
|
|
select MN10300_PROC_HAS_TTYSM0
|
|
|
|
select MN10300_PROC_HAS_TTYSM1
|
|
|
|
select MN10300_PROC_HAS_TTYSM2
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2010-10-27 20:28:40 +04:00
|
|
|
config MN10300_HAS_ATOMIC_OPS_UNIT
|
|
|
|
def_bool n
|
|
|
|
help
|
|
|
|
This should be enabled if the processor has an atomic ops unit
|
|
|
|
capable of doing LL/SC equivalent operations.
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
config FPU
|
|
|
|
bool "FPU present"
|
|
|
|
default y
|
2010-10-27 20:28:55 +04:00
|
|
|
depends on MN10300_PROC_MN103E010 || MN10300_PROC_MN2WS0050
|
2008-02-08 15:19:31 +03:00
|
|
|
|
2010-10-27 20:28:52 +04:00
|
|
|
config LAZY_SAVE_FPU
|
|
|
|
bool "Save FPU state lazily"
|
|
|
|
default y
|
|
|
|
depends on FPU && !SMP
|
|
|
|
help
|
|
|
|
Enable this to be lazy in the saving of the FPU state to the owning
|
|
|
|
task's thread struct. This is useful if most tasks on the system
|
|
|
|
don't use the FPU as only those tasks that use it will pass it
|
|
|
|
between them, and the state needn't be saved for a task that isn't
|
|
|
|
using it.
|
|
|
|
|
|
|
|
This can't be so easily used on SMP as the process that owns the FPU
|
|
|
|
state on a CPU may be currently running on another CPU, so for the
|
|
|
|
moment, it is disabled.
|
|
|
|
|
2010-10-27 20:28:41 +04:00
|
|
|
source "arch/mn10300/mm/Kconfig.cache"
|
2008-02-08 15:19:31 +03:00
|
|
|
|
2010-10-27 20:28:49 +04:00
|
|
|
config MN10300_TLB_USE_PIDR
|
|
|
|
def_bool y
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
menu "Memory layout options"
|
|
|
|
|
|
|
|
config KERNEL_RAM_BASE_ADDRESS
|
|
|
|
hex "Base address of kernel RAM"
|
|
|
|
default "0x90000000"
|
|
|
|
|
|
|
|
config INTERRUPT_VECTOR_BASE
|
|
|
|
hex "Base address of vector table"
|
|
|
|
default "0x90000000"
|
|
|
|
help
|
|
|
|
The base address of the vector table will be programmed into
|
|
|
|
the TBR register. It must be on 16MiB address boundary.
|
|
|
|
|
|
|
|
config KERNEL_TEXT_ADDRESS
|
|
|
|
hex "Base address of kernel"
|
|
|
|
default "0x90001000"
|
|
|
|
|
|
|
|
config KERNEL_ZIMAGE_BASE_ADDRESS
|
|
|
|
hex "Base address of compressed vmlinux image"
|
2010-10-27 20:28:55 +04:00
|
|
|
default "0x50700000"
|
|
|
|
|
|
|
|
config BOOT_STACK_OFFSET
|
|
|
|
hex
|
|
|
|
default "0xF00" if SMP
|
|
|
|
default "0xFF0" if !SMP
|
2008-02-08 15:19:31 +03:00
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
config BOOT_STACK_SIZE
|
|
|
|
hex
|
|
|
|
depends on SMP
|
|
|
|
default "0x100"
|
2008-02-08 15:19:31 +03:00
|
|
|
endmenu
|
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
config SMP
|
|
|
|
bool "Symmetric multi-processing support"
|
|
|
|
default y
|
2014-09-26 13:15:18 +04:00
|
|
|
depends on MN10300_PROC_MN2WS0050
|
2010-10-27 20:28:55 +04:00
|
|
|
---help---
|
|
|
|
This enables support for systems with more than one CPU. If you have
|
2014-01-24 03:55:29 +04:00
|
|
|
a system with only one CPU, say N. If you have a system with more
|
|
|
|
than one CPU, say Y.
|
2010-10-27 20:28:55 +04:00
|
|
|
|
2014-01-24 03:55:29 +04:00
|
|
|
If you say N here, the kernel will run on uni- and multiprocessor
|
2010-10-27 20:28:55 +04:00
|
|
|
machines, but will use only one CPU of a multiprocessor machine. If
|
|
|
|
you say Y here, the kernel will run on many, but not all,
|
2014-01-24 03:55:29 +04:00
|
|
|
uniprocessor machines. On a uniprocessor machine, the kernel
|
2010-10-27 20:28:55 +04:00
|
|
|
will run faster if you say N here.
|
|
|
|
|
2011-08-15 04:02:26 +04:00
|
|
|
See also <file:Documentation/x86/i386/IO-APIC.txt>,
|
2010-10-27 20:28:55 +04:00
|
|
|
<file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
2008-02-08 15:19:31 +03:00
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
If you don't know what to do here, say N.
|
|
|
|
|
|
|
|
config NR_CPUS
|
|
|
|
int
|
|
|
|
depends on SMP
|
|
|
|
default "2"
|
|
|
|
|
|
|
|
source "kernel/Kconfig.preempt"
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
config MN10300_CURRENT_IN_E2
|
|
|
|
bool "Hold current task address in E2 register"
|
2010-10-27 20:28:55 +04:00
|
|
|
depends on !SMP
|
2008-02-08 15:19:31 +03:00
|
|
|
default y
|
|
|
|
help
|
|
|
|
This option removes the E2/R2 register from the set available to gcc
|
|
|
|
for normal use and instead uses it to store the address of the
|
|
|
|
current process's task_struct whilst in the kernel.
|
|
|
|
|
|
|
|
This means the kernel doesn't need to calculate the address each time
|
|
|
|
"current" is used (take SP, AND with mask and dereference pointer
|
|
|
|
just to get the address), and instead can just use E2+offset
|
|
|
|
addressing each time.
|
|
|
|
|
|
|
|
This has no effect on userspace.
|
|
|
|
|
|
|
|
config MN10300_USING_JTAG
|
|
|
|
bool "Using JTAG to debug kernel"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
This options indicates that JTAG will be used to debug the kernel. It
|
|
|
|
suppresses the use of certain hardware debugging features, such as
|
|
|
|
single-stepping, which are taken over completely by the JTAG unit.
|
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
source "kernel/Kconfig.hz"
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
config MN10300_RTC
|
|
|
|
bool "Using MN10300 RTC"
|
2010-10-27 20:28:55 +04:00
|
|
|
depends on MN10300_PROC_MN103E010 || MN10300_PROC_MN2WS0050
|
2016-06-01 17:46:22 +03:00
|
|
|
select RTC_CLASS
|
|
|
|
select RTC_DRV_CMOS
|
|
|
|
select RTC_SYSTOHC
|
2008-02-08 15:19:31 +03:00
|
|
|
default n
|
|
|
|
help
|
|
|
|
This option enables support for the RTC, thus enabling time to be
|
|
|
|
tracked, even when system is powered down. This is available on-chip
|
|
|
|
on the MN103E010.
|
|
|
|
|
|
|
|
config MN10300_WD_TIMER
|
|
|
|
bool "Using MN10300 watchdog timer"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
This options indicates that the watchdog timer will be used.
|
|
|
|
|
|
|
|
config PCI
|
|
|
|
bool "Use PCI"
|
|
|
|
depends on MN10300_UNIT_ASB2305
|
|
|
|
default y
|
2011-12-01 14:41:36 +04:00
|
|
|
select GENERIC_PCI_IOMAP
|
2008-02-08 15:19:31 +03:00
|
|
|
help
|
|
|
|
Some systems (such as the ASB2305) have PCI onboard. If you have one
|
|
|
|
of these boards and you wish to use the PCI facilities, say Y here.
|
|
|
|
|
|
|
|
The PCI-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>, contains valuable
|
|
|
|
information about which PCI hardware does work under Linux and which
|
|
|
|
doesn't.
|
|
|
|
|
|
|
|
source "drivers/pci/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/pcmcia/Kconfig"
|
|
|
|
|
|
|
|
menu "MN10300 internal serial options"
|
|
|
|
|
|
|
|
config MN10300_PROC_HAS_TTYSM0
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
|
|
|
config MN10300_PROC_HAS_TTYSM1
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
|
|
|
config MN10300_PROC_HAS_TTYSM2
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
|
|
|
config MN10300_TTYSM
|
|
|
|
bool "Support for ttySM serial ports"
|
|
|
|
depends on MN10300
|
|
|
|
default y
|
|
|
|
select SERIAL_CORE
|
|
|
|
help
|
|
|
|
This option enables support for the on-chip serial ports that the
|
|
|
|
MN10300 has available.
|
|
|
|
|
|
|
|
config MN10300_TTYSM_CONSOLE
|
|
|
|
bool "Support for console on ttySM serial ports"
|
|
|
|
depends on MN10300_TTYSM
|
|
|
|
select SERIAL_CORE_CONSOLE
|
|
|
|
help
|
|
|
|
This option enables support for a console on the on-chip serial ports
|
|
|
|
that the MN10300 has available.
|
|
|
|
|
|
|
|
#
|
|
|
|
# /dev/ttySM0
|
|
|
|
#
|
|
|
|
config MN10300_TTYSM0
|
|
|
|
bool "Enable SIF0 (/dev/ttySM0)"
|
|
|
|
depends on MN10300_TTYSM && MN10300_PROC_HAS_TTYSM0
|
|
|
|
help
|
|
|
|
Enable access to SIF0 through /dev/ttySM0 or gdb-stub
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Select the timer to supply the clock for SIF0"
|
|
|
|
default MN10300_TTYSM0_TIMER8
|
|
|
|
depends on MN10300_TTYSM0
|
|
|
|
|
|
|
|
config MN10300_TTYSM0_TIMER8
|
|
|
|
bool "Use timer 8 (16-bit)"
|
|
|
|
|
|
|
|
config MN10300_TTYSM0_TIMER2
|
|
|
|
bool "Use timer 2 (8-bit)"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
#
|
|
|
|
# /dev/ttySM1
|
|
|
|
#
|
|
|
|
config MN10300_TTYSM1
|
|
|
|
bool "Enable SIF1 (/dev/ttySM1)"
|
|
|
|
depends on MN10300_TTYSM && MN10300_PROC_HAS_TTYSM1
|
|
|
|
help
|
|
|
|
Enable access to SIF1 through /dev/ttySM1 or gdb-stub
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Select the timer to supply the clock for SIF1"
|
2010-10-27 20:28:55 +04:00
|
|
|
default MN10300_TTYSM1_TIMER12 \
|
|
|
|
if !(AM33_2 || AM33_3)
|
|
|
|
default MN10300_TTYSM1_TIMER9 \
|
|
|
|
if AM33_2 || AM33_3
|
2008-02-08 15:19:31 +03:00
|
|
|
depends on MN10300_TTYSM1
|
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
config MN10300_TTYSM1_TIMER12
|
|
|
|
bool "Use timer 12 (16-bit)"
|
|
|
|
depends on !(AM33_2 || AM33_3)
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
config MN10300_TTYSM1_TIMER9
|
|
|
|
bool "Use timer 9 (16-bit)"
|
2010-10-27 20:28:55 +04:00
|
|
|
depends on AM33_2 || AM33_3
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
config MN10300_TTYSM1_TIMER3
|
|
|
|
bool "Use timer 3 (8-bit)"
|
2010-10-27 20:28:55 +04:00
|
|
|
depends on AM33_2 || AM33_3
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
#
|
|
|
|
# /dev/ttySM2
|
|
|
|
#
|
|
|
|
config MN10300_TTYSM2
|
|
|
|
bool "Enable SIF2 (/dev/ttySM2)"
|
|
|
|
depends on MN10300_TTYSM && MN10300_PROC_HAS_TTYSM2
|
|
|
|
help
|
|
|
|
Enable access to SIF2 through /dev/ttySM2 or gdb-stub
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Select the timer to supply the clock for SIF2"
|
2010-10-27 20:28:55 +04:00
|
|
|
default MN10300_TTYSM2_TIMER3 \
|
|
|
|
if !(AM33_2 || AM33_3)
|
|
|
|
default MN10300_TTYSM2_TIMER10 \
|
|
|
|
if AM33_2 || AM33_3
|
2008-02-08 15:19:31 +03:00
|
|
|
depends on MN10300_TTYSM2
|
|
|
|
|
2010-10-27 20:28:55 +04:00
|
|
|
config MN10300_TTYSM2_TIMER9
|
|
|
|
bool "Use timer 9 (16-bit)"
|
|
|
|
depends on !(AM33_2 || AM33_3)
|
|
|
|
|
|
|
|
config MN10300_TTYSM2_TIMER1
|
|
|
|
bool "Use timer 1 (8-bit)"
|
|
|
|
depends on !(AM33_2 || AM33_3)
|
|
|
|
|
|
|
|
config MN10300_TTYSM2_TIMER3
|
|
|
|
bool "Use timer 3 (8-bit)"
|
|
|
|
depends on !(AM33_2 || AM33_3)
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
config MN10300_TTYSM2_TIMER10
|
|
|
|
bool "Use timer 10 (16-bit)"
|
2010-10-27 20:28:55 +04:00
|
|
|
depends on AM33_2 || AM33_3
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
config MN10300_TTYSM2_CTS
|
|
|
|
bool "Enable the use of the CTS line /dev/ttySM2"
|
2010-10-27 20:28:55 +04:00
|
|
|
depends on MN10300_TTYSM2 && AM33_2
|
2008-02-08 15:19:31 +03:00
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
2010-10-27 20:28:54 +04:00
|
|
|
menu "Interrupt request priority options"
|
|
|
|
|
|
|
|
comment "[!] NOTE: A lower number/level indicates a higher priority (0 is highest, 6 is lowest)"
|
|
|
|
|
|
|
|
comment "____Non-maskable interrupt levels____"
|
|
|
|
comment "The following must be set to a higher priority than local_irq_disable() and on-chip serial"
|
|
|
|
|
2011-03-18 19:54:30 +03:00
|
|
|
config DEBUGGER_IRQ_LEVEL
|
|
|
|
int "DEBUGGER interrupt priority"
|
2011-03-18 19:54:30 +03:00
|
|
|
depends on KERNEL_DEBUGGER
|
2010-10-27 20:28:54 +04:00
|
|
|
range 0 1 if LINUX_CLI_LEVEL = 2
|
|
|
|
range 0 2 if LINUX_CLI_LEVEL = 3
|
|
|
|
range 0 3 if LINUX_CLI_LEVEL = 4
|
|
|
|
range 0 4 if LINUX_CLI_LEVEL = 5
|
|
|
|
range 0 5 if LINUX_CLI_LEVEL = 6
|
|
|
|
default 0
|
|
|
|
|
|
|
|
comment "The following must be set to a higher priority than local_irq_disable()"
|
|
|
|
|
|
|
|
config MN10300_SERIAL_IRQ_LEVEL
|
|
|
|
int "MN10300 on-chip serial interrupt priority"
|
|
|
|
depends on MN10300_TTYSM
|
|
|
|
range 1 1 if LINUX_CLI_LEVEL = 2
|
|
|
|
range 1 2 if LINUX_CLI_LEVEL = 3
|
|
|
|
range 1 3 if LINUX_CLI_LEVEL = 4
|
|
|
|
range 1 4 if LINUX_CLI_LEVEL = 5
|
|
|
|
range 1 5 if LINUX_CLI_LEVEL = 6
|
|
|
|
default 1
|
|
|
|
|
|
|
|
comment "-"
|
|
|
|
comment "____Maskable interrupt levels____"
|
|
|
|
|
|
|
|
config LINUX_CLI_LEVEL
|
|
|
|
int "The highest interrupt priority excluded by local_irq_disable() (2-6)"
|
|
|
|
range 2 6
|
|
|
|
default 2
|
|
|
|
help
|
|
|
|
local_irq_disable() doesn't actually disable maskable interrupts -
|
|
|
|
what it does is restrict the levels of interrupt which are permitted
|
|
|
|
(a lower level indicates a higher priority) by lowering the value in
|
|
|
|
EPSW.IM from 7. Any interrupt is permitted for which the level is
|
|
|
|
lower than EPSW.IM.
|
|
|
|
|
2011-03-18 19:54:30 +03:00
|
|
|
Certain interrupts, such as DEBUGGER and virtual MN10300 on-chip
|
2010-10-27 20:28:54 +04:00
|
|
|
serial DMA interrupts are allowed to interrupt normal disabled
|
|
|
|
sections.
|
|
|
|
|
|
|
|
comment "The following must be set to a equal to or lower priority than LINUX_CLI_LEVEL"
|
|
|
|
|
|
|
|
config TIMER_IRQ_LEVEL
|
|
|
|
int "Kernel timer interrupt priority"
|
|
|
|
range LINUX_CLI_LEVEL 6
|
|
|
|
default 4
|
|
|
|
|
|
|
|
config PCI_IRQ_LEVEL
|
|
|
|
int "PCI interrupt priority"
|
|
|
|
depends on PCI
|
|
|
|
range LINUX_CLI_LEVEL 6
|
|
|
|
default 5
|
|
|
|
|
|
|
|
config ETHERNET_IRQ_LEVEL
|
|
|
|
int "Ethernet interrupt priority"
|
|
|
|
depends on SMC91X || SMC911X || SMSC911X
|
|
|
|
range LINUX_CLI_LEVEL 6
|
|
|
|
default 6
|
|
|
|
|
|
|
|
config EXT_SERIAL_IRQ_LEVEL
|
|
|
|
int "External serial port interrupt priority"
|
|
|
|
depends on SERIAL_8250
|
|
|
|
range LINUX_CLI_LEVEL 6
|
|
|
|
default 6
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
2008-02-08 15:19:31 +03:00
|
|
|
source "mm/Kconfig"
|
|
|
|
|
|
|
|
menu "Power management options"
|
|
|
|
source kernel/power/Kconfig
|
|
|
|
endmenu
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
|
|
menu "Executable formats"
|
|
|
|
|
|
|
|
source "fs/Kconfig.binfmt"
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
|
|
source "net/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/Kconfig"
|
|
|
|
|
|
|
|
source "fs/Kconfig"
|
|
|
|
|
|
|
|
source "arch/mn10300/Kconfig.debug"
|
|
|
|
|
|
|
|
source "security/Kconfig"
|
|
|
|
|
|
|
|
source "crypto/Kconfig"
|
|
|
|
|
|
|
|
source "lib/Kconfig"
|