Searched refs:Client (Results 1 – 25 of 138) sorted by relevance
123456
/linux-6.1.9/tools/testing/selftests/tpm2/ |
D | tpm2_tests.py | 15 self.client = tpm2.Client() 246 space1 = tpm2.Client(tpm2.Client.FLAG_SPACE) 248 space2 = tpm2.Client(tpm2.Client.FLAG_SPACE) 260 space1 = tpm2.Client(tpm2.Client.FLAG_SPACE) 270 space1 = tpm2.Client(tpm2.Client.FLAG_SPACE) 272 space2 = tpm2.Client(tpm2.Client.FLAG_SPACE) 289 space1 = tpm2.Client(tpm2.Client.FLAG_SPACE) 314 async_client = tpm2.Client(tpm2.Client.FLAG_NONBLOCK) 323 async_client = tpm2.Client(tpm2.Client.FLAG_SPACE | tpm2.Client.FLAG_NONBLOCK)
|
D | tpm2.py | 354 class Client: class 363 if (self.flags & Client.FLAG_SPACE) == 0: 368 if (self.flags & Client.FLAG_NONBLOCK): 384 if (self.flags & Client.FLAG_NONBLOCK): 390 if (self.flags & Client.FLAG_NONBLOCK): 393 if (self.flags & Client.FLAG_DEBUG) != 0:
|
/linux-6.1.9/Documentation/driver-api/surface_aggregator/ |
D | client-api.rst | 4 Client Driver API Documentation 32 Client Bus and Client Device API
|
/linux-6.1.9/Documentation/devicetree/bindings/rtc/ |
D | fsl,scu-rtc.yaml | 7 title: i.MX SCU Client Device Node - RTC bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
/linux-6.1.9/Documentation/devicetree/bindings/watchdog/ |
D | fsl,scu-wdt.yaml | 7 title: i.MX SCU Client Device Node - Watchdog bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
/linux-6.1.9/Documentation/devicetree/bindings/thermal/ |
D | fsl,scu-thermal.yaml | 7 title: i.MX SCU Client Device Node - Thermal bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
/linux-6.1.9/Documentation/devicetree/bindings/input/ |
D | fsl,scu-key.yaml | 7 title: i.MX SCU Client Device Node - SCU key bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
/linux-6.1.9/Documentation/devicetree/bindings/power/ |
D | fsl,scu-pd.yaml | 7 title: i.MX SCU Client Device Node - Power domain bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
/linux-6.1.9/Documentation/devicetree/bindings/nvmem/ |
D | fsl,scu-ocotp.yaml | 7 title: i.MX SCU Client Device Node - OCOTP bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
/linux-6.1.9/Documentation/devicetree/bindings/pinctrl/ |
D | fsl,scu-pinctrl.yaml | 7 title: i.MX SCU Client Device Node - Pinctrl bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node. 32 Client device subnodes use below standard properties.
|
D | intel,lgm-io.yaml | 23 # Client device subnode's properties 29 Client device subnodes use below standard properties.
|
D | fsl,imx8ulp-pinctrl.yaml | 23 # Client device subnode's properties 29 Client device subnodes use below standard properties.
|
D | fsl,imxrt1050.yaml | 24 # Client device subnode's properties 30 Client device subnodes use below standard properties.
|
D | fsl,imxrt1170.yaml | 24 # Client device subnode's properties 30 Client device subnodes use below standard properties.
|
D | fsl,imx8mm-pinctrl.yaml | 23 # Client device subnode's properties 29 Client device subnodes use below standard properties.
|
D | fsl,imx8mn-pinctrl.yaml | 23 # Client device subnode's properties 29 Client device subnodes use below standard properties.
|
D | fsl,imx8mp-pinctrl.yaml | 23 # Client device subnode's properties 29 Client device subnodes use below standard properties.
|
D | fsl,imx8mq-pinctrl.yaml | 23 # Client device subnode's properties 29 Client device subnodes use below standard properties.
|
/linux-6.1.9/Documentation/devicetree/bindings/clock/ |
D | fsl,scu-clk.yaml | 7 title: i.MX SCU Client Device Node - Clock bindings based on SCU Message Protocol 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
/linux-6.1.9/drivers/ntb/test/ |
D | Kconfig | 3 tristate "NTB Ping Pong Test Client" 12 tristate "NTB Debugging Tool Test Client" 31 tristate "NTB MSI Test Client"
|
/linux-6.1.9/drivers/block/rnbd/ |
D | README | 29 Client side: 69 2. Client requests to open a device by sending RNBD_MSG_OPEN message. This 75 3. Client attaches RNBD_MSG_IO to each IO message send to a device. This 79 4. Client closes a device by sending RNBD_MSG_CLOSE which contains only the
|
/linux-6.1.9/arch/arm/boot/dts/ |
D | kirkwood-openrd-client.dts | 3 * Marvell OpenRD Client Board Description 16 model = "OpenRD Client";
|
/linux-6.1.9/Documentation/driver-api/mei/ |
D | mei-client-bus.rst | 4 Intel(R) Management Engine (ME) Client bus API 26 A driver implementation for an MEI Client is very similar to any other existing bus 56 To actually register a driver on the ME Client bus one must call the :c:func:`mei_cl_add_driver` 161 MEI Client Bus Drivers
|
D | mei.rst | 17 Each Intel ME feature, or Intel ME Client is addressed by a unique GUID and 84 Connect to firmware Feature/Client. 102 out_client_properties - Client Properties: MTU and Protocol Version. 139 out_client_properties - Client Properties: MTU and Protocol Version.
|
/linux-6.1.9/Documentation/staging/ |
D | tee.rst | 146 The GlobalPlatform TEE Client API [5] is implemented on top of the generic 155 | Client | | Trusted | 165 | Client| || | TEE | OP-TEE | | OP-TEE | 238 | Client | | | Trusted | 250 | Client | | subsystem | driver | | Trusted | 291 The GlobalPlatform TEE Client API [5] can be used by the user space (client) to 307 "TEE Client API Specification v1.0" and click download.
|
123456