| /Linux-v5.15/Documentation/filesystems/ |
| 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 …]
|
| /Linux-v5.15/include/linux/ |
| D | visorbus.h | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright (C) 2010 - 2013 UNISYS CORPORATION
26 * @CHANNELSRV_UNINITIALIZED: Channel is in an undefined state.
27 * @CHANNELSRV_READY: Channel has been initialized by server.
37 * @CHANNELCLI_DISABLED: Client can see channel but is NOT allowed to use it
41 * @CHANNELCLI_ATTACHED: Idle, but client may want to use channel any time.
42 * @CHANNELCLI_BUSY: Client either wants to use or is using channel.
43 * @CHANNELCLI_OWNED: "No worries" state - client can access channel
57 * a guest can look at the FeatureFlags in the io channel, and configure the
58 * driver to use interrupts or not based on this setting. All feature bits for
[all …]
|
| 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 …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/dma/ |
| D | ste-dma40.txt | 4 - compatible: "stericsson,dma40"
5 - reg: Address range of the DMAC registers
6 - reg-names: Names of the above areas to use during resource look-up
7 - interrupt: Should contain the DMAC interrupt number
8 - #dma-cells: must be <3>
9 - memcpy-channels: Channels to be used for memcpy
12 - dma-channels: Number of channels supported by hardware - if not present
14 - disabled-channels: Channels which can not be used
18 dma: dma-controller@801c0000 {
19 compatible = "stericsson,db8500-dma40", "stericsson,dma40";
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/sound/ |
| 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 …]
|
| /Linux-v5.15/Documentation/driver-api/dmaengine/ |
| 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 …]
|
| /Linux-v5.15/include/linux/iio/ |
| 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 …]
|
| /Linux-v5.15/drivers/w1/slaves/ |
| 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 …]
|
| /Linux-v5.15/Documentation/driver-api/rapidio/ |
| 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 …]
|
| /Linux-v5.15/drivers/tty/ |
| 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 …]
|
| /Linux-v5.15/arch/powerpc/boot/dts/fsl/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /Linux-v5.15/Documentation/sound/cards/ |
| 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 …]
|
| /Linux-v5.15/Documentation/s390/ |
| 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 …]
|
| /Linux-v5.15/Documentation/networking/device_drivers/wan/ |
| D | z8530book.rst | 24 three different modes. Each mode can be applied to an individual channel
34 The DMA mode supports the chip when it is configured to use dual DMA
36 operation for a single channel. With DMA running the Z85230 tops out
41 Transmit DMA mode uses a single DMA channel. The DMA channel is used for
59 rather than each channel). You are responsible for allocating the
65 The structure holds two channel structures. Initialise chanA.ctrlio and
74 name field you may use as you wish. The private field is unused by the
78 Repeat the same operation with the B channel if your chip has both
98 Once you have called z8530_init you can also make use of the utility
106 If you wish to use the network interface facilities of the driver, then
[all …]
|
| /Linux-v5.15/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | scan.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * Copyright (C) 2012-2014, 2018-2021 Intel Corporation
4 * Copyright (C) 2013-2015 Intel Mobile Communications GmbH
5 * Copyright (C) 2016-2017 Intel Deutschland GmbH
19 * struct iwl_ssid_ie - directed scan network information element
23 * each channel may select different ssids from among the 20 entries.
62 * struct iwl_scan_offload_blocklist - SCAN_OFFLOAD_BLACKLIST_S
65 * @client_bitmap: clients ignore this entry - enum scan_framework_client
86 * struct iwl_scan_offload_profile - SCAN_OFFLOAD_PROFILE_S
88 * @unicast_cipher: encryption algorithm to match - bitmap
[all …]
|
| /Linux-v5.15/sound/pci/emu10k1/ |
| D | p16v.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Copyright (c) by James Courtier-Dutton <James@superbug.demon.co.uk>
8 * Output fixed at S32_LE, 2 channel to hw:0,0
13 * Use separate card based buffer for periods table.
15 * Use 2 channel output streams instead of 8 channel.
16 * (8 channel output streams might be good for ASIO type output)
17 * Corrected speaker output, so Front -> Front etc.
26 * Use single trigger for multichannel.
36 * Merging with snd-emu10k1 driver.
38 * One stereo channel at 24bit now works.
[all …]
|
| /Linux-v5.15/Documentation/hid/ |
| 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 …]
|
| /Linux-v5.15/Documentation/core-api/ |
| 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 …]
|
| /Linux-v5.15/drivers/net/wireless/ath/ath9k/ |
| 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 …]
|
| /Linux-v5.15/Documentation/leds/ |
| D | leds-lp5523.rst | 9 Contact: Samu Onkalo (samu.p.onkalo-at-nokia.com)
12 -----------
15 The name of each channel is configurable in the platform data - name and label.
16 There are three options to make the channel name.
20 To make specific channel name, then use 'name' platform data.
22 - /sys/class/leds/R1 (name: 'R1')
23 - /sys/class/leds/B1 (name: 'B1')
25 b) Use the 'label' with no 'name' field
27 For one device name with channel number, then use 'label'.
28 - /sys/class/leds/RGB:channelN (label: 'RGB', N: 0 ~ 8)
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/mfd/ |
| D | atmel-usart.txt | 4 - compatible: Should be one of the following:
5 - "atmel,at91rm9200-usart"
6 - "atmel,at91sam9260-usart"
7 - "microchip,sam9x60-usart"
8 - "atmel,at91rm9200-dbgu", "atmel,at91rm9200-usart"
9 - "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart"
10 - "microchip,sam9x60-dbgu", "microchip,sam9x60-usart"
11 - reg: Should contain registers location and length
12 - interrupts: Should contain interrupt
13 - clock-names: tuple listing input clock names.
[all …]
|
| /Linux-v5.15/include/linux/dma/ |
| D | k3-psil.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (C) 2019 Texas Instruments Incorporated - https://www.ti.com
16 * enum udma_tp_level - Channel Throughput Levels
17 * @UDMA_TP_NORMAL: Normal channel
18 * @UDMA_TP_HIGH: High Throughput channel
19 * @UDMA_TP_ULTRAHIGH: Ultra High Throughput channel
29 * enum psil_endpoint_type - PSI-L Endpoint type
30 * @PSIL_EP_NATIVE: Normal channel
43 * struct psil_endpoint_config - PSI-L Endpoint configuration
44 * @ep_type: PSI-L endpoint type
[all …]
|
| /Linux-v5.15/include/uapi/linux/ |
| D | ipmi.h | 1 /* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note */
23 * have a fairly good understanding of IPMI to use this, so go read
26 * With that said, this driver provides a multi-user interface to the
32 * Multi-user means that multiple applications may use the driver,
52 /* Try to take these from the "Channel Medium Type" table
55 short channel; member
61 * The channel is the BMC's channel number for the channel (usually
67 short channel; member
78 short channel; member
88 * spec. We do not use rqSWID and rsSWID like it shows in the
[all …]
|
