| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-memory.json | 7 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
11 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
27 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
51 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read…
59 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Writ…
70 "PublicDescription": "Uncore Fixed Counter - uclks",
104 …channel. This counter is only useful with ECC DRAM devices. This count will increment one time f…
112 …a major mode (selected by a filter) on the given channel. Major modea are channel-wide, and not …
121 …a major mode (selected by a filter) on the given channel. Major modea are channel-wide, and not …
130 …a major mode (selected by a filter) on the given channel. Major modea are channel-wide, and not …
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-memory.json | 7 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
16 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
25 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
54 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
58 … RD_CAS and WR_CAS Commands; Counts the total number of DRAM CAS commands issued on this channel.",
67 …mmands; Counts the total number of DRAM Read CAS commands issued on this channel (including underf…
72 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
76 …mmands; Counts the total number or DRAM Read CAS commands issued on this channel. This includes b…
110 …S and WR_CAS Commands; Counts the total number of DRAM Write CAS commands issued on this channel.",
115 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/ |
| D | uncore-memory.json | 7 …ts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issued on this channel. This …
17 …"Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.",
27 …All Activates : Counts the number of DRAM Activate commands sent on this channel. Activate comman…
36 …due to Bypass : Counts the number of DRAM Activate commands sent on this channel. Activate comman…
45 "PublicDescription": "Counts the total number of DRAM CAS commands issued on this channel.",
54 …ts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issued on this channel. This …
59 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre",
63 …_CAS commands w/auto-pre : DRAM RD_CAS and WR_CAS Commands : Counts the total number or DRAM Read …
81 …tion": "Counts the total number of DRAM Read CAS commands issued on this channel. This includes b…
99 …"Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.",
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr-channel.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr-channel.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LPDDR channel with chip/rank topology description
10 An LPDDR channel is a completely independent set of LPDDR pins (DQ, CA, CS,
16 - Julius Werner <jwerner@chromium.org>
21 - jedec,lpddr2-channel
22 - jedec,lpddr3-channel
23 - jedec,lpddr4-channel
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/ |
| D | fsl,rpmsg.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shengjiu Wang <shengjiu.wang@nxp.com>
15 Linux side is a device which provides audio service by rpmsg channel.
18 Cortex-A and Cortex-M.
21 - $ref: sound-card-common.yaml#
26 - fsl,imx7ulp-rpmsg-audio
27 - fsl,imx8mn-rpmsg-audio
28 - fsl,imx8mm-rpmsg-audio
[all …]
|
| D | samsung-i2s.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/sound/samsung-i2s.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
14 - $ref: dai-common.yaml#
19 samsung,s3c6410-i2s: for 8/16/24bit stereo I2S.
21 samsung,s5pv210-i2s: for 8/16/24bit multichannel (5.1) I2S with
25 samsung,exynos5420-i2s: for 8/16/24bit multichannel (5.1) I2S for
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 3 ADI is the abbreviation of Anolog-Digital interface, which is used to access
12 which means we can just link one analog chip address to one hardware channel,
13 then users can access the mapped analog chip address by this hardware channel
16 Thus we introduce one property named "sprd,hw-channels" to configure hardware
17 channels, the first value specifies the hardware channel id which is used to
21 Since we have multi-subsystems will use unique ADI to access analog chip, when
26 Then we need one hardware spinlock to synchronize between the multiple subsystems.
28 The new version ADI controller supplies multiple master channels for different
34 - compatible: Should be "sprd,sc9860-adi".
35 - reg: Offset and length of ADI-SPI controller register space.
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/spi/ |
| D | sprd,spi-adi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/spi/sprd,spi-adi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Orson Zhai <orsonzhai@gmail.com>
11 - Baolin Wang <baolin.wang7@gmail.com>
12 - Chunyan Zhang <zhang.lyra@gmail.com>
15 ADI is the abbreviation of Anolog-Digital interface, which is used to access
24 which means we can just link one analog chip address to one hardware channel,
25 then users can access the mapped analog chip address by this hardware channel
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | pci.h | 26 * Each pci channel is a top-level PCI bus seem by CPU. A machine with
27 * multiple PCI channels may have multiple PCI host controllers or a
28 * single controller supporting multiple channels.
90 hose->need_domain_info = need_domain_info; in set_pci_need_domain_info()
97 already-configured bus numbers - to be used for buggy BIOSes
129 #define pci_domain_nr(bus) ((struct pci_controller *)(bus)->sysdata)->index
133 struct pci_controller *hose = bus->sysdata; in pci_proc_domain()
134 return hose->need_domain_info; in pci_proc_domain()
143 /* Chances are this interrupt is wired PC-style ... */
144 static inline int pci_get_legacy_ide_irq(struct pci_dev *dev, int channel) in pci_get_legacy_ide_irq() argument
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/drivers/staging/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)
48 .name = "daqcard-1200",
[all …]
|
| /kernel/linux/linux-5.10/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.txt 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|