Searched +full:system +full:- +full:on +full:- +full:a +full:- +full:chip (Results 1 – 25 of 1069) sorted by relevance
12345678910>>...43
| /kernel/linux/linux-5.10/drivers/tty/serial/ |
| 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
27 an Integrator/AP or Integrator/PP2 platform, or if you have a
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
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | edac.rst | 5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
13 creating a common ground for discussion, terms and their definitions
18 The individual DRAM chips on a memory stick. These devices commonly
25 A printed circuit board that aggregates multiple memory devices in
32 A physical connector on the motherboard that accepts a single memory
33 stick. Also called as "slot" on several datasheets.
37 A memory controller channel, responsible to communicate with a group of
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
50 of correcting more errors than on single mode.
[all …]
|
| /kernel/linux/linux-6.6/drivers/tty/serial/ |
| 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 || COMPILE_TEST
27 an Integrator/AP or Integrator/PP2 platform, or if you have a
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
[all …]
|
| /kernel/linux/linux-5.10/drivers/rtc/ |
| 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
30 the value read from a specified RTC device. This is useful to avoid
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/rtc/ |
| D | Kconfig | 1 # 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
30 the value read from a specified RTC device. This is useful to avoid
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
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | frontend.json | 5 …"BriefDescription": "Branch instruction completed with a target address less than current instruct…
41 "BriefDescription": "Cycles when a demand ifetch was pending",
47 "BriefDescription": "Number of I-ERAT reloads",
53 "BriefDescription": "IERAT Reloaded (Miss) for a 16M page",
59 "BriefDescription": "IERAT Miss (Not implemented as DI on POWER6)",
60 "PublicDescription": "IERAT Reloaded (Miss) for a 4k page"
65 "BriefDescription": "IERAT Reloaded (Miss) for a 64k page",
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), …
[all …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | frontend.json | 5 …"BriefDescription": "Branch instruction completed with a target address less than current instruct…
41 "BriefDescription": "Cycles when a demand ifetch was pending",
47 "BriefDescription": "Number of I-ERAT reloads",
53 "BriefDescription": "IERAT Reloaded (Miss) for a 16M page",
59 "BriefDescription": "IERAT Miss (Not implemented as DI on POWER6)",
60 "PublicDescription": "IERAT Reloaded (Miss) for a 4k page"
65 "BriefDescription": "IERAT Reloaded (Miss) for a 64k page",
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), …
[all …]
|
| 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 …]
|
| /kernel/linux/patches/ |
| D | README.md | 1 # 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)
9 ## Introduction<a name="section11660541593"></a>
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).
[all …]
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| 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 …]
|
| /kernel/linux/config/ |
| D | README.md | 1 # 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)
10 ## Introduction<a name="section11660541593"></a>
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).
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | marked.json | 5 …"BriefDescription": "Number of cycles the marked instruction is experiencing a stall while it is n…
10 …"BriefDescription": "A Page Directory Entry was reloaded to a level 1 page walk cache from beyond …
20 …BriefDescription": "A Page Table Entry was loaded into the TLB with Shared (S) data from another c…
25 …ocessor's data cache was reloaded from another chip's memory on the same Node or Group ( Remote) d…
30 …"BriefDescription": "Completion stall by Dcache miss which resolved from remote chip (cache or mem…
45 …"BriefDescription": "A Page Table Entry was reloaded to a level 3 page walk cache from the core's …
50 …"BriefDescription": "A Page Table Entry was reloaded to a level 3 page walk cache from the core's …
60 …"BriefDescription": "A Page Table Entry was loaded into the TLB from the local chip's L4 cache due…
70 …iefDescription": "A Page Table Entry was loaded into the TLB with Shared (S) data from another cor…
85 …he processor's Instruction cache was reloaded from a location other than the local core's L3 due t…
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | marked.json | 5 …"BriefDescription": "Number of cycles the marked instruction is experiencing a stall while it is n…
10 …"BriefDescription": "A Page Directory Entry was reloaded to a level 1 page walk cache from beyond …
20 …BriefDescription": "A Page Table Entry was loaded into the TLB with Shared (S) data from another c…
25 …ocessor's data cache was reloaded from another chip's memory on the same Node or Group ( Remote) d…
30 …"BriefDescription": "Completion stall by Dcache miss which resolved from remote chip (cache or mem…
45 …"BriefDescription": "A Page Table Entry was reloaded to a level 3 page walk cache from the core's …
50 …"BriefDescription": "A Page Table Entry was reloaded to a level 3 page walk cache from the core's …
60 …"BriefDescription": "A Page Table Entry was loaded into the TLB from the local chip's L4 cache due…
70 …iefDescription": "A Page Table Entry was loaded into the TLB with Shared (S) data from another cor…
85 …he processor's Instruction cache was reloaded from a location other than the local core's L3 due t…
[all …]
|
| /kernel/linux/linux-6.6/drivers/mfd/ |
| D | Kconfig | 1 # 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/irqchip/ |
| D | Kconfig | 1 # 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/hwmon/ |
| 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.
23 This support can also be built as a module. If so, the module
32 bool "Hardware Monitoring Chip debugging messages"
34 Say Y here if you want the I2C chip drivers to produce a bunch of
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/atm/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/atm/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/fsi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
8 depends on OF
11 FSI - the FRU Support Interface - is a simple bus for low-level
12 access to POWER-based hardware.
21 located under a common /dev/fsi/ directory. Set to N unless your
25 by one so that chip 0 will have /dev/scom1 and chip1 /dev/scom2
29 symlinks in /dev/fsi/by-path when this option is enabled.
32 tristate "GPIO-based FSI master"
33 depends on GPIOLIB
36 This option enables a FSI master driver using GPIO lines.
[all …]
|
| /kernel/linux/linux-5.10/drivers/hwmon/ |
| 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.
23 This support can also be built as a module. If so, the module
32 bool "Hardware Monitoring Chip debugging messages"
34 Say Y here if you want the I2C chip drivers to produce a bunch of
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/devices/ |
| 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
10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
12 These devices come in memory configurations from 32M - 1G. If you
15 If this driver is compiled as a module you get the ability to select
17 What this means is that if you have a 1G card, normally the kernel
18 will use a 1G memory map as its view of the device. As a module,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| 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
18 can generate interrupts in response to a key press. Also supports debounce.
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
22 by a timer.
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
[all …]
|
12345678910>>...43