| /linux/include/sound/sof/ |
| H A D | channel_map.h | 1 /* SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) */
16 * \brief Channel map, specifies transformation of one-to-many or many-to-one.
18 * In case of one-to-many specifies how the output channels are computed out of
20 * in case of many-to-one specifies how a single target channel is computed
23 * Channel index specifies position of the channel in the stream on the 'one'
29 * Channel mask describes which channels are taken into account on the "many"
30 * side. Bit[i] set to 1 means that i-th channel is used for computation
34 * one per each channel set in the mask (left to right, LS bit set in the
35 * mask corresponds to ch_coeffs[0]).
49 * More than one transformation per a single channel is allowed (in case
|
| /linux/drivers/remoteproc/ |
| H A D | pru_rproc.h | 1 /* SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) */
5 * Copyright (C) 2014-2020 Texas Instruments Incorporated - https://www.ti.com/
6 * Suman Anna <s-anna@ti.com>
13 * struct pruss_int_map - PRU system events _to_ channel and host mapping
15 * @chnl: channel number assigned to a given @event
16 * @host: host number assigned to a given @chnl
18 * PRU system events are mapped to channels, and these channels are mapped
19 * to host interrupts. Events can be mapped to channels in a one-to-one or
20 * many-to-one ratio (multiple events per channel), and channels can be
21 * mapped to host interrupts in a one-to-one or many-to-one ratio (multiple
[all …]
|
| /linux/drivers/usb/gadget/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
22 USB is a host/device protocol, organized with one host (such as a
23 PC) controlling up to 127 peripheral devices.
24 The USB hardware is asymmetric, which makes it easier to set up:
[all …]
|
| /linux/Documentation/i2c/ |
| H A D | summary.rst | 2 Introduction to I2C and SMBus
6 a protocol developed by Philips. It is a two-wire protocol with variable
7 speed (typically up to 400 kHz, high speed modes up to 5 MHz). It provides
8 an inexpensive bus for connecting many types of devices with infrequent or
14 The latest official I2C specification is the `"I²C-bus specification and user
15 manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_
19 a subset of I2C protocols and signaling. Many I2C devices will work on an
20 SMBus, but some SMBus protocols add semantics beyond what is required to
26 use its protocols on many I2C systems. However, there are systems that don't
34 The I2C bus connects one or more controller chips and one or more target chips.
[all …]
|
| /linux/drivers/mtd/ubi/ |
| H A D | ubi-media.h | 1 /* SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause) */
10 * This file defines the layout of UBI headers and all the other UBI on-flash
47 * @UBI_VTBL_AUTORESIZE_FLG: auto-resize this volume
51 * check. Main use-case for this flag is
52 * boot-time reduction
54 * %UBI_VTBL_AUTORESIZE_FLG flag can be set only for one volume in the volume
55 * table. UBI automatically re-sizes the volume which has this flag and makes
56 * the volume to be of largest possible size. This means that if after the
58 * present on the device, it automatically appends all of them to the volume
66 * The auto-resize feature is useful for device production purposes. For
[all …]
|
| /linux/Documentation/userspace-api/media/drivers/ |
| H A D | imx-uapi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 ---------
18 - V4L2_EVENT_IMX_FRAME_INTERVAL_ERROR
20 The user application can subscribe to this event from the ipuX_csiY
30 -----------------------------------
33 NTSC/PAL signal re-sync (too little or too many video lines). When
34 this happens, the IPU triggers a mechanism to re-establish vertical
36 from image to image, and can last a long time before a stable image is
38 permanent split image (one frame contains lines from two consecutive
43 value for the current standard, by about one frame time (60 usec),
[all …]
|
| /linux/Documentation/devicetree/bindings/perf/ |
| H A D | riscv,pmu.yaml | 1 # SPDX-License-Identifier: BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RISC-V SBI PMU events
10 - Atish Patra <atishp@rivosinc.com>
13 The SBI PMU extension allows supervisor software to configure, start and
18 The platform must provide information about PMU event to counter mappings
19 either via device tree or another way, specific to the platform.
20 Without the event to counter mappings, the SBI PMU extension cannot be used.
25 or another way, specific to the platform.
[all …]
|
| /linux/fs/btrfs/ |
| H A D | raid56.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (C) 2012 Fusion-io All rights reserved.
44 * bio_list and bio_list_lock are used to add more bios into the stripe
52 * plugging code to collect partial bios while plugged. The stripe
53 * locking code also uses it to hand off the stripe lock to the next
58 /* Flags that tell us if it is safe to merge with this bio. */
67 /* How many pages there are for the full stripe including P/Q */
70 /* How many sectors there are for the full stripe including P/Q */
79 /* How many pages there are for each stripe */
82 /* How many sectors there are for each stripe */
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-interconnect.json | 8 …"PublicDescription": "Counts the number of times when an inbound write (from a device to memory or…
18 …"PublicDescription": "Counts the number of times when an inbound write (from a device to memory or…
28 …t have not yet returned their data to the uncore. These writes are generally queued up in the swi…
38 …t have not yet returned their data to the uncore. These writes are generally queued up in the swi…
48 …utstanding in the uncore trying to acquire ownership in each cycle. This can be used with the wri…
58 …utstanding in the uncore trying to acquire ownership in each cycle. This can be used with the wri…
68 …he uncore in each cycle. This can be used with the read transaction count to calculate the averag…
78 …he uncore in each cycle. This can be used with the read transaction count to calculate the averag…
108 …to calculate the average latency in the uncore. The occupancy increments when the ownership fetch…
118 …to calculate the average latency in the uncore. The occupancy increments when the ownership fetch…
[all …]
|
| /linux/tools/testing/selftests/futex/include/ |
| H A D | futextest.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
13 * 2009-Nov-6: Initial version by Darren Hart <dvhart@linux.intel.com>
28 /* Define the newer op codes if the system header file is not up to date. */
51 * SYS_futex is expected from system C library, in glibc some 32-bit
52 * architectures (e.g. RV32) are using 64-bit time_t, therefore it doesn't have
54 * SYS_futex_time64 in this situation to ensure the compilation and the
62 * On 32bit systems if we use "-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64" or if
64 * however, the SYS_futex will still point to the 32bit futex system call.
73 * futex() - SYS_futex syscall wrapper
81 * @opflags: flags to be bitwise OR'd with op, such as FUTEX_PRIVATE_FLAG
[all …]
|
| /linux/Documentation/input/ |
| H A D | gamepad.rst | 1 ---------------------------
3 ---------------------------
10 Linux provides many different input drivers for gamepad hardware. To avoid
11 having user-space deal with different button-mappings for each gamepad, this
12 document defines how gamepads are supposed to report their data.
25 | <===DP===> |SE| |ST| (W) -|- (E) | |
35 D-Pad Left Right Action Pad
43 - Action-Pad
44 4 buttons in diamonds-shape (on the right side). The buttons are
47 - D-Pad (Direction-pad)
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H A D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use
14 development project. This is the first such API released on Linux to
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
22 they're easy to port to new hardware.
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
[all …]
|
| /linux/drivers/net/ethernet/8390/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 If you have a network (Ethernet) card belonging to this class, say Y.
13 Note that the answer to this question doesn't directly affect the
14 kernel: saying N will just cause the configurator to skip all
24 Say Y here if you intend to attach an Asix AX88190-based PCMCIA
25 (PC-card) Fast Ethernet card to your computer. These cards are
26 nearly NE2000 compatible but need a separate driver due to a few
29 To compile this driver as a module, choose M here: the module will be
39 AX88796 driver, using platform bus to provide
55 This driver is for the Individual Computers X-Surf 100 Ethernet
[all …]
|
| /linux/Documentation/process/ |
| H A D | cve.rst | 6 unambiguous way to identify, define, and catalog publicly disclosed
8 regards to the kernel project, and CVE numbers were very often assigned
10 the kernel development community has tended to avoid them. However, the
11 combination of continuing pressure to assign CVEs and other forms of
16 The Linux kernel developer team does have the ability to assign CVEs for
19 process<../process/security-bugs>`.
22 archives of the linux-cve mailing list, as seen on
23 https://lore.kernel.org/linux-cve-announce/. To get notice of the
25 <https://subspace.kernel.org/subscribing.html>`_ to that mailing list.
33 to them. These assignments are published on the linux-cve-announce
[all …]
|
| H A D | 4.Coding.rst | 6 While there is much to be said for a solid and community-oriented design
19 ---------
25 :ref:`Documentation/process/coding-style.rst <codingstyle>`. For much of
29 leads to two independent hazards for kernel developers.
31 The first of these is to believe that the kernel coding standards do not
33 code to the kernel is very difficult if that code is not coded according to
34 the standard; many developers will request that the code be reformatted
36 requires some uniformity of code to make it possible for developers to
38 strangely-formatted code.
41 employer's mandated style. In such cases, the kernel's style will have to
[all …]
|
| H A D | 6.Followthrough.rst | 8 patches. One of the biggest mistakes that even experienced kernel
9 developers can make is to conclude that their work is now done. In truth,
11 with, possibly, quite a bit of work yet to be done.
16 code. You, as the author of that code, will be expected to work with the
17 kernel community to ensure that your code is up to the kernel's quality
18 standards. A failure to participate in this process is quite likely to
23 ----------------------
27 many developers, the most intimidating part of the kernel development
31 - If you have explained your patch well, reviewers will understand its
32 value and why you went to the trouble of writing it. But that value
[all …]
|
| /linux/arch/arm/common/ |
| H A D | vlock.S | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * vlock.S - simple voting lock implementation for ARM
5 * Created by: Dave Martin, 2012-08-16
6 * Copyright: (C) 2012-2013 Linaro Limited
15 .arch armv7-a
20 #define MANY(x...) x macro
23 #define MANY(x...) macro
26 @ voting lock for first-man coordination
43 * The vlock structure must reside in Strongly-Ordered or Device memory.
46 * writes to neighbouring locations within a cacheline do not interfere
[all …]
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | knfsd-stats.rst | 5 :Authors: Greg Banks <gnb@sgi.com> - 26 Mar 2009
8 which the kernel NFS server makes available to userspace. These
12 In most cases you don't need to know these formats, as the nfsstat(8)
13 program from the nfs-utils distribution provides a helpful command-line
30 a sequence of unsigned decimal numeric fields. One line is shown
34 to zero these counters, instead applications should do their own
38 The id number of the NFS thread pool to which this line applies.
48 packets-arrived
49 Counts how many NFS packets have arrived. More precisely, this
58 However this is a more accurate and less workload-dependent measure
[all …]
|
| /linux/tools/testing/selftests/sync/ |
| H A D | sync_fence.c | 2 * sync fence tests with one timeline
3 * Copyright 2015-2016 Collabora Ltd.
9 * Permission is hereby granted, free of charge, to any person obtaining a
11 * to deal in the Software without restriction, including without limitation
12 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
13 * and/or sell copies of the Software, and to permit persons to whom the
14 * Software is furnished to do so, subject to the following conditions:
20 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
48 /* Advance timeline from 0 -> 1 */ in test_fence_one_timeline_wait()
96 /* confirm all fences have one active point (even d) */ in test_fence_one_timeline_merge()
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | transhuge.rst | 16 But in the future it can expand to other filesystems.
26 requiring larger clear-page copy-page in page faults which is a
32 factor will affect all subsequent accesses to the memory for the whole
44 hugepages but a significant speedup already happens if only one of
46 going to run faster.
48 Modern kernels support "multi-size THP" (mTHP), which introduces the
49 ability to allocate memory in blocks that are bigger than a base page
50 but smaller than traditional PMD-size (as described above), in
51 increments of a power-of-2 number of pages. mTHP can back anonymous
52 memory (for example 16K, 32K, 64K, etc). These THPs continue to be
[all …]
|
| /linux/Documentation/arch/arm/ |
| H A D | vlocks.rst | 2 vlocks for Bare-Metal Mutual Exclusion
5 Voting Locks, or "vlocks" provide a simple low-level mutual exclusion
9 These are intended to be used to coordinate critical activity among CPUs
10 which are otherwise non-coherent, in situations where the hardware
11 provides no other mechanism to support this and ordinary spinlocks
16 writes to a single memory location. To arbitrate, every CPU "votes for
17 itself", by storing a unique number to a common memory location. The
21 In order to make sure that the election produces an unambiguous result
23 no winner has been chosen and the election does not appear to have
28 ---------
[all …]
|
| /linux/Documentation/networking/ |
| H A D | scaling.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 networking stack to increase parallelism and improve performance for
13 multi-processor systems.
17 - RSS: Receive Side Scaling
18 - RPS: Receive Packet Steering
19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
21 - XPS: Transmit Packet Steering
28 (multi-queue). On reception, a NIC can send different packets to different
29 queues to distribute processing among CPUs. The NIC distributes packets by
[all …]
|
| /linux/Documentation/cdrom/ |
| H A D | cdrom-standard.rst | 2 A Linux CD-ROM standard
14 Linux is probably the Unix-like operating system that supports
18 - The large list of hardware devices available for the many platforms
19 that Linux now supports (i.e., i386-PCs, Sparc Suns, etc.)
20 - The open design of the operating system, such that anybody can write a
22 - There is plenty of source code around as examples of how to write a driver.
24 The openness of Linux, and the many different types of available
25 hardware has allowed Linux to support many different hardware devices.
26 Unfortunately, the very openness that has allowed Linux to support
28 device driver to differ significantly from one device to another.
[all …]
|
| /linux/drivers/net/ethernet/intel/igbvf/ |
| H A D | igbvf.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
2 /* Copyright(c) 2009 - 2018 Intel Corporation. */
52 * PTHRESH - MAC will consider prefetch if it has fewer than this number of
54 * Setting this to 0 disables RX descriptor prefetch.
55 * HTHRESH - MAC will only prefetch if there are at least this many descriptors
58 * WTHRESH - RX descriptor writeback threshold - MAC will delay writing back
59 * descriptors until either it has this many to write back, or the
71 /* How many Tx Descriptors do we need to call netif_wake_queue ? */
73 /* How many Rx Buffers do we bundle into one write to the hardware ? */
79 #define IGBVF_MNG_VLAN_NONE (-1)
[all …]
|
| /linux/Documentation/security/ |
| H A D | self-protection.rst | 2 Kernel Self-Protection
5 Kernel self-protection is the design and implementation of systems and
6 structures within the Linux kernel to protect against security flaws in
13 In the worst-case scenario, we assume an unprivileged local attacker
14 has arbitrary read and write access to the kernel's memory. In many
17 cover the more limited cases as well. A higher bar, and one that should
19 local attacker, since the root user has access to a vastly increased
20 attack surface. (Especially when they have the ability to load arbitrary
23 The goals for successful self-protection systems would be that they
24 are effective, on by default, require no opt-in by developers, have no
[all …]
|