Searched full:component (Results 1 – 25 of 173) sorted by relevance
1234567
| /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/ |
| 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/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/media/uapi/v4l/ |
| D | ext-ctrls-image-source.rst | 48 Test pattern red colour component.
51 Test pattern green (next to red) colour component.
54 Test pattern blue colour component.
57 Test pattern green (next to blue) colour component.
|
| D | yuv-formats.rst | 19 *color difference* signals, this way the green component can be
20 reconstructed by subtracting from the brightness component. See
26 component. This is an analog video compression technique taking
|
| D | control.rst | 255 interpreted as Cr component, bits [15:8] as Cb component and bits
292 .. _v4l2-alpha-component:
295 Sets the alpha color component. When a capture device (or capture
297 an alpha component (e.g.
300 control lets you select the alpha component value of all pixels.
302 consumes a frame format that doesn't include an alpha component and
304 set the alpha component value of all pixels for further processing
|
| D | pixfmt-intro.rst | 56 buffers, with Y component in one buffer and CbCr components in another
57 in the 2-planar version or with each component in its own buffer in the
|
| /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/hwmon/ |
| 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/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/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 | coresight.txt | 8 sink. Each CoreSight component device should use these properties to describe
49 set(s) of the component.
51 * clocks: the clocks associated to this component.
57 clocks the core of that coresight component. The latter clock
113 Each coresight component must describe the "input" and "output" connections.
116 component represents a hardware port and the connection.
|
| /Documentation/filesystems/ |
| D | path-lookup.rst | 51 component, but that isn't always accurate: a pathname can lack both
59 These paths can be divided into two sections: the final component and
64 The final component is not so simple. Not only do different system
67 pathname that is just slashes have a final component. If it does
74 tempting to consider that to have an empty final component. In many
77 by the final component, and they are required to work with pathnames
82 be resolved successfully unless the last pathname component before
89 "everything else" quite separately from the final component, and
109 "dentry") contains three significant fields: a component name, a
265 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);
|
| D | overview.rst | 54 multiple re-usable component drivers :-
67 describes and binds the other component drivers together to form an ALSA
|
| /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)
|
| D | debugfs-ideapad | 8 capability and what graphic component within the machine.
|
| /Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 27 a single Component.
35 SLIMbus example for Qualcomm's slimbus manager component:
|
| /Documentation/devicetree/bindings/arm/marvell/ |
| D | armada-37xx.txt | 23 Power Management component is needed:
40 For AVS an other component is needed:
|
| /Documentation/firmware-guide/acpi/ |
| D | debug.rst | 20 When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages
26 debug_layer (component)
149 Show all valid component values::
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-w1 | 4 Description: Bus scanning interval, microseconds component.
|
1234567