Home
last modified time | relevance | path

Searched +full:many +full:- +full:to +full:- +full:one (Results 1 – 25 of 585) sorted by relevance

12345678910>>...24

/Documentation/i2c/
Dsummary.rst2 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 …]
/Documentation/userspace-api/media/drivers/
Dimx-uapi.rst1 .. 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 …]
/Documentation/kernel-hacking/
Dfalse-sharing.rst1 .. SPDX-License-Identifier: GPL-2.0
10 coherence of one cache line stored in multiple CPU's caches; then
20 Member 'refcount'(A) and 'name'(B) _share_ one cache line like below::
22 +-----------+ +-----------+
24 +-----------+ +-----------+
28 +----------------------+ +----------------------+
30 +----------------------+ +----------------------+
32 ---------------------------+------------------+-----------------------------
34 +----------------------+
36 +----------------------+
[all …]
/Documentation/devicetree/bindings/perf/
Driscv,pmu.yaml1 # 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 …]
/Documentation/process/
Dmaintainer-soc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 --------
10 The SoC subsystem is a place of aggregation for SoC-specific code.
13 * devicetrees for 32- & 64-bit ARM and RISC-V
14 * 32-bit ARM board files (arch/arm/mach*)
15 * 32- & 64-bit ARM defconfigs
16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
17 ARM, RISC-V and Loongarch
19 These "SoC-specific drivers" do not include clock, GPIO etc drivers that have
20 other top-level maintainers. The drivers/soc/ directory is generally meant
[all …]
Dcve.rst6 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 …]
Dprogramming-language.rst6 The kernel is written in the C programming language [c-language]_.
8 under ``-std=gnu11`` [gcc-c-dialect-options]_: the GNU dialect of ISO C11.
12 This dialect contains many extensions to the language [gnu-extensions]_,
13 and many of them are used within the kernel as a matter of course.
16 ----------
18 One of the common extensions used throughout the kernel are attributes
19 [gcc-attribute-syntax]_. Attributes allow to introduce
20 implementation-defined semantics to language entities (like variables,
21 functions or types) without having to make significant syntactic changes
22 to the language (e.g. adding a new keyword) [n2049]_.
[all …]
/Documentation/input/
Dgamepad.rst1 ---------------------------
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 …]
/Documentation/devicetree/bindings/sound/
Dmt6358.txt10 - compatible - "string" - One of:
11 "mediatek,mt6358-sound"
12 "mediatek,mt6366-sound"
13 - Avdd-supply : power source of AVDD
16 - mediatek,dmic-mode : Indicates how many data pins are used to transmit two
17 channels of PDM signal. 0 means two wires, 1 means one wire. Default
23 compatible = "mediatek,mt6358-sound";
24 Avdd-supply = <&mt6358_vaud28_reg>;
25 mediatek,dmic-mode = <0>;
/Documentation/filesystems/nfs/
Dknfsd-stats.rst5 :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 …]
/Documentation/devicetree/bindings/
Dwriting-bindings.rst1 .. SPDX-License-Identifier: GPL-2.0
8 every rule, there are exceptions and bindings have many gray areas.
10 For guidelines related to patches, see
11 Documentation/devicetree/bindings/submitting-patches.rst
17 - DO attempt to make bindings complete even if a driver doesn't support some
21 - DON'T refer to Linux or "device driver" in bindings. Bindings should be
24 - DO use node names matching the class of the device. Many standard names are
25 defined in the DT Spec. If there isn't one, consider adding it.
27 - DO check that the example matches the documentation especially after making
30 - DON'T create nodes just for the sake of instantiating drivers. Multi-function
[all …]
/Documentation/admin-guide/device-mapper/
Dkcopyd.rst5 Kcopyd provides the ability to copy a range of sectors from one block-device
6 to one or more other block-devices, with an asynchronous completion
7 notification. It is used by dm-snapshot and dm-mirror.
9 Users of kcopyd must first create a client and indicate how many memory pages
10 to set aside for their copy jobs. This is done with a call to
16 To start a copy job, the user must set up io_region structures to describe
18 block-device along with the starting sector and size of the region. The source
19 of the copy is given as one io_region structure, and the destinations of the
28 To start the copy, the user calls kcopyd_copy(), passing in the client
29 pointer, pointers to the source and destination io_regions, the name of a
[all …]
/Documentation/arch/arm/samsung/
Doverview.rst6 ------------
8 The Samsung range of ARM SoCs spans many similar devices, from the initial
9 ARM9 through to the newest ARM cores. This document shows an overview of
10 the current kernel support, how to use it and where to find the code
15 - S3C64XX: S3C6400 and S3C6410
16 - S5PC110 / S5PV210
20 -------------
23 unifying all the SoCs into one kernel.
26 - S5PC110 specific default configuration
28 - S5PV210 specific default configuration
[all …]
/Documentation/driver-api/usb/
Dgadget.rst11 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 …]
/Documentation/arch/arm/
Dvlocks.rst2 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 …]
/Documentation/arch/x86/
Dtlb.rst1 .. SPDX-License-Identifier: GPL-2.0
10 1. Flush the entire TLB with a two-instruction sequence. This is
12 from areas other than the one we are trying to flush will be
14 2. Use the invlpg instruction to invalidate a single page at a
15 time. This could potentially cost many more instructions, but
17 damage to other TLB entries.
19 Which method to do depends on a few things:
32 4. The microarchitecture. The TLB has become a multi-level
34 expensive relative to single-page flushes.
39 well. There is essentially no "right" point to choose.
[all …]
/Documentation/timers/
Dhpet.rst8 Each HPET has one fixed-rate counter (at 10+ MHz, hence "High Precision")
9 and up to 32 comparators. Normally three or more comparators are provided,
10 each of which can generate oneshot interrupts and at least one of which has
11 additional hardware to support periodic interrupts. The comparators are
15 HPET devices can support two interrupt routing modes. In one mode, the
17 role. Many x86 BIOS writers don't route HPET interrupts at all, which
24 platform code which uses timer 0 or 1 as the main timer to intercept HPET
/Documentation/ABI/testing/
Dsysfs-devices-soc5 The /sys/devices/ directory contains a sub-directory for each
6 System-on-Chip (SoC) device on a running platform. Information
13 devices would be better suited to appear as children of that SoC.
19 Read-only attribute common to all SoCs. Contains the SoC machine
26 Read-only attribute common to all SoCs. Contains SoC family name
29 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
34 This manufacturer’s identification code is defined by one
36 data bits plus one (1) odd parity bit. It is a single field,
37 limiting the possible number of vendors to 126. To expand
44 may be extended to multiple continuation codes followed
[all …]
/Documentation/trace/
Dstm.rst1 .. SPDX-License-Identifier: GPL-2.0
9 protocol multiplexing data from multiple trace sources, each one of
11 these masters and channels are statically allocated to certain
12 hardware trace sources, others are available to software. Software
13 trace sources are usually free to pick for themselves any
18 order for the decoder to be able to make sense of the trace that
19 involves multiple trace sources, it needs to be able to map those
20 master/channel pairs to the trace sources that it understands.
22 For instance, it is helpful to know that syslog messages come on
24 48 to 63 and channels 0 to 127.
[all …]
/Documentation/doc-guide/
Dmaintainer-profile.rst1 .. SPDX-License-Identifier: GPL-2.0
13 fuzzier than normal. Many other subsystem maintainers like to keep control
14 of portions of Documentation/, and many more freely apply changes there
19 The mailing list for documentation is linux-doc@vger.kernel.org. Patches
20 should be made against the docs-next tree whenever possible.
23 -------------------------
28 to avoid unsightly misunderstandings about how things will be rendered.
30 All new documentation (including additions to existing documents) should
38 ---------------
41 the merge window. The docs tree tends to close late before the merge
[all …]
/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marek Szyprowski <m.szyprowski@samsung.com>
14 physical memory chunks visible as a contiguous region to DMA-capable peripheral
15 devices like MFC, FIMC, FIMD, GScaler, FIMC-IS and so forth.
17 System MMU is an IOMMU and supports identical translation table format to
20 another capabilities like L2 TLB or block-fetch buffers to minimize translation
23 System MMUs are in many to one relation with peripheral devices, i.e. single
24 peripheral device might have multiple System MMUs (usually one for each bus
[all …]
/Documentation/driver-api/gpio/
Dintro.rst9 The documents in this directory give detailed instructions on how to access
10 GPIOs in drivers, and how to write a driver for a device that provides GPIOs
17 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
18 digital signal. They are provided from many kinds of chips, and are familiar
19 to Linux developers working with embedded and custom hardware. Each GPIO
20 represents a bit connected to a particular pin, or "ball" on Ball Grid Array
21 (BGA) packages. Board schematics show which external hardware connects to
23 passes such pin configuration data to drivers.
25 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
26 non-dedicated pin can be configured as a GPIO; and most chips have at least
[all …]
/Documentation/mm/
Dremap_file_pages.rst5 The remap_file_pages() system call is used to create a nonlinear mapping,
8 over using repeated calls to mmap(2) is that the former approach does not
9 require the kernel to create additional VMA (Virtual Memory Area) data
12 Supporting of nonlinear mapping requires significant amount of non-trivial
13 code in kernel virtual memory subsystem including hot paths. Also to get
14 nonlinear mapping work kernel need a way to distinguish normal page table
17 architectures. It would be nice to free up the flag for other usage.
19 Fortunately, there are not many users of remap_file_pages() in the wild.
20 It's only known that one enterprise RDBMS implementation uses the syscall
21 on 32-bit systems to map files bigger than can linearly fit into 32-bit
[all …]
/Documentation/filesystems/
Dhpfs.rst1 .. SPDX-License-Identifier: GPL-2.0
7 1998-2004, Mikulas Patocka
10 :homepage: https://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi
14 Chris Smith, 1993, original read-only HPFS, some code and hpfs structures file
25 attributes. Mode is inverted umask - for example umask 027 gives owner
27 that for files mode is anded with 0666. If you want files to have 'x'
32 CR/LF -> LF conversion, if auto, decision is made according to extension
33 - there is a list of text extensions (I thing it's better to not convert
34 text file than to damage binary file). If you want to change that list,
36 heuristic algorithm that I removed. I thing it's danger to let the
[all …]
/Documentation/hwmon/
Dltc4261.rst10 Addresses scanned: -
16 Author: Guenter Roeck <linux@roeck-us.net>
20 -----------
22 The LTC4261/LTC4261-2 negative voltage Hot Swap controllers allow a board
23 to be safely inserted and removed from a live backplane.
27 -----------
30 which can be safely used to identify the chip. You will have to instantiate
37 $ echo ltc4261 0x10 > /sys/bus/i2c/devices/i2c-1/new_device
41 -------------
54 The chip has two voltage sensors, but only one set of voltage alarm status bits.
[all …]

12345678910>>...24