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 14:07:57 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2007-03-16 14:32:17 +00:00
|
|
|
menu "Platform support"
|
|
|
|
|
|
2011-09-19 17:44:52 +00:00
|
|
|
source "arch/powerpc/platforms/powernv/Kconfig"
|
2007-03-16 14:32:17 +00:00
|
|
|
source "arch/powerpc/platforms/pseries/Kconfig"
|
|
|
|
|
source "arch/powerpc/platforms/chrp/Kconfig"
|
2008-01-28 17:28:53 +00:00
|
|
|
source "arch/powerpc/platforms/512x/Kconfig"
|
2007-03-16 14:32:17 +00:00
|
|
|
source "arch/powerpc/platforms/52xx/Kconfig"
|
|
|
|
|
source "arch/powerpc/platforms/powermac/Kconfig"
|
|
|
|
|
source "arch/powerpc/platforms/maple/Kconfig"
|
|
|
|
|
source "arch/powerpc/platforms/pasemi/Kconfig"
|
2007-04-12 23:01:34 +00:00
|
|
|
source "arch/powerpc/platforms/ps3/Kconfig"
|
|
|
|
|
source "arch/powerpc/platforms/cell/Kconfig"
|
2007-04-12 22:35:54 +00:00
|
|
|
source "arch/powerpc/platforms/8xx/Kconfig"
|
2007-04-12 21:53:32 +00:00
|
|
|
source "arch/powerpc/platforms/82xx/Kconfig"
|
2007-04-12 20:46:21 +00:00
|
|
|
source "arch/powerpc/platforms/83xx/Kconfig"
|
2007-04-12 22:44:07 +00:00
|
|
|
source "arch/powerpc/platforms/85xx/Kconfig"
|
2007-04-12 20:41:26 +00:00
|
|
|
source "arch/powerpc/platforms/86xx/Kconfig"
|
2007-04-12 23:01:34 +00:00
|
|
|
source "arch/powerpc/platforms/embedded6xx/Kconfig"
|
2007-05-08 04:10:01 +00:00
|
|
|
source "arch/powerpc/platforms/44x/Kconfig"
|
2007-09-07 12:51:24 +00:00
|
|
|
source "arch/powerpc/platforms/40x/Kconfig"
|
2009-02-10 12:20:49 +00:00
|
|
|
source "arch/powerpc/platforms/amigaone/Kconfig"
|
2021-06-17 20:29:48 +00:00
|
|
|
source "arch/powerpc/platforms/book3s/Kconfig"
|
2021-06-18 03:43:41 +00:00
|
|
|
source "arch/powerpc/platforms/microwatt/Kconfig"
|
2007-03-16 14:32:17 +00:00
|
|
|
|
2010-07-29 12:47:57 +00:00
|
|
|
config KVM_GUEST
|
|
|
|
|
bool "KVM Guest support"
|
2012-03-15 10:52:13 +00:00
|
|
|
select EPAPR_PARAVIRT
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2010-07-29 12:47:57 +00:00
|
|
|
This option enables various optimizations for running under the KVM
|
|
|
|
|
hypervisor. Overhead for the kernel when not running inside KVM should
|
|
|
|
|
be minimal.
|
|
|
|
|
|
|
|
|
|
In case of doubt, say Y
|
|
|
|
|
|
2012-03-15 10:52:13 +00:00
|
|
|
config EPAPR_PARAVIRT
|
|
|
|
|
bool "ePAPR para-virtualization support"
|
|
|
|
|
help
|
|
|
|
|
Enables ePAPR para-virtualization support for guests.
|
|
|
|
|
|
|
|
|
|
In case of doubt, say Y
|
|
|
|
|
|
2021-12-01 14:41:37 +00:00
|
|
|
config PPC_HASH_MMU_NATIVE
|
2007-03-16 14:32:17 +00:00
|
|
|
bool
|
2021-12-01 14:41:37 +00:00
|
|
|
depends on PPC_BOOK3S
|
2007-03-16 14:32:17 +00:00
|
|
|
help
|
|
|
|
|
Support for running natively on the hardware, i.e. without
|
|
|
|
|
a hypervisor. This option is not user-selectable but should
|
|
|
|
|
be selected by all platforms that need it.
|
|
|
|
|
|
2009-03-10 17:53:27 +00:00
|
|
|
config PPC_OF_BOOT_TRAMPOLINE
|
|
|
|
|
bool "Support booting from Open Firmware or yaboot"
|
2018-11-17 10:24:58 +00:00
|
|
|
depends on PPC_BOOK3S_32 || PPC64
|
2021-06-23 13:04:54 +00:00
|
|
|
select RELOCATABLE if PPC64
|
2009-03-10 17:53:27 +00:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Support from booting from Open Firmware or yaboot using an
|
|
|
|
|
Open Firmware client interface. This enables the kernel to
|
2011-04-04 22:04:46 +00:00
|
|
|
communicate with open firmware to retrieve system information
|
2009-03-10 17:53:27 +00:00
|
|
|
such as the device tree.
|
|
|
|
|
|
|
|
|
|
In case of doubt, say Y
|
|
|
|
|
|
2017-06-08 06:29:59 +00:00
|
|
|
config PPC_DT_CPU_FTRS
|
|
|
|
|
bool "Device-tree based CPU feature discovery & setup"
|
|
|
|
|
depends on PPC_BOOK3S_64
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This enables code to use a new device tree binding for describing CPU
|
|
|
|
|
compatibility and features. Saying Y here will attempt to use the new
|
|
|
|
|
binding if the firmware provides it. Currently only the skiboot
|
|
|
|
|
firmware provides this binding.
|
|
|
|
|
If you're not sure say Y.
|
|
|
|
|
|
2007-03-16 14:32:17 +00:00
|
|
|
config UDBG_RTAS_CONSOLE
|
|
|
|
|
bool "RTAS based debug console"
|
|
|
|
|
depends on PPC_RTAS
|
|
|
|
|
|
2011-05-10 19:29:42 +00:00
|
|
|
config PPC_SMP_MUXED_IPI
|
|
|
|
|
bool
|
|
|
|
|
help
|
2017-09-26 03:47:59 +00:00
|
|
|
Select this option if your platform supports SMP and your
|
2011-05-10 19:29:42 +00:00
|
|
|
interrupt controller provides less than 4 interrupts to each
|
|
|
|
|
cpu. This will enable the generic code to multiplex the 4
|
|
|
|
|
messages on to one ipi.
|
|
|
|
|
|
2008-01-18 00:05:31 +00:00
|
|
|
config IPIC
|
|
|
|
|
bool
|
|
|
|
|
|
2007-04-12 23:01:34 +00:00
|
|
|
config MPIC
|
|
|
|
|
bool
|
|
|
|
|
|
2013-04-09 02:22:30 +00:00
|
|
|
config MPIC_TIMER
|
|
|
|
|
bool "MPIC Global Timer"
|
|
|
|
|
depends on MPIC && FSL_SOC
|
|
|
|
|
help
|
|
|
|
|
The MPIC global timer is a hardware timer inside the
|
|
|
|
|
Freescale PIC complying with OpenPIC standard. When the
|
|
|
|
|
specified interval times out, the hardware timer generates
|
|
|
|
|
an interrupt. The driver currently is only tested on fsl
|
|
|
|
|
chip, but it can potentially support other global timers
|
|
|
|
|
complying with the OpenPIC standard.
|
|
|
|
|
|
2013-04-09 02:22:32 +00:00
|
|
|
config FSL_MPIC_TIMER_WAKEUP
|
|
|
|
|
tristate "Freescale MPIC global timer wakeup driver"
|
|
|
|
|
depends on FSL_SOC && MPIC_TIMER && PM
|
|
|
|
|
help
|
|
|
|
|
The driver provides a way to wake up the system by MPIC
|
|
|
|
|
timer.
|
|
|
|
|
e.g. "echo 5 > /sys/devices/system/mpic/timer_wakeup"
|
|
|
|
|
|
2011-05-19 13:54:28 +00:00
|
|
|
config PPC_EPAPR_HV_PIC
|
|
|
|
|
bool
|
2012-07-03 05:48:54 +00:00
|
|
|
select EPAPR_PARAVIRT
|
2011-05-19 13:54:28 +00:00
|
|
|
|
2007-04-12 23:01:34 +00:00
|
|
|
config MPIC_WEIRD
|
|
|
|
|
bool
|
|
|
|
|
|
2012-02-17 02:49:03 +00:00
|
|
|
config MPIC_MSGR
|
|
|
|
|
bool "MPIC message register support"
|
|
|
|
|
depends on MPIC
|
|
|
|
|
help
|
|
|
|
|
Enables support for the MPIC message registers. These
|
|
|
|
|
registers are used for inter-processor communication.
|
|
|
|
|
|
2007-04-12 23:01:34 +00:00
|
|
|
config PPC_I8259
|
|
|
|
|
bool
|
|
|
|
|
|
2007-03-16 14:32:17 +00:00
|
|
|
config U3_DART
|
|
|
|
|
bool
|
2009-03-10 17:53:27 +00:00
|
|
|
depends on PPC64
|
2007-03-16 14:32:17 +00:00
|
|
|
|
|
|
|
|
config PPC_RTAS
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config RTAS_ERROR_LOGGING
|
|
|
|
|
bool
|
|
|
|
|
depends on PPC_RTAS
|
|
|
|
|
|
2009-09-24 19:30:05 +00:00
|
|
|
config PPC_RTAS_DAEMON
|
|
|
|
|
bool
|
|
|
|
|
depends on PPC_RTAS
|
|
|
|
|
|
2007-03-16 14:32:17 +00:00
|
|
|
config RTAS_PROC
|
|
|
|
|
bool "Proc interface to RTAS"
|
2013-05-06 18:43:39 +00:00
|
|
|
depends on PPC_RTAS && PROC_FS
|
2007-03-16 14:32:17 +00:00
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config RTAS_FLASH
|
|
|
|
|
tristate "Firmware flash interface"
|
|
|
|
|
depends on PPC64 && RTAS_PROC
|
|
|
|
|
|
|
|
|
|
config MMIO_NVRAM
|
|
|
|
|
bool
|
|
|
|
|
|
2007-04-23 08:47:08 +00:00
|
|
|
config MPIC_U3_HT_IRQS
|
2007-03-16 14:32:17 +00:00
|
|
|
bool
|
|
|
|
|
|
2007-09-07 19:13:19 +00:00
|
|
|
config MPIC_BROKEN_REGREAD
|
|
|
|
|
bool
|
|
|
|
|
depends on MPIC
|
|
|
|
|
help
|
|
|
|
|
This option enables a MPIC driver workaround for some chips
|
|
|
|
|
that have a bug that causes some interrupt source information
|
|
|
|
|
to not read back properly. It is safe to use on other chips as
|
|
|
|
|
well, but enabling it uses about 8KB of memory to keep copies
|
|
|
|
|
of the register contents in software.
|
|
|
|
|
|
2013-06-20 05:20:52 +00:00
|
|
|
config EEH
|
|
|
|
|
bool
|
|
|
|
|
depends on (PPC_POWERNV || PPC_PSERIES) && PCI
|
|
|
|
|
default y
|
|
|
|
|
|
2007-03-16 14:32:17 +00:00
|
|
|
config PPC_MPC106
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config PPC_970_NAP
|
|
|
|
|
bool
|
|
|
|
|
|
2011-01-24 07:42:41 +00:00
|
|
|
config PPC_P7_NAP
|
|
|
|
|
bool
|
|
|
|
|
|
2019-07-11 02:24:03 +00:00
|
|
|
config PPC_BOOK3S_IDLE
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on (PPC_970_NAP || PPC_P7_NAP)
|
|
|
|
|
|
2011-04-11 21:25:01 +00:00
|
|
|
config PPC_INDIRECT_PIO
|
|
|
|
|
bool
|
2013-07-15 03:03:08 +00:00
|
|
|
select GENERIC_IOMAP
|
2011-04-11 21:25:01 +00:00
|
|
|
|
|
|
|
|
config PPC_INDIRECT_MMIO
|
|
|
|
|
bool
|
2007-03-16 14:32:17 +00:00
|
|
|
|
2011-04-11 21:25:01 +00:00
|
|
|
config PPC_IO_WORKAROUNDS
|
|
|
|
|
bool
|
|
|
|
|
|
2007-03-16 14:32:17 +00:00
|
|
|
source "drivers/cpufreq/Kconfig"
|
|
|
|
|
|
2011-11-30 02:46:55 +00:00
|
|
|
menu "CPUIdle driver"
|
|
|
|
|
|
|
|
|
|
source "drivers/cpuidle/Kconfig"
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2007-03-16 14:32:17 +00:00
|
|
|
config TAU
|
|
|
|
|
bool "On-chip CPU temperature sensor support"
|
2018-11-17 10:24:58 +00:00
|
|
|
depends on PPC_BOOK3S_32
|
2007-03-16 14:32:17 +00:00
|
|
|
help
|
|
|
|
|
G3 and G4 processors have an on-chip temperature sensor called the
|
|
|
|
|
'Thermal Assist Unit (TAU)', which, in theory, can measure the on-die
|
|
|
|
|
temperature within 2-4 degrees Celsius. This option shows the current
|
|
|
|
|
on-die temperature in /proc/cpuinfo if the cpu supports it.
|
|
|
|
|
|
2020-09-04 23:02:20 +00:00
|
|
|
Unfortunately, this sensor is very inaccurate when uncalibrated, so
|
|
|
|
|
don't assume the cpu temp is actually what /proc/cpuinfo says it is.
|
2007-03-16 14:32:17 +00:00
|
|
|
|
|
|
|
|
config TAU_INT
|
2020-09-04 23:02:20 +00:00
|
|
|
bool "Interrupt driven TAU driver (EXPERIMENTAL)"
|
2007-03-16 14:32:17 +00:00
|
|
|
depends on TAU
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-03-16 14:32:17 +00:00
|
|
|
The TAU supports an interrupt driven mode which causes an interrupt
|
|
|
|
|
whenever the temperature goes out of range. This is the fastest way
|
|
|
|
|
to get notified the temp has exceeded a range. With this option off,
|
|
|
|
|
a timer is used to re-check the temperature periodically.
|
|
|
|
|
|
2020-09-04 23:02:20 +00:00
|
|
|
If in doubt, say N here.
|
2007-03-16 14:32:17 +00:00
|
|
|
|
|
|
|
|
config TAU_AVERAGE
|
|
|
|
|
bool "Average high and low temp"
|
|
|
|
|
depends on TAU
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-03-16 14:32:17 +00:00
|
|
|
The TAU hardware can compare the temperature to an upper and lower
|
|
|
|
|
bound. The default behavior is to show both the upper and lower
|
|
|
|
|
bound in /proc/cpuinfo. If the range is large, the temperature is
|
|
|
|
|
either changing a lot, or the TAU hardware is broken (likely on some
|
|
|
|
|
G4's). If the range is small (around 4 degrees), the temperature is
|
|
|
|
|
relatively stable. If you say Y here, a single temperature value,
|
|
|
|
|
halfway between the upper and lower bounds, will be reported in
|
|
|
|
|
/proc/cpuinfo.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N here.
|
|
|
|
|
|
2008-10-03 19:40:36 +00:00
|
|
|
config QE_GPIO
|
|
|
|
|
bool "QE GPIO support"
|
|
|
|
|
depends on QUICC_ENGINE
|
2016-04-19 11:21:02 +00:00
|
|
|
select GPIOLIB
|
2008-10-03 19:40:36 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you're going to use hardware that connects to the
|
|
|
|
|
QE GPIOs.
|
|
|
|
|
|
2007-04-12 21:53:32 +00:00
|
|
|
config CPM2
|
2008-01-24 23:41:25 +00:00
|
|
|
bool "Enable support for the CPM2 (Communications Processor Module)"
|
2009-10-16 23:31:48 +00:00
|
|
|
depends on (FSL_SOC_BOOKE && PPC32) || 8260
|
2007-07-16 16:43:43 +00:00
|
|
|
select CPM
|
2018-11-15 19:05:32 +00:00
|
|
|
select HAVE_PCI
|
2016-04-19 11:21:02 +00:00
|
|
|
select GPIOLIB
|
2007-04-12 21:53:32 +00:00
|
|
|
help
|
|
|
|
|
The CPM2 (Communications Processor Module) is a coprocessor on
|
|
|
|
|
embedded CPUs made by Freescale. Selecting this option means that
|
|
|
|
|
you wish to build a kernel for a machine with a CPM2 coprocessor
|
|
|
|
|
on it (826x, 827x, 8560).
|
|
|
|
|
|
2007-08-17 04:55:55 +00:00
|
|
|
config FSL_ULI1575
|
|
|
|
|
bool
|
2007-09-10 19:57:34 +00:00
|
|
|
select GENERIC_ISA_DMA
|
2007-08-17 04:55:55 +00:00
|
|
|
help
|
|
|
|
|
Supports for the ULI1575 PCIe south bridge that exists on some
|
|
|
|
|
Freescale reference boards. The boards all use the ULI in pretty
|
|
|
|
|
much the same way.
|
|
|
|
|
|
2007-07-16 16:43:43 +00:00
|
|
|
config CPM
|
|
|
|
|
bool
|
2015-11-30 02:48:54 +00:00
|
|
|
select GENERIC_ALLOCATOR
|
2007-07-16 16:43:43 +00:00
|
|
|
|
2008-01-11 03:25:34 +00:00
|
|
|
config OF_RTC
|
|
|
|
|
bool
|
|
|
|
|
help
|
2009-01-26 10:12:25 +00:00
|
|
|
Uses information from the OF or flattened device tree to instantiate
|
2008-01-11 03:25:34 +00:00
|
|
|
platform devices for direct mapped RTC chips like the DS1742 or DS1743.
|
|
|
|
|
|
2016-05-30 18:58:01 +00:00
|
|
|
config GEN_RTC
|
|
|
|
|
bool "Use the platform RTC operations from user space"
|
|
|
|
|
select RTC_CLASS
|
|
|
|
|
select RTC_DRV_GENERIC
|
|
|
|
|
help
|
|
|
|
|
This option provides backwards compatibility with the old gen_rtc.ko
|
|
|
|
|
module that was traditionally used for old PowerPC machines.
|
|
|
|
|
Platforms should migrate to enabling the RTC_DRV_GENERIC by hand
|
|
|
|
|
replacing their get_rtc_time/set_rtc_time callbacks with
|
|
|
|
|
a proper RTC device driver.
|
|
|
|
|
|
2009-01-11 16:55:39 +00:00
|
|
|
config MCU_MPC8349EMITX
|
2011-08-15 14:19:30 +00:00
|
|
|
bool "MPC8349E-mITX MCU driver"
|
2011-11-09 02:10:29 +00:00
|
|
|
depends on I2C=y && PPC_83xx
|
2016-04-19 11:21:02 +00:00
|
|
|
select GPIOLIB
|
2009-01-11 16:55:39 +00:00
|
|
|
help
|
|
|
|
|
Say Y here to enable soft power-off functionality on the Freescale
|
|
|
|
|
boards with the MPC8349E-mITX-compatible MCU chips. This driver will
|
|
|
|
|
also register MCU GPIOs with the generic GPIO API, so you'll able
|
|
|
|
|
to use MCU pins as GPIOs.
|
|
|
|
|
|
2007-03-16 14:32:17 +00:00
|
|
|
endmenu
|
