| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-v4l2.rst | 1 .. 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 …]
|
| /linux/Documentation/admin-guide/ |
| H A D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details
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
31 - sysfs is always at ``/sys``
35 application's behavior, but never try to search for sysfs. Never try
38 - devices are only "devices"
39 There is no such thing like class-, bus-, physical devices,
41 just simply a "device". Class-, bus-, physical, ... types are just
[all …]
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | net_prio.rst | 9 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
26 Each net_prio cgroup contains two files that are subsystem specific
29 This file is read-only, and is simply informative. It contains a unique
52 One usage for the net_prio cgroup is with mqprio qdisc allowing application
|
| /linux/Documentation/arch/powerpc/ |
| H A D | vas-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. _VAS-API:
12 allows both userspace and kernel communicate to co-processor
14 unit comprises of one or more hardware engines or co-processor types
21 Requests to the GZIP engine must be formatted as a co-processor Request
37 Application access to the GZIP engine is provided through
38 /dev/crypto/nx-gzip device node implemented by the VAS/NX device driver.
39 An application must open the /dev/crypto/nx-gzip device to obtain a file
42 engine for this process. Once a connection is established, the application
44 request queue into the application's virtual address space.
[all …]
|
| /linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 libbpf is a C-based library containing a BPF loader that takes compiled BPF
10 kernel hooks, allowing BPF application developers to focus only on BPF program
13 The following are the high-level features supported by libbpf:
15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
17 functionality, which is useful when users need more fine-grained control
22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
24 * Supports BPF CO-RE mechanism, enabling BPF developers to write portable
35 A BPF application consists of one or more BPF programs (either cooperating or
[all …]
|
| /linux/arch/mips/include/asm/octeon/ |
| H A D | cvmx-boot-vector.h | 6 * Copyright (C) 2003-2017 Cavium, Inc.
19 * Once cvmx_boot_vector_get() returns a non-NULL value (indicating
24 * be used by the application that has set the target_ptr in any
25 * application specific manner, they are not touched by the vectoring
30 * registers are preserved, except on pre-OCTEON II CPUs, where k1 is
37 * Applications install the boot bus code in cvmx-boot-vector.c, which
45 /* Three application specific arguments. */
|
| H A D | cvmx-sysinfo.h | 7 * Copyright (c) 2003-2016 Cavium, Inc.
14 * AS-IS and WITHOUT ANY WARRANTY; without even the implied warranty
21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
35 #include "cvmx-coremask.h"
39 * Structure describing application specific information.
46 * u-boot, etc.) The cvmx_sysinfo_minimal_initialize() function is
57 /* Application image specific variables */
66 /* coremask defining cores running application */
92 * addresses, and it is up to the application to use the
101 * application to use the proper addressing mode (XKPHYS,
|
| H A D | cvmx-bootmem.h | 7 * Copyright (c) 2003-2008 Cavium Networks
14 * AS-IS and WITHOUT ANY WARRANTY; without even the implied warranty
21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
30 * application start time.
54 * application init code converts addresses to 64 bit addresses before the
55 * application starts.
150 * passed to the application by the bootloader at a specific
151 * address. This is an allocate-only algorithm, so
158 * @alignment: Alignment required - must be power of 2
176 * to the application by the bootloader, and assign it a name in the
[all …]
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A 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 …]
|
| H A D | snps,dw-pcie-ep.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie-ep
23 - compatible
[all …]
|
| /linux/Documentation/crypto/ |
| H A D | async-tx-api.rst | 1 .. 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
54 operations to be submitted, like xor->copy->xor in the raid5 case. The
64 -----------------------------
69 async_<operation>(<op specific parameters>, struct async_submit_ctl *submit)
72 ------------------------
92 -------------------------
94 The return value is non-NULL and points to a 'descriptor' when the operation
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | tee.h | 2 * Copyright (c) 2015-2016, Linaro Limited
37 * Each TEE driver defines a TEE specific protocol which is used for the
52 #define TEE_MEMREF_NULL (__u64)(-1) /* NULL MemRef Buffer */
62 * OP-TEE specific capabilities
67 * struct tee_ioctl_version_data - TEE version
69 * @impl_caps: [out] Implementation specific capabilities
73 * @impl_caps is implementation specific, for example TEE_OPTEE_CAP_*
83 * TEE_IOC_VERSION - query version of TEE
92 * struct tee_ioctl_shm_alloc_data - Shared memory allocate argument
108 * TEE_IOC_SHM_ALLOC - allocate shared memory
[all …]
|
| /linux/Documentation/networking/ |
| H A D | napi.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
30 of the NAPI instance while the method is the driver-specific event
37 -----------
55 ------------
64 argument - drivers can process completions for any number of Tx
69 packets driver can process in a single poll. Rx specific APIs like page
96 or return ``budget - 1``.
101 -------------
109 As mentioned in the :ref:`drv_ctrl` section - napi_disable() and subsequent
118 --------------------------
[all …]
|
| H A 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
39 transport has to be IP-based. In fact, RDS over IB uses a
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
73 with setsockopt(2) and getsockopt(2) for RDS specific socket
[all …]
|
| H A D | cdc_mbim.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 cdc_mbim - Driver for CDC MBIM Mobile Broadband modems
24 -----------
26 :Valid Range: N/Y (0-1)
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:
57 - open the control channel
58 - configure network connection settings
[all …]
|
| H A D | mctp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 The core code provides a socket-based interface to send and receive MCTP
21 (as defined by DSP0236, section 3.2.47), likely connected to a specific hardware
24 A network defines a unique address space for MCTP endpoints by endpoint-ID
25 (described by DSP0236, section 3.2.31). A network has a user-visible identifier
26 to allow references from userspace. Route definitions are specific to one
39 --------------------
41 MCTP uses ``AF_MCTP`` / ``PF_MCTP`` for the address- and protocol- families.
42 Since MCTP is message-based, only ``SOCK_DGRAM`` sockets are supported.
44 .. code-block:: C
[all …]
|
| H A D | can.rst | 2 SocketCAN - Controller Area Network
20 .. _socketcan-motivation:
29 functionality. Usually, there is only a hardware-specific device
32 Queueing of frames and higher-level transport protocols like ISO-TP
34 character-device implementations support only one single process to
37 often the need for adaption of large parts of the application to the
47 protocol family module and also vice-versa. Also, the protocol family
56 same received matching CAN frames. An application wishing to
57 communicate using a specific transport protocol, e.g. ISO-TP, just
59 write application data byte streams, without having to deal with
[all …]
|
| /linux/Documentation/gpu/ |
| H A D | tegra.rst | 11 supports the built-in GPU, comprised of the gr2d and gr3d engines. Starting
18 - A host1x driver that provides infrastructure and access to the host1x
21 - A KMS driver that supports the display controllers as well as a number of
24 - A set of custom userspace IOCTLs that can be used to submit jobs to the
40 device using a driver-provided function which will set up the bits specific to
45 the subsystem specific bits are torn down and the clients destroyed in turn.
48 -------------------------------
50 .. kernel-doc:: include/linux/host1x.h
52 .. kernel-doc:: drivers/gpu/host1x/bus.c
56 --------------------------
[all …]
|
| /linux/net/netlabel/ |
| H A D | netlabel_unlabeled.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
9 * Author: Paul Moore <paul@paul-moore.com>
13 * (c) Copyright Hewlett-Packard Development Company, L.P., 2006
25 * This message is sent from an application to add a new static label for
44 * This message is sent from an application to remove an existing static
62 * This message can be sent either from an application or by the kernel in
63 * response to an application generated STATICLIST message. When sent by an
64 * application there is no payload and the NLM_F_DUMP flag should be set.
83 * This message is sent from an application to set the default static
101 * This message is sent from an application to remove the existing default
[all …]
|
| H A D | netlabel_mgmt.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
9 * Author: Paul Moore <paul@paul-moore.com>
13 * (c) Copyright Hewlett-Packard Development Company, L.P., 2006
26 * Sent by an application to add a domain mapping to the NetLabel system.
53 * Sent by an application to remove a domain mapping from the NetLabel
61 * This message can be sent either from an application or by the kernel in
62 * response to an application generated LISTALL message. When sent by an
63 * application there is no payload and the NLM_F_DUMP flag should be set.
90 * Sent by an application to set the default domain mapping for the NetLabel
107 * Sent by an application to remove the default domain mapping from the
[all …]
|
| H A D | netlabel_cipso_v4.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
9 * Author: Paul Moore <paul@paul-moore.com>
13 * (c) Copyright Hewlett-Packard Development Company, L.P., 2006
25 * Sent by an application to add a new DOI mapping table.
42 * Sent by an application to remove a specific DOI mapping table from the
50 * Sent by an application to list the details of a DOI definition. On
74 * This message is sent by an application to list the valid DOIs on the
75 * system. When sent by an application there is no payload and the
147 #define NLBL_CIPSOV4_A_MAX (__NLBL_CIPSOV4_A_MAX - 1)
|
| /linux/arch/arm/mach-pxa/ |
| H A D | pxa3xx-regs.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * arch/arm/mach-pxa/include/mach/pxa3xx-regs.h
5 * PXA3xx specific register definitions
13 #include "pxa-regs.h"
30 #define PWER __REG(0x40F50010) /* Power Manager Wake-up Enable Register */
31 #define PWSR __REG(0x40F50014) /* Power Manager Wake-up Status Register */
33 #define DCDCSR __REG(0x40F50080) /* DC-DC Controller Status Register */
40 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration */
41 #define ARSR __REG(0x40f40004) /* Application Subsystem Reset Status */
42 #define AD3ER __REG(0x40f40008) /* Application Subsystem Wake-Up from D3 Enable */
[all …]
|
| /linux/Documentation/userspace-api/media/drivers/ |
| H A D | uvcvideo.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 This file documents some driver-specific aspects of the UVC driver, such as
7 driver-specific ioctls and implementation notes.
10 linux-media@vger.kernel.org.
14 ---------------------------
19 The UVC specification allows for vendor-specific extensions through extension
23 - through mappings of XU controls to V4L2 controls
24 - through a driver-specific ioctl interface
30 The second mechanism requires uvcvideo-specific knowledge for the application to
40 The UVC driver provides an API for user space applications to define so-called
[all …]
|
| /linux/drivers/scsi/mpt3sas/ |
| H A D | mpt3sas_ctl.h | 6 * Copyright (C) 2012-2014 LSI Corporation
7 * Copyright (C) 2013-2014 Avago Technologies
8 * (mailto: MPT-FusionLinux.pdl@avagotech.com)
23 * LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
42 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
113 * struct mpt3_ioctl_header - main header structure
114 * @ioc_number - IOC unit number
115 * @port_number - IOC port number
116 * @max_data_size - maximum number bytes to transfer on read
125 * struct mpt3_ioctl_diag_reset - diagnostic reset
[all …]
|
| /linux/Documentation/sound/designs/ |
| H A D | timestamping.rst | 7 - Trigger_tstamp is the system time snapshot taken when the .trigger
9 general case, but specific hardware may have synchronization
11 estimate with a delay. In the latter two cases, the low-level driver
17 - tstamp is the current system timestamp updated during the last
18 event or application query.
19 The difference (tstamp - trigger_tstamp) defines the elapsed time.
27 the application needs:
29 - ``avail`` reports how much can be written in the ring buffer
30 - ``delay`` reports the time it will take to hear a new sample after all
43 ascii-art, this could be represented as follows (for the playback
[all …]
|