Home
last modified time | relevance | path

Searched +full:in +full:- +full:application (Results 1 – 25 of 568) sorted by relevance

12345678910>>...23

/Documentation/userspace-api/media/v4l/
Dpixfmt-v4l2.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 Single-planar format structure
13 .. flat-table:: struct v4l2_pix_format
14 :header-rows: 0
15 :stub-columns: 0
18 * - __u32
19 - ``width``
20 - Image width in pixels.
21 * - __u32
22 - ``height``
[all …]
Dvidioc-subdev-enum-mbus-code.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_MBUS_CODE - Enumerate media bus formats
34 This call is used by the application to access the enumeration
42 Therefore, to enumerate media bus formats available at a given sub-device pad,
48 A successful call will return with the ``code`` field filled in
58 other pads of the sub-device, as well as on the current active links.
66 .. flat-table:: struct v4l2_subdev_mbus_code_enum
67 :header-rows: 0
68 :stub-columns: 0
71 * - __u32
[all …]
Dvidioc-enum-fmt.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENUM_FMT - Enumerate image formats
40 formats in preference order, where preferred formats are returned before
41 (that is, with lower ``index`` value) less-preferred formats.
43 Depending on the ``V4L2_CAP_IO_MC`` :ref:`capability <device-capabilities>`,
46 1) ``V4L2_CAP_IO_MC`` is not set (also known as a 'video-node-centric' driver)
58 2) ``V4L2_CAP_IO_MC`` is set (also known as an 'MC-centric' driver)
63 If the ``mbus_code`` field is initialized to a valid (non-zero)
64 :ref:`media bus format code <v4l2-mbus-pixelcode>`, then drivers
80 .. flat-table:: struct v4l2_fmtdesc
[all …]
Duserp.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
11 ``V4L2_CAP_STREAMING`` flag in the ``capabilities`` field of struct
19 methods. Buffers (planes) are allocated by the application itself, and
20 can reside for example in virtual or shared memory. Only pointers to
21 data are exchanged, these pointers and meta-information are passed in
22 struct :c:type:`v4l2_buffer` (or in struct
23 :c:type:`v4l2_plane` in the multi-planar API case). The
33 .. code-block:: c
41 if (ioctl (fd, VIDIOC_REQBUFS, &reqbuf) == -1) {
55 area of memory. This happens transparently to the application in the
[all …]
Dvidioc-enum-frameintervals.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENUM_FRAMEINTERVALS - Enumerate frame intervals
46 - **Discrete:** The function returns success if the given index value
47 (zero-based) is valid. The application should increase the index by
53 - **Step-wise:** The function returns success if the given index value
59 - **Continuous:** This is a special case of the step-wise type above.
66 When the application calls the function with index zero, it must check
74 The order in which the frame intervals are returned has no
75 special meaning. In particular does it not say anything about potential
79 without any interaction from the application itself. This means that the
[all …]
Dvidioc-enum-framesizes.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENUM_FRAMESIZES - Enumerate frame sizes
37 and height in pixels) that the device supports for the given pixel
47 - **Discrete:** The function returns success if the given index value
48 (zero-based) is valid. The application should increase the index by
54 - **Step-wise:** The function returns success if the given index value
60 - **Continuous:** This is a special case of the step-wise type above.
67 When the application calls the function with index zero, it must check
74 The order in which the frame sizes are returned has no special
75 meaning. In particular does it not say anything about potential default
[all …]
Dapp-pri.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _app-pri:
6 Application Priority
10 them different priorities. Contrary to the traditional "rm -rf /" school
11 of thought, a video recording application could for example block other
14 working in background, which can be preempted by user controlled
18 Since these features cannot be implemented entirely in user space V4L2
30 after another application obtained higher priority.
/Documentation/ABI/testing/
Dsysfs-driver-w1_therm6 Values shall be space separated and in the device range
7 (typical -55 degC to 125 degC), if not values will be trimmed
9 stored in a 8bit register in the device. Lowest value is
11 master level, refer to Documentation/w1/w1-generic.rst for
13 Users: any user space application which wants to communicate with
23 embedded in device EEPROM. Be aware that devices support
27 * 'restore': restore EEPROM data in device RAM
29 Users: any user space application which wants to communicate with
41 * '-xx': xx is kernel error when reading power status
43 Users: any user space application which wants to communicate with
[all …]
Dsysfs-platform-chipidea-usb-otg6 Set a_bus_req(A-device bus request) input to be 1 if
7 the application running on the A-device wants to use the bus,
8 and to be 0 when the application no longer wants to use
10 be set to 1 by kernel in response to remote wakeup signaling
11 from the B-device, the A-device should decide to resume the bus.
15 Reading: returns 1 if the application running on the A-device
23 The a_bus_drop(A-device bus drop) input is 1 when the
24 application running on the A-device wants to power down
31 A-device, otherwise 0.
38 The b_bus_req(B-device bus request) input is 1 during the time
[all …]
/Documentation/networking/
Dkcm.rst1 .. SPDX-License-Identifier: GPL-2.0
8 interface over TCP for generic application protocols. With KCM an application
9 can efficiently send and receive application protocol messages over TCP using
12 KCM implements an NxM multiplexor in the kernel as diagrammed below::
14 +------------+ +------------+ +------------+ +------------+
16 +------------+ +------------+ +------------+ +------------+
18 +-----------+ | | +----------+
20 +----------------------------------+
22 +----------------------------------+
24 +---------+ | | | ------------+
[all …]
Dtcp-thin.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Thin-streams and TCP
7 A wide range of Internet-based services that use reliable transport
8 protocols display what we call thin-stream properties. This means
9 that the application sends data with such a low rate that the
11 effective. In time-dependent scenarios (like online games, control
15 dependency on the arrival of new data from the application to trigger
19 After analysing a large number of time-dependent interactive
22 lifespan. The combination of time-dependency and the fact that the
25 In order to reduce application-layer latency when packets are lost,
[all …]
Dcdc_mbim.rst1 .. SPDX-License-Identifier: GPL-2.0
4 cdc_mbim - Driver for CDC MBIM Mobile Broadband modems
20 "NCM/MBIM function" as defined in section 3.2 of [1]) is affected
24 -----------
26 :Valid Range: N/Y (0-1)
45 not participate in the management of the function. This implies that a
46 userspace MBIM management application always is required to enable a
51 - mbimcli (included with the libmbim [3] library), and
52 - ModemManager [4]
55 management application:
[all …]
Daf_xdp.rst1 .. SPDX-License-Identifier: GPL-2.0
20 XDP programs to redirect frames to a memory buffer in a user-space
21 application.
29 descriptor ring points to a data buffer in a memory area called a
36 The UMEM consists of a number of equally sized chunks. A descriptor in
43 FILL ring is used by the application to send down addr for the kernel
44 to fill in with RX packet data. References to these frames will then
45 appear in the RX ring once each packet has been received. The
48 space, for either TX or RX. Thus, the frame addrs appearing in the
50 TX ring. In summary, the RX and FILL rings are used for the RX path
[all …]
/Documentation/admin-guide/cgroup-v1/
Dnet_prio.rst9 Nominally, an application would set the priority of its traffic via the
12 1) The application may not have been coded to set this value
13 2) The priority of application traffic is often a site-specific administrative
14 decision rather than an application defined one.
20 # mount -t cgroup -onet_prio none /sys/fs/cgroup/net_prio
23 becomes visible at '/sys/fs/cgroup/net_prio'. This group includes all tasks in
24 the system. '/sys/fs/cgroup/net_prio/tasks' lists the tasks in this cgroup.
29 This file is read-only, and is simply informative. It contains a unique
35 from processes in this group and egressing the system on various interfaces.
36 It contains a list of tuples in the form <ifname priority>. Contents of this
[all …]
/Documentation/arch/arm/
Dmarvell.rst6 supported in mainline by the Linux kernel. As the Marvell families of
8 for a particular SoC is available in the Linux kernel. This document
9 tries to help in understanding where those SoCs are supported, and to
13 ------------
16 - 88F5082
17 - 88F5181 a.k.a Orion-1
18 - 88F5181L a.k.a Orion-VoIP
19 - 88F5182 a.k.a Orion-NAS
21 …- Datasheet: https://web.archive.org/web/20210124231420/http://csclub.uwaterloo.ca/~board/ts7800/M…
22 …- Programmer's User Guide: https://web.archive.org/web/20210124231536/http://csclub.uwaterloo.ca/~…
[all …]
/Documentation/admin-guide/
Dsysfs-rules.rst1 Rules on how to access information in sysfs
4 The kernel-exported sysfs exports internal kernel implementation details
10 To minimize the risk of breaking users of sysfs, which are in most cases
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
24 implementation details in its own API. Therefore it is not better than
26 Also, it is not actively maintained, in the sense of reflecting the
29 violates many of the rules in this document.
[all …]
Dsyscall-user-dispatch.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ----------
11 calls of only a part of their process - the part that has the
12 incompatible code - while being able to execute native syscalls without
19 address back to userspace. The application is in control of a flip
21 multiple-personality application can then flip the switch without
24 syscalls directly (disabled) or send them to be emulated in userspace
31 personality, and the application simply modifies that variable to
40 non-native applications, it must function on syscalls whose invocation
49 ---------
[all …]
/Documentation/networking/device_drivers/wwan/
Dt7xx.rst1 .. SPDX-License-Identifier: GPL-2.0-only
3 .. Copyright (C) 2020-21 Intel Corporation
13 application (e.g. Modem Manager) could easily manage the MBIM interface to enable
21 not play any role in managing their functionality. It is the job of a userspace
22 application to detect port enumeration and enable MBIM & AT functionalities.
26 - mbimcli (included with the libmbim [2] library), and
27 - Modem Manager [3]
32 - open the MBIM control channel
33 - configure network connection settings
34 - connect to network
[all …]
Diosm.rst1 .. SPDX-License-Identifier: GPL-2.0-only
3 .. Copyright (C) 2020-21 Intel Corporation
13 MBIM protocol [1]. Any front end application ( eg: Modem Manager) could easily
20 not play any role in managing the functionality. It is the job of a userspace
21 application to detect port enumeration and enable MBIM functionality.
23 Examples of few such userspace application are:
24 - mbimcli (included with the libmbim [2] library), and
25 - Modem Manager [3]
29 - open the MBIM control channel
30 - configure network connection settings
[all …]
/Documentation/misc-devices/
Dibmvmc.rst1 .. SPDX-License-Identifier: GPL-2.0+
21 https://openpowerfoundation.org/wp-content/uploads/2016/05/LoPAPR_DRAFT_v11_24March2016_cmt1.pdf
27 Console (HMC) - based system management.
31 packaged as an external tower or rack-mounted personal computer. In a
33 processor-based systems.
35 Management Application
36 ----------------------
38 In the management partition, a management application exists which enables
41 State Transfer Application (REST API's).
43 The management application runs on a Linux logical partition on a
[all …]
/Documentation/devicetree/bindings/remoteproc/
Dti,pru-consumer.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,pru-consumer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 A PRU application/consumer/user node typically uses one or more PRU device
14 nodes to implement a PRU application/functionality. Each application/client
20 The application nodes shall define their own bindings like regular platform
21 devices, so below are in addition to each node's bindings.
25 $ref: /schemas/types.yaml#/definitions/phandle-array
[all …]
/Documentation/block/
Ddata-integrity.rst12 application tried to write is most likely lost.
15 application meant it to. Recent additions to both the SCSI family
19 metadata (or protection information in SCSI terminology) includes a
21 ensures the individual sectors are written in the right order. And
27 technologies are working in their own isolated domains or at best
28 between adjacent nodes in the I/O path. The interesting thing about
30 is well defined and every node in the I/O path can verify the
47 in 520 byte sectors on disk. Data + IMD are interleaved when
54 scatter-gather lists.
60 Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
[all …]
/Documentation/power/
Dswsusp-and-swap-files.rst7 The Linux kernel handles swap files almost in the same way as it handles swap
11 (2) the header of a swap file is not in the first block of the partition that
13 already taken care of by the swap-handling code, but (2) has to be taken into
16 In principle the location of a swap file's header may be determined with the
22 header is located. For convenience, this offset is expressed in <PAGE_SIZE>
25 In order to use a swap file with swsusp, you need to:
33 2) Use an application that will bmap the swap file with the help of the
35 offset, in <PAGE_SIZE> units, from the beginning of the partition which
44 application in 2) (of course, this step may be carried out automatically
45 by the same application that determines the swap file's header offset using the
[all …]
/Documentation/core-api/
Dprotection-keys.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Memory Protection Keys provide a mechanism for enforcing page-based
9 application changes protection domains.
19 Pkeys work by dedicating 4 previously Reserved bits in each page table entry to
22 Protections for each key are defined with a per-CPU user-accessible register
23 (PKRU). Each of these is a 32-bit register storing two bits (Access Disable
26 Being a CPU register, PKRU is inherently thread-local, potentially giving each
30 register. The feature is only available in 64-bit mode, even though there is
31 theoretically space in the PAE PTEs. These permissions are enforced on data
37 Pkeys use 3 bits in each page table entry, to encode a "protection key index",
[all …]
/Documentation/crypto/
Dasync-tx-api.rst1 .. SPDX-License-Identifier: GPL-2.0
24 4.2 "My application needs exclusive control of hardware channels"
32 bulk memory transfers/transforms with support for inter-transactional
43 xor-parity-calculations of the md-raid5 driver using the offload engines
44 present in the Intel(R) Xscale series of I/O processors. It also built
45 on the 'dmaengine' layer developed for offloading memory copies in the
52 in software otherwise.
54 operations to be submitted, like xor->copy->xor in the raid5 case. The
64 -----------------------------
72 ------------------------
[all …]

12345678910>>...23