| /openbmc/ipmitool/contrib/ |
| H A D | bmclanconf | 5 # Redistribution and use in source and binary forms, with or without
23 # PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED.
30 # LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS SOFTWARE,
35 # It may work with other setups as long as you use the correct channel
39 # If the wrong channel is used you could lose network access to the
41 # with the wrong MAC address. You will need to use a console or
47 usage: $0 -c <chan> -i <interface> [options]
48 $0 -c <chan> [-v|w|x|y|z address] [options]
50 -c channel Which BMC channel to configure [-c help for more info]
51 -i interface Auto-configure BMC based on interface network settings
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | relay.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 to userspace via user-defined 'relay channels'.
11 A 'relay channel' is a kernel->user data relay mechanism implemented
12 as a set of per-cpu kernel buffers ('channel buffers'), each
14 clients write into the channel buffers using efficient write
15 functions; these automatically log into the current cpu's channel
19 are associated with the channel buffers using the API described below.
21 The format of the data logged into the channel buffers is completely
25 filtering - this also is left to the kernel client. The purpose is to
30 functions in the relay interface code - please see that for details.
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | mISDNhw.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
18 * H - hardware driver specific bits
19 * G - for all drivers
34 /* channel->Flags bit field */
35 #define FLG_TX_BUSY 0 /* tx_buf in use */
36 #define FLG_TX_NEXT 1 /* next_skb in use */
39 #define FLG_OPEN 5 /* channel is in use */
40 #define FLG_ACTIVE 6 /* channel is activated */
42 /* channel type */
43 #define FLG_DCHANNEL 8 /* channel is D-channel */
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/dma/ |
| H A D | stericsson,dma40.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ST-Ericsson DMA40 DMA Engine
10 - Linus Walleij <linus.walleij@linaro.org>
13 - $ref: dma-controller.yaml#
16 "#dma-cells":
19 The first cell is the unique device channel number as indicated by this
20 table for DB8500 which is the only ASIC known to use DMA40:
32 10: Multi-Channel Display Engine MCDE RX
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | fsl,ssi.txt | 4 be programmed in AC97, I2S, left-justified, or right-justified modes.
7 - compatible: Compatible list, should contain one of the following
9 fsl,mpc8610-ssi
10 fsl,imx51-ssi
11 fsl,imx35-ssi
12 fsl,imx21-ssi
13 - cell-index: The SSI, <0> = SSI1, <1> = SSI2, and so on.
14 - reg: Offset and length of the register set for the device.
15 - interrupts: <a b> where a is the interrupt number and b is a
21 - fsl,fifo-depth: The number of elements in the transmit and receive FIFOs.
[all …]
|
| /openbmc/ipmitool/doc/ |
| H A D | ipmitool.1 | 3 ipmitool \- utility for controlling IPMI\-enabled devices
6 ipmitool [ <options> ] <command> [ <sub-commands and sub-options> ]
8 <options> := [ <general-options> | <conditional-opts> ]
13 <general-options> := [ -h | -V | -v | -I <interface> | -H <address> |
14 -d <N> | -p <port> | -c | -U <username> |
15 -L <privlvl> | -l <lun> | -m <local_address> |
16 -N <sec> | -R <count> | <password-option> |
17 <oem-option> | <bridge-options> ]
19 <conditional-opts> := [ <lan-options> | <lanplus-options> |
20 <command-options> ]
[all …]
|
| /openbmc/linux/Documentation/driver-api/dmaengine/ |
| H A D | client.rst | 8 ``Documentation/crypto/async-tx-api.rst``
11 Below is a guide to device driver writers on how to use the Slave-DMA API of the
19 - Allocate a DMA slave channel
21 - Set slave and controller specific parameters
23 - Get a descriptor for transaction
25 - Submit the transaction
27 - Issue pending requests and wait for callback notification
31 1. Allocate a DMA slave channel
33 Channel allocation is slightly different in the slave DMA context,
34 client drivers typically need a channel from a particular DMA
[all …]
|
| /openbmc/linux/drivers/w1/slaves/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # 1-wire slaves configuration
6 menu "1-wire Slaves"
11 Say Y here if you want to connect 1-wire thermal sensors to your
17 Say Y here if you want to connect 1-wire
23 Say Y or M here if you want to use a DS2405 1-wire
24 single-channel addressable switch.
25 This device can also work as a single-channel
29 tristate "8-Channel Addressable Switch (IO Expander) 0x29 family support (DS2408)"
31 Say Y here if you want to use a 1-wire
[all …]
|
| /openbmc/qemu/include/io/ |
| H A D | channel-tls.h | 24 #include "io/channel.h"
29 #define TYPE_QIO_CHANNEL_TLS "qio-channel-tls"
36 * The QIOChannelTLS class provides a channel wrapper which
39 * technical restriction on which type of master channel is
42 * This channel object is capable of running as either a
56 * @master: the underlying channel object
57 * @creds: the credentials to use for TLS handshake
59 * @errp: pointer to a NULL-initialized error object
61 * Create a new TLS channel that runs the server side of
62 * a TLS session. The TLS session handshake will use the
[all …]
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | rio_cm.rst | 19 This driver (RIO_CM) provides to user-space applications shared access to
23 messaging mailboxes in case of multi-packet message (up to 4KB) and
24 up to 64 mailboxes if single-packet messages (up to 256 B) are used. In addition
30 capability to large number of user-space processes by introducing socket-like
32 use the limited RapidIO messaging hardware resources efficiently.
39 Following ioctl commands are available to user-space applications:
41 - RIO_CM_MPORT_GET_LIST:
46 - RIO_CM_EP_GET_LIST_SIZE:
49 - RIO_CM_EP_GET_LIST:
53 - RIO_CM_CHAN_CREATE:
[all …]
|
| /openbmc/linux/include/linux/iio/ |
| H A D | consumer.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
19 * struct iio_channel - everything needed for a consumer to use a channel
20 * @indio_dev: Device on which the channel exists.
21 * @channel: Full description of the channel.
22 * @data: Data about the channel used by consumer.
26 const struct iio_chan_spec *channel; member
31 * iio_channel_get() - get description of all that is needed to access channel.
36 * @consumer_channel: Unique name to identify the channel on the consumer
37 * side. This typically describes the channels use within
44 * iio_channel_release() - release channels obtained via iio_channel_get
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | edac.rst | 5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
35 * Channel
37 A memory controller channel, responsible to communicate with a group of
38 DIMMs. Each channel has its own independent control (command) and data
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
52 * Single-channel
55 only. E. g. if the data is 64 bits-wide, the data flows to the CPU using
57 memories. FB-DIMM and RAMBUS use a different concept for channel, so
60 * Double-channel
[all …]
|
| /openbmc/linux/arch/powerpc/boot/dts/fsl/ |
| H A D | elo3-dma-2.dtsi | 6 * Redistribution and use in source and binary forms, with or without
29 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
31 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
36 #address-cells = <1>;
37 #size-cells = <1>;
38 compatible = "fsl,elo3-dma";
42 dma-channel@0 {
43 compatible = "fsl,eloplus-dma-channel";
47 dma-channel@80 {
48 compatible = "fsl,eloplus-dma-channel";
[all …]
|
| H A D | elo3-dma-1.dtsi | 6 * Redistribution and use in source and binary forms, with or without
29 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
31 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
36 #address-cells = <1>;
37 #size-cells = <1>;
38 compatible = "fsl,elo3-dma";
42 dma-channel@0 {
43 compatible = "fsl,eloplus-dma-channel";
47 dma-channel@80 {
48 compatible = "fsl,eloplus-dma-channel";
[all …]
|
| H A D | elo3-dma-0.dtsi | 6 * Redistribution and use in source and binary forms, with or without
29 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
31 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
36 #address-cells = <1>;
37 #size-cells = <1>;
38 compatible = "fsl,elo3-dma";
42 dma-channel@0 {
43 compatible = "fsl,eloplus-dma-channel";
47 dma-channel@80 {
48 compatible = "fsl,eloplus-dma-channel";
[all …]
|
| /openbmc/linux/drivers/tty/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
23 one can be used for a text-mode user session, and a third could run
25 is done with certain key combinations, usually Alt-<function key>.
35 You need at least one virtual terminal device in order to make use
42 shiny Linux system :-)
68 would use the third virtual terminal as system console. (Try "man
95 See <file:Documentation/driver-api/console.rst> for more
110 Linux has traditionally used the BSD-like names /dev/ptyxx for
119 All modern Linux systems use the Unix98 ptys. Say Y unless
133 Linux has traditionally used the BSD-like names /dev/ptyxx
[all …]
|
| /openbmc/linux/Documentation/sound/cards/ |
| H A D | hdspm.rst | 2 Software Interface ALSA-DSP MADI Driver
5 (translated from German, so no good English ;-),
7 2004 - winfried ritsch
11 the Controls and startup-options are ALSA-Standard and only the
19 ------------------
21 * number of channels -- depends on transmission mode
24 use for a lower number of channels is only resource allocation,
29 * Single Speed -- 1..64 channels
32 (Note: Choosing the 56channel mode for transmission or as
34 all 64 channels are available for the mixer, so channel count
[all …]
|
| /openbmc/linux/Documentation/arch/s390/ |
| H A D | vfio-ccw.rst | 2 vfio-ccw: the basic infrastructure
6 ------------
9 Linux/s390. Motivation for vfio-ccw is to passthrough subchannels to a
13 I/O access method, which is so called Channel I/O. It has its own access
16 - Channel programs run asynchronously on a separate (co)processor.
17 - The channel subsystem will access any memory designated by the caller
18 in the channel program directly, i.e. there is no iommu involved.
24 regions to pass the channel programs from the mdev to its parent device
31 - A good start to know Channel I/O in general:
33 - s390 architecture:
[all …]
|
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | scan.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * Copyright (C) 2012-2014, 2018-2023 Intel Corporation
4 * Copyright (C) 2013-2015 Intel Mobile Communications GmbH
5 * Copyright (C) 2016-2017 Intel Deutschland GmbH
13 * enum iwl_scan_subcmd_ids - scan commands
29 * struct iwl_ssid_ie - directed scan network information element
33 * each channel may select different ssids from among the 20 entries.
72 * struct iwl_scan_offload_blocklist - SCAN_OFFLOAD_BLACKLIST_S
75 * @client_bitmap: clients ignore this entry - enum scan_framework_client
106 * struct iwl_scan_offload_profile - SCAN_OFFLOAD_PROFILE_S
[all …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | dma-isa-lpc.rst | 12 ------------------------
16 #include <linux/dma-mapping.h>
20 bus addresses (see Documentation/core-api/dma-api.rst for details).
28 -----------------
37 The DMA-able address space is the lowest 16 MB of _physical_ memory.
39 or 128 KiB depending on which channel you use).
45 allocate the memory during boot-up it's a good idea to also pass
52 -------------------
54 To translate the virtual address to a bus address, use the normal DMA
55 API. Do _not_ use isa_virt_to_bus() even though it does the same
[all …]
|
| /openbmc/linux/Documentation/hid/ |
| H A D | hid-transport.rst | 8 Bluetooth, I2C and user-space I/O drivers.
17 report-parsing, report interpretation and the user-space API. Device specifics
22 +-----------+ +-----------+ +-----------+ +-----------+
24 +-----------+ +-----------+ +-----------+ +-----------+
26 +------------+ +------------+
28 +------------+ +------------+
30 +------------------+ +------------------+
32 +------------------+ +------------------+
35 +----------------+
37 +----------------+
[all …]
|
| /openbmc/linux/Documentation/arch/arm/stm32/ |
| H A D | stm32-dma-mdma-chaining.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 STM32 DMA-MDMA chaining
9 ------------
11 This document describes the STM32 DMA-MDMA chaining feature. But before going
44 ----------
46 STM32 DMA-MDMA chaining feature relies on the strengths of STM32 DMA and
50 (when DMA data counter - DMA_SxNDTR - reaches 0), the memory pointers
56 With STM32 MDMA linked-list mode, a single request initiates the data array
57 (collection of nodes) to be transferred until the linked-list pointer for the
58 channel is null. The channel transfer complete of the last node is the end of
[all …]
|
| /openbmc/linux/drivers/net/wireless/ath/ath9k/ |
| H A D | common-init.c | 2 * Copyright (c) 2008-2011 Atheros Communications Inc.
4 * Permission to use, copy, modify, and/or distribute this software for any
12 * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14 * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
17 /* We use the hw_value as an index into our private channel structure */
35 /* Some 2 GHz radios are actually tunable on 2312-2732
40 CHAN2G(2412, 0), /* Channel 1 */
41 CHAN2G(2417, 1), /* Channel 2 */
42 CHAN2G(2422, 2), /* Channel 3 */
43 CHAN2G(2427, 3), /* Channel 4 */
[all …]
|
| /openbmc/qemu/migration/ |
| H A D | multifd.h | 4 * Copyright (c) 2019-2020 Red Hat Inc
10 * See the COPYING file in the top-level directory.
65 uint32_t unused32[1]; /* Reserved for future use */
66 uint64_t unused64[3]; /* Reserved for future use */
70 * - normal pages (initial normal_pages entries)
71 * - zero pages (following zero_pages entries)
109 return data->type == MULTIFD_PAYLOAD_NONE; in multifd_payload_empty()
115 data->type = type; in multifd_set_payload_type()
122 /* channel number */
124 /* channel thread name */
[all …]
|
| /openbmc/linux/arch/um/drivers/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
14 The User-Mode Linux environment allows you to create virtual serial
18 See <http://user-mode-linux.sourceforge.net/old/input.html> for more
19 information and command line examples of how to use this facility.
24 bool "null channel support"
31 bool "port channel support"
41 bool "pty channel support"
44 lines to host pseudo-terminals. Access to both traditional
45 pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
51 bool "tty channel support"
[all …]
|