Searched full:component (Results 1 – 25 of 194) sorted by relevance
12345678
| /Documentation/gpu/ |
| D | afbc.rst | 21 AFBC streams can contain several components - where a component
29 maximum compression efficiency), the component order must be:
31 * Component 0: R
32 * Component 1: G
33 * Component 2: B
35 The component ordering is communicated via the fourcc code in the
36 fourcc:modifier pair. In general, component '0' is considered to
42 * Component 0: R(8)
43 * Component 1: G(8)
44 * Component 2: B(8)
[all …]
|
| D | komeda-kms.rst | 16 functional pipeline stages called components, and every component has some
301 struct komeda_pipeline/component
305 a similar architecture: Pipeline/Component to describe the HW features and
306 capabilities, and a specific component includes two parts:
309 - Specific component capabilities and features.
321 Pipeline and component are used to describe how to handle the pixel data. We
353 Komeda abstracts resources by pipeline/component, but DRM-KMS uses
354 crtc/plane/connector. One KMS-obj cannot represent only one single component,
356 single component, usually that needs multiple components to fit the requirement.
368 component, and at any one time a pipeline/component only can be used by one
[all …]
|
| D | kms-properties.csv | 4 ,TV,“subconnector”,ENUM,"{ ""Unknown"", ""Composite"", ""SVIDEO"", ""Component"", ""SCART"" }",Conn…
5 ,,“select subconnector”,ENUM,"{ ""Automatic"", ""Composite"", ""SVIDEO"", ""Component"", ""SCART"" …
68 …NUM,"{ ""disabled"", ""Y component"", ""U component"" , ""V component"", ""RGB"", “R component"", …
|
| /Documentation/driver-api/pldmfw/ |
| D | driver-ops.rst | 34 The ``.send_component_table`` operation is used to forward component
35 information to the device. It is called once for each applicable component,
36 that is, for each component indicated by the matching record. The
37 device driver should send the component information to the device firmware,
39 is the first, last, or a middle component, and is expected to be forwarded
40 to firmware as part of the component table information. The driver should an
41 error in the case when the firmware indicates that the component cannot be
42 updated, or return zero if the component can be updated.
48 flash a given component. The driver must perform any steps necessary to send
49 the component data to the device.
|
| D | file-format.rst | 25 | Component Info |
33 | Component Image 1 |
37 | Component Image 2 |
45 | Component Image N |
55 component bitmap, and an overall package version.
69 | Component Bitmap Length |
136 Component Info
139 The component information area begins with a count of the number of
140 components. Following this count is a description for each component. The
141 component information points to the location in the file where the component
[all …]
|
| D | index.rst | 31 so, it sends the record and component data to the firmware using the device
60 1. Parse the firmware file for record and component information
65 4. For each component that the record indicates, send the component data to
66 the device. For each component, the firmware may respond with an
67 indication of whether the update is suitable or not. If any component is
69 5. For each component, send the binary data to the device firmware for
|
| /Documentation/hwmon/ |
| D | intel-m10-bmc-hwmon.rst | 41 tempX_input Temperature of the component (specified by tempX_label)
42 tempX_max Temperature maximum setpoint of the component
43 tempX_crit Temperature critical setpoint of the component
44 tempX_max_hyst Hysteresis for temperature maximum of the component
45 tempX_crit_hyst Hysteresis for temperature critical of the component
55 inX_input Measured voltage of the component (specified by
66 currX_input Measured current of the component (specified by
72 powerX_input Measured power of the component (specified by
|
| D | occ.rst | 47 Measured temperature of the component in millidegrees
54 (represented by an integer) for the component
70 Measured temperature of the component in
76 Measured frequency of the component in MHz.
78 Latest measured power reading of the component in
81 Average power of the component in microwatts.
|
| /Documentation/driver-api/ |
| D | component.rst | 4 Component Helper for Aggregate Drivers
7 .. kernel-doc:: drivers/base/component.c
14 .. kernel-doc:: include/linux/component.h
17 .. kernel-doc:: drivers/base/component.c
|
| D | slimbus.rst | 39 Each SLIMbus component has an interface device for monitoring physical layer.
41 Typically each SoC contains SLIMbus component having 1 manager, 1 framer device,
43 External peripheral SLIMbus component usually has 1 generic device (for
68 slim_device represents the 'generic device/component' for SLIMbus, and a
|
| /Documentation/networking/devlink/ |
| D | nfp.rst | 53 - The CPLD firmware component version
56 - The APP firmware component version
59 - The UNDI firmware component version
62 - The NSCI firmware component version
65 - The CFGR firmware component version
|
| /Documentation/devicetree/bindings/sound/ |
| D | name-prefix.txt | 4 audio components as list of string pair. Component using the same
10 the component.
12 Example: Two instances of the same component.
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-image-source.rst | 41 Test pattern red colour component.
44 Test pattern green (next to red) colour component.
47 Test pattern blue colour component.
50 Test pattern green (next to blue) colour component.
|
| D | yuv-formats.rst | 12 *color difference* signals, this way the green component can be
13 reconstructed by subtracting from the brightness component. See
19 component. This is an analog video compression technique taking
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | tvp514x.txt | 5 video formats into digital video component. The tvp514x decoder supports analog-
6 to-digital (A/D) conversion of component RGB and YPbPr signals as well as A/D
8 component YCbCr.
|
| D | tda1997x.txt | 8 - YUV422 semi-planar 8bit per component (16 bits total): Y[11:4] CbCr[11:4]
9 - YUV422 semi-planar 10bit per component (20 bits total): Y[11:2] CbCr[11:2]
10 - YUV422 semi-planar 12bit per component (24 bits total): - Y[11:0] CbCr[11:0]
11 - YUV422 BT656 8bit per component (8 bits total): YCbCr[11:4] (2-cycles)
12 - YUV422 BT656 10bit per component (10 bits total): YCbCr[11:2] (2-cycles)
13 - YUV422 BT656 12bit per component (12 bits total): YCbCr[11:0] (2-cycles)
18 - YUV422 semi-planar 12bit per component (24 bits total): Y[11:0] CbCr[11:0]
19 - YUV422 BT656 12bit per component (12 bits total): YCbCr[11:0] (2-cycles)
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cpu-debug.txt | 1 * CoreSight CPU Debug Component:
3 CoreSight CPU debug component are compliant with the ARMv8 architecture
20 - clocks : the clock associated to this component.
|
| D | trbe.yaml | 14 Arm Trace Buffer Extension (TRBE) is a per CPU component
17 if it is permitted to use the component by checking the
|
| D | coresight.txt | 8 sink. Each CoreSight component device should use these properties to describe
56 set(s) of the component.
58 * clocks: the clocks associated to this component.
64 clocks the core of that coresight component. The latter clock
105 coresight component and CPU in the same power domain. When the CPU
106 powers down the coresight component also powers down and loses its
145 Each coresight component must describe the "input" and "output" connections.
148 component represents a hardware port and the connection.
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | composite.txt | 16 The binding must provide a list of the component clocks that shall be
17 merged to this clock. The component clocks shall be of one of the
27 - clocks : link phandles of component clocks
|
| /Documentation/filesystems/ |
| D | path-lookup.rst | 52 component, but that isn't always accurate: a pathname can lack both
60 These paths can be divided into two sections: the final component and
65 The final component is not so simple. Not only do different system
68 pathname that is just slashes have a final component. If it does
75 tempting to consider that to have an empty final component. In many
78 by the final component, and they are required to work with pathnames
83 be resolved successfully unless the last pathname component before
90 "everything else" quite separately from the final component, and
110 "dentry") contains three significant fields: a component name, a
273 Secondly, when pathname lookup reaches the final component, it will
[all …]
|
| /Documentation/sound/soc/ |
| D | codec.rst | 182 struct snd_soc_component *component = dai->component;
183 u16 mute_reg = snd_soc_component_read32(component, WM8974_DAC) & 0xffbf;
186 snd_soc_component_write(component, WM8974_DAC, mute_reg | 0x40);
188 snd_soc_component_write(component, WM8974_DAC, mute_reg);
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-switchtec | 18 Description: Component identifier as stored in the hardware (eg. PM8543)
27 Description: Component revision stored in the hardware (read only)
35 Description: Component vendor as stored in the hardware (eg. MICROSEM)
|
| /Documentation/devicetree/bindings/arm/marvell/ |
| D | armada-37xx.txt | 23 Power Management component is needed:
40 For AVS an other component is needed:
|
| /Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 27 a single Component.
39 SLIMbus example for Qualcomm's slimbus manager component:
|
12345678