Searched +full:sub +full:- +full:message (Results 1 – 25 of 74) sorted by relevance
123
| /Documentation/userspace-api/netlink/ |
| D | netlink-raw.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
8 families such as ``NETLINK_ROUTE`` which use the ``netlink-raw`` protocol
14 The netlink-raw schema extends the :doc:`genetlink-legacy <genetlink-legacy>`
17 information. The raw netlink families also make use of type-specific
18 sub-messages.
21 -------
29 .. code-block:: yaml
31 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
33 name: rt-addr
34 protocol: netlink-raw
[all …]
|
| D | genetlink-legacy.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
9 the ``genetlink-legacy`` protocol level.
15 -------
29 --------------------
31 New Netlink families should use ``multi-attr`` to define arrays.
35 For reference the ``multi-attr`` array may look like this::
37 [ARRAY-ATTR]
41 [SOME-OTHER-ATTR]
42 [ARRAY-ATTR]
47 where ``ARRAY-ATTR`` is the array entry type.
[all …]
|
| D | specs.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
17 - the C uAPI header
18 …- documentation of the protocol as a ReST file - see :ref:`Documentation/networking/netlink_spec/i…
19 - policy tables for input attribute validation
20 - operation tables
25 See :doc:`intro-specs` for a practical starting guide.
28 ``((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)``
40 - ``genetlink`` - most streamlined, should be used by all new families
41 - ``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing
45 - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | srio-rmu.txt | 1 Message unit node:
3 For SRIO controllers that implement the message unit as part of the controller
5 node is composed of three types of sub-nodes ("fsl-srio-msg-unit",
6 "fsl-srio-dbell-unit" and "fsl-srio-port-write-unit").
10 - compatible
13 Definition: Must include "fsl,srio-rmu-vX.Y", "fsl,srio-rmu".
18 - reg
20 Value type: <prop-encoded-array>
22 length of the SRIO configuration registers for message units
25 - fsl,liodn
[all …]
|
| /Documentation/netlink/ |
| D | netlink-raw.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/netlink-raw.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
21 required: [ name, doc, attribute-sets, operations ]
31 enum: [ netlink-raw ] # Trim
32 # Start netlink-raw
34 description: Protocol number to use for netlink-raw
[all …]
|
| D | genetlink-legacy.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
|
| D | genetlink.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
|
| D | genetlink-c.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-c.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | arm,scpi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: System Control and Power Interface (SCPI) Message Protocol
11 - Sudeep Holla <sudeep.holla@arm.com>
15 0922B ("ARM Compute Subsystem SCP: Message Interface Protocols")[0] can be
33 - const: arm,scpi # SCPI v1.0 and above
34 - const: arm,scpi-pre-1.0 # Unversioned SCPI before v1.0
35 - items:
36 - enum:
[all …]
|
| D | arm,scmi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: System Control and Management Interface (SCMI) Message Protocol
11 - Sudeep Holla <sudeep.holla@arm.com>
26 - $ref: /schemas/firmware/nxp,imx95-scmi.yaml
34 - description: SCMI compliant firmware with mailbox transport
36 - const: arm,scmi
37 - description: SCMI compliant firmware with ARM SMC/HVC transport
39 - const: arm,scmi-smc
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-vduse | 6 The vduse/ class sub-directory belongs to the VDUSE
18 What: /sys/class/vduse/<device-name>/
26 What: /sys/class/vduse/<device-name>/msg_timeout
32 message's response from userspace. Default value is 30s.
|
| /Documentation/filesystems/ |
| D | relay.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 to userspace via user-defined 'relay channels'.
11 A 'relay channel' is a kernel->user data relay mechanism implemented
12 as a set of per-cpu kernel buffers ('channel buffers'), each
25 filtering - this also is left to the kernel client. The purpose is to
30 functions in the relay interface code - please see that for details.
36 sub-buffers. Messages are written to the first sub-buffer until it is
37 too full to contain a new message, in which case it is written to
38 the next (if available). Messages are never split across sub-buffers.
40 sub-buffer, while the kernel continues writing to the next.
[all …]
|
| /Documentation/sound/designs/ |
| D | procfile.rst | 15 card-specific files are stored in the ``card*`` subdirectories.
40 ``<card>-<device>: <name>``
44 ``<card>-<device>: <id>: <name> : <sub-streams>``
61 The card-specific files are found in ``/proc/asound/card*`` directories.
81 mapping by writing to this device. Read OSS-Emulation.txt for
109 kernel log when an xrun is detected. The debug message is
123 ``card*/pcm*/sub*/info``
124 The general information of this PCM sub-stream.
126 ``card*/pcm*/sub*/status``
127 The current status of this PCM sub-stream, elapsed time,
[all …]
|
| /Documentation/usb/ |
| D | acm.rst | 23 Temple Place, Suite 330, Boston, MA 02111-1307 USA
25 Should you need to contact me, the author, you can do so either by e-mail -
26 mail your message to <vojtech@suse.cz>, or by paper mail: Vojtech Pavlik,
34 The drivers/usb/class/cdc-acm.c drivers works with USB modems and USB ISDN terminal
40 - 3Com OfficeConnect 56k
41 - 3Com Voice FaxModem Pro
42 - 3Com Sportster
43 - MultiTech MultiModem 56k
44 - Zoom 2986L FaxModem
45 - Compaq 56k FaxModem
[all …]
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
34 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
36 named ``char-misc-next``, you would be using the following command::
38 git tag -s char-misc-4.15-rc1 char-misc-next
40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
41 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
42 (see Documentation/maintainer/configure-git.rst).
57 Anyway, at least to me, the important part is the *message*. I want
[all …]
|
| /Documentation/core-api/ |
| D | netlink.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
13 ---------------
20 Message enums
21 -------------
31 ---------------
36 added whether it replies with a full message or only an ACK is uAPI and
44 ----------
51 ------------------------
54 them - make sure to report dump inconsistency with ``NLM_F_DUMP_INTR``.
65 -------
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | ti,omap-mailbox.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
17 for message storage and interrupt configuration registers.
35 lines can also be routed to different processor sub-systems on DRA7xx as they
49 within a SoC. The sub-mailboxes (actual communication channels) are
56 "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
59 phandle to the intended sub-mailbox child node to be used for communication.
[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/devicetree/bindings/pci/ |
| D | snps,dw-pcie-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
23 Interface - DBI. In accordance with the reference manual the register
24 configuration space belongs to the Configuration-Dependent Module (CDM)
25 and is split up into several sub-parts Standard PCIe configuration
26 space, Port Logic Registers (PL), Shadow Config-space Registers,
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | hisilicon,mbigen-v2.txt | 4 Mbigen means: message based interrupt generator.
6 MBI is kind of msi interrupt only used on Non-PCI devices.
12 Non-pci devices can connect to mbigen and generate the
18 -------------------------------------------
19 - compatible: Should be "hisilicon,mbigen-v2"
21 - reg: Specifies the base physical address and size of the Mbigen
24 Mbigen sub node required properties:
25 ------------------------------------------
26 - interrupt controller: Identifies the node as an interrupt controller
28 - msi-parent: Specifies the MSI controller this mbigen use.
[all …]
|
| /Documentation/crypto/ |
| D | architecture.rst | 5 ----------------------
10 - Symmetric ciphers
12 - AEAD ciphers
14 - Message digest, including keyed message digest
16 - Random number generation
18 - User space interface
21 ---------------------
24 and message digests. In addition, the kernel crypto API provides
26 block ciphers and message digests. Templates include all types of block
29 Single block ciphers and message digests can either be directly used by
[all …]
|
| /Documentation/netlink/specs/ |
| D | tc.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: netlink-raw
12 -
16 -
19 -
23 -
26 -
29 -
32 -
35 -
[all …]
|
| D | nftables.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: netlink-raw
11 -
15 -
16 name: nfgen-family
18 -
21 -
22 name: res-id
23 byte-order: big-endian
25 -
[all …]
|
| /Documentation/process/ |
| D | maintainer-tip.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------------
11 aggregation tree for several sub-maintainer trees. The tip tree gitweb URL
16 - **x86 architecture**
22 x86-specific KVM and XEN patches.
30 mail alias which distributes mails to the x86 top-level maintainer
32 ``linux-kernel@vger.kernel.org``, otherwise your mail ends up only in
35 - **Scheduler**
37 Scheduler development takes place in the -tip tree, in the
38 sched/core branch - with occasional sub-topic trees for
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | cache.rst | 8 dm-cache is a device mapper target written by Joe Thornber, Heinz
15 This device-mapper solution allows us to insert this caching at
17 a thin-provisioning pool. Caching solutions that are integrated more
20 The target reuses the metadata library used in the thin-provisioning
23 The decision as to what data to migrate and when is left to a plug-in
46 Sub-devices
47 -----------
52 1. An origin device - the big, slow one.
54 2. A cache device - the small, fast one.
56 3. A small metadata device - records which blocks are in the cache,
[all …]
|
123