| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | v4l2.rst | 35 Revision and Copyright
46 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter.
50 - Original author of the V4L2 API and documentation.
59 - Original author of the V4L2 API and documentation.
72 - Designed and documented the multi-planar API.
80 - Introduce HSV formats and other minor changes.
84 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls.
92 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl…
97 part can be used and distributed without restrictions.
111 ctrl_class and which. Which is used to select the current value of the
[all …]
|
| H A 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 …]
|
| H A D | crop.rst | 7 Image Cropping, Insertion and Scaling -- the CROP API
15 implemented by :ref:`VIDIOC_CROPCAP <VIDIOC_CROPCAP>` and has no
19 Some video capture devices can sample a subsection of the picture and
21 abilities cropping and scaling. Some video output devices can scale an
22 image up or down and insert it at an arbitrary scan line and horizontal
26 signal, query the default area and the hardware limits.
31 :ref:`VIDIOC_G_CROP <VIDIOC_G_CROP>` and :ref:`VIDIOC_S_CROP
34 Scaling requires a source and a target. On a video capture or overlay
35 device the source is the video signal, and the cropping ioctls determine
37 or overlaid onto the graphics screen. Their size (and position for an
[all …]
|
| /linux/LICENSES/deprecated/ |
| H A D | CC0-1.0 | 25 exclusive Copyright and Related Rights (defined below) upon the creator
26 and subsequent owner(s) (each and all, an "owner") of an original work of
27 authorship and/or a database (each, a "Work").
30 the purpose of contributing to a commons of creative, cultural and
31 scientific works ("Commons") that the public can reliably and without fear
33 works, reuse and redistribute as freely as possible in any form whatsoever
34 and for any purposes, including without limitation commercial purposes.
36 culture and the further production of creative, cultural and scientific
38 part through the use and efforts of others.
40 For these and/or other purposes and motivations, and without any
[all …]
|
| /linux/Documentation/hwmon/ |
| H A D | xdpe152c4.rst | 24 XDPE152C4 and XDPE15284 dual loop voltage regulators.
27 - Intel VR13, VR13HC and VR14 rev 1.86
32 Devices support linear format for reading input and output voltage, input
33 and output current, input and output power and temperature.
37 The driver provides for current: input, maximum and critical thresholds
38 and maximum and critical alarms. Low Critical thresholds and Low critical alarm are
41 indexes 1, 2 are for "iin" and 3, 4 for "iout":
61 The driver provides for voltage: input, critical and low critical thresholds
62 and critical and low critical alarms.
64 indexes 1, 2 are for "vin" and 3, 4 for "vout":
[all …]
|
| H A D | xdpe12284.rst | 27 This driver implements support for Infineon Multi-phase XDPE112 and XDPE122
29 These families include XDPE11280, XDPE12284 and XDPE12254 devices.
32 - Intel VR13 and VR13HC rev 1.3, IMVP8 rev 1.2 and IMPVP9 rev 1.3 DC-DC
37 Devices support linear format for reading input voltage, input and output current,
38 input and output power and temperature.
48 The driver provides for current: input, maximum and critical thresholds
49 and maximum and critical alarms. Critical thresholds and critical alarm are
52 indexes 1, 2 are for "iin" and 3, 4 for "iout":
66 The driver provides for voltage: input, critical and low critical thresholds
67 and critical and low critical alarms.
[all …]
|
| H A D | aquacomputer_d5next.rst | 30 The Aquaero devices expose eight physical, eight virtual and four calculated
32 speed (in RPM), power, voltage and current. Temperature offsets and fan speeds
35 For the D5 Next pump, available sensors are pump and fan speed, power, voltage
36 and current, as well as coolant temperature and eight virtual temp sensors. Also
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
48 The Octo exposes four physical and sixteen virtual temperature sensors, a flow sensor
50 and current. Flow sensor pulses are also available.
52 The Quadro exposes four physical and sixteen virtual temperature sensors, a flow
53 sensor and four PWM controllable fans, along with their speed (in RPM), power,
[all …]
|
| H A 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 …]
|
| /linux/Documentation/admin-guide/cifs/ |
| H A 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 …]
|
| H A D | todo.rst | 13 is a partial list of the known problems and missing features:
15 a) SMB3 (and SMB3.1.1) missing optional features:
20 T10 copy offload ie "ODX" (copy chunk, and "Duplicate Extents" ioctl
23 b) Better optimized compounding and error handling for sparse file support,
25 and insert range more atomic
27 c) Support for SMB3.1.1 over QUIC (and perhaps other socket based protocols
34 open/query/close and open/setinfo/close) to reduce the number of
35 roundtrips to the server and improve performance. Various cases
39 handle caching leases) and better using reference counters on file
42 f) Finish inotify support so kde and gnome file list windows
[all …]
|
| /linux/drivers/message/fusion/lsi/ |
| H A 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/lib/crypto/powerpc/ |
| H A D | curve25519-ppc64le_asm.S | 3 # This code is taken from CRYPTOGAMs[1] and is included here using the option
5 # is free software; you can redistribute it and/or modify it under the terms of
14 # Redistribution and use in source and binary forms, with or without
19 # this list of conditions and the following disclaimer.
22 # copyright notice, this list of conditions and the following
23 # disclaimer in the documentation and/or other materials
27 # copyright holder and contributors may be used to endorse or
50 # project. The module is, however, dual licensed under OpenSSL and
57 # Written and Modified by Danny Tsen <dtsen@us.ibm.com>
59 # and x25519_cswap
[all …]
|
| /linux/Documentation/timers/ |
| H A 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/Documentation/networking/caif/ |
| H A 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/tools/memory-model/Documentation/ |
| H A 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/Documentation/fb/ |
| H A 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 …]
|
| H A 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/Documentation/admin-guide/ |
| H A 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/Documentation/driver-api/surface_aggregator/ |
| H A D | overview.rst | 10 its responsibilities and feature-set have since been expanded significantly
14 Features and Integration
19 between host and EC (as detailed below). On 5th (Surface Pro 2017, Surface
20 Book 2, Surface Laptop 1) and later generation devices, SAM is responsible
21 for providing battery information (both current status and static values,
23 sensors (e.g. skin temperature) and cooling/performance-mode setting to the
27 and 2 it is required for keyboard HID input. This HID subsystem has been
28 restructured for 7th generation devices and on those, specifically Surface
29 Laptop 3 and Surface Book 3, is responsible for all major HID input (i.e.
30 keyboard and touchpad).
[all …]
|
| /linux/drivers/infiniband/ulp/rtrs/ |
| H A 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/Documentation/arch/x86/ |
| H A 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 …]
|
| /linux/Documentation/w1/masters/ |
| H A 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/drivers/iio/humidity/ |
| H A D | Kconfig | 8 tristate "Aosong AM2315 relative humidity and temperature sensor"
14 relative humidity and ambient temperature sensor.
20 tristate "DHT11 (and compatible sensors) driver"
24 generating GPIO line. Currently tested are DHT11 and DHT22.
29 tristate "ENS210 temperature and humidity sensor"
34 humidity and temperature sensors.
40 tristate "TI HDC100x relative humidity and temperature sensor"
46 HDC1000, HDC1008, HDC1010, HDC1050, and HDC1080 relative
47 humidity and temperature sensors.
53 tristate "TI HDC2010 relative humidity and temperature sensor"
[all …]
|
| /linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_overview.rst | 8 object files and prepares and loads them into the Linux kernel. libbpf takes the
9 heavy lifting of loading, verifying, and attaching BPF programs to various
11 correctness and performance.
15 * Provides high-level and low-level APIs for user space programs to interact
18 over the interactions between user space and BPF programs.
21 global variables and work with BPF programs.
23 and tracing helpers, allowing developers to simplify BPF code writing.
25 BPF programs that can be compiled once and run across different kernel
29 understanding of the capabilities and advantages of libbpf and how it can help
32 BPF App Lifecycle and libbpf APIs
[all …]
|
| /linux/drivers/platform/surface/aggregator/ |
| H A D | Kconfig | 5 tristate "Microsoft Surface System Aggregator Module Subsystem and Drivers"
11 embedded controller (EC) found on 5th- and later-generation Microsoft
13 and newer, with exception of Surface Go series devices).
17 - EC access from ACPI via Surface ACPI Notify (5th- and 6th-generation)
21 - clipboard detachment system control (Surface Book 2 and 3)
26 is the device responsible for the communication with the EC, and a
28 drivers, i.e. allowing them to make requests to the EC and receive
30 client drivers and therefore no functionality beyond the in-kernel
36 only 5th and later generations are currently supported. Specifically,
41 Choose m if you want to build the SAM subsystem core and SSH driver as
[all …]
|