Home
last modified time | relevance | path

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

12345678910>>...32

/linux/Documentation/devicetree/bindings/clock/
H A Damlogic,axg-audio-clkc.yaml46 - 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 …]
/linux/Documentation/gpu/
H A 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/sound/soc/sdw_utils/
H A Dsoc_sdw_rt_dmic.c25 * rt715-sdca (aka rt714) is a special case that uses different name in card->components in asoc_sdw_rt_dmic_rtd_init()
35 card->components = devm_kasprintf(card->dev, GFP_KERNEL, in asoc_sdw_rt_dmic_rtd_init()
36 "%s mic:%s", card->components, in asoc_sdw_rt_dmic_rtd_init()
38 if (!card->components) in asoc_sdw_rt_dmic_rtd_init()
41 dev_dbg(card->dev, "card->components: %s\n", card->components); in asoc_sdw_rt_dmic_rtd_init()
H A Dsoc_sdw_cs42l43.c63 card->components = devm_kasprintf(card->dev, GFP_KERNEL, "%s hs:cs42l43", in asoc_sdw_cs42l43_hs_rtd_init()
64 card->components); in asoc_sdw_cs42l43_hs_rtd_init()
65 if (!card->components) in asoc_sdw_cs42l43_hs_rtd_init()
115 card->components = devm_kasprintf(card->dev, GFP_KERNEL, in asoc_sdw_cs42l43_spk_rtd_init()
117 card->components); in asoc_sdw_cs42l43_spk_rtd_init()
118 if (!card->components) in asoc_sdw_cs42l43_spk_rtd_init()
159 card->components = devm_kasprintf(card->dev, GFP_KERNEL, "%s mic:cs42l43-dmic", in asoc_sdw_cs42l43_dmic_rtd_init()
160 card->components); in asoc_sdw_cs42l43_dmic_rtd_init()
161 if (!card->components) in asoc_sdw_cs42l43_dmic_rtd_init()
H A Dsoc_sdw_rt_sdca_jack_common.c103 card->components = devm_kasprintf(card->dev, GFP_KERNEL, in asoc_sdw_rt_sdca_jack_rtd_init()
105 card->components, component->name_prefix); in asoc_sdw_rt_sdca_jack_rtd_init()
106 if (!card->components) in asoc_sdw_rt_sdca_jack_rtd_init()
112 card->components = devm_kasprintf(card->dev, GFP_KERNEL, in asoc_sdw_rt_sdca_jack_rtd_init()
113 "%s-sdca", card->components); in asoc_sdw_rt_sdca_jack_rtd_init()
114 if (!card->components) in asoc_sdw_rt_sdca_jack_rtd_init()
/linux/drivers/base/
H A Dcomponent.c18 * 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/Documentation/networking/device_drivers/ethernet/huawei/
H A Dhinic.rst37 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/lib/
H A Dbuild_OID_registry58 my @components = split(/[.]/, $oid);
61 my $size = $#components;
62 for (my $loop = 2; $loop <= $#components; $loop++) {
63 my $c = $components[$loop];
98 my @components = split(/[.]/, $oids[$i]);
100 push @octets, $components[0] * 40 + $components[1];
102 for (my $loop = 2; $loop <= $#components; $loop++) {
103 my $c = $components[$loop];
/linux/Documentation/sphinx/
H A Dtranslations.py42 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:])
/linux/drivers/misc/
H A Denclosure.c108 * @components: number of components in the enclosure
116 enclosure_register(struct device *dev, const char *name, int components, in enclosure_register() argument
120 kzalloc(struct_size(edev, component, components), GFP_KERNEL); in enclosure_register()
128 edev->components = components; in enclosure_register()
138 for (i = 0; i < components; i++) { in enclosure_register()
172 for (i = 0; i < edev->components; i++) in enclosure_unregister()
255 for (i = 0; i < edev->components; i++) { in enclosure_component_find_by_name()
276 * The name is optional for enclosures that give their components a unique
292 if (number >= edev->components) in enclosure_component_alloc()
306 /* Some hardware (e.g. enclosure in RX300 S6) has components in enclosure_component_alloc()
[all …]
/linux/Documentation/virt/kvm/s390/
H A Ds390-pv-boot.rst16 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/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-jpeg.rst30 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.
H A Dpixfmt-packed-yuv.rst10 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
/linux/Documentation/sound/soc/
H A 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/Documentation/networking/devlink/
H A Ddevlink-flash.rst23 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/drivers/scsi/
H A Dses.c538 for (i = 0; i < edev->components; i++) { in ses_enclosure_find_by_addr()
558 int i, j, page7_len, len, components; in ses_enclosure_data_process() local
596 components = 0; in ses_enclosure_data_process()
625 components++, in ses_enclosure_data_process()
628 else if (components < edev->components) in ses_enclosure_data_process()
629 ecomp = &edev->component[components++]; in ses_enclosure_data_process()
698 int i, types, len, components = 0; in ses_intf_add() local
758 components += type_ptr[1]; in ses_intf_add()
802 if (components > 0) { in ses_intf_add()
803 scomp = kcalloc(components, sizeof(struct ses_component), GFP_KERNEL); in ses_intf_add()
[all …]
/linux/Documentation/devicetree/bindings/spi/
H A Dsprd,spi-adi.yaml23 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.
/linux/Documentation/driver-api/pldmfw/
H A Dindex.rst41 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/Documentation/userspace-api/media/
H A Dglossary.rst71 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
/linux/drivers/i2c/
H A Di2c-core-of-prober.c24 * vendors each using their preferred components. Such components are all
99 * Probe for possible I2C components of the same "type" (&i2c_of_probe_cfg->type)
104 * the ones that need handling for second source components. In other words,
118 * has components of the type to be probed already enabled. This
120 * the status of the to-be-probed components as "fail-needs-probe".
123 * the user had multiple types of components to probe, and one of
327 dev_dbg(dev, "Requesting resources for components under I2C bus %pOF\n", bus_node); in i2c_of_probe_simple_enable()
/linux/drivers/hwtracing/coresight/
H A DKconfig15 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
182 This driver provides support for CoreSight CTI and CTM components.
184 source and sink components. These can be used to halt trace or
/linux/Documentation/devicetree/bindings/display/
H A Dallwinner,sun4i-a10-display-engine.yaml18 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/Documentation/userspace-api/media/dvb/
H A Dintro.rst69 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
/linux/drivers/gpu/drm/i915/gt/uc/
H A 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/Documentation/devicetree/bindings/arm/
H A Darm,coresight-cti.yaml12 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.

12345678910>>...32