| /Linux-v4.19/Documentation/media/uapi/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.
58 - Original author of the V4L2 API and documentation.
66 - Designed and documented the multi-planar API.
74 - Introduce HSV formats and other minor changes.
78 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls.
86 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl…
91 part can be used and distributed without restrictions.
105 ctrl_class and which. Which is used to select the current value of the
[all …]
|
| D | hist-v4l2.rst | 11 and began to work on documentation, example drivers and applications.
14 another four years and two stable kernel releases until the new API was
28 meaningless ``O_TRUNC`` :ref:`open() <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 …]
|
| D | crop.rst | 6 Image Cropping, Insertion and Scaling -- the CROP API
14 implemented by :ref:`VIDIOC_CROPCAP <VIDIOC_CROPCAP>` and has no
18 Some video capture devices can sample a subsection of the picture and
20 abilities cropping and scaling. Some video output devices can scale an
21 image up or down and insert it at an arbitrary scan line and horizontal
25 signal, query the default area and the hardware limits.
30 :ref:`VIDIOC_G_CROP <VIDIOC_G_CROP>` and :ref:`VIDIOC_S_CROP
33 Scaling requires a source and a target. On a video capture or overlay
34 device the source is the video signal, and the cropping ioctls determine
36 or overlaid onto the graphics screen. Their size (and position for an
[all …]
|
| /Linux-v4.19/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 7 POHMELFS first began as a network filesystem with coherent local data and
11 * Locally coherent cache for data and metadata with (potentially) byte-range locks.
13 is very simple and does not use byte-ranges, although they are sent in
15 * Completely async processing of all events except creation of hard and symbolic
16 links, and rename events.
17 Object creation and data reading and writing are processed asynchronously.
19 Ability to create long paths to objects and remove arbitrarily huge
23 * Fast and scalable multithreaded userspace server. Being in userspace it works
24 with any underlying filesystem and still is much faster than async in-kernel NFS one.
26 automatically reconnects to second and so on).
[all …]
|
| /Linux-v4.19/Documentation/filesystems/cifs/ |
| D | AUTHORS | 5 The author wishes to express his appreciation and thanks to:
7 improvements. Thanks to IBM for allowing me time and test resources to pursue
8 this project, to Jim McDonough from IBM (and the Samba Team) for his help, to
11 side of the original CIFS Unix extensions and reviewing and implementing
16 Newbigin and others for their work on the Linux smbfs module. Thanks to
18 Workgroup for their work specifying this highly complex protocol and finally
19 thanks to the Samba team for their technical advice and encouragement.
33 Vince Negri and Dave Stahl (for finding an important caching bug)
38 Shaggy (Dave Kleikamp) for innumerable small fs suggestions and some good cleanup
39 Gunter Kukkukk (testing and suggestions for support of old servers)
[all …]
|
| D | TODO | 8 is a partial list of the known problems and missing features:
10 a) SMB3 (and SMB3.02) missing optional features:
13 - T10 copy offload ie "ODX" (copy chunk, and "Duplicate Extents" ioctl
24 e) Compounding (in progress) to reduce number of roundtrips, and also
27 f) Finish inotify support so kde and gnome file list windows
31 g) Add GUI tool to configure /proc/fs/cifs settings and for display of
34 h) implement support for security and trusted categories of xattrs
44 k) Add tools to take advantage of more smb3 specific ioctls and features
53 file attribute via chflags) and improve user space tools for managing and
60 move, server failover, and server adapter changes. And also improve other
[all …]
|
| /Linux-v4.19/Documentation/timers/ |
| D | hrtimers.txt | 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-v4.19/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-v4.19/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 on the AMD 76x
114 Support for error detection and correction on the Intel
[all …]
|
| /Linux-v4.19/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-v4.19/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 11 communication between Modem and host. The host processes can open virtual AT
12 channels, initiate GPRS Data connections, Video channels and Utility Channels.
13 The Utility Channels are general purpose pipes between modem and host.
16 and host. Currently, UART and Loopback are available for Linux.
22 * CAIF Socket Layer and GPRS IP Interface.
59 The architecture is inspired by the design patterns "Protocol Layer" and
69 CAIF payload with receive and transmit functions.
70 - Clients must call configuration function to add and connect the
77 The CAIF protocol can be divided into two parts: Support functions and Protocol
81 CAIF Packet has functions for creating, destroying and adding content
[all …]
|
| /Linux-v4.19/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-v4.19/Documentation/hwmon/ |
| D | smsc47m192 | 5 * SMSC LPC47M192, LPC47M15x, LPC47M292 and LPC47M997
10 The LPC47M15x, LPC47M292 and LPC47M997 are compatible for
15 of the code and many helpful comments and suggestions.
22 of the SMSC LPC47M192 and compatible Super-I/O chips.
24 These chips support 3 temperature channels and 8 voltage inputs
27 They do also have fan monitoring and control capabilities, but the
28 these features are accessed via ISA bus and are not supported by this
29 driver. Use the 'smsc47m1' driver for fan monitoring and control.
31 Voltages and temperatures are measured by an 8-bit ADC, the resolution
37 Both voltage and temperature values are scaled by 1000, the sys files
[all …]
|
| /Linux-v4.19/drivers/pinctrl/intel/ |
| D | Kconfig | 16 platforms. Supports 3 banks with 102, 28 and 44 gpios.
23 tristate "Intel Cherryview/Braswell pinctrl and GPIO driver"
32 allows configuring of SoC pins and using them as GPIOs.
42 interface that allows configuring of SoC pins and using them as
54 tristate "Intel Broxton pinctrl and GPIO driver"
59 configuring of SoC pins and using them as GPIOs.
62 tristate "Intel Cannon Lake PCH pinctrl and GPIO driver"
67 of Intel Cannon Lake PCH pins and using them as GPIOs.
70 tristate "Intel Cedar Fork pinctrl and GPIO driver"
75 of Intel Cedar Fork PCH pins and using them as GPIOs.
[all …]
|
| /Linux-v4.19/Documentation/fb/ |
| D | internals.txt | 19 Device independent unchangeable information about a frame buffer device and
25 Device independent changeable information about a frame buffer device and a
27 ioctl, and updated with the FBIOPUT_VSCREENINFO ioctl. If you want to pan
32 Device independent colormap information. You can get and set the colormap
33 using the FBIOGETCMAP and FBIOPUTCMAP ioctls.
40 Generic information, API and low level information about a specific frame
54 Monochrome (FB_VISUAL_MONO01 and FB_VISUAL_MONO10)
59 Pseudo color (FB_VISUAL_PSEUDOCOLOR and FB_VISUAL_STATIC_PSEUDOCOLOR)
62 color (including red, green, and blue intensities) for each possible pixel
63 value, and that color is displayed.
[all …]
|
| D | api.txt | 11 with frame buffer devices. In-kernel APIs between device drivers and the frame
15 behaviours differ in subtle (and not so subtle) ways. This document describes
23 Device and driver capabilities are reported in the fixed screen information
33 expect from the device and driver.
42 2. Types and visuals
49 Formats are described by frame buffer types and visuals. Some visuals require
51 bits_per_pixel, grayscale, red, green, blue and transp fields.
53 Visuals describe how color information is encoded and assembled to create
55 types and visuals are supported.
63 Padding at end of lines may be present and is then reported through the fixed
[all …]
|
| /Linux-v4.19/Documentation/media/v4l-drivers/ |
| D | soc-camera.rst | 11 of connecting to a variety of systems and interfaces, typically uses i2c for
12 control and configuration, and a parallel or a serial bus for data.
14 specialised interface, present on many SoCs, e.g. PXA27x and PXA3xx, SuperH,
16 - camera host bus - a connection between a camera host and a camera. Can be
17 parallel or serial, consists of data and control lines, e.g. clock, vertical
18 and horizontal synchronization signals.
24 drivers and camera sensor drivers. Later the soc-camera sensor API has been
33 The subsystem has been designed to support multiple camera host interfaces and
42 omap1_camera.c, pxa_camera.c, sh_mobile_ceu_camera.c, and multiple sensor
82 .add and .remove methods are called when a sensor is attached to or detached
[all …]
|
| /Linux-v4.19/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-v4.19/Documentation/w1/masters/ |
| D | ds2490 | 17 which has 0x81 family ID integrated chip and DS2490
20 Notes and limitations.
21 - The weak pullup current is a minimum of 0.9mA and maximum of 6.0mA.
22 - The 5V strong pullup is supported with a minimum of 5.9mA and a
30 a write buffer and a read buffer (along with sizes) as arguments.
32 buffer, and strong pullup all in one command, instead of the current
33 1 reset bus, 2 write the match rom command and slave rom id, 3 block
34 write and read data. The write buffer needs to have the match rom
35 command and slave rom id prepended to the front of the requested
37 - The hardware supports normal, flexible, and overdrive bus
[all …]
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/ |
| D | intel_txt.txt | 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 …]
|
| /Linux-v4.19/Documentation/filesystems/nfs/ |
| D | nfs-rdma.txt | 7 Author: NetApp and Open Grid Computing
15 - Check RDMA and NFS Setup
21 This document describes how to install and setup the Linux NFS/RDMA client
22 and server software.
29 the full Connectathon test suite and operates over both Infiniband and iWARP
52 Ammasso AMS1100 iWARP adapter, and the Chelsio cxgb3 iWARP adapter.
54 - Install a Linux distribution and tools
56 The first kernel release to contain both the NFS/RDMA client and server was
57 Linux 2.6.25 Therefore, a distribution compatible with this and subsequent
80 Uncompress the package and follow the installation instructions.
[all …]
|
| /Linux-v4.19/Documentation/core-api/ |
| D | workqueue.rst | 14 is needed and the workqueue (wq) API is the most commonly used
20 queue is called workqueue and the thread is called worker.
32 worker thread per CPU and a single threaded (ST) wq had one worker
35 wq users over the years and with the number of CPU cores continuously
40 provided was unsatisfactory. The limitation was common to both ST and
47 The tension between the provided level of concurrency and resource
49 choosing to use ST wq for polling PIOs and accepting an unnecessary
64 * Automatically regulate worker pool and level of concurrency so that
77 item pointing to that function and queue that work item on a
86 subsystems and drivers queue work items on and the backend mechanism
[all …]
|
| /Linux-v4.19/Documentation/bpf/ |
| D | bpf_design_QA.rst | 5 BPF extensibility and applicability to networking, tracing, security
6 in the linux kernel and several user space implementations of BPF
8 This short QA is an attempt to address that and outline a direction
15 Questions and Answers
18 Q: Is BPF a generic instruction set similar to x64 and arm64?
34 with two most used architectures x64 and arm64 (and takes into
35 consideration important quirks of other architectures) and
47 (unlike x64 ISA that allows msft, cdecl and other conventions)
67 of kernel helper functions and kernel objects like BPF maps with
69 BPF programs and programs call kernel helpers with zero overhead.
[all …]
|
