| /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 …]
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| /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
|
| /Documentation/devicetree/bindings/crypto/ |
| D | brcm,spu-crypto.txt | 1 The Broadcom Secure Processing Unit (SPU) hardware supports symmetric
2 cryptographic offload for Broadcom SoCs. A SoC may have multiple SPU hardware
7 brcm,spum-crypto - for devices with SPU-M hardware
8 brcm,spu2-crypto - for devices with SPU2 hardware
9 brcm,spu2-v2-crypto - for devices with enhanced SPU2 hardware features like SHA3
11 brcm,spum-nsp-crypto - for the Northstar Plus variant of the SPU-M hardware
|
| /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
|
| /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 …]
|
| /Documentation/driver-api/iio/ |
| D | hw-consumer.rst | 4 An IIO device can be directly connected to another device in hardware. In this
5 case the buffers between IIO provider and IIO consumer are handled by hardware.
11 * struct iio_hw_consumer — Hardware consumer structure
12 * :c:func:`iio_hw_consumer_alloc` — Allocate IIO hardware consumer
13 * :c:func:`iio_hw_consumer_free` — Free IIO hardware consumer
14 * :c:func:`iio_hw_consumer_enable` — Enable IIO hardware consumer
15 * :c:func:`iio_hw_consumer_disable` — Disable IIO hardware consumer
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| /Documentation/devicetree/bindings/timestamp/ |
| D | hardware-timestamps-common.yaml | 4 $id: http://devicetree.org/schemas/timestamp/hardware-timestamps-common.yaml#
7 title: Hardware timestamp providers
13 Some devices/SoCs have hardware timestamp engines (HTE) which can use
14 hardware means to timestamp entity in realtime. The entity could be anything
15 from GPIOs, IRQs, Bus and so on. The hardware timestamp engine present
|
| /Documentation/arch/powerpc/ |
| D | ptrace.rst | 5 GDB intends to support the following hardware debug features of BookE
8 4 hardware breakpoints (IAC)
9 2 hardware watchpoints (read, write and read-write) (DAC)
10 2 value conditions for the hardware watchpoints (DVC)
21 Query for GDB to discover the hardware debug features. The main info to
22 be returned here is the minimum alignment for the hardware watchpoints.
24 an 8-byte alignment restriction for hardware watchpoints. We'd like to avoid
28 GDB: this query will return the number of hardware breakpoints, hardware
53 Sets a hardware breakpoint or watchpoint, according to the provided structure::
86 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
[all …]
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-trigger-pattern | 29 Specify a hardware pattern for the LED, for LED hardware that
31 to some preprogrammed hardware patterns. It deactivates any active
34 Since different LED hardware can have different semantics of
35 hardware patterns, each driver is expected to provide its own
36 description for the hardware patterns in their documentation
|
| D | debugfs-pfo-nx-crypto | 33 The total number of AES operations submitted to the hardware.
36 The total number of bytes hashed by the hardware using SHA-256.
39 The total number of SHA-256 operations submitted to the hardware.
42 The total number of bytes hashed by the hardware using SHA-512.
45 The total number of SHA-512 operations submitted to the hardware.
|
| D | sysfs-ptp | 7 features of PTP hardware clocks.
14 hardware clock registered into the PTP class driver
21 This file contains the name of the PTP hardware clock
32 This file contains the PTP hardware clock's maximum
48 alarms offer by the PTP hardware clock.
55 channels offered by the PTP hardware clock.
62 output channels offered by the PTP hardware clock.
69 offered by the PTP hardware clock.
89 pin offered by the PTP hardware clock. The file name
90 is the hardware dependent pin name. Reading from this
[all …]
|
| /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 …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | intro.rst | 72 following main hardware components:
75 Here the raw signal reaches the digital TV hardware from a satellite dish or
82 Conditional Access (CA) hardware like CI adapters and smartcard slots
83 The complete TS is passed through the CA hardware. Programs to which
89 Not every digital TV hardware provides conditional access hardware.
104 Modern hardware usually doesn't have a separate decoder hardware, as
106 adapter of the system or by a signal processing hardware embedded on
122 The Linux Digital TV API lets you control these hardware components through
125 control the MPEG2 decoder hardware, the frontend device the tuner and
127 and section filters of the hardware. If the hardware does not support
[all …]
|
| /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 …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-intro.rst | 9 cameras include microphones, video capture hardware can also output
13 Independent functions, even when implemented in the same hardware, can
23 complex and can't always be represented by a tree structure. Hardware
28 applications to access hardware parameters. As newer hardware expose an
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-configuration.rst | 9 settings and hardware limits.
11 Video hardware can have various cropping, composing and scaling
41 according to hardware limitations.
55 The part of a buffer into which the image is inserted by the hardware is
61 adjustments according to hardware limitations. The application can
69 The part of a buffer that is modified by the hardware is given by
71 ``V4L2_SEL_TGT_COMPOSE`` plus all padding data modified by hardware
73 be changed by the hardware. The content of pixels that lie inside the
96 the area from which image date are processed by the hardware, is given
100 further adjust the requested size and/or position according to hardware
[all …]
|
| /Documentation/networking/ |
| D | netdev-features.rst | 36 hardware or software.
81 This callback should not modify hardware nor driver state (should be
91 Hardware should be reconfigured to match passed feature set. The set
94 should update netdev->features to match resulting hardware state.
116 NETIF_F_TSO_ECN means that hardware can properly split packets with CWR bit
164 This requests that the NIC enables Hardware GRO (generic receive offload).
165 Hardware GRO is basically the exact reverse of TSO, and is generally
166 stricter than Hardware LRO. A packet stream merged by Hardware GRO must
168 Hardware GRO is dependent on RXCSUM since every packet successfully merged
169 by hardware must also have the checksum verified by hardware.
[all …]
|