Home
last modified time | relevance | path

Searched +full:non +full:- +full:continuous (Results 1 – 25 of 36) sorted by relevance

12

/Documentation/devicetree/bindings/media/i2c/
Dtc358743.txt1 * Toshiba TC358743 HDMI-RX to MIPI CSI2-TX Bridge
3 The Toshiba TC358743 HDMI-RX to MIPI CSI2-TX (H2C) is a bridge that converts
4 a HDMI stream to MIPI CSI-2 TX. It is programmable through I2C.
8 - compatible: value should be "toshiba,tc358743"
9 - clocks, clock-names: should contain a phandle link to the reference clock
14 - reset-gpios: gpio phandle GPIO connected to the reset pin
15 - interrupts: GPIO connected to the interrupt pin
16 - data-lanes: should be <1 2 3 4> for four-lane operation,
17 or <1 2> for two-lane operation
18 - clock-lanes: should be <0>
[all …]
/Documentation/devicetree/bindings/iio/adc/
Daspeed,ast2600-adc.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/aspeed,ast2600-adc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Billy Tsai <billy_tsai@aspeedtech.com>
13 • 10-bits resolution for 16 voltage channels.
16 • Channel scanning can be non-continuous.
21 • Built-in a compensating method.
22 • Built-in a register to trim internal reference voltage.
30 - aspeed,ast2600-adc0
[all …]
/Documentation/devicetree/bindings/input/
Dmicrochip,qt1050.txt1 Microchip AT42QT1050 Five-channel Touch Sensor IC
11 - compatible: Must be "microchip,qt1050"
12 - reg: The I2C address of the device
13 - interrupts: The sink for the touchpad's IRQ output,
14 see ../interrupt-controller/interrupts.txt
17 - wakeup-source: touch keys can be used as a wakeup source
19 Each button (key) is represented as a sub-node:
25 - linux,code: Keycode to emit.
26 - reg: The key number. Valid values: 0, 1, 2, 3, 4.
28 Optional subnode-properties:
[all …]
/Documentation/core-api/
Dlibrs.rst2 Reed-Solomon Library Programming Interface
10 The generic Reed-Solomon Library provides encoding, decoding and error
13 Reed-Solomon codes are used in communication and storage applications to
30 ------------
54 --------
56 The encoder calculates the Reed-Solomon code over the given data length
60 The expanded data can be inverted on the fly by providing a non-zero
63 Reed-Solomon code for all 0x00 is all 0x00. The code is inverted before
68 no support for encoding continuous bitstreams with a symbol size != 8 at
83 --------
[all …]
Dprintk-index.rst1 .. SPDX-License-Identifier: GPL-2.0
19 Finding these changes in the sources would require non-trivial parsers.
36 named according to the binaries where the printk formats are built-in. There
44 might appear in "vmlinux" when the module is built-in.
48 $> head -1 /sys/kernel/debug/printk/index/vmlinux; shuf -n 5 vmlinux
50 <5> block/blk-settings.c:661 disk_stack_limits "%s: Warning: Device %s is misaligned\n"
54 <6> drivers/acpi/osl.c:1410 acpi_no_auto_serialize_setup "ACPI: auto-serialization disabled\n"
58 - :level: log level value: 0-7 for particular severity, -1 as default,
59 'c' as continuous line without an explicit log level
60 - :flags: optional flags: currently only 'c' for KERN_CONT
[all …]
/Documentation/userspace-api/media/v4l/
Dfunc-read.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _func-read:
13 v4l2-read - Read from a V4L2 device
18 .. code-block:: c
85 continuous capturing when the application can empty the buffers fast
101 :c:func:`read()` was interrupted by a signal. On error, -1 is
107 Non-blocking I/O has been selected using O_NONBLOCK and no data was
Dvidioc-enum-fmt.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENUM_FMT - Enumerate image formats
41 (that is, with lower ``index`` value) less-preferred formats.
43 Depending on the ``V4L2_CAP_IO_MC`` :ref:`capability <device-capabilities>`,
46 1) ``V4L2_CAP_IO_MC`` is not set (also known as a 'video-node-centric' driver)
58 2) ``V4L2_CAP_IO_MC`` is set (also known as an 'MC-centric' driver)
63 If the ``mbus_code`` field is initialized to a valid (non-zero)
64 :ref:`media bus format code <v4l2-mbus-pixelcode>`, then drivers
80 .. flat-table:: struct v4l2_fmtdesc
81 :header-rows: 0
[all …]
/Documentation/iio/
Diio_devbuf.rst1 .. SPDX-License-Identifier: GPL-2.0
10 The Industrial I/O core offers a way for continuous data capture based on a
14 Devices with buffer support feature an additional sub-directory in the
25 ----------
31 ----------
34 be written last, after length and selection of scan elements. Writing a non-zero
39 -------------
49 Non-blocking read will retrieve the available samples from the buffer even if
55 --------------
57 Read-only attribute indicating the bytes of data available in the buffer. In the
[all …]
/Documentation/driver-api/iio/
Dbuffers.rst11 The Industrial I/O core offers a way for continuous data capture based on a
35 is non *zero*, then a triggered capture will contain data samples for this
52 For example, a driver for a 3-axis accelerometer with 12 bit resolution where
53 data is stored in two 8-bits registers as follows::
56 +---+---+---+---+---+---+---+---+
58 +---+---+---+---+---+---+---+---+
61 +---+---+---+---+---+---+---+---+
63 +---+---+---+---+---+---+---+---+
118 Setting **scan_index** to -1 can be used to indicate that the specific channel
124 .. kernel-doc:: include/linux/iio/buffer.h
[all …]
/Documentation/admin-guide/blockdev/
Dfloppy.rst19 Example: If your kernel is called linux-2.6.9, type the following line
22 linux-2.6.9 floppy=thinkpad
25 of linux-2.6.9::
31 linux-2.6.9 floppy=daring floppy=two_fdc
95 Indeed, dma memory needs to be continuous in physical memory,
96 and is thus harder to find, whereas non-dma buffers may be
104 If you have a FIFO-able FDC, the floppy driver automatically
105 falls back on non DMA mode if no DMA-able memory can be found.
130 using 'floppycontrol --messages'. Then access a floppy
131 disk. If you get a huge amount of "Over/Underrun - retrying"
[all …]
/Documentation/networking/
Dtipc.rst1 .. SPDX-License-Identifier: GPL-2.0
11 designed for intra-cluster communication. It can be configured to transmit
18 -------------
20 - Cluster wide IPC service
26 to monitor the continuous existence of peer sockets? And yet without the
32 - Service Addressing
38 - Service Tracking
45 i.e., subscribing for availability/non-availability of cluster nodes.
51 - Transmission Modes
64 - Inter Node Links
[all …]
Dnexthop-group-resilient.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Resilient Next-hop Groups
7 Resilient groups are a type of next-hop group that is aimed at minimizing
12 the legacy multipath next-hop group, which uses the hash-threshold
15 To select a next hop, hash-threshold algorithm first assigns a range of
22 +-------+-------+-------+-------+-------+
24 +-------+-+-----+---+---+-----+-+-------+
26 +---------+---------+---------+---------+
29 under the hash-threshold algorithm.
36 If a multipath group is used for load-balancing between multiple servers,
[all …]
Dpktgen.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Enable CONFIG_NET_PKTGEN to compile and build pktgen either in-kernel
31 overload type of benchmarking, as this could hurt the normal use-case.
35 # ethtool -G ethX tx 1024
44 ring-buffers for various performance reasons, and packets stalling
49 and the cleanup interval is affected by the ethtool --coalesce setting
50 of parameter "rx-usecs".
54 # ethtool -C ethX rx-usecs 30
72 * add_device DEVICE@NAME -- adds a single device
73 * rem_device_all -- remove all associated devices
[all …]
/Documentation/driver-api/
Dxillybus.rst10 - Introduction
11 -- Background
12 -- Xillybus Overview
14 - Usage
15 -- User interface
16 -- Synchronization
17 -- Seekable pipes
19 - Internals
20 -- Source code organization
21 -- Pipe attributes
[all …]
/Documentation/devicetree/bindings/media/
Dvideo-interfaces.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/video-interfaces.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sakari Ailus <sakari.ailus@linux.intel.com>
11 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
29 #address-cells = <1>;
30 #size-cells = <0>;
45 a common scheme using '#address-cells', '#size-cells' and 'reg' properties is
49 specify #address-cells, #size-cells properties independently for the 'port'
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-counter3 Contact: linux-iio@vger.kernel.org
11 Contact: linux-iio@vger.kernel.org
16 MTCLKA-MTCLKB:
20 MTCLKC-MTCLKD:
26 Contact: linux-iio@vger.kernel.org
33 Contact: linux-iio@vger.kernel.org
39 Contact: linux-iio@vger.kernel.org
45 Contact: linux-iio@vger.kernel.org
52 Contact: linux-iio@vger.kernel.org
59 Contact: linux-iio@vger.kernel.org
[all …]
/Documentation/process/
Dstable-api-nonsense.rst8 Greg Kroah-Hartman <greg@kroah.com>
27 -----------------
38 -----
41 to worry about the in-kernel interfaces changing. For the majority of
59 -----------------------
64 - Depending on the version of the C compiler you use, different kernel
71 - Depending on what kernel build options you select, a wide range of
74 - different structures can contain different fields
75 - Some functions may not be implemented at all, (i.e. some locks
76 compile away to nothing for non-SMP builds.)
[all …]
/Documentation/driver-api/dmaengine/
Dprovider.rst20 DMA-eligible devices to the controller itself. Whenever the device
44 transfer into smaller sub-transfers.
49 non-contiguous buffers to a contiguous buffer, which is called
50 scatter-gather.
53 scatter-gather. So we're left with two cases here: either we have a
56 that implements in hardware scatter-gather.
79 These were just the general memory-to-memory (also called mem2mem) or
80 memory-to-device (mem2dev) kind of transfers. Most devices often
98 documentation file in Documentation/crypto/async-tx-api.rst.
104 ------------------------------------
[all …]
/Documentation/sound/cards/
Dcmipci.rst2 Brief Notes on C-Media 8338/8738/8768/8770 Driver
8 Front/Rear Multi-channel Playback
9 ---------------------------------
13 DACs, both streams are handled independently unlike the 4/6ch multi-
22 - The first DAC supports U8 and S16LE formats, while the second DAC
24 - The second DAC supports only two channel stereo.
26 Please note that the CM8x38 DAC doesn't support continuous playback
51 control switch in the driver "Line-In As Rear", which you can change
52 via alsamixer or somewhat else. When this switch is on, line-in jack
60 4/6 Multi-Channel Playback
[all …]
/Documentation/networking/device_drivers/can/ctu/
Dctucanfd-driver.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
10 ------------------------
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
20 and Intel Cyclone V 5CSEMA4U23C6 based DE0-Nano-SoC Terasic board
21 `QSys integration <https://gitlab.fel.cvut.cz/canbus/intel-soc-ctucanfd>`_
23 `PCIe integration <https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd>`_ of the core.
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
34 development `repository <https://gitlab.fel.cvut.cz/canbus/qemu-canbus>`_.
38 ---------------
59 it allows for device hot-plug.
[all …]
/Documentation/hwmon/
Dsysfs-interface.rst5 through the sysfs interface. Since lm-sensors 3.0.0, libsensors is
6 completely chip-independent. It assumes that all the kernel drivers
10 This is a major improvement compared to lm-sensors 2.
22 For this reason, even if we aim at a chip-independent libsensors, it will
37 Up to lm-sensors 3.0.0, libsensors looks for hardware monitoring attributes
38 in the "physical" device directory. Since lm-sensors 3.0.1, attributes found
61 to cause an alarm) is chip-dependent.
69 ----------------
76 -------------------------------------------------------------------------
79 `[0-*]` denotes any positive number starting from 0
[all …]
/Documentation/admin-guide/
Dcgroup-v2.rst1 .. _cgroup-v2:
11 conventions of cgroup v2. It describes all userland-visible aspects
14 v1 is available under :ref:`Documentation/admin-guide/cgroup-v1/index.rst <cgroup-v1>`.
19 1-1. Terminology
20 1-2. What is cgroup?
22 2-1. Mounting
23 2-2. Organizing Processes and Threads
24 2-2-1. Processes
25 2-2-2. Threads
26 2-3. [Un]populated Notification
[all …]
/Documentation/kbuild/
Dkconfig-language.rst6 ------------
11 +- Code maturity level options
12 | +- Prompt for development and/or incomplete code/drivers
13 +- General setup
14 | +- Networking support
15 | +- System V IPC
16 | +- BSD Process Accounting
17 | +- Sysctl support
18 +- Loadable module support
19 | +- Enable loadable module support
[all …]
/Documentation/admin-guide/media/
Dipu3.rst1 .. SPDX-License-Identifier: GPL-2.0
24 ImgU). The CIO2 driver is available as drivers/media/pci/intel/ipu3/ipu3-cio2*
36 Both of the drivers implement V4L2, Media Controller and V4L2 sub-device
38 MIPI CSI-2 interfaces through V4L2 sub-device sensor drivers.
44 interface to the user space. There is a video node for each CSI-2 receiver,
47 The CIO2 contains four independent capture channel, each with its own MIPI CSI-2
48 receiver and DMA engine. Each channel is modelled as a V4L2 sub-device exposed
49 to userspace as a V4L2 sub-device node and has two pads:
53 .. flat-table::
54 :header-rows: 1
[all …]
/Documentation/sound/kernel-api/
Dwriting-an-alsa-driver.rst11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
19 low-level driver implementation details. It only describes the standard
26 -------
56 --------------
60 sub-directories contain different modules and are dependent upon the
74 This directory and its sub-directories are for the ALSA sequencer. This
76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
85 -----------------
88 to be exported to user-space, or included by several files in different
94 -----------------
[all …]

12