| /linux/Documentation/arch/riscv/ |
| H A D | hwprobe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 RISC-V Hardware Probing Interface
4 ---------------------------------
6 The RISC-V hardware probing interface is based around a single syscall, which
7 is defined in <asm/hwprobe.h>::
18 The arguments are split into three groups: an array of key-value pairs, a CPU
19 set, and some flags. The key-value pairs are supplied with a count. Userspace
21 value if the key is recognized. If a key is unknown to the kernel, its key field
22 will be cleared to -1, and its value set to 0. The CPU set is defined by
23 CPU_SET(3) with size ``cpusetsize`` bytes. For value-like keys (eg. vendor,
[all …]
|
| /linux/drivers/media/i2c/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
8 comment "IR I2C driver auto-selected by 'Autoselect ancillary drivers'"
45 tristate "Allied Vision ALVIUM MIPI CSI-2 camera support"
48 This is a Video4Linux2 sensor-level driver for the Allied Vision
49 ALVIUM camera connected via MIPI CSI-2 interface.
51 To compile this driver as a module, choose M here: the
52 module will be called alvium-csi2.
57 This is a Video4Linux2 sensor driver for the ON Semiconductor
60 To compile this driver as a module, choose M here: the
67 This is a Video4Linux2 sensor driver for the GalaxyCore
[all …]
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | ti,tlv320adcx140.yaml | 1 # SPDX-License-Identifier: (GPL-2.0+ OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Texas Instruments TLV320ADCX140 Quad Channel Analog-to-Digital Converter
11 - Andrew Davis <afd@ti.com>
14 The TLV320ADCX140 are multichannel (4-ch analog recording or 8-ch digital
15 PDM microphones recording), high-performance audio, analog-to-digital
28 - ti,tlv320adc3140
29 - ti,tlv320adc5140
30 - ti,tlv320adc6140
[all …]
|
| /linux/Documentation/input/ |
| H A D | gamepad.rst | 1 ---------------------------
3 ---------------------------
11 having user-space deal with different button-mappings for each gamepad, this
16 As "gamepad" we define devices which roughly look like this::
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
45 differently labeled on most devices so we define them as NORTH,
47 - D-Pad (Direction-pad)
[all …]
|
| /linux/Documentation/pcmcia/ |
| H A D | driver-changes.rst | 7 * pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
8 If `struct pcmcia_device *p_dev->config_flags` is set accordingly,
14 - CONF_AUTO_CHECK_VCC : check for matching Vcc
15 - CONF_AUTO_SET_VPP : set Vpp
16 - CONF_AUTO_AUDIO : auto-enable audio line, if required
17 - CONF_AUTO_SET_IO : set ioport resources (->resource[0,1])
18 - CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
20 * pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
22 as it mirrors pcmcia_disable_device(). Configuration settings are now
26 * pcmcia_request_window changes (as of 2.6.36)
[all …]
|
| /linux/Documentation/networking/device_drivers/can/ |
| H A D | can327.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause)
7 --------
14 -----------
21 Let's use ELM327s as CAN adapters.
26 -------------
28 This driver is an effort to turn abundant ELM327 based OBD interfaces
29 into full fledged (as far as possible) CAN interfaces.
32 the driver has to switch between its modes as quickly as possible in
33 order to fake full-duplex operation.
35 As such, can327 is a best effort driver. However, this is more than
[all …]
|
| /linux/drivers/watchdog/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 on-line as fast as possible after a lock-up. There's both a watchdog
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
23 The watchdog is usually used together with the watchdog daemon
24 which is available from
27 process table is full.
44 The default watchdog behaviour (which you get if you say N here) is
51 bool "Update boot-enabled watchdog until userspace takes over"
54 The default watchdog behaviour (which you get if you say Y here) is
56 been loaded until control is taken over from userspace using the
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | cxlflash.rst | 9 Accelerator Power Interface), which is available to certain PCIe slots
10 on Power 8 systems. CAPI can be thought of as a special tunneling
12 purpose co-processors which can read or write an application's
13 memory and generate page faults. As a result, the host interface to
19 devices as a PCI device by implementing a virtual PCI host bridge.
29 The CXL Flash Adapter Driver is a kernel module that sits in the
30 SCSI stack as a low level device driver (below the SCSI disk and
31 protocol drivers) for the IBM CXL Flash Adapter. This driver is
35 as described in Documentation/arch/powerpc/cxl.rst.
40 - Any flash device (LUN) can be configured to be accessed as a
[all …]
|
| /linux/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright 2021-2023 Collabora Ltd.
8 As originally designed, the Linux graphics subsystem had extremely limited
9 support for sharing pixel-buffer allocations between processes, devices, and
12 approach this sharing for two-dimensional image data.
14 It is written with reference to the DRM subsystem for GPU and display devices,
25 Conceptually a two-dimensional array of pixels. The pixels may be stored
30 A span along a single y-axis value, e.g. from co-ordinates (0,100) to
37 A span along a single x-axis value, e.g. from co-ordinates (100,0) to
46 A two-dimensional array of some or all of an image's color and alpha
[all …]
|
| /linux/include/linux/ |
| H A D | jiffies.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
20 * OSF/1 kernel. The SHIFT_HZ define expresses the same value as the
53 * - (NOM / DEN) fits in (32 - LSH) bits.
54 * - (NOM % DEN) fits in (32 - LSH) bits.
59 /* LATCH is used in the interval timer and ftape setup. */
64 /* TICK_USEC is the time between ticks in usec assuming SHIFTED_HZ */
67 /* USER_TICK_USEC is the time between ticks in usec assuming fake USER_HZ */
75 * The 64-bit value is not atomic on 32-bit systems - you MUST NOT read it
77 * get_jiffies_64() will do this for you as appropriate.
79 * jiffies and jiffies_64 are at the same address for little-endian systems
[all …]
|
| H A D | rculist.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 * RCU-protected list version
14 * INIT_LIST_HEAD_RCU - Initialize a list_head visible to RCU readers
19 * However, if the list being initialized is visible to readers, you
24 WRITE_ONCE(list->next, list); in INIT_LIST_HEAD_RCU()
25 WRITE_ONCE(list->prev, list); in INIT_LIST_HEAD_RCU()
29 * return the ->next pointer of a list_head in an rcu safe
32 #define list_next_rcu(list) (*((struct list_head __rcu **)(&(list)->next)))
35 * list_tail_rcu - returns the prev pointer of the head of the list
42 #define list_tail_rcu(head) (*((struct list_head __rcu **)(&(head)->prev)))
[all …]
|
| H A D | percpu-refcount.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
7 * This implements a refcount with similar semantics to atomic_t - atomic_inc(),
8 * atomic_dec_and_test() - but percpu.
15 * The refcount will have a range of 0 to ((1U << 31) - 1), i.e. one bit less
16 * than an atomic_t - this is because of the way shutdown works, see
20 * refcount hitting 0 - it can't, if it was in percpu mode. percpu_ref_kill()
22 * issuing the appropriate barriers, and then marks the ref as shutting down so
29 * is created when userspaces calls io_setup(), and destroyed when userspace
32 * In the aio code, kill_ioctx() is called when we wish to destroy a kioctx; it
44 * once - percpu_ref_kill() does this for you, it returns true once and false if
[all …]
|
| /linux/drivers/accessibility/speakup/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
8 This is the Speakup screen reader. Think of it as a
12 point your browser at <http://www.linux-speakup.org/>.
13 There is also a mailing list at the above url that you
24 Speakup can either be built in or compiled as a module
28 the synthesizer drivers below can only be built as
32 used in conjunction with Speakup. Think of them as
36 The Dectalk pc driver can only be built as a module, and
37 requires software to be pre-loaded on to the card before
54 This is the Speakup driver for the Accent SA
[all …]
|
| /linux/drivers/scsi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
29 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
40 To compile this driver as a module, choose M here and read
44 However, do not compile this as a module if your root file system
45 (the one containing the directory /) is located on a SCSI device.
79 comment "SCSI support type (disk, tape, CD-ROM)"
89 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
90 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
91 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
92 CD-ROMs.
[all …]
|
| /linux/arch/mips/include/asm/octeon/ |
| H A D | cvmx-spi.h | 5 * This file is part of the OCTEON SDK
7 * Copyright (c) 2003-2008 Cavium Networks
9 * This file is free software; you can redistribute it and/or modify
10 * it under the terms of the GNU General Public License, Version 2, as
13 * This file is distributed in the hope that it will be useful, but
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 <asm/octeon/cvmx-gmxx-defs.h>
37 /* CSR typedefs have been moved to cvmx-csr-*.h */
66 /** Called when interface is up */
[all …]
|
| /linux/Documentation/timers/ |
| H A D | timekeeping.rst | 10 If you grep through the kernel source you will find a number of architecture-
12 architecture-specific overrides of the sched_clock() function and some
17 on this timeline, providing facilities such as high-resolution timers.
18 sched_clock() is used for scheduling and timestamping, and delay timers
23 -------------
25 The purpose of the clock source is to provide a timeline for the system that
28 what time it is.
30 Typically the clock source is a monotonic, atomic counter which will provide
31 n bits which count from 0 to (2^n)-1 and then wraps around to 0 and start over.
32 It will ideally NEVER stop ticking as long as the system is running. It
[all …]
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | timekeeping.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Timekeeping Virtualization for X86-Based Architectures
21 the virtualization of this platform is the plethora of timing devices available
30 The purpose of this document is to collect data and information relevant to
32 information relevant to KVM and hardware-based virtualization.
41 2.1. i8254 - PIT
42 ----------------
44 One of the first timer devices available is the programmable interrupt timer,
46 channels which can be programmed to deliver periodic or one-shot interrupts.
50 speaker. Now the PIT is typically integrated as part of an emulated chipset
[all …]
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-delayed-logging-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 subsystem is based on. This document describes the design and algorithms that
12 the XFS journalling subsystem is based on so that readers may familiarize
19 the basic concepts covered, the design of the delayed logging mechanism is
32 Some objects, such as inodes and dquots, are logged in logical format where the
33 details logged are made up of the changes to in-core structures rather than
34 on-disk structures. Other objects - typically buffers - have their physical
40 The reason for these differences is to keep the amount of log space and CPU time
41 required to process objects being modified as small as possible and hence the
42 logging overhead as low as possible. Some items are very frequently modified,
[all …]
|
| /linux/fs/cramfs/ |
| H A D | README | 2 --------------------------
7 a given directory are contiguous, as this is used by readdir).
9 All data is currently in host-endian format; neither mkcramfs nor the
22 Filename. Not generally null-terminated, but it is
23 null-padded to a multiple of 4 bytes.
25 The order of inode traversal is described as "width-first" (not to be
26 confused with breadth-first); i.e. like depth-first but listing all of
28 same order as `ls -AUR' (but without the /^\..*:$/ directory header
29 lines); put another way, the same order as `find -type d -exec
30 ls -AU1 {} \;'.
[all …]
|
| /linux/Documentation/networking/ |
| H A D | xfrm_sync.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The sync patches work is based on initial patches from
11 The end goal for syncing is to be able to insert attributes + generate
14 The idea is to synchronize the SA so that the takeover machine can do
15 the processing of the SA as accurate as possible if it has access to it.
20 with as minimal loss at failover time.
21 This way a backup stays as closely up-to-date as an active member.
24 it is possible for a lot of the events to be generated.
25 For this reason, we also add a nagle-like algorithm to restrict
27 know if the replay sequence threshold is reached or 10 secs have passed"
[all …]
|
| /linux/drivers/i2c/busses/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 for Cypress CCGx Type-C controller. Individual bus drivers
25 controller is part of the 7101 device, which is an ACPI-compliant
28 This driver can also be built as a module. If so, the module
29 will be called i2c-ali1535.
37 controller is part of the 7101 device, which is an ACPI-compliant
40 This driver can also be built as a module. If so, the module
41 will be called i2c-ali1563.
50 This driver can also be built as a module. If so, the module
51 will be called i2c-ali15x3.
[all …]
|
| /linux/Documentation/bpf/ |
| H A D | kfuncs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. _kfuncs-header-label:
12 BPF Kernel Functions or more commonly known as kfuncs are functions in the Linux
30 ----------------------------
33 This prevents the compiler from optimizing away dead code, as this wrapper kfunc
34 is not invoked anywhere in the kernel itself. It is not necessary to provide a
37 An example is given below::
49 A wrapper kfunc is often needed when we need to annotate parameters of the
54 -------------------------------
56 Similar to BPF helpers, there is sometime need for additional context required
[all …]
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | driver.rst | 5 This document serves as a guide for writers of GPIO chip drivers.
18 line is not general purpose, it is not GPIO and should not be handled by a
19 GPIO chip. The use case is the indicative: certain lines in a system may be
21 of a general purpose I/O. On the other hand a LED driver line may be used as a
25 number, sometime also referred to as ``offset``, which is a unique number
26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
34 This number is purely internal: the hardware number of a particular GPIO
35 line is never made visible outside of the driver.
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | spkguide.txt | 13 Permission is granted to copy, distribute and/or modify this document
16 Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
17 copy of the license is included in the section entitled "GNU Free
22 The purpose of this document is to familiarize users with the user
25 http://linux-speakup.org/. Speakup is a set of patches to the standard
26 Linux kernel source tree. It can be built as a series of modules, or as
30 Speakup. If Speakup is built as a part of a monolithic kernel, and the
31 user is using a hardware synthesizer, then Speakup will be able to
32 provide speech access from the time the kernel is loaded, until the time
33 the system is shutdown. This means that if you have obtained Linux
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | fscrypt.rst | 2 Filesystem-level encryption (fscrypt)
8 fscrypt is a library which filesystems can hook into to support
11 Note: "fscrypt" in this document refers to the kernel-level portion,
12 implemented in ``fs/crypto/``, as opposed to the userspace tool
14 covers the kernel-level portion. For command-line examples of how to
16 <https://github.com/google/fscrypt>`_. Also, it is recommended to use
17 the fscrypt userspace tool, or other existing userspace tools such as
20 <https://source.android.com/security/encryption/file-based>`_, over
25 Unlike dm-crypt, fscrypt operates at the filesystem level rather than
28 filesystem. This is useful for multi-user systems where each user's
[all …]
|