Home
last modified time | relevance | path

Searched +full:system +full:- +full:on +full:- +full:chip (Results 1 – 25 of 1064) sorted by relevance

12345678910>>...43

/kernel/linux/linux-5.10/Documentation/hwmon/
Dmax16065.rst11 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 …]
/kernel/linux/linux-6.6/Documentation/hwmon/
Dmax16065.rst11 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 …]
/kernel/linux/linux-5.10/drivers/tty/serial/
DKconfig1 # 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 …]
/kernel/linux/linux-6.6/drivers/tty/serial/
DKconfig1 # 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 || COMPILE_TEST
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 …]
/kernel/linux/linux-6.6/Documentation/driver-api/
Dedac.rst5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
18 The individual DRAM chips on a memory stick. These devices commonly
32 A physical connector on the motherboard that accepts a single memory
33 stick. Also called as "slot" on several datasheets.
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
50 of correcting more errors than on single mode.
52 * Single-channel
55 only. E. g. if the data is 64 bits-wide, the data flows to the CPU using
57 memories. FB-DIMM and RAMBUS use a different concept for channel, so
[all …]
/kernel/linux/linux-5.10/drivers/rtc/
DKconfig1 # 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 …]
/kernel/linux/linux-6.6/drivers/rtc/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
16 depends on !S390
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 …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power8/
Dfrontend.json47 "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 …]
Dother.json11 …"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 …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power8/
Dfrontend.json47 "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 …]
Dother.json11 …"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 …]
/kernel/linux/linux-6.6/arch/arm/mach-vt8500/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
8 Support for VIA/WonderMedia VT8500/WM85xx System-on-Chip.
12 depends on ARCH_MULTI_V5
13 depends on CPU_LITTLE_ENDIAN
19 depends on ARCH_MULTI_V6
22 Support for WonderMedia WM8750 System-on-Chip.
26 depends on ARCH_MULTI_V7
29 Support for WonderMedia WM8850 System-on-Chip.
/kernel/linux/linux-5.10/arch/arm/mach-vt8500/
DKconfig1 # 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.
/kernel/linux/patches/
DREADME.md1 # Patch<a name="EN-US_TOPIC_0000001078264110"></a>
3 - [Introduction](#section11660541593)
4 - [Directory Structure](#section21571344112)
5 - [Usage](#section1393789267)
6 - [Build](#section19369206113115)
7 - [Repositories Involved](#section27639463106)
11 Evolved from the open-source Linux kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has i…
13 …nel website](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-4.19.y).
15 …nel website](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y).
17 During the build process, you can merge the driver code based on the chip platform and build the ke…
[all …]
/kernel/linux/linux-5.10/drivers/mfd/
DKconfig1 # 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 …]
/kernel/linux/config/
DREADME.md1 # Config<a name="EN-US_TOPIC_0000001102487950"></a>
3 - [Introduction](#section11660541593)
4 - [Composition of Config](#section28381947133910)
5 - [Directory Structure](#section161941989596)
6 - [Usage](#section1393789267)
7 - [Build](#section19369206113115)
8 - [Repositories Involved](#section1371113476307)
12 Evolved from the open-source Linux kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has i…
14 …nel website](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-4.19.y).
16 …nel website](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y).
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Datmel-sysregs.txt1 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 …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power9/
Dmarked.json20 …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 …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power9/
Dmarked.json20 …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 …]
/kernel/linux/linux-6.6/drivers/irqchip/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "IRQ chip support"
6 depends on (OF_IRQ || ACPI_GENERIC_GSI)
10 depends on OF
16 depends on PM
21 depends on ARM_GIC
27 depends on PCI
48 depends on ARM_GIC_V3_ITS
49 depends on PCI
50 depends on PCI_MSI
[all …]
/kernel/linux/linux-6.6/drivers/mfd/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
17 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 depends on !UML
24 bool "Altera Arria10 DevKit System Resource chip"
25 depends on ARCH_INTEL_SOCFPGA && SPI_MASTER=y && OF
29 Support for the Altera Arria10 DevKit MAX5 System Resource chip
35 bool "Altera SOCFPGA System Manager"
36 depends on ARCH_INTEL_SOCFPGA && OF
39 Select this to get System Manager support for all Altera branded
40 SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
[all …]
/kernel/linux/linux-6.6/drivers/thermal/tegra/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on ARCH_TEGRA || COMPILE_TEST
8 Enable this option for integrated thermal management support on NVIDIA
9 Tegra systems-on-chip. The driver supports four thermal zones
16 depends on TEGRA_BPMP || COMPILE_TEST
18 Enable this option for support for sensing system temperature of NVIDIA
19 Tegra systems-on-chip with the BPMP coprocessor (Tegra186).
23 depends on ARCH_TEGRA_3x_SOC || COMPILE_TEST
26 system-on-chip.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/
Daspeed-wdt.txt4 - 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 …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/watchdog/
Daspeed-wdt.txt4 - 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 …]
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/atm/
Diphase.rst1 .. 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 …]

12345678910>>...43