Searched full:providers (Results 1 – 25 of 61) sorted by relevance
123
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 5 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
|
| D | qcom,msm8939.yaml | 13 The Qualcomm MSM8937/MSM8939/MSM8976 interconnect providers support
40 The interconnect providers do not have a separate QoS register space,
|
| D | qcom,msm8953.yaml | 13 The Qualcomm MSM8953 interconnect providers support adjusting the
43 The interconnect providers do not have a separate QoS register space,
|
| D | qcom,qcm2290.yaml | 13 The Qualcomm QCM2290 interconnect providers support adjusting the
34 The interconnect providers do not have a separate QoS register space,
|
| D | qcom,sm7150-rpmh.yaml | 13 RPMh interconnect providers support system bandwidth requirements through
42 The interconnect providers do not have a separate QoS register space,
|
| D | qcom,sm6115.yaml | 13 The Qualcomm SM6115 interconnect providers support adjusting the
39 The interconnect providers do not have a separate QoS register space,
|
| D | qcom,rpm-common.yaml | 13 RPM interconnect providers support for managing system bandwidth requirements
|
| D | qcom,rpm.yaml | 13 RPM interconnect providers support system bandwidth requirements through
|
| D | qcom,rpmh-common.yaml | 14 RPMh interconnect providers support system bandwidth requirements through
|
| D | qcom,sc8280xp-rpmh.yaml | 14 RPMh interconnect providers support system bandwidth requirements through
|
| D | qcom,msm8974.yaml | 13 The Qualcomm MSM8974 interconnect providers support setting system
|
| D | qcom,sa8775p-rpmh.yaml | 13 RPMh interconnect providers support system bandwidth requirements through
|
| /Documentation/driver-api/ |
| D | interconnect.rst | 56 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
|
| D | miscellaneous.rst | 30 The PWM framework provides an abstraction for providers and consumers of
32 registered as :c:type:`struct pwm_chip <pwm_chip>`. Providers
|
| D | pwrseq.rst | 69 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
|
| /Documentation/driver-api/hte/ |
| D | hte.rst | 21 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
|
| /Documentation/dev-tools/kunit/api/ |
| D | clk.rst | 7 The KUnit clk API is used to test clk providers and clk consumers.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-catpt | 15 build hash and log-providers hash. This information is
|
| /Documentation/devicetree/bindings/leds/ |
| D | trigger-source.yaml | 7 title: Trigger source providers
|
| /Documentation/devicetree/bindings/arm/ux500/ |
| D | power_domain.txt | 9 ==PM domain providers==
|
| /Documentation/devicetree/bindings/ata/ |
| D | ahci-dm816.txt | 10 phandles for clock providers with '0' defined for
|
| /Documentation/devicetree/bindings/timestamp/ |
| D | hardware-timestamps-common.yaml | 7 title: Hardware timestamp providers
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm.yaml | 7 title: PWM controllers (providers)
|
| /Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 8 their PM domains provided by PM domain providers. A PM domain provider can be
14 ==PM domain providers==
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | nvmem-consumer.yaml | 18 List of phandle to the nvmem providers.
|
123