Searched full:client (Results 1 – 25 of 514) sorted by relevance
12345678910>>...21
| /Documentation/filesystems/nfs/ |
| D | client-identifier.rst | 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
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.
29 The client is responsible for periodically renewing its leases.
31 guarantees the file locks the client has created remain in place.
33 If a client stops renewing its lease (for example, if it crashes),
[all …]
|
| /Documentation/driver-api/mei/ |
| D | mei.rst | 17 Each Intel ME feature, or Intel ME Client is addressed by a unique GUID and
18 each client has its own protocol. The protocol is message-based with a
19 header and payload up to maximal number of bytes advertised by the client,
43 A code snippet for an application communicating with Intel AMTHI client:
48 virtual channels such client with answer EOPNOTSUPP.
84 Connect to firmware Feature/Client.
102 out_client_properties - Client Properties: MTU and Protocol Version.
106 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
109 ENOMEM Unable to allocate memory to client internal data.
114 max_msg_length (MTU) in client properties describes the maximum
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 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
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
30 bindings for the individual client devices in use by that board, i.e. whether
33 == Pinctrl client devices ==
[all …]
|
| D | fsl,scu-pinctrl.yaml | 7 title: i.MX SCU Client Device Node - Pinctrl 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.
31 Pinctrl node's client devices use subnodes for desired pin configuration.
32 Client device subnodes use below standard properties.
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-g-client-cap.rst | 13 VIDIOC_SUBDEV_G_CLIENT_CAP - VIDIOC_SUBDEV_S_CLIENT_CAP - Get or set client
39 These ioctls are used to get and set the client (the application using the
40 subdevice ioctls) capabilities. The client capabilities are stored in the file
41 handle of the opened subdev device node, and the client must set the
44 By default no client capabilities are set when a subdev device node is opened.
46 The purpose of the client capabilities are to inform the kernel of the behavior
47 of the client, mainly related to maintaining compatibility with different
50 The ``VIDIOC_SUBDEV_G_CLIENT_CAP`` ioctl returns the current client capabilities
53 The ``VIDIOC_SUBDEV_S_CLIENT_CAP`` ioctl sets client capabilities for the file
64 .. flat-table:: Client Capabilities
[all …]
|
| D | dev-decoder.rst | 12 from the client to process these buffers.
56 client
84 ``OUTPUT`` buffers must be queued by the client in decode order; for
92 buffers must be queued by the client in display order; for decoders,
218 client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.
227 2. To enumerate the set of supported raw formats, the client may call
234 the client must first set that coded format on ``OUTPUT`` and then
237 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
291 event, regardless of whether they match the values set by the client or
298 and the client must ensure it matches its needs afterwards.
[all …]
|
| D | dev-stateless-decoder.rst | 11 of any previous and future frames, and that the client is responsible for
14 where the hardware and driver maintain the decoding state and all the client
18 This section describes how user-space ("the client") is expected to communicate
20 Compared to stateful codecs, the decoder/client sequence is simpler, but the
21 cost of this simplicity is extra complexity in the client which is responsible
38 1. To enumerate the set of coded formats supported by the decoder, the client
48 2. To enumerate the set of supported raw formats, the client calls
56 The client is responsible for making sure that these controls are set
59 that may not be usable for the media the client is trying to decode.
61 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
[all …]
|
| D | dev-encoder.rst | 12 further post-processing by the client.
88 client may call :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.
93 2. To enumerate the set of supported raw formats, the client may call
100 the client must first set that coded format on ``CAPTURE`` and then
103 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
116 4. The client may use :c:func:`VIDIOC_ENUM_FRAMEINTERVALS` to detect supported
179 and the client must ensure it matches its needs afterwards.
366 size. To avoid encoding the padding, the client needs to explicitly
372 supported ones to meet codec and hardware requirements. The client needs
398 given. The client must check the updated value of ``count`` after the
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rtrs-client | 1 What: /sys/class/rtrs-client
6 the name of that session is created under /sys/class/rtrs-client/<session-name>/
8 What: /sys/class/rtrs-client/<session-name>/add_path
18 What: /sys/class/rtrs-client/<session-name>/max_reconnect_attempts
22 Description: Maximum number reconnect attempts the client should make before giving up
25 What: /sys/class/rtrs-client/<session-name>/mp_policy
40 What: /sys/class/rtrs-client/<session-name>/paths/
48 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/state
55 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/reconnect
62 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/disconnect
[all …]
|
| D | sysfs-class-rnbd-client | 1 What: /sys/class/rnbd-client
5 Description: Provide information about RNBD-client.
10 # cat /sys/class/rnbd-client/ctl/map_device
18 What: /sys/class/rnbd-client/ctl/map_device
33 a given session on the client and on the server.
37 describes a connection between the client and the server by
50 The connection will be established to this server from any client IP address.
66 The rnbd_server prepends the <device_path> received from client
70 directory and an entry in /sys/class/rnbd-client/ctl/devices
76 client has this string "sessname=blya device_path=sda", then server
[all …]
|
| D | sysfs-bus-mei | 13 Description: Stores mei client device name
20 Description: Stores mei client device uuid
27 Description: Stores mei client protocol version
34 Description: Stores mei client maximum number of connections
41 Description: Stores mei client fixed address, if any
48 Description: Stores mei client vtag support status
55 Description: Stores mei client maximum message length
|
| /Documentation/i2c/ |
| D | writing-clients.rst | 29 provide. A client structure holds device-specific information like the
70 Extra client data
73 Each client structure has a special ``data`` field that can point to any
79 void i2c_set_clientdata(struct i2c_client *client, void *data);
82 void *i2c_get_clientdata(const struct i2c_client *client);
90 Accessing the client
93 Let's say we have a valid client structure. At some time, we will need
94 to gather information from the client, or write new information to the
95 client.
105 int foo_read_value(struct i2c_client *client, u8 reg)
[all …]
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-rdma.rst | 14 This document describes how to install and setup the Linux NFS/RDMA client
17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
21 wire bandwidth at minimal client CPU) under many workloads. The code passes
46 The first kernel release to contain both the NFS/RDMA client and server was
53 - Install nfs-utils-1.1.2 or greater on the client
101 on the NFS client machine. You do not need this specific version of
103 nfs-utils-1.1.2 is needed on the client.
107 The NFS/RDMA client and server are both included in the mainline Linux
125 - Configure the NFS client and server
134 are turned on. The NFS/RDMA client and server are configured via the hidden
[all …]
|
| D | nfs-client.rst | 2 NFS Client
5 The NFS client
13 The Linux NFS client currently supports all the above published versions,
18 special features of the NFS client that can be configured by system
26 string. File open and lock state shared between one client and one server
29 across client reboots.
31 Without any other intervention, the Linux client uses a string that contains
34 over the lifetime of a client system. Node names can have other
39 used together with a system's node name when an NFS client identifies itself to
45 nfs4_unique_id string should be chosen when a client system is installed,
[all …]
|
| D | pnfs-block-server.rst | 9 shared with the client.
19 support it. On the client make sure the kernel has the CONFIG_PNFS_BLOCK
23 If the nfsd server needs to fence a non-responding client it calls
25 the client, and the second argument set to the device node without the /dev
35 CLIENT="$1"
41 echo "fencing client ${CLIENT} serial ${EVPD}" >> /var/log/pnfsd-fence.log
|
| D | nfsroot.rst | 24 of this text 'client' means the diskless system, and 'server' means the NFS
33 In order to use nfsroot, NFS client support needs to be selected as
70 replaced by the ASCII-representation of the client's
88 ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<nt…
106 <client-ip> IP address of the client.
111 the client address and this parameter is NOT empty only
128 If unspecified the netmask is derived from the client IP address
133 <hostname> Name of the client.
135 before the first '.' is used as the client's hostname, and anything
140 may cause a DNS record to be created or updated for the client.
[all …]
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra20-dc.yaml | 95 - description: window A memory client
96 - description: window B memory client
97 - description: window B memory client (vertical filter)
98 - description: window C memory client
99 - description: cursor memory client
141 - description: window A memory client
142 - description: window B memory client
143 - description: window C memory client
144 - description: cursor memory client
145 - description: window D memory client
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | mailbox.txt | 1 * Generic Mailbox Controller and client driver bindings
4 assign appropriate mailbox channel to client drivers.
19 * Mailbox Client
29 communication between the mailbox client and the remote.
50 compatible = "client-shmem";
55 client@2e000000 {
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | index.rst | 4 Client Driver Documentation
7 This is the documentation for client drivers themselves. Refer to
8 Documentation/driver-api/surface_aggregator/client.rst for documentation
9 on how to write client drivers.
|
| D | san.rst | 21 The public interface of this driver is split into two parts: Client
24 A client to the SAN interface can be linked as consumer to the SAN device
25 via |san_client_link|. This can be used to ensure that the a client
27 being set up as this forces the client driver to unbind once the SAN driver
31 loaded, regardless of being linked as client or not. Registration is done
|
| /Documentation/devicetree/bindings/hsi/ |
| D | nokia-modem.txt | 1 Nokia modem client bindings
3 The Nokia modem HSI client follows the common HSI client binding
5 properties are needed by the Nokia modem HSI client:
30 modem: hsi-client {
|
| /Documentation/devicetree/bindings/media/ |
| D | mediatek,mdp3-rsz.yaml | 25 mediatek,gce-client-reg:
33 description: The register of client driver can be configured by gce with
35 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
50 - mediatek,gce-client-reg
64 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0x3000 0x1000>;
73 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0x4000 0x1000>;
|
| /Documentation/driver-api/surface_aggregator/ |
| D | client.rst | 27 Writing Client Drivers
35 client-api
41 Client drivers can be set up in two main ways, depending on how the
49 Non-SSAM Client Drivers
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
94 means, it should be provided as |ssam_device| via the SSAM client device
104 necessary, by use of |ssam_client_link| as is done for non-SSAM client
107 A client device must always be removed by the party which added the
111 unbinds. Client devices registered with the controller as parent are
[all …]
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | mediatek,ccorr.yaml | 25 mediatek,gce-client-reg:
33 description: The register of client driver can be configured by gce with
35 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
50 - mediatek,gce-client-reg
64 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0xc000 0x1000>;
|
| /Documentation/driver-api/ |
| D | ntb.rst | 22 hardware drivers. The term "client" is used here to mean an upper layer
26 NTB Client Drivers
29 NTB client drivers should register with the NTB core driver. After
30 registering, the client probe and remove functions will be called appropriately
35 NTB Typical client driver implementation
123 NTB Transport Client (ntb\_transport) and NTB Netdev (ntb\_netdev)
126 The primary client for NTB is the Transport client, used in tandem with NTB
128 across the ntb, to exchange packets of network data. The Transport client
132 Transport queue pair buffer. The Transport client may be used for other things
135 NTB Ping Pong Test Client (ntb\_pingpong)
[all …]
|
12345678910>>...21