Home
last modified time | relevance | path

Searched +full:flow +full:- +full:controlled (Results 1 – 25 of 31) sorted by relevance

12

/Documentation/hwmon/
Daquacomputer_d5next.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Kernel driver aquacomputer-d5next
14 * Aquacomputer High Flow Next sensor
19 * Aquacomputer High Flow USB flow meter
20 * Aquacomputer MPS Flow devices
25 -----------
31 virtual temperature sensors, as well as two flow sensors. The fans expose their
33 can be controlled.
37 available through debugfs are the serial number, firmware version and power-on
38 count. Attaching a fan to it is optional and allows it to be controlled using
[all …]
/Documentation/networking/device_drivers/ethernet/freescale/
Ddpaa.rst1 .. SPDX-License-Identifier: GPL-2.0
8 - Madalin Bucur <madalin.bucur@nxp.com>
9 - Camelia Groza <camelia.groza@nxp.com>
13 - DPAA Ethernet Overview
14 - DPAA Ethernet Supported SoCs
15 - Configuring DPAA Ethernet in your kernel
16 - DPAA Ethernet Frame Processing
17 - DPAA Ethernet Features
18 - DPAA IRQ Affinity and Receive Side Scaling
19 - Debugging
[all …]
/Documentation/networking/device_drivers/ethernet/intel/
Di40e.rst1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 1999-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Intel(R) Ethernet Flow Director
16 - Additional Configurations
17 - Known Issues
18 - Support
47 ----------------------
49 …intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-m…
[all …]
/Documentation/networking/device_drivers/ethernet/netronome/
Dnfp.rst1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
5 Network Flow Processor (NFP) Kernel Drivers
14 - `Overview`_
15 - `Acquiring Firmware`_
16 - `Devlink Info`_
17 - `Configure Device`_
18 - `Statistics`_
23 This driver supports Netronome and Corigine's line of Network Flow Processor
25 are also incorporated in the companies' family of Agilio SmartNICs. The SR-IOV
35 Firmware files on the host filesystem contain card type (`AMDA-*` string), media
[all …]
/Documentation/userspace-api/media/v4l/
Ddev-osd.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 **Also known as On-Screen Display (OSD)**
57 ---------------------------------------------
59 .. code-block:: c
67 if (-1 == ioctl(fd, VIDIOC_G_FBUF, &fbuf)) {
79 if (-1 == fb_fd) {
99 fb_fd = -1;
103 for the video output overlay, or -1 if no device was found. */
109 The overlay is controlled by source and target rectangles. The source
143 direction of the data flow. For more information see :ref:`crop`.
/Documentation/userspace-api/media/
Dglossary.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
58 **Field-programmable Gate Array**
63 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
72 together make a larger user-facing functional peripheral. For
80 **Inter-Integrated Circuit**
82 A multi-master, multi-slave, packet switched, single-ended,
84 like sub-device hardware components.
86 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
120 - :term:`CEC API`;
121 - :term:`Digital TV API`;
[all …]
/Documentation/devicetree/bindings/dma/ti/
Dk3-udma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
5 ---
6 $id: http://devicetree.org/schemas/dma/ti/k3-udma.yaml#
7 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 - Peter Ujfalusi <peter.ujfalusi@gmail.com>
15 The UDMA-P is intended to perform similar (but significantly upgraded)
16 functions as the packet-oriented DMA used on previous SoC devices. The UDMA-P
18 The UDMA-P architecture facilitates the segmentation and reassembly of SoC DMA
28 is indirectly controlled by the order in which blocks are pushed into the DMA
29 on the Rx PSI-L interface.
[all …]
/Documentation/userspace-api/media/dvb/
Dintro.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
17 part I of the MPEG2 specification ISO/IEC 13818 (aka ITU-T H.222), i.e
19 meant by a packetized elementary stream (PES) or an I-frame.
23 - European standards (DVB): http://www.dvb.org and/or http://www.etsi.org.
24 - American standards (ATSC): https://www.atsc.org/standards/
25 - Japanese standards (ISDB): http://www.dibeg.org/
65 .. kernel-figure:: dvbstb.svg
71 A Digital TV card or set-top-box (STB) usually consists of the
76 antenna or directly from cable. The frontend down-converts and
84 the user has access (controlled by the smart card) are decoded in
[all …]
/Documentation/networking/
Dtipc.rst1 .. SPDX-License-Identifier: GPL-2.0
11 designed for intra-cluster communication. It can be configured to transmit
13 sequence guaranteed, loss free and flow controlled. Latency times are shorter
18 -------------
20 - Cluster wide IPC service
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 …]
Dip-sysctl.rst1 .. SPDX-License-Identifier: GPL-2.0
10 ip_forward - BOOLEAN
11 - 0 - disabled (default)
12 - not 0 - enabled
20 ip_default_ttl - INTEGER
25 ip_no_pmtu_disc - INTEGER
27 fragmentation-required ICMP is received, the PMTU to this
38 accept fragmentation-needed errors if the underlying protocol
48 Possible values: 0-3
52 min_pmtu - INTEGER
[all …]
Dsfp-phylink.rst1 .. SPDX-License-Identifier: GPL-2.0
10 phylink is a mechanism to support hot-pluggable networking modules
11 directly connected to a MAC without needing to re-initialise the
12 adapter on hot-plug events.
14 phylink supports conventional phylib-based setups, fixed link setups
35 3. In-band mode
37 In-band mode is used with 802.3z, SGMII and similar interface modes,
38 and we are expecting to use and honor the in-band negotiation or
43 .. code-block:: none
47 phy-mode = "sgmii";
[all …]
/Documentation/misc-devices/
Dxilinx_sdfec.rst1 .. SPDX-License-Identifier: GPL-2.0+
4 Xilinx SD-FEC Driver
10 This driver supports SD-FEC Integrated Block for Zynq |Ultrascale+ (TM)| RFSoCs.
15 …f SD-FEC core features, see the `SD-FEC Product Guide (PG256) <https://www.xilinx.com/cgi-bin/docs…
19 - Retrieval of the Integrated Block configuration and status information
20 - Configuration of LDPC codes
21 - Configuration of Turbo decoding
22 - Monitoring errors
24 Missing features, known issues, and limitations of the SD-FEC driver are as
27 - Only allows a single open file handler to any instance of the driver at any time
[all …]
/Documentation/dev-tools/
Dtesting-overview.rst1 .. SPDX-License-Identifier: GPL-2.0
26 ------------------------------------------
28 KUnit (Documentation/dev-tools/kunit/index.rst) is an entirely in-kernel system
32 KUnit tests therefore are best written against small, self-contained parts
44 Documentation/dev-tools/kunit/style.rst
47 kselftest (Documentation/dev-tools/kselftest.rst), on the other hand, is
62 details. This aligns well with 'system' or 'end-to-end' testing.
72 and for finding corner-cases which are not covered by the appropriate test.
74 Documentation/dev-tools/gcov.rst is GCC's coverage testing tool, which can be
75 used with the kernel to get global or per-module coverage. Unlike KCOV, it
[all …]
/Documentation/i2c/
Ddev-interface.rst5 Usually, I2C devices are controlled by a kernel driver. But it is also
7 the /dev interface. You need to load module i2c-dev for this.
10 examine /sys/class/i2c-dev/ to see what number corresponds to which adapter.
11 Alternatively, you can run "i2cdetect -l" to obtain a formatted list of all
13 the i2c-tools package.
17 explained above. They should be called "i2c-%d" (i2c-0, i2c-1, ...,
18 i2c-10, ...). All 256 minor device numbers are reserved for I2C.
27 #include <linux/i2c-dev.h>
31 inspect /sys/class/i2c-dev/ or run "i2cdetect -l" to decide this.
41 snprintf(filename, 19, "/dev/i2c-%d", adapter_nr);
[all …]
/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
Dethernet-driver.rst1 .. SPDX-License-Identifier: GPL-2.0
8 :Copyright: |copy| 2017-2018 NXP
24 - network interfaces
25 - queues, channels
26 - buffer pools
27 - MAC/PHY
31 and exposes ABIs through which they can be configured and controlled. A few
45 -----------------------
47 -----------------------
53 ---------- ---------- -----------
[all …]
/Documentation/security/
Dself-protection.rst2 Kernel Self-Protection
5 Kernel self-protection is the design and implementation of systems and
13 In the worst-case scenario, we assume an unprivileged local attacker
23 The goals for successful self-protection systems would be that they
24 are effective, on by default, require no opt-in by developers, have no
36 from limiting the exposed APIs available to userspace, making in-kernel
41 --------------------------------
44 to redirect execution flow. To reduce the availability of these targets
47 Executable code and read-only data must not be writable
61 writable, data is not executable, and read-only data is neither writable
[all …]
Dsnp-tdx-threat-model.rst17 the kernel through various networking or limited HW-specific exposed
47 more tightly controlled guest interrupt injection, as well as some
48 additional mechanisms to control guest-host page mapping. More details on
49 the x86-specific solutions can be found in
51 …https://www.amd.com/system/files/techdocs/sev-snp-strengthening-vm-isolation-with-integrity-protec…
56 that acts as a security manager. The host-side virtual machine monitor
63 In the following diagram, the "<--->" lines represent bi-directional
65 the rest of the components (data flow for guest, host, hardware) ::
67 +-------------------+ +-----------------------+
68 | CoCo guest VM |<---->| |
[all …]
/Documentation/devicetree/bindings/usb/
Dsnps,dwc3.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Felipe Balbi <balbi@kernel.org>
14 be presented as a standalone DT node with an optional vendor-specific
18 - $ref: usb-drd.yaml#
19 - if:
25 - dr_mode
29 $ref: usb-xhci.yaml#
35 - const: snps,dwc3
[all …]
/Documentation/sound/soc/
Ddapm.rst11 management frameworks and, as such, can easily co-exist with them.
24 can flow from one widget to the other
32 The graph for the STM32MP1-DK1 sound card is shown in picture:
34 .. kernel-figure:: dapm-graph.svg
46 Usually controlled at codec probe/remove and suspend/resume, although
139 (Widgets are defined in include/sound/soc-dapm.h)
142 There are convenience macros defined in soc-dapm.h that can be used to quickly
150 ---------------------
179 -------------------
208 ----------------------
[all …]
/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.rst13 There are two flavors of RCU (RCU-preempt and RCU-sched), with an earlier
14 third RCU-bh flavor having been implemented in terms of the other two.
38 RCU-preempt Expedited Grace Periods
41 ``CONFIG_PREEMPTION=y`` kernels implement RCU-preempt.
42 The overall flow of the handling of a given CPU by an RCU-preempt
45 .. kernel-figure:: ExpRCUFlow.svg
59 can check to see if the CPU is currently running in an RCU read-side
63 invocation will provide the needed quiescent-state report.
64 This flag-setting avoids the previous forced preemption of all
65 CPUs that might have RCU read-side critical sections.
[all …]
/Documentation/driver-api/
Dclk.rst22 clk which unifies the framework-level accounting and infrastructure that
28 The second half of the interface is comprised of the hardware-specific
30 hardware-specific structures needed to model a particular clock. For
32 clk_ops, such as .enable or .set_rate, implies the hardware-specific
35 hardware-specific bits for the hypothetical "foo" hardware.
62 api itself defines several driver-facing functions which operate on
66 clk_ops pointer in struct clk_core to perform the hardware-specific parts of
67 the operations defined in clk-provider.h::
107 which abstract the details of struct clk from the hardware-specific bits, and
109 drivers/clk/clk-gate.c::
[all …]
Dvfio.rst2 VFIO - "Virtual Function I/O" [1]_
7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d,
12 safe [2]_, non-privileged, userspace drivers.
19 bare-metal device drivers [3]_.
22 field, also benefit from low-overhead, direct device access from
23 userspace. Examples include network adapters (often non-TCP/IP based)
36 ---------------------------
42 as allowing a device read-write access to system memory imposes the
55 For instance, an individual device may be part of a larger multi-
59 could be anything from a multi-function PCI device with backdoors
[all …]
/Documentation/admin-guide/sysctl/
Dnet.rst9 - Terrehon Bowden <terrehon@pacbell.net>
10 - Bodo Bauer <bb@ricochet.net>
14 - Jorge Nerin <comandante@zaralinux.com>
18 - Shen Feng <shen@cn.fujitsu.com>
22 ------------------------------------------------------------------------------
47 1. /proc/sys/net/core - Network core options
51 --------------
63 - x86_64
64 - x86_32
65 - arm64
[all …]
/Documentation/driver-api/gpio/
Ddriver.rst26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
44 So for example one platform could use global numbers 32-159 for GPIOs, with a
46 global numbers 0..63 with one set of GPIO controllers, 64-79 with another type
47 of GPIO controller, and on one particular board 80-95 with an FPGA. The legacy
49 2000-2063 to identify GPIO lines in a bank of I2C GPIO expanders.
60 - methods to establish GPIO line direction
61 - methods used to access GPIO line values
62 - method to set electrical configuration for a given GPIO line
[all …]
/Documentation/hid/
Dhid-bpf.rst1 .. SPDX-License-Identifier: GPL-2.0
4 HID-BPF
17 When (and why) to use HID-BPF
20 There are several use cases when using HID-BPF is better
24 -----------------------
30 With HID-BPF, we can apply this filtering in the kernel directly so userspace
38 HID-BPF allows the userspace program to load the program itself, ensuring we
42 ---------------------------------
57 ------------------------------------------------
63 on eBPF to have the kernel API controlled by the consumer and to not
[all …]

12