Searched full:components (Results 1 – 25 of 325) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/clock/ |
| D | amlogic,axg-audio-clkc.yaml | 46 - description: slave bit clock N0 provided by external components
47 - description: slave bit clock N1 provided by external components
48 - description: slave bit clock N2 provided by external components
49 - description: slave bit clock N3 provided by external components
50 - description: slave bit clock N4 provided by external components
51 - description: slave bit clock N5 provided by external components
52 - description: slave bit clock N6 provided by external components
53 - description: slave bit clock N7 provided by external components
54 - description: slave bit clock N8 provided by external components
55 - description: slave bit clock N9 provided by external components
[all …]
|
| /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 …]
|
| /Documentation/sphinx/ |
| D | translations.py | 42 components = docname.split(os.sep)
43 if components[0] == 'translations' and len(components) > 2:
44 this_lang_code = components[1]
47 docname = os.path.join(*components[2:])
|
| /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/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.
|
| D | pixfmt-packed-yuv.rst | 10 Cr components consecutively in memory. They may apply subsampling to the chroma
11 components and thus differ in how they interlave the three components.
17 'U') and red chroma (also known as 'V') components respectively. 'A'
25 These formats do not subsample the chroma components and store each pixels as a
29 component. They are named based on the order of the Y, Cb and Cr components as
157 They are named based on the order of the Y, Cb and Cr components as stored in
293 components horizontally by 2, storing 2 pixels in a container. The container
425 This format subsamples the chroma components horizontally by 4, storing 8
|
| /Documentation/virt/kvm/s390/ |
| 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/networking/device_drivers/ethernet/meta/ |
| D | fbnic.rst | 10 fbnic has three components stored on the flash which are provided in one PLDM
21 fbnic stores two copies of these three components on flash. This allows fbnic
27 devlink dev info provides version information for all three components. In
|
| /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 | sprd,spi-adi.yaml | 23 we can configure them to allow other hardware components to use it independently,
26 triggered by hardware components instead of ADI software channels.
31 the analog chip address where user want to access by hardware components.
77 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
|
| /Documentation/networking/devlink/ |
| 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
152 Part number of the board and its components.
|
| 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).
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-dummy-source.yaml | 10 CoreSight components are compliant with the ARM CoreSight architecture
12 SoCs tracing needs. These trace components can generally be classified as
19 there would be Coresight source trace components on sub-processor which
|
| D | arm,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
18 CTI and the components it is directly connected to, consisting of input and
30 In general the connections between CTI and components via the trigger signals
44 on the connections between the CTI and other components for correct operation.
48 between CTI and other CoreSight components.
60 components (e.g. UART etc) depending on hardware implementation.
|
| D | arm,coresight-etb10.yaml | 16 CoreSight components are compliant with the ARM CoreSight architecture
18 SoCs tracing needs. These trace components can generally be classified as
|
| /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/devicetree/bindings/arm/samsung/ |
| D | samsung-soc.yaml | 13 Guidelines for new compatibles for SoC blocks/components.
30 - description: Preferred naming style for compatibles of SoC components
|
| /Documentation/userspace-api/media/ |
| D | glossary.rst | 71 A group of :term:`hardware components <Hardware Component>` that
83 serial computer bus used to control some hardware components
84 like sub-device hardware components.
180 An integrated circuit that integrates all components of a computer
203 V4L2 hardware components that aren't controlled by a
|
| /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
|
| /Documentation/devicetree/bindings/soc/renesas/ |
| D | renesas-soc.yaml | 14 Guidelines for new compatibles for SoC blocks/components.
38 # Preferred naming style for compatibles of SoC components
64 # Some SoC components in addition to a Renesas compatible list
|
| /Documentation/gpu/amdgpu/ |
| D | driver-core.rst | 12 The driver is arranged by IPs. There are driver components to handle
22 components are shared between the CPU, platform, and the GPU (e.g.,
23 SMU, PSP, etc.). Specific components (CPU, GPU, etc.) usually have
24 their interface to interact with those common components. For things
26 components, but that is probably a bit beyond the scope of this
|
12345678910>>...13