Searched +full:send +full:- +full:not +full:- +full:empty (Results 1 – 25 of 66) sorted by relevance
123
| /Documentation/devicetree/bindings/mailbox/ |
| D | apple,mailbox.yaml | 1 # 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/ |
| D | caif.rst | 1 .. 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/ |
| D | vmbus.rst | 1 .. 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/power/ |
| D | power_supply_class.rst | 8 properties to user-space.
16 power supply, specific monitoring hardware may not be able to provide them
60 +--------------------------------------------------------------------------+
61 | **Charge/Energy/Capacity - how to not confuse** |
62 +--------------------------------------------------------------------------+
66 | - `CHARGE_*` |
68 | - `ENERGY_*` |
70 | - `CAPACITY` |
72 +--------------------------------------------------------------------------+
91 'unknown', if the status is not known).
[all …]
|
| /Documentation/hid/ |
| D | uhid.rst | 2 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/ |
| D | rds.rst | 1 .. 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
38 The fact that IPv4 addresses are used does not mean the underlying
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.
58 does not change. RDS will tolerate IPs moving around (eg in
[all …]
|
| D | ipvs-sysctl.rst | 1 .. 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 …]
|
| D | timestamping.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 Generates a timestamp for each incoming packet in (not necessarily
43 -------------------------------------------------------------
46 path. Because the destination socket, if any, is not known early in
59 -------------------------------------------------------------------
72 ----------------------------------------------------------------------
75 socket option takes a bitmap of flags, not a boolean. In::
80 bit returns EINVAL and does not change the current state.
93 created packets, not to packets already in the stack. As a result, it
95 (e.g., for sampling) by embedding an send() call within two setsockopt
[all …]
|
| D | can_ucan_protocol.rst | 5 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 ------------
49 ``wValue`` Subcommand Number (16 Bit) or 0 if not used
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 --------------
[all …]
|
| D | ip-sysctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 ip_forward - BOOLEAN
11 - 0 - disabled (default)
12 - not 0 - enabled
20 ip_default_ttl - INTEGER
21 Default value of TTL field (Time To Live) for outgoing (but not
25 ip_no_pmtu_disc - INTEGER
27 fragmentation-required ICMP is received, the PMTU to this
38 accept fragmentation-needed errors if the underlying protocol
42 association. This mode should not be enabled globally but is
[all …]
|
| /Documentation/networking/devlink/ |
| D | mlx5.rst | 1 .. 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/mhi/ |
| D | mhi.rst | 1 .. 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/accel/qaic/ |
| D | qaic.rst | 1 .. 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 ---------------
44 MultiMSI is not well supported on all systems; virtualized ones even less so
69 all of the transactions. QAIC does not understand commands (the payload of a
72 QAIC handles and enforces the required little endianness and 64-bit alignment,
73 to the degree that it can. Since QAIC does not know the contents of a
76 The terminate transaction is of particular use to QAIC. QAIC is not aware of
[all …]
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 5 - 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/userspace-api/media/v4l/ |
| D | vidioc-encoder-cmd.rst | 1 .. 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,
57 call sends an implicit START command to the encoder if it has not been
65 These ioctls are optional, not all drivers may support them. They were
73 .. flat-table:: struct v4l2_encoder_cmd
74 :header-rows: 0
75 :stub-columns: 0
[all …]
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 5 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/ |
| D | chipidea,usb2-common.yaml | 1 # 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/networking/device_drivers/fddi/ |
| D | skfp.rst | 1 .. 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/sound/designs/ |
| D | oss-emulation.rst | 2 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
39 even if "NOT ENABLED IN CONFIG" is shown in it.
66 /dev/midi1. They are NOT for OSS but for tclmidi, which is
[all …]
|
| D | seq-oss.rst | 15 What this does - it provides the emulation of the OSS sequencer, access
29 The timer is not selectable by ioctl. The control rate is fixed to
53 However, each MIDI device is exclusive - that is, if a MIDI device
57 * Real-time event processing:
60 ioctl. To switch to real-time mode, send ABSTIME 0 event. The followed
61 events will be processed in real-time without queued. To switch off the
62 real-time mode, send RELTIME 0 event.
74 Run configure script with both sequencer support (``--with-sequencer=yes``)
75 and OSS emulation (``--with-oss=yes``) options. A module ``snd-seq-oss.o``
102 midi 0: [Emu8000 Port-0] ALSA port 65:0
[all …]
|
| /Documentation/w1/slaves/ |
| D | w1_therm.rst | 16 -----------
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
50 but at least one sensor value has not been read yet. Result temperature is
52 may return empty if conversion is still in progress. Note that if a bulk
53 read is sent but one sensor is not read immediately, the next access to
55 time of issue of the bulk read command (not the current temperature).
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.
[all …]
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
13 - `Overview`_
14 - `Groups`_
15 - `Types`_
16 - `Descriptions`_
27 ----------------------------------------
29 ---------------------------------------- ---------------------------------------- |
32 | ------------------- --------------- | | ------------------- --------------- | |
34 | ------------------- --------------- | | ------------------- --------------- | |
36 | ------------------- | | ------------------- | |
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm-security.rst | 1 .. 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 ---------------------------------------
86 either hierarchy would not have some type of authorization.
[all …]
|
| /Documentation/process/ |
| D | submitting-patches.rst | 7 kernel, the process can sometimes be daunting if you're not familiar
13 works, see Documentation/process/development-process.rst. Also, read
14 Documentation/process/submit-checklist.rst
17 Documentation/devicetree/bindings/submitting-patches.rst.
20 If you're unfamiliar with ``git``, you would be well-advised to learn how to
26 :ref:`Documentation/process/maintainer-handbooks.rst <maintainer_handbooks_main>`.
29 ----------------------------
31 If you do not have a repository with the current kernel source handy, use
37 Note, however, that you may not want to develop against the mainline tree
41 the tree is not listed there.
[all …]
|
| /Documentation/driver-api/ |
| D | xillybus.rst | 10 - 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 …]
|
123