| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | nxp,pcf8575.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: PCF857x-compatible I/O expanders
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
13 The PCF857x-compatible chips have "quasi-bidirectional" I/O lines that can be
14 driven high by a pull-up current source or driven low to ground. This
25 - maxim,max7328
26 - maxim,max7329
27 - nxp,pca8574
[all …]
|
| /linux/Documentation/trace/rv/ |
| H A D | deterministic_automata.rst | 10 - *X* is the set of states;
11 - *E* is the finite set of events;
12 - x\ :subscript:`0` is the initial state;
13 - X\ :subscript:`m` (subset of *X*) is the set of marked (or final) states.
14 - *f* : *X* x *E* -> *X* $ is the transition function. It defines the state
22 - *X* = { ``preemptive``, ``non_preemptive``}
23 - *E* = { ``preempt_enable``, ``preempt_disable``, ``sched_waking``}
24 - x\ :subscript:`0` = ``preemptive``
25 - X\ :subscript:`m` = {``preemptive``}
26 - *f* =
[all …]
|
| /linux/tools/gpio/ |
| H A D | gpio-hammer.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * gpio-hammer - example swiss army knife to shake GPIO lines on a system
8 * gpio-hammer -n <device-name> -o <offset1> -o <offset2>
23 #include "gpio-utils.h"
25 int hammer_device(const char *device_name, unsigned int *lines, int num_lines, in hammer_device() argument
30 char swirr[] = "-\\|/"; in hammer_device()
39 ret = gpiotools_request_line(device_name, lines, num_lines, in hammer_device()
40 &config, "gpio-hammer"); in hammer_device()
55 fprintf(stdout, "Hammer lines ["); in hammer_device()
57 fprintf(stdout, "%u", lines[i]); in hammer_device()
[all …]
|
| /linux/tools/thermal/tmon/ |
| H A D | tmon.8 | 2 # SPDX-License-Identifier: GPL-2.0
4 \fBtmon\fP - A monitoring and testing tool for Linux kernel thermal subsystem
13 real-time thermal data; tune
16 states via sysfs.
22 - show thermal zone information
23 - show cooling device information
24 - show trip point binding within each thermal zone
25 - show trip point and cooling device instance bindings
28 - show temperature of all thermal zones w.r.t. its trip points and types
29 - show states of all cooling devices
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | uncore-cache.json | 59 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
70 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
81 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
92 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
103 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
114 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
125 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
136 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
147 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
158 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| H A D | uncore-cache.json | 59 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
70 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
81 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
92 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
103 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
114 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
125 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
136 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
147 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
158 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
[all …]
|
| /linux/arch/arm/boot/dts/ti/omap/ |
| H A D | dra72-evm-common.dtsi | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2014-2016 Texas Instruments Incorporated - https://www.ti.com/
5 /dts-v1/;
8 #include "dra7-ipu-dsp-common.dtsi"
9 #include <dt-bindings/gpio/gpio.h>
10 #include <dt-bindings/clock/ti-dra7-atl.h>
13 compatible = "ti,dra72-evm", "ti,dra722", "ti,dra72", "ti,dra7";
20 stdout-path = &uart1;
23 evm_12v0: fixedregulator-evm12v0 {
25 compatible = "regulator-fixed";
[all …]
|
| H A D | dra7-evm.dts | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2013 Texas Instruments Incorporated - https://www.ti.com/
5 /dts-v1/;
8 #include "dra7-evm-common.dtsi"
9 #include "dra74x-mmc-iodelay.dtsi"
13 compatible = "ti,dra7-evm", "ti,dra742", "ti,dra74", "ti,dra7";
20 evm_12v0: fixedregulator-evm_12v0 {
22 compatible = "regulator-fixed";
23 regulator-name = "evm_12v0";
24 regulator-min-microvolt = <12000000>;
[all …]
|
| /linux/include/linux/mfd/ |
| H A D | tps65010.h | 34 * ----------------------------------------------------------------------------
36 * ----------------------------------------------------------------------------
109 * ----------------------------------------------------------------------------
111 * ----------------------------------------------------------------------------
127 * ----------------------------------------------------------------------------
129 * ----------------------------------------------------------------------------
133 * 0 mA -- DON'T DRAW (might supply power instead)
134 * 100 mA -- usb unit load (slowest charge rate)
135 * 500 mA -- usb high power (fast battery charge)
180 * struct tps65010_board - packages GPIO and LED lines
[all …]
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 15 Data-Structure Relationships
25 .. kernel-figure:: BigTreeClassicRCU.svg
34 which results in a three-level ``rcu_node`` tree.
38 The purpose of this combining tree is to allow per-CPU events
39 such as quiescent states, dyntick-idle transitions,
42 Quiescent states are recorded by the per-CPU ``rcu_data`` structures,
43 and other events are recorded by the leaf-level ``rcu_node``
54 As can be seen from the diagram, on a 64-bit system
55 a two-level tree with 64 leaves can accommodate 1,024 CPUs, with a fanout
58 +-----------------------------------------------------------------------+
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A D | uncore-cache.json | 1025 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1036 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1047 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1058 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1069 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1080 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1091 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1102 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1113 …ed in Counter 0. The filtering available is found in the control register - threshold, invert an…
1249 "BriefDescription": "Distress signal asserted : DPT Stalled - IV",
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | uncore-cache.json | 1113 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1124 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1135 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1146 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1157 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1168 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1179 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1190 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1201 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
1212 …s an RFO, it would need to invalidate the lines. This event can be filtered based on who triggere…
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | vfio.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
37 /* Two-stage IOMMU */
43 * The No-IOMMU IOMMU offers no translation or isolation for devices and
44 * supports no ioctls outside of VFIO_CHECK_EXTENSION. Use of VFIO's No-IOMMU
100 /* -------- IOCTLs for VFIO file descriptor (/dev/vfio/vfio) -------- */
103 * VFIO_GET_API_VERSION - _IO(VFIO_TYPE, VFIO_BASE + 0)
114 * VFIO_CHECK_EXTENSION - _IOW(VFIO_TYPE, VFIO_BASE + 1, __u32)
123 * VFIO_SET_IOMMU - _IOW(VFIO_TYPE, VFIO_BASE + 2, __s32)
130 * Return: 0 on success, -errno on failure
135 /* -------- IOCTLs for GROUP file descriptors (/dev/vfio/$GROUP) -------- */
[all …]
|
| /linux/drivers/gpio/ |
| H A D | gpio-pcf857x.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
61 * that pin be used as an input; it's not an open-drain model, but acts
62 * a bit like one. This is described as "quasi-bidirectional"; read the
82 /*-------------------------------------------------------------------------*/
84 /* Talk to 8-bit I/O expander */
96 /* Talk to 16-bit I/O expander */
118 /*-------------------------------------------------------------------------*/
125 mutex_lock(&gpio->lock); in pcf857x_input()
126 gpio->out |= (1 << offset); in pcf857x_input()
127 status = gpio->write(gpio->client, gpio->out); in pcf857x_input()
[all …]
|
| /linux/drivers/macintosh/ |
| H A D | via-macii.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Device driver for the via ADB on (many) Mac II-class machines
13 * 1999-08-02 (jmt) - Initial rewrite for Unified ADB.
14 * 2000-03-29 Tony Mantler <tonym@mac.linux-m68k.org>
15 * - Big overhaul, should actually work now.
16 * 2006-12-31 Finn Thain - Another overhaul.
24 * ftp://ftp.apple.com/developer/Tool_Chest/Devices_-_Hardware/Apple_Desktop_Bus/
39 /* VIA registers - spaced 0x200 bytes apart */
41 #define B 0 /* B-side data */
42 #define A RS /* A-side data */
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A D | uncore-cache.json | 25 "BriefDescription": "LLC misses - Uncacheable reads (from cpu) . Derived from unc_cha_tor_inserts.ia_miss",
694 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
705 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
716 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
726 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
737 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines
[all...] |
| /linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | uncore-cache.json | 637 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
648 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
659 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
669 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoop(s).",
680 "PublicDescription": "Counts the number of transactions that trigger a configurable number of cross snoops. Cores are snooped if the transaction looks up the cache and determines that it is necessary based on the operation type and what CoreValid bits are set. For example, if 2 CV bits are set on a data read, the cores must have the data in S state so it is not necessary to snoop them. However, if only 1 CV bit is set the core my have modified the data. If the transaction was an RFO, it would need to invalidate the lines. This event can be filtered based on who triggered the initial snoo
[all...] |
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-raid.rst | 2 dm-raid
5 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
6 It allows the MD RAID drivers to be accessed using a device-mapper
11 -----------------------
26 - Transitory layout
29 - rotating parity 0 with data continuation
32 - rotating parity N with data continuation
35 - rotating parity 0 with data restart
38 - rotating parity N with data restart
41 - rotating parity zero (left-to-right) with data restart
[all …]
|
| /linux/drivers/gpu/drm/xe/ |
| H A D | xe_devcoredump.c | 1 // SPDX-License-Identifier: MIT
44 * The 'data' file contains a snapshot of the HW and driver states at the time
55 * .. code-block:: shell
61 * hangs can be a consequence of the initial hang. For this reason a snapshot
80 return &q->gt->uc.guc; in exec_queue_to_guc()
95 ss = &coredump->snapshot; in __xe_devcoredump_read()
104 drm_printf(&p, "Reason: %s\n", ss->reason); in __xe_devcoredump_read()
108 ts = ktime_to_timespec64(ss->snapshot_time); in __xe_devcoredump_read()
110 ts = ktime_to_timespec64(ss->boot_time); in __xe_devcoredump_read()
112 drm_printf(&p, "Process: %s [%d]\n", ss->process_name, ss->pid); in __xe_devcoredump_read()
[all …]
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.lpfc | 2 * Please read the associated RELEASE-NOTES file !!!
8 * Fixed build warning for 2.6.12-rc2 kernels: mempool_alloc now
17 to luns on nodes in NPR or other relevant states (PLOGI,
19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1.
26 * Added PCI ID for LP10000-S.
31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent
33 - was causing spurious 0710 messages.
50 * Changed a few lines from patch submitted by Christoph Hellwig
55 - stop using volatile. if you need special ordering use memory
57 - switch lpfc_sli_pcimem_bcopy to take void * arguments.
[all …]
|
| /linux/drivers/i2c/algos/ |
| H A D | i2c-algo-bit.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * i2c-algo-bit.c: i2c driver algorithms for bit-shift adapters
5 * Copyright (C) 1995-2000 Simon G. Vogl
17 #include <linux/i2c-algo-bit.h>
20 /* ----- global defines ----------------------------------------------- */
33 /* ----- global variables --------------------------------------------- */
35 static int bit_test; /* see if the line-setting functions work */
37 MODULE_PARM_DESC(bit_test, "lines testing - 0 off; 1 report; 2 fail if stuck");
43 "debug level - 0 off; 1 normal; 2 verbose; 3 very verbose");
46 /* --- setting states on the bus with the right timing: --------------- */
[all …]
|
| /linux/drivers/net/slip/ |
| H A D | slhc.c | 3 * over low speed serial lines).
21 * - Initial distribution.
28 * - 01-31-90 initial adaptation (from 1.19)
29 * PPP.05 02-15-90 [ks]
30 * PPP.08 05-02-90 [ks] use PPP protocol field to signal compression
31 * PPP.15 09-90 [ks] improve mbuf handling
32 * PPP.16 11-02 [karn] substantially rewritten to use NOS facilities
34 * - Feb 1991 Bill_Simpson@um.cc.umich.edu
39 * - Jul 1994 Dmitry Gorodchanin
41 * - Oct 1994 Dmitry Gorodchanin
[all …]
|
| /linux/tools/arch/x86/kcpuid/ |
| H A D | cpuid.csv | 1 # SPDX-License-Identifier: CC0-1.0
2 # Generator: x86-cpuid-db v2.4
5 # Auto-generated file.
6 # Please submit all updates and bugfixes to https://x86-cpuid.org
16 0x0, 0, ebx, 31:0, cpu_vendorid_0 , CPU vendor ID string bytes 0 - 3
17 0x0, 0, ecx, 31:0, cpu_vendorid_2 , CPU vendor ID string bytes 8 - 11
18 0x0, 0, edx, 31:0, cpu_vendorid_1 , CPU vendor ID string bytes 4 -
[all...] |
| /linux/Documentation/spi/ |
| H A D | spi-summary.rst | 5 02-Feb-2012
8 ------------
15 and parallel data lines with "Master Out, Slave In" (MOSI) or "Master In,
17 clocking modes through which data is exchanged; mode-0 and mode-3 are most
32 - SPI may be used for request/response style device protocols, as with
35 - It may also be used to stream data in either direction (half duplex),
38 - Some devices may use eight bit words. Others may use different word
39 lengths, such as streams of 12-bit or 20-bit digital samples.
41 - Words are usually sent with their most significant bit (MSB) first,
44 - Sometimes SPI is used to daisy-chain devices, like shift registers.
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | spkguide.txt | 16 Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
25 http://linux-speakup.org/. Speakup is a set of patches to the standard
72 acntsa -- Accent SA
73 acntpc -- Accent PC
74 apollo -- Apollo
75 audptr -- Audapter
76 bns -- Braille 'n Speak
77 dectlk -- DecTalk Express (old and new, db9 serial only)
78 decext -- DecTalk (old) External
79 dtlk -- DoubleTalk PC
[all …]
|