Searched +full:data +full:- +full:out (Results 1 – 25 of 535) sorted by relevance
12345678910>>...22
| /Documentation/sound/cards/ |
| D | serial-u16550.rst | 7 * 0 - Roland Soundcanvas support (default)
8 * 1 - Midiator MS-124T support (1)
9 * 2 - Midiator MS-124W S/A mode (2)
10 * 3 - MS-124W M/B mode support (3)
11 * 4 - Generic device with multiple input support (4)
13 For the Midiator MS-124W, you must set the physical M-S and A-B
17 (midiCnD0-midiCnD15). Whenever you write to a different substream, the driver
28 /sbin/modprobe snd-serial-u16550 port=0x3f8 irq=4 speed=115200
34 /sbin/modprobe snd-serial-u16550 port=0x3f8 irq=4 outs=4
36 In MS-124T mode, one raw MIDI substream is supported (midiCnD0); the outs
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ---------------------------------
6 ext4 recognizes (better than ext3, anyway) that data locality is
9 that the head actuator and disk must perform to access a data block,
17 The first tool that ext4 uses to combat fragmentation is the multi-block
23 files) then the file data gets written out in a single multi-block
27 the dirty buffers are being written out to disk. By not committing to a
29 is hit, or sync() is called, or the kernel runs out of memory), the hope
33 file's data blocks in the same block group as its inode. This cuts down
35 to learn where the file's data blocks live and then seek over to the
[all …]
|
| /Documentation/crypto/ |
| D | api-samples.rst | 5 -----------------------------------------------
7 This code encrypts some data with AES-256-XTS. For sake of example,
8 all inputs are random bytes, the encryption is done in-place, and it's
17 u8 *data = NULL;
18 const size_t datasize = 512; /* data size in bytes */
21 u8 iv[16]; /* AES-256-XTS takes a 16-byte IV */
22 u8 key[64]; /* AES-256-XTS takes a 64-byte key */
28 * In real-world use, a tfm and key are typically used for many
43 goto out;
49 err = -ENOMEM;
[all …]
|
| /Documentation/hwmon/ |
| D | smsc47b397.rst | 6 * SMSC LPC47B397-NC
8 * SMSC SCH5307-NS
20 - Mark M. Hoffman <mhoffman@lightlink.com>
21 - Utilitek Systems, Inc.
25 The following specification describes the SMSC LPC47B397-NC [1]_ sensor chip
27 provided by Craig Kelly (In-Store Broadcast Network) and edited/corrected
30 .. [1] And SMSC SCH5307-NS and SCH5317, which have different device IDs but are
33 -------------------------------------------------------------------------
35 Methods for detecting the HP SIO and reading the thermal data on a dc7100
36 -------------------------------------------------------------------------
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,q6afe.txt | 7 - compatible:
10 Definition: must be "qcom,q6afe-v<MAJOR-NUMBER>.<MINOR-NUMBER>"
20 - compatible:
23 Definition: must be "qcom,q6afe-dais"
25 - #sound-dai-cells
30 - #address-cells
35 - #size-cells
43 - reg
48 - qcom,sd-lines
50 Value type: <prop-encoded-array>
[all …]
|
| /Documentation/networking/ |
| D | PLIP.txt | 10 -----------------
13 This device interface allows a point-to-point connection between two
21 printer port. PLIP is a non-standard, but [can use] uses the standard
22 LapLink null-printer cable [can also work in turbo mode, with a PLIP
58 -------------------
68 PLIP driver is signaled whenever data is sent to it via the cable, such that
69 when no data is available, the driver isn't being used.
73 On these machines, the PLIP driver can be used in IRQ-less mode, where
74 the PLIP driver would constantly poll the parallel port for data waiting,
75 and if such data is available, process it. This mode is less efficient than
[all …]
|
| D | can_ucan_protocol.rst | 5 UCAN is the protocol used by the microcontroller-based USB-CAN
6 adapter that is integrated on System-on-Modules from Theobroma Systems
9 The UCAN protocol has been designed to be hardware-independent.
11 internally. All multi-byte integers are encoded as Little Endian.
25 The device sends CAN data frames and CAN error frames
27 OUT endpoint
28 The driver sends CAN data frames on the out endpoint
40 The driver uses ``ucan_ctrl_command_in/out`` and
44 ------------
51 ``wLength`` * Host to Device - Number of bytes to transmit
[all …]
|
| D | tls-offload.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
13 For details regarding the user-facing interface refer to the TLS
18 * Software crypto mode (``TLS_SW``) - CPU handles the cryptography.
24 * Packet-based NIC offload mode (``TLS_HW``) - the NIC handles crypto
28 (``ethtool`` flags ``tls-hw-tx-offload`` and ``tls-hw-rx-offload``).
29 * Full TCP NIC offload mode (``TLS_HW_RECORD``) - mode of operation where
33 abilities or QoS and packet scheduling (``ethtool`` flag ``tls-hw-record``).
36 offload opt-in or opt-out on per-connection basis is not currently supported.
39 --
52 --
[all …]
|
| /Documentation/RCU/ |
| D | arrayRCU.txt | 1 Using RCU to Protect Read-Mostly Arrays
13 Each of these three situations involves an RCU-protected pointer to an
16 case is -not- supported. The problem with RCU-protected indexes into
19 are far more trouble than they are worth. If RCU-protected indexes into
24 That aside, each of the three RCU-protected pointer situations are
31 has a linked-list hash chain. Each hash chain can be protected by RCU
33 to other array-of-list situations, such as radix trees.
38 Static arrays, where the data (rather than a pointer to the data) is
41 this situation, which would also have minimal read-side overhead as long
52 to map from semaphore, message-queue, and shared-memory IDs to the data
[all …]
|
| /Documentation/dev-tools/ |
| D | gcov.rst | 5 tool gcov_ with the Linux kernel. Coverage data of a running kernel
6 is exported in gcov-compatible format via the "gcov" debugfs directory.
7 To get coverage data for a specific file, change to the kernel build
8 directory and use gcov with the ``-o`` option as follows (requires root)::
10 # cd /tmp/linux-out
11 # gcov -o /sys/kernel/debug/gcov/tmp/linux-out/kernel spinlock.c
14 in the current directory. In addition, graphical gcov front-ends such
15 as lcov_ can be used to automate the process of collecting data
30 -----------
37 and to get coverage data for the entire kernel::
[all …]
|
| /Documentation/scsi/ |
| D | cxgb3i.txt | 7 series of products) support iSCSI acceleration and iSCSI Direct Data Placement
12 - iSCSI PDU digest generation and verification
15 Data digest into the PDUs.
17 Data digest of the PDUs.
19 - Direct Data Placement (DDP)
21 S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
22 payload into pre-posted final destination host-memory buffers based
23 on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
24 in Data-Out PDUs.
26 - PDU Transmit and Recovery
[all …]
|
| D | scsi_eh.txt | 12 [1-1] struct scsi_cmnd
13 [1-2] How do scmd's get completed?
14 [1-2-1] Completing a scmd w/ scsi_done
15 [1-2-2] Completing a scmd w/ timeout
16 [1-3] How EH takes over
18 [2-1] EH through fine-grained callbacks
19 [2-1-1] Overview
20 [2-1-2] Flow of scmds through EH
21 [2-1-3] Flow of control
22 [2-2] EH through transportt->eh_strategy_handler()
[all …]
|
| /Documentation/sphinx/ |
| D | parse-headers.pl | 18 pod2usage(-exitstatus => 0, -verbose => 2) if $man;
23 my $data;
31 require Data::Dumper if ($debug);
41 $data .= $_;
59 $n =~ tr/A-Z/a-z/;
60 $n =~ tr/_/-/;
72 $n =~ tr/A-Z/a-z/;
81 $n =~ tr/A-Z/a-z/;
82 $n =~ tr/_/-/;
120 # Handle multi-line typedefs
[all …]
|
| /Documentation/bpf/ |
| D | prog_flow_dissector.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 Flow dissector is a routine that parses metadata out of the packets. It's
13 BPF flow dissector is an attempt to reimplement C-based flow dissector logic
21 limited set of fields is allowed: ``data``, ``data_end`` and ``flow_keys``.
26 * ``nhoff`` - initial offset of the networking header
27 * ``thoff`` - initial offset of the transport header, initialized to nhoff
28 * ``n_proto`` - L3 protocol type, parsed out of L2 header
29 * ``flags`` - optional flags
31 Flow dissector BPF program should fill out the rest of the ``struct
38 __sk_buff->data
[all …]
|
| /Documentation/driver-api/ |
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
8 line, and a "Master In, Slave Out" (MISO) data line. SPI is a full
9 duplex protocol; for each bit shifted out the MOSI line (one per clock)
12 additional chipselect line is usually active-low (nCS); four signals are
33 board-specific initialization code. A :c:type:`struct spi_driver
46 .. kernel-doc:: include/linux/spi/spi.h
49 .. kernel-doc:: drivers/spi/spi.c
52 .. kernel-doc:: drivers/spi/spi.c
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-tegra-fuse | 1 What: /sys/devices/*/<our-device>/fuse
4 Description: read-only access to the efuses on Tegra20, Tegra30, Tegra114
6 data programmed at the factory. The data is layed out in 32bit
|
| D | sysfs-fs-ext4 | 45 parameter will have their blocks allocated out of a
48 will have its blocks allocated out of its own unique
57 algorithm will pre-read into the buffer cache
63 This file is read-only and shows the number of blocks
71 This file is read-only and shows the number of kilobytes
72 of data that have been written to this filesystem since it was
79 This file is read-only and shows the number of
80 kilobytes of data that have been written to this
87 Tuning parameter which (if non-zero) controls the goal
98 try to write out before move on to another inode.
[all …]
|
| /Documentation/admin-guide/ |
| D | ext4.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 (64 bit) in keeping with increasing disk capacities and state-of-the-art
12 Mailing list: linux-ext4@vger.kernel.org
23 - The latest version of e2fsprogs can be found at:
35 - Create a new filesystem using the ext4 filesystem type:
37 # mke2fs -t ext4 /dev/hda1
41 # tune2fs -O extents /dev/hda1
46 # tune2fs -I 256 /dev/hda1
48 - Mounting:
50 # mount -t ext4 /dev/hda1 /wherever
[all …]
|
| /Documentation/arm/ |
| D | tcm.rst | 2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoC:s have a so-called TCM (Tightly-Coupled Memory).
8 This is usually just a few (4-64) KiB of RAM inside the ARM
12 Harvard-architecture, so there is an ITCM (instruction TCM)
13 and a DTCM (data TCM). The DTCM can not contain any
14 instructions, but the ITCM can actually contain data.
18 ARM CPU:s have special registers to read out status, physical
20 defines a CPUID_TCM register that you can read out from the
24 determine if ITCM (bits 1-0) and/or DTCM (bit 17-16) is present
29 size of TCM memories at runtime. This is used to read out and modify
[all …]
|
| /Documentation/devicetree/bindings/net/can/ |
| D | cc770.txt | 8 - compatible : should be "bosch,cc770" for the CC770 and "intc,82527"
11 - reg : should specify the chip select, address offset and size required
14 - interrupts : property with a value describing the interrupt source
19 - bosch,external-clock-frequency : frequency of the external oscillator
24 - bosch,clock-out-frequency : slock frequency in Hz on the CLKOUT pin.
28 - bosch,slew-rate : slew rate of the CLKOUT signal. If not specified,
31 - bosch,disconnect-rx0-input : see data sheet.
33 - bosch,disconnect-rx1-input : see data sheet.
35 - bosch,disconnect-tx1-output : see data sheet.
37 - bosch,polarity-dominant : see data sheet.
[all …]
|
| /Documentation/x86/ |
| D | orc-unwinder.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 format of the ORC data is much simpler than DWARF, which in turn allows
15 The ORC data consists of unwind tables which are generated by objtool.
16 They contain out-of-band data which is used by the in-kernel ORC
17 unwinder. Objtool generates the ORC data by first doing compile-time
23 The per-object ORC sections are combined at link time and are sorted and
24 post-processed at boot time. The unwinder uses the resulting data to
33 3.2%, resulting in a broad kernel-wide slowdown. Measurements by Mel
34 Gorman [1]_ have shown a slowdown of 5-10% for some workloads.
37 performance, because the debuginfo is out of band. So if you disable
[all …]
|
| /Documentation/ioctl/ |
| D | hdio.rst | 5 - Edward A. Falk <efalk@google.com>
10 the HD/IDE layer. These are by-and-large implemented (as of Linux 2.6)
22 HDIO_GET_QDMA get use-qdma flag
25 HDIO_GET_KEEPSETTINGS get keep-settings-on-reset flag
27 HDIO_GET_NOWERR get ignore-write-error flag
28 HDIO_GET_DMA get use-dma flag
43 ioctls that pass non-pointer values:
50 HDIO_SET_NOWERR change ignore-write-error flag
51 HDIO_SET_DMA change use-dma flag
56 HDIO_SET_WCACHE change write cache enable-disable
[all …]
|
| /Documentation/w1/masters/ |
| D | ds2490.rst | 13 -----------
16 which allows to build USB <-> W1 bridges.
18 DS9490(R) is a USB <-> W1 bus master device
20 low-level operational chip.
24 - The weak pullup current is a minimum of 0.9mA and maximum of 6.0mA.
25 - The 5V strong pullup is supported with a minimum of 5.9mA and a
27 - The hardware will detect when devices are attached to the bus on the
31 - The number of USB bus transactions could be reduced if w1_reset_send
37 write and read data. The write buffer needs to have the match rom
40 - The hardware supports normal, flexible, and overdrive bus
[all …]
|
| /Documentation/driver-api/iio/ |
| D | buffers.rst | 11 The Industrial I/O core offers a way for continuous data capture based on a
12 trigger source. Multiple data channels can be read at once from
21 * :file:`length`, the total number of data samples (capacity) that can be
35 is non *zero*, then a triggered capture will contain data samples for this
37 * :file:`type`, description of the scan element data storage within the buffer
42 * *bits*, is the number of valid data bits.
46 masking out unused bits.
50 For example, a driver for a 3-axis accelerometer with 12 bit resolution where
51 data is stored in two 8-bits registers as follows::
54 +---+---+---+---+---+---+---+---+
[all …]
|
| /Documentation/ |
| D | kref.txt | 8 A lot of this was lifted from Greg Kroah-Hartman's 2004 OLS paper and
11 - http://www.kroah.com/linux/talks/ols_2004_kref_paper/Reprint-Kroah-Hartman-OLS2004.pdf
12 - http://www.kroah.com/linux/talks/ols_2004_kref_talk/
22 To use a kref, add one to your data structures like::
33 The kref can occur anywhere within the data structure.
41 struct my_data *data;
43 data = kmalloc(sizeof(*data), GFP_KERNEL);
44 if (!data)
45 return -ENOMEM;
46 kref_init(&data->refcount);
[all …]
|
12345678910>>...22