Searched full:clients (Results 1 – 25 of 125) sorted by relevance
12345
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,llcc.txt | 4 that can be shared by multiple clients. Clients here are different cores in the
5 SOC, the idea is to minimize the local caches at the clients and migrate to
7 which are assigned to clients. Clients can query the slice details, activate
|
| /Documentation/devicetree/bindings/dma/ |
| D | renesas,rcar-dmac.txt | 4 controller instances named DMAC capable of serving multiple clients. Channels
5 can be dedicated to specific clients or shared between a large number of
6 clients.
10 256 clients in total. When the number of hardware channels is lower than the
11 number of clients to be served, channels must be shared between multiple DMA
12 clients. The association of DMA clients to DMAC channels is fully dynamic and
|
| D | moxa,moxart-dma.txt | 23 Clients:
25 DMA clients connected to the MOXA ART DMA controller must use the format
|
| D | jz4780-dma.txt | 15 DMA clients (see below).
42 DMA clients must use the format described in dma.txt, giving a phandle to the
|
| D | atmel-xdma.txt | 29 * DMA clients
30 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.
|
| /Documentation/filesystems/nfs/ |
| D | pnfs-scsi-server.txt | 8 also hands out layouts to the clients so that they can directly access the
13 file system must sit on a SCSI LUN that is accessible to the clients in
15 exported LUN, striping or concatenation of LUNs on the MDS and clients
|
| D | pnfs-block-server.txt | 6 to the clients to directly access the underlying block devices that are
12 to the clients in addition to the MDS. As of now the file system needs to
14 volumes on the MDS and clients is not supported yet.
|
| D | nfs.txt | 22 NFSv4 requires clients to identify themselves to servers with a unique
38 nfs.nfs4_unique_id stays the same, preventing collision with other clients
42 anything that is believed to be unique across all NFS clients. An
54 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 | 126 clients no longer require running compositors or graphics servers to
127 make use of a GPU. But the DRM API required unprivileged clients to
129 step and to grant clients GPU access without authenticating, render
130 nodes were introduced. Render nodes solely serve render clients, that
135 clients together with the legacy drmAuth authentication procedure.
141 nodes are designed to avoid the buffer-leaks, which occur if clients
145 clients can use them. Driver authors must be careful not to allow any
150 authenticates clients on the privileged primary/legacy node is no longer
152 granted GPU access. Communication between clients (or servers) is done
154 clients must not use the insecure FLINK interface.
[all …]
|
| D | drm-client.rst | 2 Kernel clients
|
| /Documentation/i2c/ |
| D | index.rst | 25 upgrading-clients
26 writing-clients
|
| 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/ |
| D | tee.txt | 45 There are two classes of clients, normal clients and supplicants. The latter is
50 Much of the communication between clients and the TEE is opaque to the
52 clients, forward them to the TEE and send back the results. In the case of
|
| /Documentation/translations/it_IT/process/ |
| D | email-clients.rst | 3 :Original: :ref:`Documentation/process/email-clients.rst <email_clients>`
|
| /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
28 Email clients that are used for Linux kernel patches should send the
38 Email clients should not modify the character set encoding of the text.
43 Email clients should generate and maintain "References:" or "In-Reply-To:"
|
| /Documentation/translations/zh_CN/process/ |
| D | index.rst | 32 email-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/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.txt | 67 - Clients must call configuration function to add PHY layer.
68 - Clients must implement CAIF layer to consume/produce
70 - Clients must call configuration function to add and connect the
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | ingenic,adc.txt | 14 ADC clients must use the format described in iio-bindings.txt, giving
|
12345