| /Documentation/driver-api/media/drivers/ |
| D | ipu6.rst | 13 Intel Chipsets such as Tiger Lake, Jasper Lake, Alder Lake, Raptor Lake and
14 Meteor Lake. IPU6 consists of two major systems: Input System (ISYS) and
28 store and load frame pixel streams and any other metadata.
31 interrupt handling, firmware authentication and global timer sync.
33 ISYS and PSYS Power flow
36 IPU6 driver initialize the ISYS and PSYS power up or down request by setting the
37 Buttress frequency control register for ISYS and PSYS
38 (``IPU6_BUTTRESS_REG_IS_FREQ_CTL`` and ``IPU6_BUTTRESS_REG_PS_FREQ_CTL``) in
56 clears the irq status and then calls specific ISYS or PSYS irq handler.
60 Security and firmware authentication
[all …]
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 6 Good development is like gardening, and codebases are our gardens. Tend to them
8 A little weeding here and there goes a long way; don't wait until things have
12 good. But appreciate beauty when you see it - and let people know.
16 A little organizing here and there goes a long way.
20 Good code is readable code, where the structure is simple and leaves nowhere
25 happen (and will have unpredictable or undefined behaviour if it does), or
26 you're not sure if it can happen and not sure how to handle it yet - make it a
30 assertions need to be handled and turned into checks with error paths, and
40 Good assertions drastically and dramatically reduce the amount of testing
46 Good invariants and assertions will hold everywhere in your codebase. This
[all …]
|
| /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 | 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 …]
|
| /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 …]
|
| D | highres.rst | 2 High resolution timers and dynamic ticks design notes
6 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
15 design of the Linux time(r) system before hrtimers and other building blocks
18 Note: the paper and the slides are talking about "clock event source", while we
24 - timeofday and clock source management
44 timeofday and clock source management
51 sources, which are registered in the framework and selected on a quality based
52 decision. The low level code provides hardware setup and readout routines and
63 The paper "We Are Not Getting Any Younger: A New Approach to Time and
75 period defined at compile time. The setup and selection of the event device
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | v4l2.rst | 34 Revision and Copyright
45 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter.
49 - Original author of the V4L2 API and documentation.
58 - Original author of the V4L2 API and documentation.
71 - Designed and documented the multi-planar API.
79 - Introduce HSV formats and other minor changes.
83 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls.
91 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl…
96 part can be used and distributed without restrictions.
110 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 …]
|
| /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 …]
|
| /Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 8 open-source community is unique and the Linux kernel is no exception.
11 to be static over time, and will adjust it as needed.
14 to "traditional" ways of developing software. Your contributions and
16 critique and criticism. The review will almost always require
21 system kernel ever, and we do not want to do anything to cause the
22 quality of submission and eventual result to ever decrease.
29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
35 The Code of Conduct mentions rights and responsibilities for
36 maintainers, and this needs some further clarifications.
38 First and foremost, it is a reasonable expectation to have maintainers
[all …]
|
| /Documentation/hwmon/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /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 …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | delay.rst | 5 Device-Mapper's "delay" target delays reads and/or writes
6 and/or flushs and optionally maps them to different devices.
15 3: apply offset and delay to read, write and flush operations on device
17 6: apply offset and delay to device, also apply write_offset and write_delay
18 to write and flush operations on optionally different write_device with
21 9: same as 6 arguments plus define flush_offset and flush_delay explicitely
35 # Create mapped device named "delayed" delaying read, write and flush operations for 500ms.
42 # Create mapped device delaying write and flush operations for 400ms and
43 # splitting reads to device $1 but writes and flushs to different device $2
44 # to different offsets of 2048 and 4096 sectors respectively.
[all …]
|
| /Documentation/arch/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 …]
|
| /Documentation/driver-api/surface_aggregator/ |
| 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 …]
|
| /Documentation/scsi/ |
| D | FlashPoint.rst | 21 drivers and information will be available on October 15th at
26 development and provided technical support for our host adapters for several
27 years, and are pleased to now make our FlashPoint products available to this
34 SPARC, SGI MIPS, Motorola 68k, Digital Alpha AXP and Motorola PowerPC
36 System, Emacs, and TCP/IP networking. Further information is available at
37 http://www.linux.org and http://www.ssc.com/.
43 and file server environments, are available in narrow, wide, dual channel,
44 and dual channel wide versions. These adapters feature SeqEngine
45 automation technology, which minimizes SCSI command overhead and reduces
52 producer of RAID technology and network management products. The company
[all …]
|
| /Documentation/userspace-api/ |
| D | dma-buf-alloc-exchange.rst | 9 support for sharing pixel-buffer allocations between processes, devices, and
11 classes; this document details how applications and kernel subsystems should
14 It is written with reference to the DRM subsystem for GPU and display devices,
15 V4L2 for media devices, and also to Vulkan, EGL and Wayland, for userspace
16 support, however any other subsystems should also follow this design and advice.
26 in one or more memory buffers. Has width and height in pixels, pixel
27 format and modifier (implicit or explicit).
41 A piece of memory for storing (parts of) pixel data. Has stride and size
42 in bytes and at least one handle in some API. May contain one or more
46 A two-dimensional array of some or all of an image's color and alpha
[all …]
|
| /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 …]
|
| /Documentation/sound/soc/ |
| D | overview.rst | 7 pxa2xx, au1x00, iMX, etc) and portable audio codecs. Prior to the ASoC
12 CPU. This is not ideal and leads to code duplication - for example,
17 event). These are quite common events on portable devices and often require
30 The ASoC layer is designed to address these issues and provide the following
34 and machines.
36 * Easy I2S/PCM audio interface setup between codec and SoC. Each SoC
37 interface and codec registers its audio interface capabilities with the
38 core and are subsequently matched and configured when the application
43 internal power blocks depending on the internal codec audio routing and any
46 * Pop and click reduction. Pops and clicks can be reduced by powering the
[all …]
|
| /Documentation/bpf/libbpf/ |
| 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 …]
|
| /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
20 Description: The <bdf> is related the function for PF and VF.
25 get related QoS in the host and VM, Such as "cat alg_qos".
31 Available for PF and VF in host. VF in guest currently only
47 Only available for PF, and take no other effect on SEC.
54 Available for both PF and VF, and take no other effect on SEC.
60 Available for both PF and VF, and take no other effect on SEC.
66 Available for both PF and VF, and take no other effect on SEC.
72 Available for both PF and VF, and take no other effect on SEC.
[all …]
|
| /Documentation/virt/hyperv/ |
| D | overview.rst | 9 equivalent to KVM and QEMU, for example). Guest VMs run in child
11 encompass both the hypervisor and the VMM service without making a
15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests
16 are supported on both. The functionality and behavior of Hyper-V is
24 some guest actions trap to Hyper-V. Hyper-V emulates the action and
30 and returns control to the caller. Parameters are passed in
31 processor registers or in memory shared between the Linux guest and
38 the guest, and the Linux kernel can read or write these MSRs using
45 the Hyper-V host and the Linux guest. It uses memory that is shared
46 between Hyper-V and the guest, along with various signaling
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm-security.rst | 7 use of the TPM reasonably robust in the face of external snooping and
8 packet alteration attacks (called passive and active interposer attack
21 Snooping and Alteration Attacks against the bus
33 secrets and integrity as far as we are able in this environment and to
45 send arbitrary PCR extends and thus disrupt the measurement system,
51 and completely substitute their own values, producing a replay of
53 a trusted state and release secrets
56 the PCRs and then send down their own measurements which would
61 extend and read command meaning measurement values cannot be
70 Certain information passing in and out of the TPM, such as key sealing
[all …]
|