Home
last modified time | relevance | path

Searched +full:send +full:- +full:empty (Results 1 – 25 of 68) sorted by relevance

123

/Documentation/devicetree/bindings/mailbox/
Dapple,mailbox.yaml1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hector Martin <marcan@marcan.st>
11 - Sven Peter <sven@svenpeter.dev>
15 messages between the main CPU and a co-processor. Multiple instances
17 One of the two FIFOs is used to send data to a co-processor while the other
25 - description:
30 - enum:
31 - apple,t8103-asc-mailbox
[all …]
/Documentation/networking/caif/
Dcaif.rst1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| ST-Ericsson AB 2010
40 The use of Start-of-frame-extension (STX) must also be set as
59 /sys/kernel/debug/caif_serial/<tty-name>/
61 * ser_state: Prints the bit-mask status where
63 - 0x02 means SENDING, this is a transient state.
64 - 0x10 means FLOW_OFF_SENT, i.e. the previous frame has not been sent
65 and is blocking further send operation. Flow OFF has been propagated
68 * tty_status: Prints the bit-mask tty status information
70 - 0x01 - tty->warned is on.
[all …]
/Documentation/virt/hyperv/
Dvmbus.rst1 .. SPDX-License-Identifier: GPL-2.0
5 VMBus is a software construct provided by Hyper-V to guest VMs. It
7 devices that Hyper-V presents to guest VMs. The control path is
11 and the synthetic device implementation that is part of Hyper-V, and
12 signaling primitives to allow Hyper-V and the guest to interrupt
17 establishes the VMBus control path with the Hyper-V host, then
21 Most synthetic devices offered by Hyper-V have a corresponding Linux
29 * PCI device pass-thru
34 * Key/Value Pair (KVP) exchange with Hyper-V
35 * Hyper-V online backup (a.k.a. VSS)
[all …]
/Documentation/mhi/
Dmhi.rst1 .. SPDX-License-Identifier: GPL-2.0
26 ----
48 ---------------
64 Event rings: Used by the device to send completion and state transition messages
70 Command rings: Used by the host to send MHI commands to the device. The command
74 --------
82 bidirectional data pipe, which can be used by the upper-layer protocols to
88 --------------
95 [Read Pointer (RP)] ----------->[Ring Element] } TD
96 [Write Pointer (WP)]- [Ring Element]
[all …]
/Documentation/hid/
Duhid.rst2 UHID - User-space I/O driver support for HID subsystem
5 UHID allows user-space to implement HID transport drivers. Please see
6 hid-transport.rst for an introduction into HID transport drivers. This document
9 With UHID, a user-space transport driver can create kernel hid-devices for each
10 device connected to the user-space controlled bus. The UHID API defines the I/O
11 events provided from the kernel to user-space and vice versa.
13 There is an example user-space application in ./samples/uhid/uhid-example.c
16 ------------
18 UHID is accessed through a character misc-device. The minor number is allocated
25 write()'ing "struct uhid_event" objects. Non-blocking operations are supported
[all …]
/Documentation/networking/devlink/
Dmlx5.rst1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 - Validation
18 * - ``enable_roce``
19 - driverinit
20 - Type: Boolean
26 * - ``io_eq_size``
27 - driverinit
[all …]
/Documentation/power/
Dpower_supply_class.rst8 properties to user-space.
60 +--------------------------------------------------------------------------+
61 | **Charge/Energy/Capacity - how to not confuse** |
62 +--------------------------------------------------------------------------+
66 | - `CHARGE_*` |
68 | - `ENERGY_*` |
70 | - `CAPACITY` |
72 +--------------------------------------------------------------------------+
107 "full"/"empty" at normal conditions. Yes, there is no direct relation
125 design charge values, when battery considered full/empty.
[all …]
/Documentation/networking/
Drds.rst1 .. SPDX-License-Identifier: GPL-2.0
14 http://oss.oracle.com/pipermail/rds-devel/2007-November/000228.html
22 cluster - so in a cluster with N processes you need N sockets, in contrast
23 to N*N if you use a connection-oriented socket transport like TCP.
25 RDS is not Infiniband-specific; it was designed to support different
29 The high-level semantics of RDS from the application's point of view are
39 transport has to be IP-based. In fact, RDS over IB uses a
55 Sockets must be bound before you can send or receive data.
59 a active-active HA scenario), but only as long as the address
72 to create RDS sockets. SOL_RDS is the socket-level to be used
[all …]
Dnfc.rst15 - NFC adapters management;
16 - Polling for targets;
17 - Low-level data exchange;
21 responsible for providing an interface to control operations and low-level
26 The low-level data exchange interface is provided by the new socket family
29 .. code-block:: none
31 +--------------------------------------+
33 +--------------------------------------+
35 | low-level | control
39 | +-----------+
[all …]
Dipvs-sysctl.rst1 .. SPDX-License-Identifier: GPL-2.0
4 IPvs-sysctl
10 am_droprate - INTEGER
16 amemthresh - INTEGER
25 backup_only - BOOLEAN
26 - 0 - disabled (default)
27 - not 0 - enabled
32 conn_reuse_mode - INTEGER
33 1 - default
52 conntrack - BOOLEAN
[all …]
Dcan_ucan_protocol.rst5 UCAN is the protocol used by the microcontroller-based USB-CAN
6 adapter that is integrated on System-on-Modules from Theobroma Systems
9 The UCAN protocol has been designed to be hardware-independent.
11 internally. All multi-byte integers are encoded as Little Endian.
44 ------------
51 ``wLength`` * Host to Device - Number of bytes to transmit
52 * Device to Host - Maximum Number of bytes to
53 receive. If the device send less. Common ZLP
58 --------------
64 ---------------
[all …]
Dtimestamping.rst1 .. SPDX-License-Identifier: GPL-2.0
43 -------------------------------------------------------------
59 -------------------------------------------------------------------
72 ----------------------------------------------------------------------
95 (e.g., for sampling) by embedding an send() call within two setsockopt
127 timestamp taken immediately before send() from this timestamp. On
135 Request tx timestamps when all data in the send buffer has been
138 over-report measurement, because the timestamp is generated when all
139 data up to and including the buffer at send() was acknowledged: the
175 queue out of order from the original send() calls. It is not always
[all …]
/Documentation/admin-guide/device-mapper/
Ddm-uevent.rst2 device-mapper uevent
5 The device-mapper uevent code adds the capability to device-mapper to create
6 and send kobject uevents (uevents). Previously device-mapper events were only
9 the event avoiding the need to query the state of the device-mapper device after
12 There are two functions currently for device-mapper events. The first function
24 ------------------------
28 :Value: Name of device-mapper target that generated the event.
31 ------------------------
35 :Value: Device-mapper specific action that caused the uevent action.
36 PATH_FAILED - A path has failed;
[all …]
/Documentation/accel/qaic/
Dqaic.rst1 .. SPDX-License-Identifier: GPL-2.0-only
14 --------------------
20 it, then the device will frequently transition the response FIFO from empty to
21 non-empty and generate MSIs at a rate equivalent to the speed of the
42 ---------------
72 QAIC handles and enforces the required little endianness and 64-bit alignment,
107 This IOCTL allows userspace to send a NNC request to the QSM. The call will
111 This IOCTL allows userspace to allocate a buffer object (BO) which can send
128 call is non-blocking. Success only indicates that the BOs have been queued
143 processed and can be re-queued to the device, or a timeout occurs.
/Documentation/driver-api/nfc/
Dnfc-hci.rst5 - Author: Eric Lapuyade, Samuel Ortiz
6 - Contact: eric.lapuyade@intel.com, samuel.ortiz@intel.com
9 -------
12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core
17 ---
30 - one for executing commands : nfc_hci_msg_tx_work(). Only one command
32 - one for dispatching received events and commands : nfc_hci_msg_rx_work().
35 --------------------------
41 In case the chip supports pre-opened gates and pseudo-static pipes, the driver
45 -------------------
[all …]
/Documentation/driver-api/md/
Dmd-cluster.rst5 The cluster MD is a shared-device RAID for a cluster, it supports
9 1. On-disk format
12 Separate write-intent-bitmaps are used for each cluster node.
14 and may not yet have finished. The on-disk layout is::
17 -------------------------------------------------------------------
26 - set the appropriate bit (if not already set)
27 - commit the write to all mirrors
28 - schedule the bit to be cleared after a timeout.
41 -------------------------------------
53 of sectors that are being re-synced by that node. No other
[all …]
/Documentation/devicetree/bindings/usb/
Dchipidea,usb2-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/chipidea,usb2-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Xu Yang <xu.yang_2@nxp.com>
25 clock-names:
31 power-domains:
37 reset-names:
40 "#reset-cells":
45 itc-setting:
[all …]
/Documentation/userspace-api/media/v4l/
Dvidioc-encoder-cmd.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENCODER_CMD - VIDIOC_TRY_ENCODER_CMD - Execute an encoder command
38 These ioctls control an audio/video (usually MPEG-) encoder.
43 To send a command applications must initialize all fields of a struct
52 the remaining data buffered by the driver. When the buffer is empty,
73 .. flat-table:: struct v4l2_encoder_cmd
74 :header-rows: 0
75 :stub-columns: 0
78 * - __u32
79 - ``cmd``
[all …]
/Documentation/security/tpm/
Dtpm-security.rst1 .. SPDX-License-Identifier: GPL-2.0-only
12 ------------
22 -----------------------------------------------
42 ---------------------------
44 Since the attacker can send their own commands to the TPM, they can
45 send arbitrary PCR extends and thus disrupt the measurement system,
56 the PCRs and then send down their own measurements which would
68 ----------------
77 ---------------------------------------
104 name, which is what is exported via sysfs so user-space can run the
[all …]
/Documentation/sound/designs/
Doss-emulation.rst2 Notes on Kernel OSS-Emulation
13 as add-on kernel modules, snd-pcm-oss, snd-mixer-oss and snd-seq-oss.
18 is called. The alias is defined ``sound-service-x-y``, where x and y are
22 Only necessary step for auto-loading of OSS modules is to define the
25 alias sound-slot-0 snd-emu10k1
27 As the second card, define ``sound-slot-1`` as well.
29 ``alias sound-slot-0 snd-card-0`` doesn't work any more like the old
38 after the corresponding OSS-emulation module is loaded. Don't worry
79 snd-pcm-oss and snd-rawmidi. In the case of PCM, the following
80 options are available for snd-pcm-oss:
[all …]
/Documentation/networking/device_drivers/fddi/
Dskfp.rst1 .. SPDX-License-Identifier: GPL-2.0
6 SysKonnect driver - SKFP
9 |copy| Copyright 1998-2000 SysKonnect,
11 skfp.txt created 11-May-2000
53 - SK-5521 (SK-NET FDDI-UP)
54 - SK-5522 (SK-NET FDDI-UP DAS)
55 - SK-5541 (SK-NET FDDI-FP)
56 - SK-5543 (SK-NET FDDI-LP)
57 - SK-5544 (SK-NET FDDI-LP DAS)
58 - SK-5821 (SK-NET FDDI-UP64)
[all …]
/Documentation/w1/slaves/
Dw1_therm.rst16 -----------
44 send the convert command to all devices on the bus, and if parasite
49 -1 if at least one sensor still in conversion, 1 if conversion is complete
52 may return empty if conversion is still in progress. Note that if a bulk
72 the sensor. Resolution is reset when the sensor gets power-cycled.
81 Some non-genuine DS18B20 chips are fixed in 12-bit mode only, so the actual
86 The write-only sysfs entry ``eeprom_cmd`` is an alternative for EEPROM operations.
94 Values shall be space separated and in the device range (typical -55 degC
106 be force-enabled.
118 location of the chip in the 1-wire bus without needing pre-existing
[all …]
/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
Dcounters.rst1 .. SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
13 - `Overview`_
14 - `Groups`_
15 - `Types`_
16 - `Descriptions`_
27 ----------------------------------------
29 ---------------------------------------- ---------------------------------------- |
32 | ------------------- --------------- | | ------------------- --------------- | |
34 | ------------------- --------------- | | ------------------- --------------- | |
36 | ------------------- | | ------------------- | |
[all …]
/Documentation/driver-api/
Dxillybus.rst10 - Introduction
11 -- Background
12 -- Xillybus Overview
14 - Usage
15 -- User interface
16 -- Synchronization
17 -- Seekable pipes
19 - Internals
20 -- Source code organization
21 -- Pipe attributes
[all …]
/Documentation/scsi/
DChangeLog.megaraid_sas1 Release Date : Thu. Jun 19, 2014 17:00:00 PST 2014 -
2 (emaild-id:megaraidlinux@lsi.com)
7 Current Version : 06.803.02.00-rc1
8 Old Version : 06.803.01.00-rc1
14 -------------------------------------------------------------------------------
15 Release Date : Mon. Mar 10, 2014 17:00:00 PST 2014 -
16 (emaild-id:megaraidlinux@lsi.com)
20 Current Version : 06.803.01.00-rc1
21 Old Version : 06.700.06.00-rc1
25 4. Add Dell PowerEdge VRTX SR-IOV VF device support.
[all …]

123