| /OK3568_Linux_fs/kernel/drivers/tty/serial/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 depends on HAS_IOMEM
11 depends on SERIAL_CORE
19 comment "Non-8250 serial port support"
23 depends on ARM_AMBA
33 bool "Support for console on AMBA serial port"
34 depends on SERIAL_AMBA_PL010=y
37 Say Y here if you wish to use an AMBA PrimeCell UART as the system
38 console (the system console is the device which receives all kernel
42 (/dev/tty0) will still be used as the system console by default, but
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/rtc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 depends on !S390 && !UML
20 be allowed to plug one or more RTCs to your system. You will
26 bool "Set system time from RTC on startup and resume"
29 If you say yes here, the system time (wall clock) will be set using
34 string "RTC used to set the system time"
35 depends on RTC_HCTOSYS
38 The RTC device that will be used to (re)initialize the system
39 clock, usually rtc0. Initialization is done when the system
44 This clock should be battery-backed, so that it reads the correct
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/hwmon/ |
| H A D | max16065.rst | 11 Addresses scanned: -
15 http://datasheets.maxim-ic.com/en/ds/MAX16065-MAX16066.pdf
21 Addresses scanned: -
25 http://datasheets.maxim-ic.com/en/ds/MAX16067.pdf
31 Addresses scanned: -
35 http://datasheets.maxim-ic.com/en/ds/MAX16068.pdf
41 Addresses scanned: -
45 http://datasheets.maxim-ic.com/en/ds/MAX16070-MAX16071.pdf
47 Author: Guenter Roeck <linux@roeck-us.net>
51 -----------
[all …]
|
| H A D | tmp513.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 Eric Tremblay <etremblay@distech-controls.com>
25 -----------
28 The TMP512 (dual-channel) and TMP513 (triple-channel) are system monitors
29 that include remote sensors, a local temperature sensor, and a high-side current
30 shunt monitor. These system monitors have the capability of measuring remote
31 temperatures, on-chip temperatures, and system voltage/power/current
35 -40 to + 125 degrees with a resolution of 0.0625 degree C.
44 **temp[1-4]_input**
46 **temp[1-4]_crit**
[all …]
|
| /OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/powerpc/power8/ |
| H A D | frontend.json | 47 "BriefDescription": "Number of I-ERAT reloads",
59 "BriefDescription": "IERAT Miss (Not implemented as DI on POWER6)",
71 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for an instru…
72 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pum…
89 …oaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (Distant), …
90 …oaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (Distant), …
95 …eloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (Distant), …
96 …eloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (Distant), …
101 …"BriefDescription": "The processor's Instruction cache was reloaded from another chip's L4 on a di…
102 …"PublicDescription": "The processor's Instruction cache was reloaded from another chip's L4 on a d…
[all …]
|
| H A D | other.json | 11 …"BriefDescription": "Cycles in 2-lpar mode. Threads 0-3 belong to Lpar0 and threads 4-7 belong to …
17 …cles in 4 LPAR mode. Threads 0-1 belong to lpar0, threads 2-3 belong to lpar1, threads 4-5 belong …
23 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for all data …
24 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pum…
36 … got data from source that was at smaller scope(Chip) Final pump was group pump and initial pump w…
41 …"BriefDescription": "Final Pump Scope (Group) ended up larger than Initial Pump Scope (Chip) for a…
42 …urced, ended up larger than Initial Pump Scope (Chip) Final pump was group pump and initial pump w…
59 …"BriefDescription": "Initial and Final Pump Scope was system pump for all data types (demand load,…
60 …n": "Initial and Final Pump Scope and data sourced across this scope was system pump for all data …
65 …n": "Final Pump Scope (system) mispredicted. Either the original scope was too small (Chip/Group) …
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/mfd/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
23 bool "Altera Arria10 DevKit System Resource chip"
24 depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
28 Support for the Altera Arria10 DevKit MAX5 System Resource chip
34 bool "Altera SOCFPGA System Manager"
35 depends on (ARCH_SOCFPGA || ARCH_STRATIX10) && OF
38 Select this to get System Manager support for all Altera branded
39 SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
44 tristate "Active-semi ACT8945A"
[all …]
|
| /OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/powerpc/power9/ |
| H A D | marked.json | 20 …was loaded into the TLB with Shared (S) data from another core's L3 on the same chip due to a data…
25 …"BriefDescription": "The processor's data cache was reloaded from another chip's memory on the sam…
30 …"BriefDescription": "Completion stall by Dcache miss which resolved from remote chip (cache or mem…
60 …"BriefDescription": "A Page Table Entry was loaded into the TLB from the local chip's L4 cache due…
70 …loaded into the TLB with Shared (S) data from another core's ECO L3 on the same chip due to a mark…
95 …aded into the TLB with Modified (M) data from another core's ECO L3 on the same chip due to a mark…
100 …loaded into the TLB with Shared (S) data from another core's ECO L3 on the same chip due to a data…
120 …tion": "The processor's Instruction cache was reloaded from another chip's memory on the same Node…
130 …"BriefDescription": "The processor's data cache was reloaded from the local chip's Memory due to a…
145 …"BriefDescription": "Final Pump Scope (Group) ended up larger than Initial Pump Scope (Chip) for a…
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/ |
| H A D | atmel-sysregs.txt | 1 Atmel system registers
4 - compatible: Should be "atmel,sama5d2-chipid"
5 - reg : Should contain registers location and length
8 - compatible: Should be "atmel,at91sam9260-pit"
9 - reg: Should contain registers location and length
10 - interrupts: Should contain interrupt for the PIT which is the IRQ line
11 shared across all System Controller members.
14 - compatible: Should be "microchip,sam9x60-pit64b"
15 - reg: Should contain registers location and length
16 - interrupts: Should contain interrupt for PIT64B timer
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-vt8500/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
8 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
12 depends on ARCH_MULTI_V5
18 depends on ARCH_MULTI_V6
21 Support for WonderMedia WM8750 System-on-Chip.
25 depends on ARCH_MULTI_V7
28 Support for WonderMedia WM8850 System-on-Chip.
|
| /OK3568_Linux_fs/kernel/drivers/hwmon/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Hardware monitoring chip drivers configuration
8 depends on HAS_IOMEM
12 of a system. Most modern motherboards include such a device. It
17 sensors chip(s) below.
20 sensors-detect script from the lm_sensors package. Read
21 <file:Documentation/hwmon/userspace-tools.rst> for details.
32 bool "Hardware Monitoring Chip debugging messages"
34 Say Y here if you want the I2C chip drivers to produce a bunch of
35 debug messages to the system log. Select this if you are having
[all …]
|
| /OK3568_Linux_fs/u-boot/arch/x86/ |
| H A D | Kconfig | 2 depends on X86
8 prompt "Run U-Boot in 32/64-bit mode"
11 U-Boot can be built as a 32-bit binary which runs in 32-bit mode
12 even on 64-bit machines. In this case SPL is not used, and U-Boot
13 runs directly from the reset vector (via 16-bit start-up).
15 Alternatively it can be run as a 64-bit binary, thus requiring a
16 64-bit machine. In this case SPL runs in 32-bit mode (via 16-bit
17 start-up) then jumps to U-Boot in 64-bit mode.
19 For now, 32-bit mode is recommended, as 64-bit is still
23 bool "32-bit"
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/atm/ |
| H A D | iphase.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ATM (i)Chip IA Linux Driver Source
9 --------------------------------------------------------------------------------
13 --------------------------------------------------------------------------------
18 This is the README file for the Interphase PCI ATM (i)Chip IA Linux driver
23 - A single VPI (VPI value of 0) is supported.
24 - Supports 4K VCs for the server board (with 512K control memory) and 1K
26 - UBR, ABR and CBR service categories are supported.
27 - Only AAL5 is supported.
28 - Supports setting of PCR on the VCs.
[all …]
|
| /OK3568_Linux_fs/u-boot/drivers/usb/host/ |
| H A D | Kconfig | 12 ---help---
21 Say Y or if your system has a Dual Role SuperSpeed
22 USB controller based on the DesignWare USB3 IP Core.
26 depends on DM_USB
30 USB controller based on the DesignWare USB3 IP Core.
35 depends on ARCH_MVEBU
38 Choose this option to add support for USB 3.0 driver on mvebu
43 bool "Support for PCI-based xHCI USB controller"
44 depends on DM_USB
47 Enables support for the PCI-based xHCI controller.
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/input/keyboard/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
18 depends on IIO
24 board-specific setup logic must also provide a configuration data
32 depends on PMIC_ADP5520
35 on Analog Devices ADP5520 PMICs.
38 be called adp5520-keys.
42 depends on I2C
45 system I2C bus.
48 module will be called adp5588-keys.
52 depends on I2C
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/mtd/devices/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
3 depends on MTD!=n
4 depends on HAS_IOMEM
8 depends on PCI
12 These devices come in memory configurations from 32M - 1G. If you
21 particularly useful on the 2.2 kernels on PPC architectures as there
26 depends on MTD_PMC551
34 depends on MTD_PMC551
37 is only really useful if you are developing on this driver or
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/dma-buf/heaps/ |
| H A D | Kconfig | 2 bool "DMA-BUF heaps deferred-free library"
4 Choose this option to enable the DMA-BUF heaps deferred-free library.
7 bool "DMA-BUF heaps page-pool library"
9 Choose this option to enable the DMA-BUF heaps page-pool library.
12 tristate "DMA-BUF System Heap"
13 depends on DMABUF_HEAPS && DMABUF_HEAPS_DEFERRED_FREE && DMABUF_HEAPS_PAGE_POOL
15 Choose this option to enable the system dmabuf heap. The system heap
19 tristate "DMA-BUF CMA Heap"
20 depends on DMABUF_HEAPS && DMA_CMA
22 Choose this option to enable dma-buf CMA heap. This heap is backed
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/input/touchscreen/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 depends on INPUT
21 depends on MFD_88PM860X
24 support for the built-in touchscreen.
29 module will be called 88pm860x-ts.
33 depends on SPI_MASTER
34 depends on HWMON = n || HWMON
38 and your board-specific setup code includes that in its
42 on your board, you will also get hwmon interfaces for the voltage
43 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/watchdog/ |
| H A D | aspeed-wdt.txt | 4 - compatible: must be one of:
5 - "aspeed,ast2400-wdt"
6 - "aspeed,ast2500-wdt"
7 - "aspeed,ast2600-wdt"
9 - reg: physical base address of the controller and length of memory mapped
14 - aspeed,reset-type = "cpu|soc|system|none"
16 Reset behavior - Whenever a timeout occurs the watchdog can be programmed
20 This is useful in situations where another watchdog engine on chip is
23 If 'aspeed,reset-type=' is not specified the default is to enable system
28 - cpu: Reset CPU on watchdog timeout
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-bus-event_source-devices-hv_24x7 | 3 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
4 Description: Read-only. Attribute group to describe the magic bits
6 (See ABI/testing/sysfs-bus-event_source-devices-format).
12 chip = "config:16-31"
13 core = "config:16-31"
14 domain = "config:0-3"
15 lpar = "config:0-15"
16 offset = "config:32-63"
17 vcpu = "config:16-31"
21 PM_PB_CYC = "domain=1,offset=0x80,chip=?,lpar=0x0"
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/gpio/ |
| H A D | legacy.rst | 5 This provides an overview of GPIO access conventions on Linux.
13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
14 digital signal. They are provided from many kinds of chip, and are familiar
16 represents a bit connected to a particular pin, or "ball" on Ball Grid Array
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
25 often have a few such pins to help with pin scarcity on SOCs; and there are
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
[all …]
|
| H A D | drivers-on-gpio.rst | 6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
14 i.e. a LED will turn on/off in response to a GPIO line going high or low
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
32 - extcon-gpio: drivers/extcon/extcon-gpio.c is used when you need to read an
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/scsi/ |
| H A D | 53c700.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 This driver supports the 53c700 and 53c700-66 chips. It also supports
12 does sync (-66 and 710 only), disconnects and tag command queueing.
29 define if the chipset must be supported in little endian mode on a big
30 endian architecture (used for the 700 on parisc).
33 Using the Chip Core Driver
36 In order to plumb the 53c700 chip core driver into a working SCSI
37 driver, you need to know three things about the way the chip is wired
38 into your system (or expansion card).
45 the SCSI Id from the card bios or whether the chip is wired for
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | pmc.txt | 4 - compatible: "fsl,<chip>-pmc".
6 "fsl,mpc8349-pmc" should be listed for any chip whose PMC is
7 compatible. "fsl,mpc8313-pmc" should also be listed for any chip
8 whose PMC is compatible, and implies deep-sleep capability.
10 "fsl,mpc8548-pmc" should be listed for any chip whose PMC is
11 compatible. "fsl,mpc8536-pmc" should also be listed for any chip
12 whose PMC is compatible, and implies deep-sleep capability.
14 "fsl,mpc8641d-pmc" should be listed for any chip whose PMC is
15 compatible; all statements below that apply to "fsl,mpc8548-pmc" also
16 apply to "fsl,mpc8641d-pmc".
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/bus/ |
| H A D | socionext,uniphier-system-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/bus/socionext,uniphier-system-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: UniPhier System Bus
10 The UniPhier System Bus is an external bus that connects on-board devices to
11 the UniPhier SoC. It is a simple (semi-)parallel bus with address, data, and
12 some control signals. It supports up to 8 banks (chip selects).
16 within each bank to the CPU-viewed address. The needed setup includes the
21 - Masahiro Yamada <yamada.masahiro@socionext.com>
[all …]
|