| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 Analog
73 If you say yes here you get hardware monitoring support for BEL
82 If you say yes here you get hardware monitoring support for BluTek
91 If you say yes here you get hardware monitoring support for
101 If you say yes here you get hardware monitoring support for
112 If you say yes here you get hardware monitoring support for the IBM
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/Documentation/userspace-api/media/ |
| D | glossary.rst | 18 media hardware.
36 Part of the Linux Kernel that implements support for a hardware
46 An API designed to control a subset of the :term:`Media Hardware`
65 Hardware Component
66 A subset of the :term:`Media Hardware`. For example an :term:`I²C` or
70 Hardware Peripheral
71 A group of :term:`hardware components <Hardware Component>` that
74 and the external camera sensors together make a camera hardware
83 serial computer bus used to control some hardware components
84 like sub-device hardware components.
[all …]
|
| /linux-6.12.1/Documentation/translations/sp_SP/process/ |
| D | embargoed-hardware-issues.rst | 4 :Original: Documentation/process/embargoed-hardware-issues.rst
7 Problemas de hardware embargados
13 Los problemas de hardware que resultan en problemas de seguridad son una
17 Los problemas de hardware como Meltdown, Spectre, L1TF, etc. deben
20 vendedores diferentes de OS, distribuciones, vendedores de hardware y
30 El equipo de seguridad de hardware del kernel de Linux es separado del
34 hardware embargados. Los informes de errores de seguridad de software puro
41 <hardware-security@kernel.org>. Esta es una lista privada de oficiales de
51 - PGP: https://www.kernel.org/static/files/hardware-security.asc
52 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 silicon vendors, hardware integrators, and other parties. For some of the
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 silicon
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| D | gadget.rst | 22 they're easy to port to new hardware.
36 - Minimalist, so it's easier to support new device controller hardware.
41 USB ``host`` hardware in a PC, workstation, or server. Linux users with
42 embedded systems are more likely to have USB peripheral hardware. To
43 distinguish drivers running inside such hardware from the more familiar
58 necessarily different (one side is a hardware-neutral master, the other
59 is a hardware-aware slave), the endpoint I/0 API used here should also
69 hardware).
75 to hardware, through registers, fifos, dma, irqs, and the like. The
77 endpoint hardware. That hardware is exposed through endpoint
[all …]
|
| /linux-6.12.1/crypto/ |
| D | crypto_engine.c | 3 * Handle async block request by crypto hardware engine.
36 * @engine: the hardware engine
46 * If hardware cannot enqueue more requests in crypto_finalize_request()
66 * @engine: the hardware engine
70 * needs processing and if so call out to the driver to initialize hardware
113 dev_err(engine->dev, "failed to unprepare crypt hardware\n"); in crypto_pump_requests()
128 * If hardware doesn't support the retry mechanism, in crypto_pump_requests()
146 dev_err(engine->dev, "failed to prepare crypt hardware\n"); in crypto_pump_requests()
163 /* Request unsuccessfully executed by hardware */ in crypto_pump_requests()
166 * If hardware queue is full (-ENOSPC), requeue request in crypto_pump_requests()
[all …]
|
| /linux-6.12.1/Documentation/driver-api/media/ |
| D | cec-core.rst | 7 hardware. It is designed to handle a multiple types of hardware (receivers,
35 The struct cec_adapter represents the CEC adapter hardware. It is created by
61 capabilities of the hardware and which parts are to be handled
128 hardware. They are all called with the mutex adap->lock held.
131 To enable/disable the hardware::
135 This callback enables or disables the CEC hardware. Enabling the CEC hardware
139 hardware is enabled. CEC drivers should not set CEC_CAP_NEEDS_HPD unless
140 the hardware design requires that as this will make it impossible to wake
152 that are not for us. Not all hardware supports this and this function is only
154 (some hardware may always be in 'monitor all' mode).
[all …]
|
| /linux-6.12.1/drivers/iio/pressure/ |
| D | zpa2326.c | 15 * A internal hardware trigger is also implemented to dispatch registered IIO
18 * ZPA2326 hardware supports 2 sampling mode: one shot and continuous.
29 * The continuous mode works according to a periodic hardware measurement
30 * process continuously pushing samples into an internal hardware FIFO (for
35 * - setup hardware sampling period,
37 * hardware FIFO and fetch temperature sample
41 * declares a valid interrupt line. In this case, the internal hardware trigger
44 * Note that hardware sampling frequency is taken into account only when
45 * internal hardware trigger is attached as the highest sampling rate seems to
51 * hardware samples averaging.
[all …]
|
| /linux-6.12.1/drivers/gpu/drm/xe/ |
| D | xe_hw_fence_types.h | 19 * struct xe_hw_fence_irq - hardware fence IRQ handler
38 * struct xe_hw_fence_ctx - hardware fence context
40 * The context for a hardware fence. 1 to 1 relationship with xe_engine. Points
44 /** @gt: graphics tile of hardware fence context */
48 /** @dma_fence_ctx: dma fence context for hardware fence */
50 /** @next_seqno: next seqno for hardware fence */
52 /** @name: name of hardware fence context */
57 * struct xe_hw_fence - hardware fence
63 /** @dma: base dma fence for hardware fence context */
67 /** @name: name of hardware fence context */
|
| /linux-6.12.1/Documentation/arch/x86/ |
| D | sva.rst | 31 Shared Hardware Workqueues
36 Machines (VM's). This allows better hardware utilization vs. hard
38 allow the hardware to distinguish the context for which work is being
39 executed in the hardware by SWQ interface, SIOV uses Process Address Space
56 command was accepted by hardware. This allows the submitter to know if the
61 to the hardware and also permits hardware to be aware of application context
68 user processes and the rest of the hardware. When an application first
94 platform hardware. ENQCMD uses the PASID stored in this MSR to tag requests
153 * Devices have a limited number (~10's to 1000's) of hardware workqueues.
154 The device driver manages allocating hardware workqueues.
[all …]
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 30 to receive data from the hardware. A "full" descriptor has data in it,
38 ring is handed off to the hardware, which sequentially fills in the
43 and "tail" pointers, managed by the OS, and a hardware current
45 currently being filled. When this descr is filled, the hardware
48 and everything in front of it should be "empty". If the hardware
52 The tail pointer tails or trails the hardware pointer. When the
53 hardware is ahead, the tail pointer will be pointing at a "full"
58 flowing, then the tail pointer can catch up to the hardware pointer.
66 dma-mapping it so as to make it visible to the hardware. The OS will
93 In the above, the hardware has filled in one descr, number 20. Both
[all …]
|
| /linux-6.12.1/Documentation/block/ |
| D | inline-encryption.rst | 12 Inline encryption hardware sits logically between memory and disk, and can
14 can control exactly how the inline encryption hardware will en/decrypt the data
18 Some inline encryption hardware accepts all encryption parameters including raw
20 hardware instead has a fixed number of "keyslots" and requires that the key,
24 Note that inline encryption hardware is very different from traditional crypto
27 hardware operates on I/O requests. Thus, inline encryption hardware needs to be
30 Inline encryption hardware is also very different from "self-encrypting drives",
33 verify the correctness of the resulting ciphertext. Inline encryption hardware
42 encryption hardware is absent. We also want inline encryption to work with
44 the inline encryption hardware of the underlying devices if present, or else
[all …]
|
| D | blk-mq.rst | 49 blk-mq has two group of queues: software staging queues and hardware dispatch
51 path possible: send it directly to the hardware queue. However, there are two
57 at the hardware queue, a second stage queue where the hardware has direct access
58 to process those requests. However, if the hardware does not have enough
60 queue, to be sent in the future, when the hardware is able.
95 eligible to be sent to the hardware. One of the possible schedulers to be
98 any reordering. When the device starts processing requests in the hardware
99 queue (a.k.a. run the hardware queue), the software queues mapped to that
100 hardware queue will be drained in sequence according to their mapping.
102 Hardware dispatch queues
[all …]
|
| /linux-6.12.1/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_rm.h | 17 * struct dpu_rm - DPU dynamic hardware resource manager
18 * @pingpong_blks: array of pingpong hardware resources
19 * @mixer_blks: array of layer mixer hardware resources
20 * @ctl_blks: array of ctl hardware resources
21 * @hw_intf: array of intf hardware resources
22 * @hw_wb: array of wb hardware resources
23 * @dspp_blks: array of dspp hardware resources
24 * @hw_sspp: array of sspp hardware resources
25 * @cdm_blk: cdm hardware resource
41 * dpu_rm_init - Read hardware catalog and create reservation tracking objects
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/net/ |
| D | fsl,fman-port.yaml | 13 The Frame Manager (FMan) supports several types of hardware ports:
31 Specifies the hardware port id.
32 Each hardware port on the FMan has its own hardware PortID.
33 Super set of all hardware Port IDs available at FMan Reference
34 Manual under "FMan Hardware Ports in Freescale Devices" table.
36 Each hardware port is assigned a 4KB, port-specific page in
37 the FMan hardware port memory region (which is part of the
38 FMan memory map). The first 4 KB in the FMan hardware ports
40 The subsequent 63 4KB pages are allocated to the hardware
|
| /linux-6.12.1/Documentation/devicetree/bindings/mailbox/ |
| D | mediatek,gce-props.yaml | 14 single-core command dispatcher for MediaTek hardware. The Command Queue
19 driver. A device driver that uses the CMDQ driver to configure its hardware
21 channel corresponding to a GCE hardware thread to send a message, specifying
22 that the GCE thread to configure its hardware. The mailbox provider can also
23 reserve a mailbox channel to configure GCE hardware register by the specific
33 Some gce-events are hardware-bound and cannot be changed by software.
38 On the other hand, some gce-events are not hardware-bound and can be
40 event ID 855, which is not bound to any hardware, to 1 when the driver
44 to any hardware and is not yet used in any software driver.
45 To determine if the event ID is bound to the hardware or used by a
|
| /linux-6.12.1/drivers/acpi/apei/ |
| D | Kconfig | 21 bool "APEI Generic Hardware Error Source"
27 Generic Hardware Error Source provides a way to report
28 platform hardware errors (such as that from chipset). It
29 works in so called "Firmware First" mode, that is, hardware
31 Linux by firmware. This way, some non-standard hardware
32 error registers or non-standard hardware link can be checked
33 by firmware to produce more valuable hardware error
59 EINJ provides a hardware error injection mechanism, it is
80 ERST is a way provided by APEI to save and retrieve hardware
|