Home
last modified time | relevance | path

Searched +full:client +full:- +full:id (Results 1 – 25 of 307) sorted by relevance

12345678910>>...13

/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-bindings.txt4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
9 designated client devices. Again, each client device must be represented as a
12 For a client device to operate correctly, certain pin controllers must
13 set up certain specific pin configurations. Some client devices need a
15 need to reconfigure pins at run-time, for example to tri-state pins when the
16 device is inactive. Hence, each client device can define a set of named
17 states. The number and names of those states is defined by the client device's
21 for client device device tree nodes to map those state names to the pin
24 Note that pin controllers themselves may also be client devices of themselves.
27 in a single place, rather than splitting it across multiple client device
[all …]
Dfsl,scu-pinctrl.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/fsl,scu-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: i.MX SCU Client Device Node - Pinctrl Based on SCU Message Protocol
10 - Dong Aisheng <aisheng.dong@nxp.com>
12 description: i.MX SCU Client Device Node
13 Client nodes are maintained as children of the relevant IMX-SCU device node.
15 (Documentation/devicetree/bindings/pinctrl/fsl,imx-pinctrl.txt)
18 - $ref: pinctrl.yaml#
[all …]
/Documentation/devicetree/bindings/media/
Dmediatek,mdp3-rsz.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-rsz.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
19 - enum:
20 - mediatek,mt8183-mdp3-rsz
21 - items:
22 - enum:
[all …]
Dmediatek,mdp3-wrot.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-wrot.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
19 - enum:
20 - mediatek,mt8183-mdp3-wrot
21 - items:
22 - enum:
[all …]
Dmediatek,mdp3-tdshp.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-tdshp.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MediaTek Media Data Path 3 Two-Dimensional Sharpness
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
14 Two-Dimensional Sharpness (TDSHP) is a Media Profile Path 3 (MDP3) component
20 - mediatek,mt8195-mdp3-tdshp
25 mediatek,gce-client-reg:
[all …]
Dmediatek,mdp3-hdr.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-hdr.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
20 - mediatek,mt8195-mdp3-hdr
25 mediatek,gce-client-reg:
28 such as gce node, subsys id, offset and register size. The subsys id that is
30 include/dt-bindings/gce/<chip>-gce.h of each chips.
[all …]
Dmediatek,mdp3-stitch.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-stitch.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
20 - mediatek,mt8195-mdp3-stitch
25 mediatek,gce-client-reg:
28 such as gce node, subsys id, offset and register size. The subsys id that is
30 include/dt-bindings/gce/<chip>-gce.h of each chips.
[all …]
Dmediatek,mdp3-fg.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-fg.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
20 - mediatek,mt8195-mdp3-fg
25 mediatek,gce-client-reg:
28 such as gce node, subsys id, offset and register size. The subsys id that is
30 include/dt-bindings/gce/<chip>-gce.h of each chips.
[all …]
Dmediatek,mdp3-tcc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-tcc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
21 - mediatek,mt8195-mdp3-tcc
26 mediatek,gce-client-reg:
29 such as gce node, subsys id, offset and register size. The subsys id that is
31 include/dt-bindings/gce/<chip>-gce.h of each chips.
32 $ref: /schemas/types.yaml#/definitions/phandle-array
[all …]
/Documentation/devicetree/bindings/soc/mediatek/
Dmediatek,ccorr.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/mediatek/mediatek,ccorr.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
19 - enum:
20 - mediatek,mt8183-mdp3-ccorr
25 mediatek,gce-client-reg:
26 $ref: /schemas/types.yaml#/definitions/phandle-array
[all …]
Dmediatek,wdma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/mediatek/mediatek,wdma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
20 - enum:
21 - mediatek,mt8183-mdp3-wdma
26 mediatek,gce-client-reg:
27 $ref: /schemas/types.yaml#/definitions/phandle-array
[all …]
/Documentation/driver-api/surface_aggregator/
Dclient.rst1 .. SPDX-License-Identifier: GPL-2.0+
27 Writing Client Drivers
35 client-api
41 Client drivers can be set up in two main ways, depending on how the
45 are non-discoverable and instead need to be explicitly provided by some
49 Non-SSAM Client Drivers
53 representing that EC to the kernel. Drivers targeting a non-SSAM device (and
58 client device and controller (this can also be done separate via
60 that the returned controller is valid for use in the client driver for as
67 .. code-block:: c
[all …]
/Documentation/devicetree/bindings/mailbox/
Dqcom-ipcc.yaml1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mailbox/qcom-ipcc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Technologies, Inc. Inter-Processor Communication Controller
10 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
13 The Inter-Processor Communication Controller (IPCC) is a centralized hardware
14 to route interrupts across various subsystems. It involves a three-level
15 addressing scheme called protocol, client and signal. For example, consider an
18 a case, the client would be Modem (client-id is 2) and the signal would be
[all …]
/Documentation/networking/
Drxrpc.rst1 .. SPDX-License-Identifier: GPL-2.0
7 The RxRPC protocol driver provides a reliable two-phase transport on top of UDP
26 (#) Example client usage.
38 RxRPC is a two-layer protocol. There is a session layer which provides
44 +-------------+
46 +-------------+
48 +-------------+
50 +-------------+
52 +-------------+
60 (2) A two-phase protocol. The client transmits a blob (the request) and then
[all …]
/Documentation/devicetree/bindings/reserved-memory/
Dqcom,rmtfs-mem.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/qcom,rmtfs-mem.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 - Bjorn Andersson <bjorn.andersson@linaro.org>
18 - $ref: reserved-memory.yaml
22 const: qcom,rmtfs-mem
24 qcom,client-id:
27 identifier of the client to use this region for buffers
29 qcom,use-guard-pages:
[all …]
/Documentation/devicetree/bindings/display/mediatek/
Dmediatek,padding.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,padding.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chun-Kuang Hu <chunkuang.hu@kernel.org>
11 - Philipp Zabel <p.zabel@pengutronix.de>
16 width of a layer to be 2-pixel-align, or 4-pixel-align when ETHDR is enabled,
24 - mediatek,mt8188-disp-padding
25 - mediatek,mt8195-mdp3-padding
30 power-domains:
[all …]
Dmediatek,postmask.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,postmask.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chun-Kuang Hu <chunkuang.hu@kernel.org>
11 - Philipp Zabel <p.zabel@pengutronix.de>
24 - enum:
25 - mediatek,mt8192-disp-postmask
26 - items:
27 - enum:
[all …]
Dmediatek,ccorr.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,ccorr.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chun-Kuang Hu <chunkuang.hu@kernel.org>
11 - Philipp Zabel <p.zabel@pengutronix.de>
24 - enum:
25 - mediatek,mt8183-disp-ccorr
26 - mediatek,mt8192-disp-ccorr
27 - items:
[all …]
Dmediatek,dither.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,dither.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chun-Kuang Hu <chunkuang.hu@kernel.org>
11 - Philipp Zabel <p.zabel@pengutronix.de>
25 - enum:
26 - mediatek,mt8183-disp-dither
27 - items:
28 - enum:
[all …]
Dmediatek,wdma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,wdma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chun-Kuang Hu <chunkuang.hu@kernel.org>
11 - Philipp Zabel <p.zabel@pengutronix.de>
24 - enum:
25 - mediatek,mt8173-disp-wdma
26 - items:
27 - const: mediatek,mt6795-disp-wdma
[all …]
/Documentation/filesystems/nfs/
Dclient-identifier.rst1 .. SPDX-License-Identifier: GPL-2.0
4 NFSv4 client identifier
7 This document explains how the NFSv4 protocol identifies client
10 on each client. These can be set by administrators, scripts
14 There are risks if a client's NFSv4 identifier and its principal
19 ------------
21 The NFSv4 protocol uses "lease-based file locking". Leases help
25 Simply put, an NFSv4 server creates a lease for each NFSv4 client.
26 The server collects each client's file open and lock state under
27 the lease for that client.
[all …]
/Documentation/devicetree/bindings/display/tegra/
Dnvidia,tegra20-dc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-dc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
15 pattern: "^dc@[0-9a-f]+$"
19 - enum:
20 - nvidia,tegra20-dc
21 - nvidia,tegra30-dc
[all …]
/Documentation/devicetree/bindings/clock/
Dfsl,scu-clk.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/fsl,scu-clk.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: i.MX SCU Client Device Node - Clock Controller Based on SCU Message Protocol
10 - Abel Vesa <abel.vesa@nxp.com>
12 description: i.MX SCU Client Device Node
13 Client nodes are maintained as children of the relevant IMX-SCU device node.
15 (Documentation/devicetree/bindings/clock/clock-bindings.txt)
17 ID in its "clocks" phandle cell. See the full list of clock IDs from
[all …]
/Documentation/devicetree/bindings/rtc/
Dfsl,scu-rtc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/rtc/fsl,scu-rtc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: i.MX SCU Client Device Node - RTC Based on SCU Message Protocol
10 - Dong Aisheng <aisheng.dong@nxp.com>
12 description: i.MX SCU Client Device Node
13 Client nodes are maintained as children of the relevant IMX-SCU device node.
16 - $ref: rtc.yaml#
20 const: fsl,imx8qxp-sc-rtc
[all …]
/Documentation/gpu/amdgpu/
Ddebugging.rst11 `vm_fault_stop` - If non-0, halt the GPU memory controller on a GPU page fault.
13 `vm_update_mode` - If non-0, use the CPU to update GPU page tables rather than
26 …[gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32777, for process glxinfo pid 2424 t…
27 in page starting at address 0x0000800102800000 from IH client 0x1b (UTCL2)
29 Faulty UTCL2 client ID: TCP (0x8)
38 memory hub used for multi-media and sdma on some chips.
41 caused by the kernel driver or firmware. If the vmid is non-0, it is generally
43 process id. If the process is active when the fault happens, the process
48 The client ID indicates the GPU block that caused the fault.
49 Some common client IDs:
[all …]

12345678910>>...13