| /Linux-v6.1/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 …]
|
| /Linux-v6.1/arch/powerpc/platforms/85xx/ |
| D | Kconfig | 167 bool "TQ Components TQM8540"
169 This option enables support for the TQ Components TQM8540 board.
174 bool "TQ Components TQM8541"
176 This option enables support for the TQ Components TQM8541 board.
182 bool "TQ Components TQM8548"
184 This option enables support for the TQ Components TQM8548 board.
189 bool "TQ Components TQM8555"
191 This option enables support for the TQ Components TQM8555 board.
197 bool "TQ Components TQM8560"
199 This option enables support for the TQ Components TQM8560 board.
|
| /Linux-v6.1/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| D | devcom.c | 11 comp = &(priv)->components[iter], iter < MLX5_DEVCOM_NUM_COMPONENTS; \
27 struct mlx5_devcom_component components[MLX5_DEVCOM_NUM_COMPONENTS]; member
162 comp = &devcom->priv->components[id]; in mlx5_devcom_register_component()
177 comp = &devcom->priv->components[id]; in mlx5_devcom_unregister_component()
194 comp = &devcom->priv->components[id]; in mlx5_devcom_send_event()
213 comp = &devcom->priv->components[id]; in mlx5_devcom_set_paired()
225 return devcom->priv->components[id].paired; in mlx5_devcom_is_paired()
237 comp = &devcom->priv->components[id]; in mlx5_devcom_get_peer_data()
254 struct mlx5_devcom_component *comp = &devcom->priv->components[id]; in mlx5_devcom_release_peer_data()
|
| /Linux-v6.1/drivers/base/ |
| D | component.c | 18 * already provide functions to get hold of such components, e.g.
24 * the SoC on various components (scanout engines, blending blocks, transcoders
30 * Components are registered using component_add() and unregistered with
181 * any components which are found to this adev. in find_components()
235 dev_dbg(adev->parent, "master has incomplete components\n"); in try_to_bring_up_aggregate_device()
248 /* Found all components */ in try_to_bring_up_aggregate_device()
430 * @compare: compare function to match against all components
436 * only matches against components added with component_add().
459 * @compare_typed: compare function to match against all typed components
465 * only matches against components added with component_add_typed().
[all …]
|
| /Linux-v6.1/include/linux/ |
| D | component.h | 13 * Components are registered with component_add() and unregistered with
30 * part-ways through and needs to unbind some already bound components.
56 * Called when all components or the aggregate driver, as specified in
62 * 2. Bind all components to the aggregate driver by calling
79 * component_master_del(), or one of its components, using
110 * @compare: compare function to match against all components
116 * only matches against components added with component_add().
|
| /Linux-v6.1/lib/ |
| D | build_OID_registry | 53 my @components = split(/[.]/, $oid);
56 my $size = $#components;
57 for (my $loop = 2; $loop <= $#components; $loop++) {
58 my $c = $components[$loop];
93 my @components = split(/[.]/, $oids[$i]);
95 push @octets, $components[0] * 40 + $components[1];
97 for (my $loop = 2; $loop <= $#components; $loop++) {
98 my $c = $components[$loop];
|
| /Linux-v6.1/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:
|
| /Linux-v6.1/drivers/misc/ |
| D | enclosure.c | 107 * @components: number of components in the enclosure
115 enclosure_register(struct device *dev, const char *name, int components, in enclosure_register() argument
119 kzalloc(struct_size(edev, component, components), GFP_KERNEL); in enclosure_register()
127 edev->components = components; in enclosure_register()
137 for (i = 0; i < components; i++) { in enclosure_register()
171 for (i = 0; i < edev->components; i++) in enclosure_unregister()
254 for (i = 0; i < edev->components; i++) { in enclosure_component_find_by_name()
275 * The name is optional for enclosures that give their components a unique
291 if (number >= edev->components) in enclosure_component_alloc()
305 /* Some hardware (e.g. enclosure in RX300 S6) has components in enclosure_component_alloc()
[all …]
|
| /Linux-v6.1/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
265 components horizontally by 2, storing 2 pixels in 4 bytes.
352 This format subsamples the chroma components horizontally by 4, storing 8
|
| /Linux-v6.1/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.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/sound/soc/intel/boards/ |
| D | sof_sdw_rt715.c | 18 card->components = devm_kasprintf(card->dev, GFP_KERNEL, in rt715_rtd_init()
20 card->components); in rt715_rtd_init()
21 if (!card->components) in rt715_rtd_init()
|
| D | sof_sdw_rt715_sdca.c | 18 card->components = devm_kasprintf(card->dev, GFP_KERNEL, in rt715_sdca_rtd_init()
20 card->components); in rt715_sdca_rtd_init()
21 if (!card->components) in rt715_sdca_rtd_init()
|
| /Linux-v6.1/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
|
| 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).
|
| /Linux-v6.1/drivers/hwtracing/coresight/ |
| D | Kconfig | 15 a topological view of the CoreSight components based on a DT
16 specification and configure the right series of components when a
68 components and a trace for bridging the gap between the on-chip
69 coresight components and a trace port collection engine, typically
170 This driver provides support for CoreSight CTI and CTM components.
172 source and sink components. These can be used to halt trace or
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/devicetree/bindings/spi/ |
| D | sprd,spi-adi.yaml | 24 we can configure them to allow other hardware components to use it independently,
27 triggered by hardware components instead of ADI software channels.
32 the analog chip address where user want to access by hardware components.
78 hardware components.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/devicetree/bindings/arm/ |
| 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.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/drivers/media/platform/nxp/imx-jpeg/ |
| D | mxc-jpeg.h | 45 * @subsampling: subsampling of jpeg components
46 * @nc: number of color components
152 * @components_no: number of color components
176 * @components_no: number of color components
|
| /Linux-v6.1/include/linux/amba/ |
| D | bus.h | 27 * for components on the AMBA bus. (ARM IHI 0029E)
31 * Class 0xF remains for PrimeCell and legacy components. (AMBA_CID above)
33 * Class 0x0, 0x1, 0xB, 0xE define components that do not have driver support
41 * Class 0x9 components use additional values to form a Unique Component
43 * components. Passed to the amba bus code from the component driver via
|
| /Linux-v6.1/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
|
