Searched full:clients (Results 1 – 25 of 126) sorted by relevance
123456
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,llcc.yaml | 15 that can be shared by multiple clients. Clients here are different cores in the
16 SoC, the idea is to minimize the local caches at the clients and migrate to
18 which are assigned to clients. Clients can query the slice details, activate
|
| /Documentation/admin-guide/nfs/ |
| D | pnfs-scsi-server.rst | 9 also hands out layouts to the clients so that they can directly access the
14 file system must sit on a SCSI LUN that is accessible to the clients in
16 exported LUN, striping or concatenation of LUNs on the MDS and clients
|
| D | pnfs-block-server.rst | 8 to the clients to directly access the underlying block devices that are
14 to the clients in addition to the MDS. As of now the file system needs to
16 volumes on the MDS and clients is not supported yet.
|
| D | nfs-client.rst | 25 NFSv4 requires clients to identify themselves to servers with a unique
41 nfs.nfs4_unique_id stays the same, preventing collision with other clients
45 anything that is believed to be unique across all NFS clients. An
57 clients running in containers.
|
| /Documentation/gpu/ |
| D | tegra.rst | 7 buffer provided directly by the CPU, to its clients via channels. Software,
30 The various host1x clients need to be bound together into a logical device in
35 tree for matching device nodes, adding the required clients to a list. Drivers
36 for individual clients register with the infrastructure as well and are added
39 Once all clients are available, the infrastructure will initialize the logical
41 the subsystem and in turn initialize each of its clients.
43 Similarly, when one of the clients is unregistered, the infrastructure will
45 the subsystem specific bits are torn down and the clients destroyed in turn.
|
| D | drm-uapi.rst | 128 clients no longer require running compositors or graphics servers to
129 make use of a GPU. But the DRM API required unprivileged clients to
131 step and to grant clients GPU access without authenticating, render
132 nodes were introduced. Render nodes solely serve render clients, that
137 clients together with the legacy drmAuth authentication procedure.
143 nodes are designed to avoid the buffer-leaks, which occur if clients
147 clients can use them. Driver authors must be careful not to allow any
152 authenticates clients on the privileged primary/legacy node is no longer
154 granted GPU access. Communication between clients (or servers) is done
156 clients must not use the insecure FLINK interface.
[all …]
|
| D | drm-client.rst | 2 Kernel clients
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-mhi | 10 Users: Any userspace application or clients interested in device info.
21 Users: Any userspace application or clients interested in device info.
|
| /Documentation/devicetree/bindings/dma/ |
| D | moxa,moxart-dma.txt | 23 Clients:
25 DMA clients connected to the MOXA ART DMA controller must use the format
|
| D | atmel-xdma.txt | 27 * DMA clients
28 DMA clients connected to the Atmel XDMA controller must use the format
|
| D | mpc512x-dma.txt | 29 DMA clients must use the format described in dma/dma.txt file.
|
| D | mtk-hsdma.txt | 33 DMA clients must use the format described in dma/dma.txt file.
|
| D | fsl-imx-dma.txt | 32 Clients have to specify the DMA requests with phandles in a list.
|
| D | atmel-dma.txt | 19 DMA clients connected to the Atmel DMA controller must use the format
|
| /Documentation/i2c/ |
| D | dma-considerations.rst | 21 Clients chapter
24 For clients, if you use a DMA safe buffer in i2c_msg, set the I2C_M_DMA_SAFE
29 more and more clients and host drivers is the planned way forward. Note also
|
| /Documentation/ABI/removed/ |
| D | raw1394 | 8 of abstraction that required userspace clients to duplicate much
|
| /Documentation/process/ |
| D | email-clients.rst | 3 Email clients info for Linux
10 email clients. The man page for this is quite good. On the receiving
31 listing recommended email clients should you not already have a preference.
33 Email clients that are used for Linux kernel patches should send the
43 Email clients should not modify the character set encoding of the text.
48 Email clients should generate and maintain "References:" or "In-Reply-To:"
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra186-mc.yaml | 16 handles memory requests for 40-bit virtual addresses from internal clients
115 * Memory clients have access to all 40 bits that the memory
|
| D | nvidia,tegra30-mc.yaml | 18 clock from a group of clients. Typically, a system has a single Arbitration
33 The Tegra30 Memory Controller handles memory requests from internal clients
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 41 clients and providers.
110 that's compatible with all clients using :c:func:`pci_p2pmem_find()`.
111 If more than one provider is supported, the one nearest to all the clients will
|
| /Documentation/translations/zh_CN/process/ |
| D | index.rst | 32 email-clients
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 6 the actual data movements across clients using destination queues. Every
53 - ti,enable-all: Enable all DMA channels vs clients opening specific channels
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra30-actmon.txt | 6 from the monitored clients.
|
| /Documentation/networking/caif/ |
| D | linux_caif.rst | 80 - Clients must call configuration function to add PHY layer.
81 - Clients must implement CAIF layer to consume/produce
83 - Clients must call configuration function to add and connect the
|
| /Documentation/devicetree/bindings/hsi/ |
| D | client-devices.txt | 3 following properties are standardized for HSI clients:
|
123456