Home
last modified time | relevance | path

Searched full:providers (Results 1 – 25 of 121) sorted by relevance

12345

/linux-6.14.4/Documentation/devicetree/bindings/interconnect/
Dinterconnect.txt5 providers/consumers properties.
8 = interconnect providers =
15 depending on the use case. Interconnect providers can also be interconnect
41 can be multiple interconnect providers on a SoC and the consumer may consume
42 multiple paths from different providers depending on use case and the
Dqcom,msm8939.yaml13 The Qualcomm MSM8937/MSM8939/MSM8976 interconnect providers support
40 The interconnect providers do not have a separate QoS register space,
Dqcom,msm8953.yaml13 The Qualcomm MSM8953 interconnect providers support adjusting the
43 The interconnect providers do not have a separate QoS register space,
Dqcom,qcm2290.yaml13 The Qualcomm QCM2290 interconnect providers support adjusting the
34 The interconnect providers do not have a separate QoS register space,
Dqcom,sm7150-rpmh.yaml13 RPMh interconnect providers support system bandwidth requirements through
42 The interconnect providers do not have a separate QoS register space,
Dqcom,sm6115.yaml13 The Qualcomm SM6115 interconnect providers support adjusting the
39 The interconnect providers do not have a separate QoS register space,
Dqcom,rpm-common.yaml13 RPM interconnect providers support for managing system bandwidth requirements
/linux-6.14.4/Documentation/driver-api/
Dinterconnect.rst56 The interconnect providers on the above diagram are M NoC, S NoC, C NoC, P NoC
62 providers. The point on the diagram where the CPUs connect to the memory is
70 include multiple master-slave pairs across several interconnect providers.
73 by the providers. The consumers send requests to providers requesting various
78 Interconnect providers
Dpwrseq.rst69 To that end the providers fill out a set of configuration structures and
75 The main difference between pwrseq and other Linux kernel providers is the
76 mechanism for dynamic matching of consumers and providers. Every power sequence
Dmiscellaneous.rst30 The PWM framework provides an abstraction for providers and consumers of
32 registered as :c:type:`struct pwm_chip <pwm_chip>`. Providers
/linux-6.14.4/include/linux/
Dhte.h90 * @line_id: The logical ID understood by the consumers and providers.
108 * and subsystem to providers.
119 * struct hte_ops - HTE operations set by providers.
134 * providers and is translated by the provider.
182 /* HTE APIs for the providers */
Dinterconnect-provider.h29 * struct icc_onecell_data - driver data for onecell interconnect providers
46 * @provider_list: list of the registered interconnect providers
/linux-6.14.4/Documentation/driver-api/hte/
Dhte.rst21 engine (HTE) framework. Both consumers and providers must include
24 The HTE framework APIs for the providers
43 consumers and the providers. It expresses timestamp data in nanoseconds in
/linux-6.14.4/drivers/scsi/libfc/
Dfc_libfc.h85 * FC-4 Providers.
87 extern struct fc4_prov *fc_active_prov[]; /* providers without recv */
88 extern struct fc4_prov *fc_passive_prov[]; /* providers with recv */
/linux-6.14.4/tools/kvm/kvm_stat/
Dkvm_stat574 """Encapsulates functionalities used by all providers."""
934 """Manages the data providers and the data they provide.
941 self.providers = self._get_providers(options)
948 """Returns a list of data providers depending on the passed options."""
949 providers = []
952 providers.append(DebugfsProvider(options.pid, options.fields,
954 if options.tracepoints or not providers:
955 providers.append(TracepointProvider(options.pid, options.fields))
957 return providers
960 """Propagates fields filters to providers."""
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/power/
Dpower_domain.txt8 their PM domains provided by PM domain providers. A PM domain provider can be
14 ==PM domain providers==
/linux-6.14.4/Documentation/dev-tools/kunit/api/
Dclk.rst7 The KUnit clk API is used to test clk providers and clk consumers.
/linux-6.14.4/drivers/clk/sophgo/
Dclk-sg2042.h11 * @onecell_data: used for adding providers.
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-pci-devices-catpt15 build hash and log-providers hash. This information is
/linux-6.14.4/Documentation/devicetree/bindings/leds/
Dtrigger-source.yaml7 title: Trigger source providers
/linux-6.14.4/drivers/clk/
Dclk_kunit_helpers.c3 * KUnit helpers for clk providers and consumers
237 MODULE_DESCRIPTION("KUnit helpers for clk providers and consumers");
/linux-6.14.4/Documentation/devicetree/bindings/arm/ux500/
Dpower_domain.txt9 ==PM domain providers==
/linux-6.14.4/drivers/hte/
DKconfig11 providers and consumer devices.
/linux-6.14.4/Documentation/devicetree/bindings/timestamp/
Dhardware-timestamps-common.yaml7 title: Hardware timestamp providers
/linux-6.14.4/Documentation/devicetree/bindings/ata/
Dahci-dm816.txt10 phandles for clock providers with '0' defined for

12345