Searched full:components (Results 1 – 25 of 250) sorted by relevance
12345678910
| /Documentation/gpu/ |
| D | afbc.rst | 18 Components and Ordering
21 AFBC streams can contain several components - where a component
59 In AFBC, 'X' components are not treated any differently from any other
61 encodes with 4 components, like so:
123 - Planes/Components
127 - Plane 0: 4 components
135 - Plane 0: 4 components
143 - Plane 0: 3 components
150 - Plane 0: 3 components
157 - Plane 0: 4 components
[all …]
|
| D | amdgpu-dc.rst | 10 1. **Display Core (DC)** contains the OS-agnostic components. Things like
12 2. **Display Manager (DM)** contains the OS-dependent components. Hooks to the
|
| /Documentation/networking/device_drivers/ethernet/huawei/ |
| D | hinic.rst | 37 hinic_hwdev - Implement the HW details of the device and include the components
40 hinic_hwdev contains the following components:
52 MGMT components:
66 IO components:
85 IO - de/constructs all the IO components. (hinic_hw_io.c, hinic_hw_io.h)
90 HW device - de/constructs the HW Interface, the MGMT components on the
91 initialization of the driver and the IO components on the case of Interface
95 hinic_dev contains the following components:
|
| /Documentation/virt/kvm/ |
| D | s390-pv-boot.rst | 16 information about the encrypted components and necessary metadata to
21 PVM, decrypt the components and verify the data and address list
51 * List of Components composed of
59 The components are for instance an encrypted kernel, kernel parameters
60 and initrd. The components are decrypted by the UV.
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-jpeg.rst | 30 how Cb and Cr components are downsampled after converting an input
42 - Horizontally subsample Cr, Cb components by a factor of 2.
44 - Subsample Cr, Cb components horizontally and vertically by 2.
46 - Horizontally subsample Cr, Cb components by a factor of 4.
48 - Subsample Cr, Cb components horizontally by 4 and vertically by 2.
|
| /Documentation/sound/soc/ |
| D | pops-clicks.rst | 6 of components within the audio subsystem. This is noticeable on PCs when an
11 because the components within the subsystem are being dynamically powered
22 components in a specific order. This order is different for startup and
39 playback in that components are powered in a sequence depending upon stream
|
| /Documentation/devicetree/bindings/power/ |
| D | power-controller.txt | 3 Power-management integrated circuits or miscellaneous hardware components are
5 components might need to define this capability, which tells the kernel that
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 11 we can configure them to allow other hardware components to use it independently,
14 triggered by hardware components instead of ADI software channels.
19 the analog chip address where user want to access by hardware components.
49 by hardware components.
|
| /Documentation/driver-api/pldmfw/ |
| D | index.rst | 41 length, including version strings and the number of records and components.
43 descriptors, or components.
52 components are stored in linked lists.
71 6. After all components are programmed, perform any final device-specific
|
| D | file-format.rst | 9 package header, one or more firmware records, and one or more components
85 which set of components that are used by this device. It is possible that
86 only subset of provided components will be used by a given record. A record
127 | Applicable Components |
140 components. Following this count is a description for each component. The
|
| /Documentation/networking/devlink/ |
| D | devlink-flash.rst | 23 how the device should handle subsections of flash components when updating.
32 - Indicates that the device should overwrite settings in the components
36 components being updated with the identifiers found in the provided
42 in the components being updated. Settings and identifiers are expected to be
54 components and versions).
|
| D | devlink-info.rst | 54 - Group for hardware identifiers, and versions of components
60 components, e.g. PCI VPD may concatenate various information
82 components stored on the flash should feature in both the ``running`` and
85 In case software/firmware components are loaded from the disk (e.g.
109 - Version of API between components. API items are usually of limited
120 but it must not be reported if any of the components covered by the
|
| /Documentation/userspace-api/media/ |
| D | glossary.rst | 64 A group of :term:`hardware components <Hardware Component>` that
76 serial computer bus used to control some hardware components
77 like sub-device hardware components.
173 An integrated circuit that integrates all components of a computer
191 V4L2 hardware components that aren't controlled by a
|
| /Documentation/devicetree/bindings/display/ |
| D | allwinner,sun4i-a10-display-engine.yaml | 18 The Allwinner A10 Display pipeline is composed of several components
21 For all connections between components up to the TCONs in the
22 display pipeline, when there are multiple components of the same
36 represent the connections between the components, while the numbers
|
| /Documentation/ABI/testing/ |
| D | configfs-most | 55 pass parameters needed by some components
110 pass parameters needed by some components
165 pass parameters needed by some components
231 pass parameters needed by some components
|
| /Documentation/userspace-api/media/dvb/ |
| D | intro.rst | 69 Components of a Digital TV card/STB
72 following main hardware components:
92 The demultiplexer splits the TS into its components like audio and
113 flow between those components.
122 The Linux Digital TV API lets you control these hardware components through
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 27 components of the system, as needed, in the working state. In consequence, if
31 the individual components of it can be either ``active`` (in use) or
37 If all of the system components are active, the system as a whole is regarded as
|
| D | suspend-flows.rst | 191 On the other platforms, however, low-level components (like interrupt
218 5. Suspending core system components.
220 This prepares the core system components for (possibly) losing power going
225 This is expected to remove power from all of the system components except
247 2. Resuming core system components.
249 The suspend-time configuration of the core system components is restored and
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 12 to one or more CoreSight components and/or a CPU, with CTIs interconnected in
14 The ECT components are not part of the trace generation data path and are thus
19 CTI and the components it is directly connected to, consisting of input and
31 In general the connections between CTI and components via the trigger signals
45 on the connections between the CTI and other components for correct operation.
49 between CTI and other CoreSight components.
61 components (e.g. UART etc) depending on hardware implementation.
|
| D | ete.yaml | 19 components (e.g, TMC-ETR) or other means (e.g, using a per CPU buffer
21 legacy CoreSight components, a node must be listed per instance, along
|
| D | coresight.txt | 1 * CoreSight Components:
3 CoreSight components are compliant with the ARM CoreSight architecture
5 SoCs tracing needs. These trace components can generally be classified as
11 * Required properties for all components *except* non-configurable replicators
100 * Optional properties for all components:
143 Coresight components are interconnected to create a data path for the flow of
|
| /Documentation/devicetree/bindings/clock/ |
| D | amlogic,axg-audio-clkc.txt | 21 components.
23 components.
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,apq8096.txt | 13 Definition: A list of the connections between audio components.
98 qcom,audio-routing: A list of the connections between audio components.
|
| /Documentation/fb/ |
| D | api.rst | 40 specifying color components layout.
115 Pixels are broken into red, green and blue components, and each component
125 blue components. The colormap is read-only for FB_VISUAL_STATIC_PSEUDOCOLOR
133 Pixels are broken into red, green and blue components, and each component
259 color components in memory::
269 green, blue and alpha (transparency) components. Location and size of each
|
| /Documentation/vm/ |
| D | numa.rst | 13 comprises multiple components or assemblies each of which may contain 0
15 disambiguate the hardware view of these physical components/assemblies
16 from the software abstraction thereof, we'll call the components/assemblies
20 of the system--although some components necessary for a stand-alone SMP system
|
12345678910