| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | v4l2.rst | 39 Revision and Copyright
50 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter.
54 - Original author of the V4L2 API and documentation.
63 - Original author of the V4L2 API and documentation.
76 - Designed and documented the multi-planar API.
84 - Introduce HSV formats and other minor changes.
88 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls.
96 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl…
101 part can be used and distributed without restrictions.
115 ctrl_class and which. Which is used to select the current value of the
[all …]
|
| D | hist-v4l2.rst | 12 and began to work on documentation, example drivers and applications.
15 another four years and two stable kernel releases until the new API was
28 meaningless ``O_TRUNC`` :c:func:`open()` flag, and the
29 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set
32 identifiers are now ordinals instead of flags, and the
33 ``video_std_construct()`` helper function takes id and
40 struct ``video_standard`` and the color subcarrier fields were
53 and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio
55 :ref:`VIDIOC_G_CTRL <VIDIOC_G_CTRL>` and
59 module. The ``YUV422`` and ``YUV411`` planar image formats were added.
[all …]
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | xdpe12284.rst | 25 The family includes XDPE12284 and XDPE12254 devices.
28 - Intel VR13 and VR13HC rev 1.3, IMVP8 rev 1.2 and IMPVP9 rev 1.3 DC-DC
33 Devices support linear format for reading input voltage, input and output current,
34 input and output power and temperature.
44 The driver provides for current: input, maximum and critical thresholds
45 and maximum and critical alarms. Critical thresholds and critical alarm are
48 indexes 1, 2 are for "iin" and 3, 4 for "iout":
62 The driver provides for voltage: input, critical and low critical thresholds
63 and critical and low critical alarms.
65 indexes 1, 2 are for "vin" and 3, 4 for "vout":
[all …]
|
| D | smsc47m192.rst | 6 * SMSC LPC47M192, LPC47M15x, LPC47M292 and LPC47M997
16 The LPC47M15x, LPC47M292 and LPC47M997 are compatible for
26 of the code and many helpful comments and suggestions.
33 of the SMSC LPC47M192 and compatible Super-I/O chips.
35 These chips support 3 temperature channels and 8 voltage inputs
38 They do also have fan monitoring and control capabilities, but the
39 these features are accessed via ISA bus and are not supported by this
40 driver. Use the 'smsc47m1' driver for fan monitoring and control.
42 Voltages and temperatures are measured by an 8-bit ADC, the resolution
48 Both voltage and temperature values are scaled by 1000, the sys files
[all …]
|
| D | mp2975.rst | 25 - Provides 8 pulse-width modulations (PWMs), and can be configured up
26 to 8-phase operation for rail 1 and up to 4-phase operation for rail
28 - Supports two pages 0 and 1 for telemetry and also pages 2 and 3 for
30 - Can configured VOUT readout in direct or VID format and allows
31 setting of different formats on rails 1 and 2. For VID the following
45 input and output power and temperature.
46 Device supports linear format for reading input voltage and input power.
47 Device supports VID and direct formats for reading output voltage.
53 - for current out input, maximum alarm and highest values;
54 - for phase current: input and label.
[all …]
|
| /Linux-v5.10/drivers/pinctrl/intel/ |
| D | Kconfig | 12 platforms. Supports 3 banks with 102, 28 and 44 gpios.
19 tristate "Intel Cherryview/Braswell pinctrl and GPIO driver"
24 allows configuring of SoC pins and using them as GPIOs.
27 tristate "Intel Lynxpoint pinctrl and GPIO driver"
36 provides an interface that allows configuring of PCH pins and
47 interface that allows configuring of SoC pins and using them as
59 tristate "Intel Broxton pinctrl and GPIO driver"
64 configuring of SoC pins and using them as GPIOs.
67 tristate "Intel Cannon Lake PCH pinctrl and GPIO driver"
72 of Intel Cannon Lake PCH pins and using them as GPIOs.
[all …]
|
| /Linux-v5.10/drivers/edac/ |
| D | Kconfig | 4 # Licensed and distributed under the GPL
40 levels are 0-4 (from low to high) and by default it is set to 2.
68 It should be noticed that keeping both GHES and a hardware-driven
81 Support for error detection and correction of DRAM ECC errors on
88 Recent Opterons (Family 10h and later) provide for Memory Error
90 allows the operator/user to inject Uncorrectable and Correctable
100 In addition, there are two control files, inject_read and inject_write,
101 which trigger the DRAM ECC Read and Write respectively.
107 Support for error detection and correction for Amazon's Annapurna
108 Labs Alpine chips which allow 1 bit correction and 2 bits detection.
[all …]
|
| /Linux-v5.10/Documentation/timers/ |
| D | hrtimers.rst | 9 back and forth trying to integrate high-resolution and high-precision
10 features into the existing timer framework, and after testing various
14 to solve this'), and spent a considerable effort trying to integrate
18 - the forced handling of low-resolution and high-resolution timers in
19 the same way leads to a lot of compromises, macro magic and #ifdef
20 mess. The timers.c code is very "tightly coded" around jiffies and
21 32-bitness assumptions, and has been honed and micro-optimized for a
23 for many years - and thus even small extensions to it easily break
25 code is very good and tight code, there's zero problems with it in its
45 error conditions in various I/O paths, such as networking and block
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/cifs/ |
| D | authors.rst | 10 The author wishes to express his appreciation and thanks to:
12 improvements. Thanks to IBM for allowing me time and test resources to pursue
13 this project, to Jim McDonough from IBM (and the Samba Team) for his help, to
16 side of the original CIFS Unix extensions and reviewing and implementing
21 Newbigin and others for their work on the Linux smbfs module. Thanks to
23 Workgroup for their work specifying this highly complex protocol and finally
24 thanks to the Samba team for their technical advice and encouragement.
39 - Vince Negri and Dave Stahl (for finding an important caching bug)
44 - Shaggy (Dave Kleikamp) for innumerable small fs suggestions and some good cleanup
45 - Gunter Kukkukk (testing and suggestions for support of old servers)
[all …]
|
| D | todo.rst | 12 is a partial list of the known problems and missing features:
14 a) SMB3 (and SMB3.1.1) missing optional features:
18 - T10 copy offload ie "ODX" (copy chunk, and "Duplicate Extents" ioctl
21 b) improved sparse file support (fiemap and SEEK_HOLE are implemented
31 open/query/close and open/setinfo/close) to reduce the number of
32 roundtrips to the server and improve performance. Various cases
36 handle caching leases) and better using reference counters on file
39 f) Finish inotify support so kde and gnome file list windows
43 g) Add GUI tool to configure /proc/fs/cifs settings and for display of
46 h) implement support for security and trusted categories of xattrs
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | debugfs-hisi-sec | 7 Only available for PF, and take no other effect on SEC.
12 Description: One SEC controller has one PF and multiple VFs, each function
21 Available for PF and VF in host. VF in guest currently only
37 Only available for PF, and take no other effect on SEC.
44 Available for both PF and VF, and take no other effect on SEC.
50 Available for both PF and VF, and take no other effect on SEC.
56 Available for both PF and VF, and take no other effect on SEC.
62 Available for both PF and VF, and take no other effect on SEC.
68 Available for both PF and VF, and take no other effect on SEC.
74 Four states: initiated, started, stopped and closed.
[all …]
|
| D | debugfs-hisi-hpre | 11 and then we can read the debug information of the core.
26 Description: One HPRE controller has one PF and multiple VFs, each function
40 Available for PF and VF in host. VF in guest currently only
64 Available for both PF and VF, and take no other effect on HPRE.
70 Available for both PF and VF, and take no other effect on HPRE.
76 Available for both PF and VF, and take no other effect on HPRE.
82 Available for both PF and VF, and take no other effect on HPRE.
88 Available for both PF and VF, and take no other effect on HPRE.
94 Four states: initiated, started, stopped and closed.
95 Available for both PF and VF, and take no other effect on HPRE.
[all …]
|
| /Linux-v5.10/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 36 * 06-06-00 01.00.01 Update MPI_VERSION_MAJOR and MPI_VERSION_MINOR.
52 * Added defines for MPI_DIAG_PREVENT_IOC_BOOT and
68 * 11-15-02 01.02.08 Added define MPI_IOCSTATUS_TARGET_INVALID_IO_INDEX and
74 * and MPI_FUNCTION_DIAG_RELEASE.
81 * Added new function codes and new IOCStatus codes.
88 * 03-11-05 01.05.07 Removed function codes for SCSI IO 32 and
91 * 06-24-05 01.05.08 Added function codes for SCSI IO 32 and
114 * _LINK_STATUS, _LOOP_STATE and _LOGOUT.
115 * 08-11-00 01.00.05 Switched positions of MsgLength and Function fields in
119 * 12-04-00 01.01.02 Modified IOCFacts reply, added FWUpload messages, and
[all …]
|
| /Linux-v5.10/Documentation/networking/caif/ |
| D | linux_caif.rst | 18 communication between Modem and host. The host processes can open virtual AT
19 channels, initiate GPRS Data connections, Video channels and Utility Channels.
20 The Utility Channels are general purpose pipes between modem and host.
23 and host. Currently, UART and Loopback are available for Linux.
31 * CAIF Socket Layer and GPRS IP Interface.
69 The architecture is inspired by the design patterns "Protocol Layer" and
82 CAIF payload with receive and transmit functions.
83 - Clients must call configuration function to add and connect the
91 The CAIF protocol can be divided into two parts: Support functions and Protocol
95 CAIF Packet has functions for creating, destroying and adding content
[all …]
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | references.txt | 1 This document provides background reading for memory models and related
6 Hardware manuals and models
18 o Intel Corporation (Ed.). 2002. "Intel 64 and IA-32 Architectures
22 and Magnus O. Myreen. 2010. "x86-TSO: A Rigorous and Usable
29 o ARM Ltd. (Ed.). 2009. "ARM Barrier Litmus Tests and Cookbook".
32 o Susmit Sarkar, Peter Sewell, Jade Alglave, Luc Maranget, and
35 Language Design and Implementation (PLDI ’11). ACM, New York,
39 Peter Sewell, Luc Maranget, Jade Alglave, and Derek Williams.
40 2012. "Synchronising C/C++ and POWER". In Proceedings of the 33rd
41 ACM SIGPLAN Conference on Programming Language Design and
[all …]
|
| /Linux-v5.10/tools/power/cpupower/ |
| D | README | 7 For compilation pciutils-devel (pci/pci.h) and a gcc version
16 tools and programs to the cpufreq core and drivers in the Linux kernel. This
18 the interaction to the cpufreq core, and support for both the sysfs and proc
22 compilation and installation
30 /usr/lib; cpupower, cpufreq-bench_plot.sh to put in /usr/bin; and
32 differently and/or want to configure the package to your specific
33 needs, you need to open "Makefile" with an editor of your choice and
39 Many thanks to Mattia Dongili who wrote the autotoolization and
40 libtoolization, the manpages and the italian language file for cpupower;
41 to Dave Jones for his feedback and his dump_psb tool; to Bruno Ducrot for his
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | perf-security.rst | 3 Perf events and tool security
12 direct usage of perf_events system call API [2]_ and over data files
15 units (PMU) [2]_ and Perf collect and expose for performance analysis.
16 Collected system and performance data may be split into several
19 1. System hardware and software configuration data, for example: a CPU
20 model and its cache configuration, an amount of available memory and
21 its topology, used kernel and Perf versions, performance monitoring
25 2. User and kernel module paths and their load addresses with sizes,
26 process and thread names with their PIDs and TIDs, timestamps for
27 captured hardware and software events.
[all …]
|
| /Linux-v5.10/Documentation/fb/ |
| D | api.rst | 12 with frame buffer devices. In-kernel APIs between device drivers and the frame
16 behaviours differ in subtle (and not so subtle) ways. This document describes
24 Device and driver capabilities are reported in the fixed screen information
34 expect from the device and driver.
43 2. Types and visuals
50 Formats are described by frame buffer types and visuals. Some visuals require
52 bits_per_pixel, grayscale, red, green, blue and transp fields.
54 Visuals describe how color information is encoded and assembled to create
56 types and visuals are supported.
64 Padding at end of lines may be present and is then reported through the fixed
[all …]
|
| D | internals.rst | 25 Device independent unchangeable information about a frame buffer device and
31 Device independent changeable information about a frame buffer device and a
33 ioctl, and updated with the FBIOPUT_VSCREENINFO ioctl. If you want to pan
38 Device independent colormap information. You can get and set the colormap
39 using the FBIOGETCMAP and FBIOPUTCMAP ioctls.
46 Generic information, API and low level information about a specific frame
59 Monochrome (FB_VISUAL_MONO01 and FB_VISUAL_MONO10)
64 Pseudo color (FB_VISUAL_PSEUDOCOLOR and FB_VISUAL_STATIC_PSEUDOCOLOR)
67 color (including red, green, and blue intensities) for each possible pixel
68 value, and that color is displayed.
[all …]
|
| /Linux-v5.10/Documentation/RCU/ |
| D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by
7 and search engines will usually find what you are looking for.
9 The first thing resembling RCU was published in 1980, when Kung and Lehman
16 In 1982, Manber and Ladner [Manber82,Manber84] recommended deferring
22 In 1986, Hennessy, Osisek, and Seigh [Hennessy89] introduced passive
47 write-side contention and parallelize the other write-side overheads by
56 error, which typically slows convergence and thus increases the number of
61 structured data, such as the matrices used in scientific programs, and
88 Their approach requires memory barriers (and thus pipeline stalls),
89 but reduces memory latency, contention, and locking overheads.
[all …]
|
| /Linux-v5.10/Documentation/usb/ |
| D | CREDITS | 31 Linux USB driver effort and writing much of the larger uusbd driver.
35 and offering suggestions and sharing implementation experiences.
37 Additional thanks to the following companies and people for donations
38 of hardware, support, time and development (this is from the original
44 - 3Com GmbH for donating a ISDN Pro TA and supporting me
45 in technical questions and with test equipment. I'd never
52 Operating System and supports this project with
74 protocol. They've also donated a F-23 digital joystick and a
79 leading manufacturer for active and passive ISDN Controllers
80 and CAPI 2.0-based software. The active design of the AVM B1
[all …]
|
| /Linux-v5.10/Documentation/w1/masters/ |
| D | ds2490.rst | 19 which has 0x81 family ID integrated chip and DS2490
22 Notes and limitations.
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
33 a write buffer and a read buffer (along with sizes) as arguments.
35 buffer, and strong pullup all in one command, instead of the current
36 1 reset bus, 2 write the match rom command and slave rom id, 3 block
37 write and read data. The write buffer needs to have the match rom
38 command and slave rom id prepended to the front of the requested
40 - The hardware supports normal, flexible, and overdrive bus
[all …]
|
| /Linux-v5.10/drivers/infiniband/ulp/rtrs/ |
| D | README | 7 between client and server machines using RDMA (InfiniBand, RoCE, iWarp)
15 RTRS provides I/O fail-over and load-balancing capabilities by using
16 multipath I/O (see "add_path" and "mp_policy" configuration entries in
27 An established connection between a client and a server is called rtrs
31 between client and server. Those are used for load balancing and failover.
36 chunks reserved for him on the server side. Their number, size and addresses
37 need to be exchanged between client and server during the connection
39 inform the server about the session name and identify each path and connection
44 acknowledged and for errno. Client uses immediate field to tell the server
45 which of the memory chunks has been accessed and at which offset the message
[all …]
|
| /Linux-v5.10/Documentation/process/ |
| D | code-of-conduct.rst | 9 In the interest of fostering an open and welcoming environment, we as
10 contributors and maintainers pledge to making participation in our project and
12 size, disability, ethnicity, sex characteristics, gender identity and
14 personal appearance, race, religion, or sexual identity and orientation.
22 * Using welcoming and inclusive language
23 * Being respectful of differing viewpoints and experiences
31 * The use of sexualized language or imagery and unwelcome sexual attention or
33 * Trolling, insulting/derogatory comments, and personal or political attacks
45 and are expected to take appropriate and fair corrective action in response to
48 Maintainers have the right and responsibility to remove, edit, or reject
[all …]
|
| /Linux-v5.10/Documentation/x86/ |
| D | intel_txt.rst | 15 - Measurement and verification of launched environment
17 Intel TXT is part of the vPro(TM) brand and is also available some
19 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell
20 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45,
21 PM45, and GS45 Express chipsets.
47 uses Intel TXT to perform a measured and verified launch of an OS
55 w/ TXT support since v3.2), and now Linux kernels.
61 While there are many products and technologies that attempt to
64 Measurement Architecture (IMA) and Linux Integrity Module interface
69 starting at system reset and requires measurement of all code
[all …]
|
