| /Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-memory.json | 8 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
12 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
32 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
62 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read…
72 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Writ…
86 "PublicDescription": "Uncore Fixed Counter - uclks",
124 …channel. This counter is only useful with ECC DRAM devices. This count will increment one time f…
133 …a major mode (selected by a filter) on the given channel. Major modea are channel-wide, and not …
143 …a major mode (selected by a filter) on the given channel. Major modea are channel-wide, and not …
153 …a major mode (selected by a filter) on the given channel. Major modea are channel-wide, and not …
[all …]
|
| /Linux-v6.1/Documentation/virt/hyperv/ |
| D | vmbus.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 VMbus is a software construct provided by Hyper-V to guest VMs. It
7 devices that Hyper-V presents to guest VMs. The control path is
11 and the synthetic device implementation that is part of Hyper-V, and
12 signaling primitives to allow Hyper-V and the guest to interrupt
17 establishes the VMbus control path with the Hyper-V host, then
21 Most synthetic devices offered by Hyper-V have a corresponding Linux
29 * PCI device pass-thru
34 * Key/Value Pair (KVP) exchange with Hyper-V
35 * Hyper-V online backup (a.k.a. VSS)
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-memory.json | 8 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
18 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
28 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
60 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
65 … RD_CAS and WR_CAS Commands; Counts the total number of DRAM CAS commands issued on this channel.",
75 …mmands; Counts the total number of DRAM Read CAS commands issued on this channel (including underf…
80 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
85 …mmands; Counts the total number or DRAM Read CAS commands issued on this channel. This includes b…
125 …S and WR_CAS Commands; Counts the total number of DRAM Write CAS commands issued on this channel.",
130 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read…
[all …]
|
| /Linux-v6.1/Documentation/trace/ |
| D | stm.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 protocol multiplexing data from multiple trace sources, each one of
10 which is assigned a unique pair of master and channel. While some of
14 master/channel combination from this pool.
17 sources can only be identified by master/channel combination, so in
19 involves multiple trace sources, it needs to be able to map those
20 master/channel pairs to the trace sources that it understands.
23 master 7 channel 15, while arbitrary user applications can use masters
34 associated with it, located in "stp-policy" subsystem directory in
40 $ ls /config/stp-policy/dummy_stm.my-policy/user
[all …]
|
| /Linux-v6.1/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 --------------------
21 0 C 0----------->: : +======>(other CTI channel IO)
22 0 P 0<-----------: : v
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
25 ####### in_trigs : : (id 0-3) ***** ::::::: v
26 # ETM #----------->: : ^ #######
27 # #<-----------: : +---# ETR #
31 channels. When an input trigger becomes active, the attached channel will
32 become active. Any output trigger attached to that channel will also
[all …]
|
| /Linux-v6.1/drivers/remoteproc/ |
| 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
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
31 * struct pru_irq_rsc - PRU firmware section header for IRQ data
|
| /Linux-v6.1/include/uapi/linux/caif/ |
| D | caif_socket.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
4 * Copyright (C) ST-Ericsson AB 2010
16 * enum caif_link_selector - Physical Link Selection.
17 * @CAIF_LINK_HIGH_BANDW: Physical interface for high-bandwidth
19 * @CAIF_LINK_LOW_LATENCY: Physical interface for low-latency
24 * setting up CAIF Channels when multiple CAIF Link Layers exists.
32 * enum caif_channel_priority - CAIF channel priorities.
34 * @CAIF_PRIO_MIN: Min priority for a channel.
35 * @CAIF_PRIO_LOW: Low-priority channel.
38 * @CAIF_PRIO_MAX: Max priority for channel
[all …]
|
| /Linux-v6.1/Documentation/hid/ |
| D | uhid.rst | 2 UHID - User-space I/O driver support for HID subsystem
5 UHID allows user-space to implement HID transport drivers. Please see
6 hid-transport.rst for an introduction into HID transport drivers. This document
9 With UHID, a user-space transport driver can create kernel hid-devices for each
10 device connected to the user-space controlled bus. The UHID API defines the I/O
11 events provided from the kernel to user-space and vice versa.
13 There is an example user-space application in ./samples/uhid/uhid-example.c
16 ------------
18 UHID is accessed through a character misc-device. The minor number is allocated
25 write()'ing "struct uhid_event" objects. Non-blocking operations are supported
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/spi/ |
| D | sprd,spi-adi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/spi/sprd,spi-adi.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Orson Zhai <orsonzhai@gmail.com>
12 - Baolin Wang <baolin.wang7@gmail.com>
13 - Chunyan Zhang <zhang.lyra@gmail.com>
16 ADI is the abbreviation of Anolog-Digital interface, which is used to access
25 which means we can just link one analog chip address to one hardware channel,
26 then users can access the mapped analog chip address by this hardware channel
[all …]
|
| /Linux-v6.1/Documentation/mm/ |
| D | multigen_lru.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Gen LRU
6 The multi-gen LRU is an alternative LRU implementation that optimizes
14 ----------
20 * Simple self-correcting heuristics
23 implementations. In the multi-gen LRU, each generation represents a
25 (time-based) common frame of reference and therefore help make better
41 choices; thus self-correction is necessary.
43 The benefits of simple self-correcting heuristics are self-evident.
51 -----------
[all …]
|
| /Linux-v6.1/drivers/comedi/drivers/ |
| D | ni_labpc.c | 1 // SPDX-License-Identifier: GPL-2.0+
4 * Driver for National Instruments Lab-PC series boards and compatibles
5 * Copyright (C) 2001-2003 Frank Mori Hess <fmhess@users.sourceforge.net>
10 * Description: National Instruments Lab-PC (& compatibles)
11 * Devices: [National Instruments] Lab-PC-1200 (lab-pc-1200),
12 * Lab-PC-1200AI (lab-pc-1200ai), Lab-PC+ (lab-pc+)
16 * Configuration options - ISA boards:
17 * [0] - I/O port base address
18 * [1] - IRQ (optional, required for timed or externally triggered
20 * [2] - DMA channel (optional)
[all …]
|
| D | ni_labpc_cs.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Driver for National Instruments daqcard-1200 boards
15 * Description: National Instruments Lab-PC (& compatibles)
17 * Devices: [National Instruments] DAQCard-1200 (daqcard-1200)
21 * helping to debug daqcard-1200 support.
31 * The daqcard-1200 has quirky chanlist requirements when scanning multiple
32 * channels. Multiple channel scan sequence must start at highest channel,
33 * then decrement down to channel 0. Chanlists consisting of all one channel
37 * 340988a (daqcard-1200)
47 .name = "daqcard-1200",
[all …]
|
| D | comedi_bond.c | 1 // SPDX-License-Identifier: GPL-2.0+
4 * A Comedi driver to 'bond' or merge multiple drivers and devices as one.
6 * COMEDI - Linux Control and Measurement Device Interface
13 * Description: A driver to 'bond' (merge) multiple subdevices from multiple
17 * Updated: Mon, 10 Oct 00:18:25 -0500
20 * This driver allows you to 'bond' (merge) multiple comedi subdevices
26 * different subdevices in the application -- you just worry about
27 * indexing one linear array of channel id's.
33 * Commands aren't supported -- although it would be cool if they were.
36 * List of comedi-minors to bond. All subdevices of the same type
[all …]
|
| /Linux-v6.1/Documentation/driver-api/iio/ |
| D | core.rst | 8 :file:`drivers/iio/industrialio-*`
11 ----------------------
13 * struct iio_dev - industrial I/O device
14 * iio_device_alloc() - allocate an :c:type:`iio_dev` from a driver
15 * iio_device_free() - free an :c:type:`iio_dev` from a driver
16 * iio_device_register() - register a device with the IIO subsystem
17 * iio_device_unregister() - unregister a device from the IIO
63 :file:`Documentation/ABI/testing/sysfs-bus-iio` file in the Linux kernel
69 struct iio_chan_spec - specification of a single channel
71 An IIO device channel is a representation of a data channel. An IIO device can
[all …]
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | max16065.rst | 11 Addresses scanned: -
15 http://datasheets.maxim-ic.com/en/ds/MAX16065-MAX16066.pdf
21 Addresses scanned: -
25 http://datasheets.maxim-ic.com/en/ds/MAX16067.pdf
31 Addresses scanned: -
35 http://datasheets.maxim-ic.com/en/ds/MAX16068.pdf
41 Addresses scanned: -
45 http://datasheets.maxim-ic.com/en/ds/MAX16070-MAX16071.pdf
47 Author: Guenter Roeck <linux@roeck-us.net>
51 -----------
[all …]
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | slimbus.rst | 9 ----------------
12 configuration, and is a 2-wire multi-drop implementation (clock, and data).
15 (System-on-Chip) and peripheral components (typically codec). SLIMbus uses
16 Time-Division-Multiplexing to accommodate multiple data channels, and
17 a control channel.
19 The control channel is used for various control functions such as bus
21 reading/writing device specific values), or multicast (e.g. data channel
24 A data channel is used for data-transfer between 2 SLIMbus devices. Data
25 channel uses dedicated ports on the device.
28 ---------------------
[all …]
|
| /Linux-v6.1/include/linux/platform_data/ |
| D | dma-ste-dma40.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright (C) ST-Ericsson SA 2007-2010
4 * Author: Per Forlin <per.forlin@stericsson.com> for ST-Ericsson
5 * Author: Jonas Aaberg <jonas.aberg@stericsson.com> for ST-Ericsson
20 * Size is in the units of addr-widths (1,2,4,8 bytes)
21 * Larger transfers will be split up to multiple linked desc
26 #define STEDMA40_DEV_DST_MEMORY (-1)
27 #define STEDMA40_DEV_SRC_MEMORY (-1)
49 /* The value 4 indicates that PEN-reg shall be set to 0 */
74 * struct stedma40_half_channel_info - dst/src channel configuration
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | uncore-memory.json | 8 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
18 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
28 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
60 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
65 … RD_CAS and WR_CAS Commands; Counts the total number of DRAM CAS commands issued on this channel.",
75 …mmands; Counts the total number of DRAM Read CAS commands issued on this channel (including underf…
80 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
85 …mmands; Counts the total number or DRAM Read CAS commands issued on this channel. This includes b…
125 …S and WR_CAS Commands; Counts the total number of DRAM Write CAS commands issued on this channel.",
130 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read…
[all …]
|
| /Linux-v6.1/include/sound/sof/ |
| 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
19 * a single source channel,
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
33 * Channel mask is followed by array of coefficients in Q2.30 format,
34 * one per each channel set in the mask (left to right, LS bit set in the
[all …]
|
| /Linux-v6.1/drivers/net/ethernet/sfc/falcon/ |
| D | efx.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Copyright 2005-2006 Fen Systems Ltd.
5 * Copyright 2006-2013 Solarflare Communications Inc.
46 void __ef4_rx_packet(struct ef4_channel *channel);
49 static inline void ef4_rx_flush_packet(struct ef4_channel *channel) in ef4_rx_flush_packet() argument
51 if (channel->rx_pkt_n_frags) in ef4_rx_flush_packet()
52 __ef4_rx_packet(channel); in ef4_rx_flush_packet()
63 /* Maximum number of TCP segments we support for soft-TSO */
75 return efx->rss_spread > 1; in ef4_rss_enabled()
83 * ef4_filter_insert_filter - add or replace a filter
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/display/ |
| D | mipi-dsi-bus.txt | 8 This document describes DSI bus-specific properties only or defines existing
25 - #address-cells: The number of cells required to represent an address on the
26 bus. DSI peripherals are addressed using a 2-bit virtual channel number, so
29 - #size-cells: Should be 0. There are cases where it makes sense to use a
33 - clock-master: boolean. Should be enabled if the host is being used in
43 ------------------------------------------------------
49 device-specific properties.
52 - reg: The virtual channel number of a DSI peripheral. Must be in the range
55 Some DSI peripherals respond to more than a single virtual channel. In that
57 - The reg property can take multiple entries, one for each virtual channel
[all …]
|
| /Linux-v6.1/include/uapi/linux/ |
| D | firewire-cdev.h | 4 * Copyright (C) 2005-2007 Kristian Hoegsberg <krh@bitplanet.net>
31 #include <linux/firewire-constants.h>
50 * struct fw_cdev_event_common - Common part of all fw_cdev_event_* types
67 * struct fw_cdev_event_bus_reset - Sent when a bus reset occurred
97 * struct fw_cdev_event_response - Sent when a response packet was received
125 * struct fw_cdev_event_request - Old version of &fw_cdev_event_request2
129 * @offset: The offset into the 48-bit per-node address space
130 * @handle: Reference to the kernel-side pending request
149 * struct fw_cdev_event_request2 - Sent on incoming request to an address region
153 * @offset: The offset into the 48-bit per-node address space
[all …]
|
| /Linux-v6.1/Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 15 The dmatest module can be configured to test a specific channel. It can also
16 test multiple channels at the same time, and it can start multiple threads
17 competing for the same channel.
21 capability of the following: DMA_MEMCPY (memory-to-memory), DMA_MEMSET
22 (const-to-memory or memory-to-memory, when emulated), DMA_XOR, DMA_PQ.
28 Part 1 - How to build the test module
33 Device Drivers -> DMA Engine support -> DMA Test client
38 Part 2 - When dmatest is built as a module
43 % modprobe dmatest timeout=2000 iterations=1 channel=dma0chan0 run=1
50 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/mailbox/ |
| D | ti,omap-mailbox.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
33 single IP instance. DRA7xx has multiple instances with different number of
35 lines can also be routed to different processor sub-systems on DRA7xx as they
38 combine multiple clusters into a single IP block present within the Main
42 block comprising of multiple clusters, but the number of clusters are
49 within a SoC. The sub-mailboxes (actual communication channels) are
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/net/wireless/ |
| D | mediatek,mt76.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (c) 2018-2019 The Linux Foundation. All rights reserved.
5 ---
7 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 - Felix Fietkau <nbd@nbd.name>
13 - Lorenzo Bianconi <lorenzo@kernel.org>
14 - Ryder Lee <ryder.lee@mediatek.com>
24 - $ref: ieee80211.yaml#
29 - mediatek,mt76
30 - mediatek,mt7628-wmac
[all …]
|
