Searched full:provider (Results 1 – 25 of 141) sorted by relevance
123456
| /Documentation/driver-api/ |
| D | pwrseq.rst | 17 exposed by the power sequence provider and delegate the actual requesting and
18 control of the underlying resources as well as to allow the provider to
44 entry point to the provider layer. It ensures coherence between different
59 Provider interface
62 The provider API is admittedly not nearly as straightforward as the one for
65 Each provider can logically split the power-up sequence into descrete chunks
77 provider driver must implement the `match()` callback and pass it to the pwrseq
81 every registered provider and let it flexibly figure out whether the proposed
82 client device is indeed its consumer. For example: if the provider binds to the
84 consumer driver controls one of its modules, the provider driver may parse the
[all …]
|
| D | interconnect.rst | 55 Interconnect provider is the software definition of the interconnect hardware.
60 port. Each interconnect provider consists of multiple interconnect nodes,
63 called an interconnect node, which belongs to the Mem NoC interconnect provider.
81 Interconnect provider is an entity that implements methods to initialize and
82 configure interconnect bus hardware. The interconnect provider drivers should
83 be registered with the interconnect provider core.
85 .. kernel-doc:: include/linux/interconnect-provider.h
111 same provider as subgraphs. The format is human-readable and can also be piped
|
| /Documentation/ABI/testing/ |
| D | configfs-tsm | 17 where the implementation is conveyed via the @provider
29 When @provider is "sev_guest" this file contains the
46 What: /sys/kernel/config/tsm/report/$name/provider
81 (WO) Attribute is visible if a TSM implementation provider
101 (WO) Attribute is visible if a TSM implementation provider
103 provider for TVMs, like SEV-SNP running under an SVSM.
104 Specifying the service provider via this attribute will create
105 an attestation report as specified by the service provider.
106 The only currently supported service provider is "svsm".
108 For the "svsm" service provider, see the Secure VM Service Module
[all …]
|
| D | sysfs-bus-nvdimm | 37 listing of the events supported by a given nvdimm provider type
38 can be found in Documentation/driver-api/nvdimm/$provider.
53 What: /sys/bus/nd/devices/nmemX/cxl/provider
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 36 * Provider - A driver which provides or publishes P2P resources like
44 it may be typical for a driver to be both a provider and a client).
48 * The NVMe PCI driver is both a client, provider and orchestrator
50 resource (provider), it accepts P2P memory pages as buffers in requests
61 memory behind it, its driver could add support as a P2P provider and
66 Provider Drivers
69 A provider simply needs to register a BAR (or a portion of a BAR)
98 a specific P2P provider to use it may check compatibility using
99 :c:func:`pci_p2pdma_distance()` otherwise it may find a memory provider
101 If more than one provider is supported, the one nearest to all the clients will
[all …]
|
| /Documentation/driver-api/hte/ |
| D | hte.rst | 20 engine provider and consumer drivers that want to use the hardware timestamping
50 - Stores GPIO raw level in raw_level variable if the provider has that
61 ``/sys/kernel/debug/hte/<provider>/<label or line id>/``. Note that these
65 The total number of entities requested from the given provider,
66 where entity is specified by the provider and could represent
69 ``/sys/kernel/debug/hte/<provider>/``.
72 The total number of entities supported by the provider.
74 ``/sys/kernel/debug/hte/<provider>/``.
79 ``/sys/kernel/debug/hte/<provider>/<label or line id>/``.
|
| D | tegra-hte.rst | 3 HTE Kernel provider driver
8 The Nvidia tegra HTE provider also known as GTE (Generic Timestamping Engine)
40 one-to-one mapping with IRQ GTE provider, consumers can simply specify the IRQ
44 The provider source code of both IRQ and GPIO GTE instances is located at
|
| /Documentation/devicetree/bindings/power/ |
| D | power-domain.yaml | 21 their PM domains provided by PM domain providers. A PM domain provider can be
23 domains. A consumer node can refer to the provider by a phandle and a set of
25 \#power-domain-cells property in the PM domain provider node.
37 power-domain provider. The idle state definitions are compatible with the
49 performance, provided by a power domain provider. If the provider provides
51 provider have identical OPP tables, then this shall contain a single
59 by device tree binding documentation of particular provider.
68 by the given provider should be subdomains of the domain specified
84 // The node above defines a power controller that is a PM domain provider and
|
| D | power_domain.txt | 8 their PM domains provided by PM domain providers. A PM domain provider can be
10 domains. A consumer node can refer to the provider by a phandle and a set of
12 #power-domain-cells property in the PM domain provider node.
22 the power controller that is the PM domain provider.
63 - OPP table for domain provider that provides two domains.
|
| /Documentation/devicetree/bindings/dvfs/ |
| D | performance-domain.yaml | 26 providers. A performance domain provider can be represented by any node in
28 node can refer to the provider by a phandle and a set of phandle arguments
30 \#performance-domain-cells property in the performance domain provider node.
41 provider.
48 performance controller/provider specified by phandle.
67 // domain provider and expects one cell as its phandle argument.
|
| /Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 9 a reset provider (e.g. power management or clock module) and received by a
11 ordinate module is reset). This binding exists to represent the provider and
14 A reset signal is represented by the phandle of the provider, plus a reset
16 provider. The length (number of cells) and semantics of the reset specifier
17 are dictated by the binding of the reset provider, although common schemes
50 device manages. Note: if the reset provider specifies '0' for
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 1 Interconnect Provider Device Tree Bindings
10 The interconnect provider binding is intended to represent the interconnect
11 controllers in the system. Each provider registers a set of interconnect
20 - compatible : contains the interconnect provider compatible string
46 interconnects : Pairs of phandles and interconnect provider specifier to denote
|
| D | qcom,rpmh-common.yaml | 15 RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
17 associated with each execution environment. Provider nodes must point to at
18 least one RPMh device child node pertaining to their RSC and each provider
|
| D | qcom,qdu1000-rpmh.yaml | 15 RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
17 associated with each execution environment. Provider nodes must point to at
18 least one RPMh device child node pertaining to their RSC and each provider
|
| D | qcom,sdx75-rpmh.yaml | 14 RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
16 associated with each execution environment. Provider nodes must point to at
17 least one RPMh device child node pertaining to their RSC and each provider
|
| D | qcom,x1e80100-rpmh.yaml | 15 RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
17 associated with each execution environment. Provider nodes must point to at
18 least one RPMh device child node pertaining to their RSC and each provider
|
| /Documentation/translations/zh_CN/driver-api/phy/ |
| D | phy.rst | 31 注册/注销PHY provider
34 PHY provider是指实现一个或多个 PHY 实例的实体。对于 PHY provider 仅
36 的 of_xlate 实现。如果 PHY provider 实现多个实例，则应提供其自己的
50 启动情况，所有 PHY provider 都应使用上述两个宏之一来注册 PHY provider。
52 与 PHY provider 关联的设备树节点通常包含一组子节点，每个子节点代表一个
185 （PHY provider 设备）的设备的子设备。
188 调用 PHY provider 设备的 pm_runtime_get_sync。还应注意，
|
| /Documentation/devicetree/bindings/timestamp/ |
| D | hte-consumer.yaml | 18 The list of HTE provider phandle. The first cell must represent the
19 provider phandle followed by the line identifiers. The meaning of the
21 HTE provider device tree binding document.
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | nvmem-provider.yaml | 4 $id: http://devicetree.org/schemas/nvmem/nvmem-provider.yaml#
7 title: NVMEM (Non Volatile Memory) Provider
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-pwrseq-simple.yaml | 7 title: Simple MMC power sequence provider
13 The purpose of the simple MMC power sequence provider is to supports a set
15 the same provider for several SOC designs.
|
| /Documentation/devicetree/bindings/access-controllers/ |
| D | access-controllers.yaml | 23 is a consumer and the access controller is the provider.
27 of the consumer device. A consumer node can refer to the provider by phandle
46 of a particular provider. The node is an access controller.
59 bindings of the access-controllers provider.
|
| /Documentation/driver-api/phy/ |
| D | phy.rst | 28 Registering/Unregistering the PHY provider
31 PHY provider refers to an entity that implements one or more PHY instances.
32 For the simple case where the PHY provider implements only a single instance of
34 of_phy_simple_xlate. If the PHY provider implements multiple instances, it
50 2 macros to register the PHY provider.
52 Often the device tree nodes associated with a PHY provider will contain a set
93 Inorder to dereference the private data (in phy_ops), the phy provider driver
194 phy_create (PHY provider device).
197 pm_runtime_get_sync of PHY provider device because of parent-child relationship.
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt8195-mt6359.yaml | 114 mediatek,clk-provider:
156 mediatek,clk-provider = "cpu";
161 mediatek,clk-provider = "cpu";
169 mediatek,clk-provider = "cpu";
177 mediatek,clk-provider = "cpu";
|
| D | fsl,sgtl5000.yaml | 31 - description: the clock provider of SYS_MCLK
34 description: the regulator provider of VDDA
37 description: the regulator provider of VDDIO
40 description: the regulator provider of VDDD
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-bindings.txt | 10 provider can use the values in cells to find the appropriate
29 That node describes an IP block (PHY provider) that implements 2 different PHYs.
70 This node represents a controller that uses one of the PHYs of the PHY provider
|
123456