Home
last modified time | relevance | path

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

12345678

/Documentation/devicetree/bindings/
D.yamllint4 quoted-strings:
5 required: only-when-needed
6 extra-allowed:
7 - '[$^,[]'
8 - '^/$'
9 line-length:
12 allow-non-breakable-words: true
15 min-spaces-inside: 0
16 max-spaces-inside: 1
17 min-spaces-inside-empty: 0
[all …]
/Documentation/devicetree/bindings/iio/multiplexer/
Dio-channel-mux.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/iio/multiplexer/io-channel-mux.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Rosin <peda@axentia.se>
16 For each non-empty string in the channels property, an io-channel will be
17 created. The number of this io-channel is the same as the index into the list
20 Documentation/devicetree/bindings/mux/mux-controller.yaml
25 const: io-channel-mux
27 io-channels:
[all …]
/Documentation/block/
Dwriteback_cache_control.rst6 ------------
10 operating system before data actually has hit the non-volatile storage. This
12 system needs to force data out to the non-volatile storage when it performs
21 ----------------------
26 guarantees that previously completed write requests are on non-volatile
28 set on an otherwise empty bio structure, which causes only an explicit cache
34 ------------------
38 signaled after the data has been committed to non-volatile storage.
42 --------------------------------------
50 ----------------------------------
[all …]
/Documentation/networking/device_drivers/ethernet/toshiba/
Dspider_net.rst1 .. SPDX-License-Identifier: GPL-2.0
28 There are three primary states that a descriptor can be in: "empty",
29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
31 and is waiting to be emptied and processed by the OS. A "not-in-use"
32 descriptor is neither empty or full; it is simply not ready. It may
37 buffers. These are all marked "empty", ready to receive data. This
40 buffers, processing them, and re-marking them empty.
48 and everything in front of it should be "empty". If the hardware
49 discovers that the current descr is not empty, it will signal an
54 descr. The OS will process this descr, and then mark it "not-in-use",
[all …]
/Documentation/ABI/testing/
Dsysfs-class-led-trigger-oneshot4 Contact: linux-leds@vger.kernel.org
13 Contact: linux-leds@vger.kernel.org
22 Contact: linux-leds@vger.kernel.org
33 Contact: linux-leds@vger.kernel.org
35 Write any non-empty string to signal an events, this starts a
Dsysfs-bus-wmi11 driver_override file (echo wmi-event-dummy > driver_override).
12 The override may be cleared with an empty string (echo > \
20 This also allows devices to opt-out of driver binding using a
31 Format: wmi:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
47 the ACPI method names used by non-event WMI devices. It contains
62 present on a given WMI device. It contains a non-negative
/Documentation/arch/x86/i386/
DIO-APIC.rst1 .. SPDX-License-Identifier: GPL-2.0
4 IO-APIC
9 Most (all) Intel-MP compliant SMP boards have the so-called 'IO-APIC',
12 IO-APIC, interrupts from hardware will be delivered only to the
16 multiple IO-APICs. Multiple IO-APICs are used in high-end servers to
20 usually worked around by the kernel. If your MP-compliant SMP board does
21 not boot Linux, then consult the linux-smp mailing list archives first.
23 If your box boots fine with enabled IO-APIC IRQs, then your
28 0: 1360293 IO-APIC-edge timer
29 1: 4 IO-APIC-edge keyboard
[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
68 * tty_status: Prints the bit-mask tty status information
70 - 0x01 - tty->warned is on.
71 - 0x04 - tty->packed is on.
[all …]
/Documentation/filesystems/
Dautofs.rst2 autofs - how it works
8 The goal of autofs is to provide on-demand mounting and race free
17 media with a media-changing robot.
23 filesystem can even be programmatic rather than database-backed,
31 There also needs to be a user-space program which looks up names
35 required with any user-space program. Subsequent text refers to this
60 empty and a regular directory when not empty. Note that *direct* and
63 and the root is empty.
66 filesystem is mounted *indirect* and they are empty.
73 precisely when they are empty.
[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 +--------------------------------------------------------------------------+
95 to the platform is authentic(1) or non authentic(0).
107 "full"/"empty" at normal conditions. Yes, there is no direct relation
[all …]
/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic.txt14 - compatible
22 - reg
24 Value type: <prop-encoded-array>
29 - interrupt-controller
31 Value type: <empty>
35 - #interrupt-cells
39 specifiers do not contain the interrupt-type or type-specific
42 - #address-cells
47 - pic-no-reset
49 Value type: <empty>
[all …]
/Documentation/userspace-api/media/v4l/
Dvidioc-qbuf.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_QBUF - VIDIOC_DQBUF - Exchange a buffer with the driver
38 Applications call the ``VIDIOC_QBUF`` ioctl to enqueue an empty
58 :ref:`multi-planar API <planar-apis>`, the ``m.planes`` field must
59 contain a userspace pointer to a filled-in array of struct
73 multi-planar API is used, ``m.userptr`` and ``length`` members of the
87 file descriptor associated with a DMABUF buffer. When the multi-planar
102 the file descriptor of a :ref:`request <media-request-api>`, if requests are
119 For :ref:`memory-to-memory devices <mem2mem>` you can specify the
130 non-critical (recoverable) streaming error. In such case the application
[all …]
/Documentation/tools/rv/
DMakefile1 # SPDX-License-Identifier: GPL-2.0-only
4 RM ?= rm -f
5 RMDIR ?= rmdir --ignore-fail-on-non-empty
16 RST2MAN_DEP := $(shell command -v rst2man 2>/dev/null)
17 RST2MAN_OPTS += --verbose
19 TEST_RST2MAN = $(shell sh -c "rst2man --version > /dev/null 2>&1 || echo n")
27 $(info ** distribution, e.g., 'dnf install python3-docutils' on Fedora,)
44 $(INSTALL) -d -m 755 $(DESTDIR)$(MAN1DIR)
45 $(INSTALL) -m 644 $(DOC_MAN1) $(DESTDIR)$(MAN1DIR)
/Documentation/tools/rtla/
DMakefile1 # SPDX-License-Identifier: GPL-2.0-only
5 RM ?= rm -f
6 RMDIR ?= rmdir --ignore-fail-on-non-empty
17 RST2MAN_DEP := $(shell command -v rst2man 2>/dev/null)
18 RST2MAN_OPTS += --verbose
20 TEST_RST2MAN = $(shell sh -c "rst2man --version > /dev/null 2>&1 || echo n")
28 $(info ** distribution, e.g., 'dnf install python3-docutils' on Fedora,)
45 $(INSTALL) -d -m 755 $(DESTDIR)$(MAN1DIR)
46 $(INSTALL) -m 644 $(DOC_MAN1) $(DESTDIR)$(MAN1DIR)
/Documentation/admin-guide/
Dcgroup-v2.rst1 .. _cgroup-v2:
11 conventions of cgroup v2. It describes all userland-visible aspects
14 v1 is available under :ref:`Documentation/admin-guide/cgroup-v1/index.rst <cgroup-v1>`.
19 1-1. Terminology
20 1-2. What is cgroup?
22 2-1. Mounting
23 2-2. Organizing Processes and Threads
24 2-2-1. Processes
25 2-2-2. Threads
26 2-3. [Un]populated Notification
[all …]
/Documentation/devicetree/bindings/gpio/
D8xxx_gpio.txt3 This is for the non-QE/CPM/GUTs GPIO controllers as found on
6 Every GPIO controller node must have #gpio-cells property defined,
7 this information will be used to translate gpio-specifiers.
12 controller, see bindings/interrupt-controller/interrupts.txt (the
18 nodes section in bindings/interrupt-controller/interrupts.txt for
22 - compatible: "fsl,<chip>-gpio" followed by "fsl,mpc8349-gpio"
23 for 83xx, "fsl,mpc8572-gpio" for 85xx, or
24 "fsl,mpc8610-gpio" for 86xx.
25 - #gpio-cells: Should be two. The first cell is the pin number
28 - interrupts: Interrupt mapping for GPIO IRQ.
[all …]
/Documentation/input/joydev/
Djoystick-api.rst1 .. _joystick-api:
7 :Author: Ragnar Hojland Espinosa <ragnar@macula.net> - 7 Aug 1998
18 driver now reports only any changes of its state. See joystick-api.txt,
65 -------------
86 ---------------
108 --------------
110 For an axis, ``value`` is a signed integer between -32767 and +32767
141 -------------
161 b) open the device in non-blocking mode (O_NONBLOCK)
165 ----------
[all …]
/Documentation/userspace-api/media/dvb/
Ddmx-qbuf.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 DMX_QBUF - DMX_DQBUF - Exchange a buffer with the driver
40 Applications call the ``DMX_QBUF`` ioctl to enqueue an empty
72 On success 0 is returned, on error -1 and the ``errno`` variable is set
74 :ref:`Generic Error Codes <gen-errors>` chapter.
77 Non-blocking I/O has been selected using ``O_NONBLOCK`` and no
/Documentation/arch/arm/
Dfirmware.rst2 Interface for registering and calling firmware-specific operations for ARM
18 The ops pointer must be non-NULL. More information about struct firmware_ops
21 There is a default, empty set of operations provided, so there is no need to
27 ((firmware_ops->op) ? firmware_ops->op(__VA_ARGS__) : (-ENOSYS))
30 -ENOSYS to signal that given operation is not available (for example, to allow
69 if (call_firmware_op(cpu_boot, cpu) == -ENOSYS)
/Documentation/admin-guide/LSM/
DSafeSetID.rst6 system-wide allowlist. These restrictions also prohibit the given UIDs/GIDs
15 CAP_SETUID is granted to programs running as root or those running as a non-root
24 tree of processes under non-root user(s) in the first place. Specifically,
28 lesser-privileged user -- not elevate privileges. Unfortunately, there is no
34 The main use case for this LSM is to allow a non-root program to transition to
35 other untrusted uids without full blown CAP_SETUID capabilities. The non-root
38 of CAP_SETUID since the non-root program cannot take advantage of CAP_SETUID to
40 namespace). The higher level goal is to allow for uid-based sandboxing of system
42 non-root programs can drop to even-lesser-privileged uids. This is especially
43 relevant when one non-root daemon on the system should be allowed to spawn other
[all …]
/Documentation/mm/
Dbalance.rst8 well as for non __GFP_IO allocations.
13 overhead of page reclaim. This may happen for opportunistic high-order
14 allocation requests that have order-0 fallback options. In such cases,
19 In the absence of non sleepable allocation requests, it seems detrimental
35 would not be done even when the dma zone was completely empty. 2.2 has
65 for non-sleepable allocations. Second, the HIGHMEM zone is also balanced,
85 are per-zone fields, used to determine when a zone needs to be balanced. When
99 2. Implement a replace_with_highmem()-like replace_with_regular() to preserve
/Documentation/trace/
Dftrace-uses.rst48 .. code-block:: c
87 .. code-block:: c
119 .. code-block:: c
129 .. code-block:: c
152 .. code-block:: c
202 kernel patches uses. Without this flag the pt_regs->ip can not be
234 .. code-block:: c
248 Non-zero to reset all filters before applying this filter.
260 .. code-block:: c
266 with new functions defined by @buf, have @reset be non-zero.
[all …]
/Documentation/bpf/
Dgraph_ds_impl.rst5 This document describes implementation details of new-style "graph" data
22 ------------
31 no longer relevant. With the introduction of kfuncs, kptrs, and the any-context
35 Two such data structures - linked_list and rbtree - have many verification
44 ------------
47 helper functions - either standard map API helpers like ``bpf_map_update_elem``
48 or map-specific helpers. The new-style graph data structures instead use kfuncs
57 -------
59 The new-style data structures are intrusive and are defined similarly to their
62 .. code-block:: c
[all …]
/Documentation/admin-guide/mm/
Dnuma_memory_policy.rst10 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
16 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
19 programming interface that a NUMA-aware application can take advantage of. When
28 ------------------------
41 not to overload the initial boot node with boot-time
45 this is an optional, per-task policy. When defined for a
61 In a multi-threaded task, task policies apply only to the thread
98 mapping-- i.e., at Copy-On-Write.
101 virtual address space--a.k.a. threads--independent of when
106 are NOT inheritable across exec(). Thus, only NUMA-aware
[all …]
/Documentation/filesystems/nfs/
Dpnfs.rst5 The are several inter-related caches. We have layouts which can
15 The on-the-wire command LAYOUTGET corresponds to struct
18 segments in nfsi->layout, of type struct pnfs_layout_hdr.
24 Each header is also (when non-empty) put on a list associated with
67 of these types there is a layout-driver with a common function-vectors
68 table which are called by the nfs-client pnfs-core to implement the
71 Files-layout-driver code is in: fs/nfs/filelayout/.. directory
72 Blocks-layout-driver code is in: fs/nfs/blocklayout/.. directory
73 Flexfiles-layout-driver code is in: fs/nfs/flexfilelayout/.. directory
75 blocks-layout setup

12345678