| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/virt/hyperv/ |
| H A 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 …]
|
| /openbmc/docs/designs/ |
| H A D | multihost-ipmi-design.md | 1 # Multi-host IPMI design
12 The current version of OpenBMC does not support multi-host implementation in
13 IPMI commands handling. We have a multi-host system and proposing the design to
14 support multi-host.
20 Issue 1: ipmbridged does not send the channel number (ie HostId) Issue 2: ipmid
21 does not have the information on which IPMB channel the request has come from.
30 +------------------------------------+
32 | +-----------+ +------------+ | +--------+
34 | | | | |-|------| Host-1 |
36 | | | | | | +--------+
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A 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 …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/trace/ |
| H A 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 …]
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | css.rst | 1 The virtual channel subsystem
4 QEMU implements a virtual channel subsystem with subchannels, (mostly
5 functionless) channel paths, and channel devices (virtio-ccw, 3270, and
6 devices passed via vfio-ccw). It supports multiple subchannel sets (MSS) and
7 multiple channel subsystems extended (MCSS-E).
9 All channel devices support the ``devno`` property, which takes a parameter
12 The default channel subsystem image id (``<cssid>``) is ``0xfe``. Devices in
13 there will show up in channel subsystem image ``0`` to guests that do not
14 enable MCSS-E. Note that devices with a different cssid will not be visible
15 if the guest OS does not enable MCSS-E (which is true for all supported guest
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ddr/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A 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 …]
|
| /openbmc/linux/drivers/remoteproc/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/include/uapi/linux/caif/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/hid/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/devicetree/bindings/spi/ |
| H A 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 …]
|
| /openbmc/linux/drivers/comedi/drivers/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/Documentation/driver-api/iio/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A 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 …]
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | ipmitool-commands-cheatsheet.md | 5 Note: If the ipmitool is on the BMC then set the interface as "-I dbus" and if
7 "-I lanplus".
13 `ipmitool lan set <channel> ipsrc static`
17 `ipmitool lan set <channel> ipaddr <x.x.x.x>`
21 `ipmitool lan set <channel> netmask <x.x.x.x>`
25 `ipmitool lan set <channel> defgw ipaddr <x.x.x.x>`
29 `ipmitool lan set <channel> vlan id <id>`
33 `ipmitool lan set <channel> vlan id off`
35 NOTE: The user can group multiple set operations since the IPMI daemon waits for
|
| /openbmc/linux/Documentation/driver-api/ |
| H A 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 …]
|
| /openbmc/u-boot/include/ |
| H A D | dma.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
4 * Copyright (C) 2015 - 2018 Texas Instruments Incorporated <www.ti.com>
16 * enum dma_direction - dma transfer direction indicator
35 * struct dma_dev_priv - information about a device used by the uclass
38 * one/multiple of DMA_SUPPORTS_*
54 * often implement multiple separate DMAs, since the hardware it manages
62 * Note. dma_send() is sync operation always - it'll start transfer and will
64 * - get/request dma channel
66 * ret = dma_get_by_name(common->dev, "tx0", &dma_tx);
69 * - enable dma channel
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
| H A D | uncore-memory.json | 7 …mmands; Counts the total number of DRAM Read CAS commands issued on this channel (including underf…
17 …S and WR_CAS Commands; Counts the total number of DRAM Write CAS commands issued on this channel.",
27 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
36 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
45 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
74 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
78 … RD_CAS and WR_CAS Commands; Counts the total number of DRAM CAS commands issued on this channel.",
87 …mmands; Counts the total number of DRAM Read CAS commands issued on this channel (including underf…
92 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
96 …mmands; Counts the total number or DRAM Read CAS commands issued on this channel. This includes b…
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
| H A D | uncore-memory.json | 7 …mmands; Counts the total number of DRAM Read CAS commands issued on this channel (including underf…
17 …S and WR_CAS Commands; Counts the total number of DRAM Write CAS commands issued on this channel.",
27 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
36 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
45 …"PublicDescription": "Counts the number of DRAM Activate commands sent on this channel. Activate …
74 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
78 … RD_CAS and WR_CAS Commands; Counts the total number of DRAM CAS commands issued on this channel.",
87 …mmands; Counts the total number of DRAM Read CAS commands issued on this channel (including underf…
92 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
96 …mmands; Counts the total number or DRAM Read CAS commands issued on this channel. This includes b…
[all …]
|