Home
last modified time | relevance | path

Searched full:components (Results 1 – 25 of 628) sorted by relevance

12345678910>>...26

/Linux-v5.4/Documentation/gpu/
Dafbc.rst18 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-v5.4/arch/powerpc/platforms/85xx/
DKconfig174 bool "TQ Components TQM8540"
176 This option enables support for the TQ Components TQM8540 board.
181 bool "TQ Components TQM8541"
183 This option enables support for the TQ Components TQM8541 board.
189 bool "TQ Components TQM8548"
191 This option enables support for the TQ Components TQM8548 board.
196 bool "TQ Components TQM8555"
198 This option enables support for the TQ Components TQM8555 board.
204 bool "TQ Components TQM8560"
206 This option enables support for the TQ Components TQM8560 board.
/Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/lib/
Ddevcom.c11 comp = &(priv)->components[iter], iter < MLX5_DEVCOM_NUM_COMPONENTS; \
27 struct mlx5_devcom_component components[MLX5_DEVCOM_NUM_COMPONENTS]; member
160 comp = &devcom->priv->components[id]; in mlx5_devcom_register_component()
175 comp = &devcom->priv->components[id]; in mlx5_devcom_unregister_component()
192 comp = &devcom->priv->components[id]; in mlx5_devcom_send_event()
211 comp = &devcom->priv->components[id]; in mlx5_devcom_set_paired()
223 return devcom->priv->components[id].paired; in mlx5_devcom_is_paired()
235 comp = &devcom->priv->components[id]; in mlx5_devcom_get_peer_data()
252 struct mlx5_devcom_component *comp = &devcom->priv->components[id]; in mlx5_devcom_release_peer_data()
/Linux-v5.4/drivers/base/
Dcomponent.c24 * already provide functions to get hold of such components, e.g.
30 * the SoC on various components (scanout engines, blending blocks, transcoders
36 * Components are registered using component_add() and unregistered with
190 * any components which are found to this master. in find_components()
243 dev_dbg(master->dev, "master has incomplete components\n"); in try_to_bring_up_master()
256 /* Found all components */ in try_to_bring_up_master()
385 * @compare: compare function to match against all components
391 * only matches against components added with component_add().
414 * @compare_typed: compare function to match against all typed components
420 * only matches against components added with component_add_typed().
[all …]
/Linux-v5.4/include/linux/
Dcomponent.h13 * 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
104 * @compare: compare function to match against all components
110 * only matches against components added with component_add().
/Linux-v5.4/Documentation/networking/
Dhinic.txt34 hinic_hwdev - Implement the HW details of the device and include the components
37 hinic_hwdev contains the following components:
49 MGMT components:
63 IO components:
82 IO - de/constructs all the IO components. (hinic_hw_io.c, hinic_hw_io.h)
87 HW device - de/constructs the HW Interface, the MGMT components on the
88 initialization of the driver and the IO components on the case of Interface
92 hinic_dev contains the following components:
/Linux-v5.4/lib/
Dbuild_OID_registry53 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-v5.4/Documentation/devicetree/bindings/mfd/
Dcirrus,lochnagar.txt37 - lochnagar-clk : Binding for the clocking components, see [4].
39 - lochnagar-pinctrl : Binding for the pin control components, see [5].
43 - Bindings for the regulator components, see [6]. Only available on
46 - lochnagar-sc : Binding for the sound card components, see [7].
48 - lochnagar-hwmon : Binding for the hardware monitor components, see [8].
/Linux-v5.4/drivers/misc/
Denclosure.c106 * @components: number of components in the enclosure
113 enclosure_register(struct device *dev, const char *name, int components, in enclosure_register() argument
117 kzalloc(struct_size(edev, component, components), GFP_KERNEL); in enclosure_register()
125 edev->components = components; in enclosure_register()
135 for (i = 0; i < components; i++) { in enclosure_register()
169 for (i = 0; i < edev->components; i++) in enclosure_unregister()
252 for (i = 0; i < edev->components; i++) { in enclosure_component_find_by_name()
273 * The name is optional for enclosures that give their components a unique
289 if (number >= edev->components) in enclosure_component_alloc()
303 /* Some hardware (e.g. enclosure in RX300 S6) has components in enclosure_component_alloc()
[all …]
/Linux-v5.4/Documentation/media/uapi/v4l/
Dext-ctrls-jpeg.rst37 how Cb and Cr components are downsampled after converting an input
49 - Horizontally subsample Cr, Cb components by a factor of 2.
51 - Subsample Cr, Cb components horizontally and vertically by 2.
53 - Horizontally subsample Cr, Cb components by a factor of 4.
55 - Subsample Cr, Cb components horizontally by 4 and vertically by 2.
/Linux-v5.4/Documentation/sound/soc/
Dpops-clicks.rst6 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-v5.4/include/media/drv-intf/
Dsoc_mediabus.h51 * @SOC_MBUS_LAYOUT_PACKED: color components packed
52 * @SOC_MBUS_LAYOUT_PLANAR_2Y_U_V: YUV components stored in 3 planes (4:2:2)
53 * @SOC_MBUS_LAYOUT_PLANAR_2Y_C: YUV components stored in a luma and a
56 * @SOC_MBUS_LAYOUT_PLANAR_Y_C: YUV components stored in a luma and a
/Linux-v5.4/Documentation/devicetree/bindings/spi/
Dspi-sprd-adi.txt11 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.
/Linux-v5.4/drivers/hwtracing/coresight/
DKconfig13 a topological view of the CoreSight components based on a DT
14 specification and configure the right series of components when a
53 components and a trace for bridging the gap between the on-chip
54 coresight components and a trace port collection engine, typically
/Linux-v5.4/drivers/gpu/drm/i915/gt/uc/
Dintel_uc_fw_abi.h29 * uCode and RSA signature are must-have components that will be used by driver.
30 * Length of each components, which is all in dwords, can be found in header.
36 * 1. Header, uCode and RSA are must-have components.
37 * 2. All firmware components, if they present, are in the sequence illustrated
/Linux-v5.4/security/integrity/
DKconfig9 of a number of different components including the Integrity
14 Each of these components can be enabled/disabled separately.
15 Refer to the individual components for additional details.
/Linux-v5.4/Documentation/media/uapi/dvb/
Dintro.rst76 Components of a Digital TV card/STB
79 following main hardware components:
99 The demultiplexer splits the TS into its components like audio and
120 flow between those components.
129 The Linux Digital TV API lets you control these hardware components through
/Linux-v5.4/drivers/staging/most/Documentation/ABI/
Dconfigfs-most.txt46 comp_params pass parameters needed by some components
90 comp_params pass parameters needed by some components
134 comp_params pass parameters needed by some components
188 comp_params pass parameters needed by some components
/Linux-v5.4/drivers/net/ethernet/huawei/hinic/
Dhinic_hw_io.c192 * @func_to_io: func to io channel that holds the IO components
260 * @func_to_io: func to io channel that holds the IO components
339 * @func_to_io: func to io channel that holds the IO components
358 * @func_to_io: func to io channel that holds the IO components
461 * @func_to_io: func to io channel that holds the IO components
488 * hinic_io_init - Initialize the IO components
489 * @func_to_io: func to io channel that holds the IO components
569 * hinic_io_free - Free the IO components
570 * @func_to_io: func to io channel that holds the IO components
/Linux-v5.4/include/linux/amba/
Dbus.h27 * 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-v5.4/Documentation/devicetree/bindings/power/
Dpower-controller.txt3 Power-management integrated circuits or miscellaneous hardware components are
5 components might need to define this capability, which tells the kernel that
/Linux-v5.4/Documentation/admin-guide/pm/
Dstrategies.rst27 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
/Linux-v5.4/arch/xtensa/platforms/xt2000/include/platform/
Dhardware.h21 * On-board components.
38 * Various other components.
/Linux-v5.4/drivers/net/ethernet/mellanox/mlxfw/
Dmlxfw_mfa2_file.h16 const void *cb; /* components block */
17 u32 cb_archive_size; /* size of compressed components block */
/Linux-v5.4/Documentation/fb/
Dapi.rst40 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

12345678910>>...26