| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
8 by hardware using this driver.
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
14 should be controlled by a hardware signal instead of the MODE register value,
15 with 0 meaning hardware control enabled and 1 hardware control disabled. This
16 is usually 1:1 for hardware to LED signals, but through the activity/link
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
20 but you can't turn it off if the hardware decides to light it up. For this
21 reason, hardware controlled LEDs aren't registered as LED class devices.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.yaml | 14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
18 Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or by hardware
20 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
25 should be controlled by a hardware signal instead of the MODE register value,
26 with 0 meaning hardware control enabled and 1 hardware control disabled. This
27 is usually 1:1 for hardware to LED signals, but through the activity/link
29 explained later in brcm,link-signal-sources). Even if a LED is hardware
31 but you can't turn it off if the hardware decides to light it up. For this
32 reason, hardware controlled LEDs aren't registered as LED class devices.
[all …]
|
| /kernel/liteos_a/arch/arm/include/ |
| D | los_hwi.h | 33 * @defgroup los_hwi Hardware interrupt
75 * Highest priority of a hardware interrupt.
81 * Lowest priority of a hardware interrupt.
87 * Max name length of a hardware interrupt.
93 * Hardware interrupt error code: Invalid interrupt number.
103 * Hardware interrupt error code: Null hardware interrupt handling function.
107 * Solution: Pass in a valid non-null hardware interrupt handling function.
113 * Hardware interrupt error code: Insufficient interrupt resources for hardware interrupt creation.
117 * Solution: Increase the configured maximum number of supported hardware interrupts.
123 * Hardware interrupt error code: Insufficient memory for hardware interrupt initialization.
[all …]
|
| /kernel/linux/linux-6.6/drivers/hwmon/pmbus/ |
| D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic
33 If you say yes here you get hardware monitoring support for the ACBEL
44 If you say yes here you get hardware monitoring support for Analog
53 If you say yes here you get hardware monitoring support for Analog
63 If you say yes here you get hardware monitoring support for BEL
72 If you say yes here you get hardware monitoring support for BluTek
81 If you say yes here you get hardware monitoring support for
91 If you say yes here you get hardware monitoring support for
102 If you say yes here you get hardware monitoring support for the IBM
111 If you say yes here you get hardware monitoring support for Delta
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/powerpc/pmu/event_code_tests/ |
| D | hw_cache_event_type_test.c | 17 * Hardware cache level : PERF_COUNT_HW_CACHE_L1D
18 * Hardware cache event operation type : PERF_COUNT_HW_CACHE_OP_READ
19 * Hardware cache event result type : PERF_COUNT_HW_CACHE_RESULT_MISS
23 * Hardware cache level : PERF_COUNT_HW_CACHE_L1D
24 * Hardware cache event operation type : PERF_COUNT_HW_CACHE_OP_WRITE
25 * Hardware cache event result type : PERF_COUNT_HW_CACHE_RESULT_ACCESS
29 * Hardware cache level : PERF_COUNT_HW_CACHE_DTLB
30 * Hardware cache event operation type : PERF_COUNT_HW_CACHE_OP_WRITE
31 * Hardware cache event result type : PERF_COUNT_HW_CACHE_RESULT_ACCESS
35 * Hardware cache level : PERF_COUNT_HW_CACHE_L1D
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/spi/ |
| D | sprd,spi-adi.yaml | 17 framework for its hardware implementation is alike to SPI bus and its timing
21 48 hardware channels to access analog chip. For 2 software read/write channels,
22 users should set ADI registers to access analog chip. For hardware channels,
23 we can configure them to allow other hardware components to use it independently,
24 which means we can just link one analog chip address to one hardware channel,
25 then users can access the mapped analog chip address by this hardware channel
26 triggered by hardware components instead of ADI software channels.
28 Thus we introduce one property named "sprd,hw-channels" to configure hardware
29 channels, the first value specifies the hardware channel id which is used to
30 transfer data triggered by hardware automatically, and the second value specifies
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 5 framework for its hardware implementation is alike to SPI bus and its timing
9 48 hardware channels to access analog chip. For 2 software read/write channels,
10 users should set ADI registers to access analog chip. For hardware channels,
11 we can configure them to allow other hardware components to use it independently,
12 which means we can just link one analog chip address to one hardware channel,
13 then users can access the mapped analog chip address by this hardware channel
14 triggered by hardware components instead of ADI software channels.
16 Thus we introduce one property named "sprd,hw-channels" to configure hardware
17 channels, the first value specifies the hardware channel id which is used to
18 transfer data triggered by hardware automatically, and the second value specifies
[all …]
|
| /kernel/linux/linux-5.10/drivers/hwmon/pmbus/ |
| D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic
34 If you say yes here you get hardware monitoring support for Analog
43 If you say yes here you get hardware monitoring support for Analog
53 If you say yes here you get hardware monitoring support for BEL
63 If you say yes here you get hardware monitoring support for the IBM
72 If you say yes here you get hardware monitoring support for the INSPUR
81 If you say yes here you get hardware monitoring support for the
90 If you say yes here you get hardware monitoring support for Infineon
99 If you say yes here you get hardware monitoring support for the
108 If you say yes here you get hardware monitoring support for Renesas
[all …]
|
| /kernel/linux/linux-5.10/drivers/hwspinlock/ |
| D | Kconfig | 7 bool "Hardware Spinlock drivers"
12 tristate "OMAP Hardware Spinlock device"
15 Say y here to support the OMAP Hardware Spinlock device (firstly
21 tristate "Qualcomm Hardware Spinlock device"
25 Say y here to support the Qualcomm Hardware Mutex functionality, which
32 tristate "SIRF Hardware Spinlock device"
35 Say y here to support the SIRF Hardware Spinlock device, which
39 It's safe to say n here if you're not interested in SIRF hardware
43 tristate "SPRD Hardware Spinlock device"
46 Say y here to support the SPRD Hardware Spinlock device.
[all …]
|
| /kernel/linux/linux-5.10/drivers/char/hw_random/ |
| D | Kconfig | 3 # Hardware Random Number Generator (RNG) configuration
7 tristate "Hardware Random Number Generator Core support"
10 Hardware Random Number Generator Core infrastructure.
15 of possibly several hardware random number generators.
17 These hardware random number generators do feed into the
44 Generator hardware found on Intel i8xx-based motherboards.
57 Generator hardware found on AMD 76x-based motherboards.
70 Generator hardware found on Atmel AT91 devices.
82 Generator hardware based on Silex Insight BA431 IP.
94 Generator hardware found on the Broadcom BCM2835 and BCM63xx SoCs.
[all …]
|
| /kernel/linux/linux-6.6/drivers/hwspinlock/ |
| D | Kconfig | 7 bool "Hardware Spinlock drivers"
12 tristate "OMAP Hardware Spinlock device"
15 Say y here to support the OMAP Hardware Spinlock device (firstly
21 tristate "Qualcomm Hardware Spinlock device"
25 Say y here to support the Qualcomm Hardware Mutex functionality, which
32 tristate "SPRD Hardware Spinlock device"
35 Say y here to support the SPRD Hardware Spinlock device.
40 tristate "STM32 Hardware Spinlock device"
43 Say y here to support the STM32 Hardware Spinlock device.
48 tristate "SUN6I Hardware Spinlock device"
[all …]
|
| /kernel/linux/linux-6.6/drivers/char/hw_random/ |
| D | Kconfig | 3 # Hardware Random Number Generator (RNG) configuration
7 tristate "Hardware Random Number Generator Core support"
10 Hardware Random Number Generator Core infrastructure.
15 of possibly several hardware random number generators.
17 These hardware random number generators do feed into the
44 Generator hardware found on Intel i8xx-based motherboards.
58 Generator hardware found on AMD 76x-based motherboards.
71 Generator hardware found on Atmel AT91 devices.
83 Generator hardware based on Silex Insight BA431 IP.
95 Generator hardware found on the Broadcom BCM2835 and BCM63xx SoCs.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/ |
| D | glossary.rst | 18 media hardware.
29 Part of the Linux Kernel that implements support for a hardware
39 An API designed to control a subset of the :term:`Media Hardware`
58 Hardware Component
59 A subset of the :term:`Media Hardware`. For example an :term:`I²C` or
63 Hardware Peripheral
64 A group of :term:`hardware components <Hardware Component>` that
67 and the external camera sensors together make a camera hardware
76 serial computer bus used to control some hardware components
77 like sub-device hardware components.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/ |
| D | glossary.rst | 18 media hardware.
29 Part of the Linux Kernel that implements support for a hardware
39 An API designed to control a subset of the :term:`Media Hardware`
58 Hardware Component
59 A subset of the :term:`Media Hardware`. For example an :term:`I²C` or
63 Hardware Peripheral
64 A group of :term:`hardware components <Hardware Component>` that
67 and the external camera sensors together make a camera hardware
76 serial computer bus used to control some hardware components
77 like sub-device hardware components.
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | fib_offload_lib.sh | 69 check_err $? "Route not in hardware when should"
73 check_err $? "Appended route in hardware when should not"
77 check_err $? "Prepended route not in hardware when should"
80 check_err $? "Route was not replaced in hardware by prepended one"
100 check_err $? "Route not in hardware when should"
104 check_err $? "Highest TOS route not in hardware when should"
107 check_err $? "Lowest TOS route still in hardware when should not"
111 check_err $? "Middle TOS route in hardware when should not"
129 check_err $? "Route not in hardware when should"
133 check_err $? "Lowest metric route not in hardware when should"
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/forwarding/ |
| D | fib_offload_lib.sh | 69 check_err $? "Route not in hardware when should"
73 check_err $? "Appended route in hardware when should not"
77 check_err $? "Prepended route not in hardware when should"
80 check_err $? "Route was not replaced in hardware by prepended one"
100 check_err $? "Route not in hardware when should"
104 check_err $? "Highest TOS route not in hardware when should"
107 check_err $? "Lowest TOS route still in hardware when should not"
111 check_err $? "Middle TOS route in hardware when should not"
129 check_err $? "Route not in hardware when should"
133 check_err $? "Lowest metric route not in hardware when should"
[all …]
|
| /kernel/liteos_m/arch/risc-v/riscv32/gcc/ |
| D | los_arch_interrupt.h | 48 * Define the type of a hardware interrupt vector table function.
73 * Highest priority of a hardware interrupt.
79 * Lowest priority of a hardware interrupt.
120 * Maximum number of supported hardware devices that generate hardware interrupts.
121 …* The maximum number of hardware devices that generate hardware interrupts supported by hi3518ev20…
154 * Hardware interrupt error code: Invalid interrupt number.
165 * Hardware interrupt error code: Null hardware interrupt handling function.
169 * Solution: Pass in a valid non-null hardware interrupt handling function.
175 * Hardware interrupt error code: Insufficient interrupt resources for hardware interrupt creation.
179 * Solution: Increase the configured maximum number of supported hardware interrupts.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues
9 Hardware issues which result in security problems are a different category
13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
16 hardware vendors and other parties. For some of the issues, software
25 The Linux kernel hardware security team is separate from the regular Linux
28 The team only handles the coordination of embargoed hardware security
34 The team can be contacted by email at <hardware-security@kernel.org>. This
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
46 While hardware security issues are often handled by the affected hardware
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues
9 Hardware issues which result in security problems are a different category
13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
16 hardware vendors and other parties. For some of the issues, software
25 The Linux kernel hardware security team is separate from the regular Linux
28 The team only handles developing fixes for embargoed hardware security
34 The team can be contacted by email at <hardware-security@kernel.org>. This
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
46 While hardware security issues are often handled by the affected hardware
[all …]
|
| /kernel/liteos_m/arch/risc-v/nuclei/gcc/ |
| D | los_arch_interrupt.h | 63 * Maximum number of supported hardware devices that generate hardware interrupts.
71 * Hardware interrupt error code: Invalid interrupt number.
82 * Hardware interrupt error code: Null hardware interrupt handling function.
86 * Solution: Pass in a valid non-null hardware interrupt handling function.
92 * Hardware interrupt error code: Insufficient interrupt resources for hardware interrupt creation.
96 * Solution: Increase the configured maximum number of supported hardware interrupts.
102 * Hardware interrupt error code: Insufficient memory for hardware interrupt initialization.
112 * Hardware interrupt error code: The interrupt has already been created.
122 * Hardware interrupt error code: Invalid interrupt priority.
132 * Hardware interrupt error code: Incorrect interrupt creation mode.
[all …]
|
| /kernel/liteos_m/arch/include/ |
| D | los_interrupt.h | 82 * @brief Delete hardware interrupt.
85 * This API is used to delete hardware interrupt.
89 * <li>The hardware interrupt module is usable only when the configuration item for hardware
91 * <li>Hardware interrupt number value range: [OS_USER_HWI_MIN,OS_USER_HWI_MAX]. The value range
97 * @param hwiNum [IN] Type#HWI_HANDLE_T: hardware interrupt number. The value range applicable
99 * @param irqParam [IN] Type #HwiIrqParam *. ID of hardware interrupt which will base on
100 * when delete the hardware interrupt.
111 * @brief Create a hardware interrupt.
114 …* This API is used to configure a hardware interrupt and register a hardware interrupt handling fu…
118 * <li>The hardware interrupt module is usable only when the configuration item for hardware
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/ |
| D | cache.json | 45 …"PublicDescription": "This event counts L1D_CACHE_REFILL caused by software or hardware prefetch.",
48 … "BriefDescription": "This event counts L1D_CACHE_REFILL caused by software or hardware prefetch."
51 …"PublicDescription": "This event counts L2D_CACHE_REFILL caused by software or hardware prefetch.",
54 … "BriefDescription": "This event counts L2D_CACHE_REFILL caused by software or hardware prefetch."
63 "PublicDescription": "This event counts L1D_CACHE_REFILL caused by hardware prefetch.",
66 "BriefDescription": "This event counts L1D_CACHE_REFILL caused by hardware prefetch."
87 "PublicDescription": "This event counts L2D_CACHE_REFILL caused by hardware prefetch.",
90 "BriefDescription": "This event counts L2D_CACHE_REFILL caused by hardware prefetch."
105 …ns where demand access hits an L2 cache refill buffer allocated by software or hardware prefetch.",
108 …ons where demand access hits an L2 cache refill buffer allocated by software or hardware prefetch."
[all …]
|
| /kernel/linux/linux-5.10/crypto/ |
| D | crypto_engine.c | 3 * Handle async block request by crypto hardware engine.
21 * @engine: the hardware engine
34 * If hardware cannot enqueue more requests in crypto_finalize_request()
63 * @engine: the hardware engine
67 * needs processing and if so call out to the driver to initialize hardware
109 dev_err(engine->dev, "failed to unprepare crypt hardware\n"); in crypto_pump_requests()
124 * If hardware doesn't support the retry mechanism, in crypto_pump_requests()
145 dev_err(engine->dev, "failed to prepare crypt hardware\n"); in crypto_pump_requests()
168 /* Request unsuccessfully executed by hardware */ in crypto_pump_requests()
171 * If hardware queue is full (-ENOSPC), requeue request in crypto_pump_requests()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 10 While performing the hardware offloading process, much of the hardware
16 Linux kernel may differ from the hardware implementation. The pipeline debug
20 The hardware offload process is expected to be done in a way that the user
21 should not be able to distinguish between the hardware vs. software
22 implementation. In this process, hardware specifics are neglected. In
28 differences in the hardware and software models some processes cannot be
32 greatly to the hardware implementation. The configuration API is the same,
34 Level Path Compression trie (LPC-trie) in hardware.
38 information about the underlying hardware, this debugging can be made
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 10 While performing the hardware offloading process, much of the hardware
16 Linux kernel may differ from the hardware implementation. The pipeline debug
20 The hardware offload process is expected to be done in a way that the user
21 should not be able to distinguish between the hardware vs. software
22 implementation. In this process, hardware specifics are neglected. In
28 differences in the hardware and software models some processes cannot be
32 greatly to the hardware implementation. The configuration API is the same,
34 Level Path Compression trie (LPC-trie) in hardware.
38 information about the underlying hardware, this debugging can be made
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
[all …]
|