| /Documentation/userspace-api/media/v4l/ |
| D | colorspaces.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
92 specific chromaticity primaries are linear colorspaces. But neither the
93 eye, nor display technology is linear. Doubling the values of all
94 components in the linear colorspace will not be perceived as twice the
96 function that takes a linear color component value and transforms it to
97 the non-linear component value, which is a closer match to the
98 non-linear performance of both the eye and displays. Linear component
99 values are denoted RGB, non-linear are denoted as R'G'B'. In general
101 linear RGB. Special care should be taken when dealing with openGL to
102 provide linear RGB colors or to use the built-in openGL support to apply
[all …]
|
| D | ext-ctrls-image-source.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _image-source-controls:
9 The Image Source control class is intended for low-level control of
15 .. _image-source-control-id:
28 same sub-device.
59 non-sensitive.
64 .. flat-table:: struct v4l2_area
65 :header-rows: 0
66 :stub-columns: 0
69 * - __u32
[all …]
|
| D | pixfmt-yuv-planar.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. planar-yuv:
12 - Semi-planar formats use two planes. The first plane is the luma plane and
16 - Fully planar formats use three planes to store the Y, Cb and Cr components
19 Within a plane, components are stored in pixel order, which may be linear or
26 and applications that support the multi-planar API, described in
27 :ref:`planar-apis`. Unless explicitly documented as supporting non-contiguous
31 Semi-Planar YUV Formats
46 For non-contiguous formats, no constraints are enforced by the format on the
57 .. flat-table:: Overview of Semi-Planar YUV Formats
[all …]
|
| D | colorspaces-defs.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
12 :c:type:`v4l2_xfer_func`) to specify non-standard
15 non-standard Y'CbCr encodings and the fourth is the quantization
17 specify non-standard quantization methods. Most of the time only the
22 .. _hsv-colorspace:
24 On :ref:`HSV formats <hsv-formats>` the *Hue* is defined as the angle on
26 degrees, i.e. 0-360. When we map this angle value into 8 bits, there are
27 two basic ways to do it: Divide the angular value by 2 (0-179), or use the
28 whole range, 0-255, dividing the angular value by 1.41. The enum
38 .. flat-table:: V4L2 Colorspaces
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-backlight | 9 hence linear changes in brightness are perceived as being
10 non-linear. To achieve a linear perception of brightness changes
12 backlights with a linear brightness curve.
19 linear
21 controls should apply a logarithmic mapping for a linear
24 non-linear
25 The brightness changes non-linearly with each step. Brightness
26 controls should use a linear mapping for a linear perception.
38 The value range is device-driver specific:
47 It returns a 13-bits integer.
[all …]
|
| /Documentation/bpf/ |
| D | redirect.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
10 --------------
14 - ``BPF_MAP_TYPE_DEVMAP``
15 - ``BPF_MAP_TYPE_DEVMAP_HASH``
16 - ``BPF_MAP_TYPE_CPUMAP``
17 - ``BPF_MAP_TYPE_XSKMAP``
22 -------
24 .. kernel-doc:: net/core/filter.c
29 those that do, not all of them support non-linear frames. Non-linear xdp
33 ----------------------
[all …]
|
| /Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 13 -------------------
18 - non-Intel processors
20 - Some Atoms (Airmont, Bonnell, Goldmont, GoldmontPlus, Saltwell, Silvermont)
22 - Intel processors that have the PSCHANGE_MC_NO bit set in the
27 ------------
32 CVE-2018-12207 Machine Check Error Avoidance on Page Size Change
37 -------
50 Under this errata, instructions are fetched from a linear address translated
52 paging structure so that the same linear address using large page size (2 MB, 4
55 the linear address, a code fetch that happens on the same linear address may
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ntc-thermistor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
2 ---
3 $id: http://devicetree.org/schemas/hwmon/ntc-thermistor.yaml#
4 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 - Linus Walleij <linus.walleij@linaro.org>
13 vary in resistance in an often non-linear way in relation to temperature.
16 temperature is non-linear, software drivers most often need to use a look
20 pull-up resistor or/and a pull-down resistor and a fixed voltage like this:
22 + e.g. 5V = pull-up voltage (puv)
24 +-+
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -----------------
9 that reference the same inode number--these are known as hard links, and
15 Linear (Classic) Directories
18 By default, each directory lists its entries in an “almost-linear”
19 array. I write “almost” because it's not a linear array in the memory
22 data blocks and that each block contains a linear array of directory
23 entries. The end of each per-block array is signified by reaching the
36 .. list-table::
38 :header-rows: 1
[all …]
|
| /Documentation/hwmon/ |
| D | bt1-pvt.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
3 Kernel driver bt1-pvt
8 * Baikal-T1 PVT sensor (in SoC)
10 Prefix: 'bt1-pvt'
12 Addresses scanned: -
21 -----------
24 embedded into Baikal-T1 process, voltage and temperature sensors. PVT IP-core
29 compile-time configurable due to the hardware interface implementation
40 in alarm-less configuration the data conversion is performed by the driver
41 on demand when read operation is requested via corresponding _input-file.
[all …]
|
| D | abituguru-datasheet.rst | 14 Olle Sandberg <ollebull@gmail.com>, 2005-05-25
27 Hans de Goede <j.w.r.degoede@hhs.nl>, 28-01-2006
33 As far as known the uGuru is always placed at and using the (ISA) I/O-ports
34 0xE0 and 0xE4, so we don't have to scan any port-range, just check what the two
35 ports are holding for detection. We will refer to 0xE0 as CMD (command-port)
39 present. We have to check for two different values at data-port, because
41 later on attached again data-port will hold 0x08, more about this later.
57 ----------
82 -----------
101 ----------------------------------------------
[all …]
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 9 that each one gets assigned non-overlapping allocations of Linux
24 For this reason we need a mechanism to separate controller-local
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
61 - irq_resolve_mapping() returns a pointer to the irq_desc structure
64 - irq_find_mapping() returns a Linux IRQ number for a given domain and
66 - irq_linear_revmap() is now identical to irq_find_mapping(), and is
68 - generic_handle_domain_irq() handles an interrupt described by a
72 compatible with a RCU read-side critical section.
80 callbacks) then it can be directly obtained from irq_data->hwirq.
90 Linear section in Types of irq_domain mappings
[all …]
|
| /Documentation/iio/ |
| D | bno055.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 angles and quaternion), linear velocity and gravity vector are also
44 bno055-caldata-0e7c26a33541515120204a35342b04ff.dat
45 bno055-caldata.dat
47 In non-fusion mode the IIO 'offset' attributes provide access to the
|
| /Documentation/userspace-api/ |
| D | dma-buf-alloc-exchange.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright 2021-2023 Collabora Ltd.
9 support for sharing pixel-buffer allocations between processes, devices, and
12 approach this sharing for two-dimensional image data.
25 Conceptually a two-dimensional array of pixels. The pixels may be stored
30 A span along a single y-axis value, e.g. from co-ordinates (0,100) to
37 A span along a single x-axis value, e.g. from co-ordinates (100,0) to
46 A two-dimensional array of some or all of an image's color and alpha
80 A value that denotes the relationship between pixel-location co-ordinates
81 and byte-offset values. Typically used as the byte offset between two
[all …]
|
| /Documentation/leds/ |
| D | leds-class-flash.rst | 5 Some LED devices provide two modes - torch and flash. In the LED subsystem
6 those modes are supported by LED class (see Documentation/leds/leds-class.rst)
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
18 - flash_brightness
19 - max_flash_brightness
20 - flash_timeout
21 - max_flash_timeout
22 - flash_strobe
23 - flash_fault
36 - dev:
[all …]
|
| /Documentation/process/ |
| D | deprecated.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 ------------
33 ------------------
35 error condition as gracefully as possible. While the BUG()-family
42 <https://lore.kernel.org/lkml/CA+55aFy6jNLsywVYdGp83AMrXBo_P-pkjkphPGrO=82SPKCpLQ@mail.gmail.com/>`_
44 <https://lore.kernel.org/lkml/CAHk-=whDHsbK3HTOpTF=ue_o04onRwTEaK_ZoJp_fjbqq4+=Jw@mail.gmail.com/>`…
46 Note that the WARN()-family should only be used for "expected to
48 but undesirable" situations, please use the pr_warn()-family of
54 open-coded arithmetic in allocator arguments
55 --------------------------------------------
[all …]
|
| /Documentation/fb/ |
| D | vesafb.rst | 14 Version 2.0 are required, because we need a linear frame buffer.
20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
22 * Most important: boot logo :-)
33 Documentation/admin-guide/svga.rst for details.
75 linear framebuffers or because it does not support this mode at all.
81 "vga=mode-number" you have to transform the numbers to decimal.
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
90 It depends on X-Server and graphics board.
92 The X-Server must restore the video mode correctly, else you end up
[all …]
|
| D | api.rst | 9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
36 - FB_CAP_FOURCC
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
58 - FB_TYPE_PACKED_PIXELS
67 - FB_TYPE_PLANES
75 - FB_TYPE_INTERLEAVED_PLANES
86 - FB_TYPE_FOURCC
[all …]
|
| /Documentation/networking/ |
| D | devmem.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 -----------
22 - Distributed training, where ML accelerators, such as GPUs on different hosts,
25 - Distributed raw block storage applications transfer large amounts of data with
28 Typically the Device-to-Device data transfers in the network are implemented as
29 the following low-level operations: Device-to-Host copy, Host-to-Host network
30 transfer, and Host-to-Device copy.
46 - Alleviate host memory bandwidth pressure, compared to existing
47 network-transfer + device-copy semantics.
49 - Alleviate PCIe bandwidth pressure, by limiting data transfer to the lowest
[all …]
|
| /Documentation/filesystems/ |
| D | cramfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Cramfs - cram a filesystem onto a small ROM
10 allows random page access. The meta-data is not compressed, but is
15 compact also makes it _very_ hard to update on-the-fly), so you have to
20 -----------
36 no need to use -noleaf in ``find``, btw.)
39 (1970 GMT). Recently-accessed files may have updated timestamps, but
52 --------------------------
55 a physical linear memory range (usually non volatile memory like Flash)
62 eXecute-In-Place (XIP) from ROM of read-only segments. Data segments mapped
[all …]
|
| /Documentation/core-api/ |
| D | swiotlb.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 These APIs use the device DMA attributes and kernel-wide settings to determine
30 ---------------
33 only provide 32-bit DMA addresses. By allocating bounce buffer memory below
40 directed to guest memory that is unencrypted. CoCo VMs set a kernel-wide option
54 IOMMU access control is per-granule, the untrusted device can gain access to
60 ------------------
85 ------------------------------
89 pre-allocated at boot time (but see Dynamic swiotlb below). Because swiotlb
93 The need to pre-allocate the default swiotlb pool creates a boot-time tradeoff.
[all …]
|
| /Documentation/virt/kvm/x86/ |
| D | mmu.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 - correctness:
18 - security:
21 - performance:
23 - scaling:
25 - hardware:
27 - integration:
31 - dirty tracking:
33 and framebuffer-based displays
34 - footprint:
[all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 10 .. kernel-figure:: dc_pipeline_overview.svg
19 * **Display Pipe and Plane (DPP)**: This block provides pre-blend pixel
24 multiple planes, using global or per-pixel alpha.
38 * **Multi-Media HUB (MMHUBBUB)**: Memory controller interface for DMCUB and DWB
43 the Display Micro-Controller Unit - version B (DMCUB), which is handled via
84 ----------------------
100 a one-to-one mapping of the link encoder to PHY, but we can configure the DCN
106 ---------
114 representation and convert them to a DCN specific floating-point format (i.e.,
115 different from the IEEE floating-point format). In the process, CNVC also
[all …]
|
| /Documentation/mm/ |
| D | hwpoison.rst | 35 Some of the operations here are somewhat inefficient and have non
36 linear algorithmic complexity, because the data structures have not
41 The code consists of a the high level handler in mm/memory-failure.c,
46 of applications. KVM support requires a recent qemu-kvm release.
109 * madvise(MADV_HWPOISON, ....) (as root) - Poison a page in the
112 * hwpoison-inject module through debugfs ``/sys/kernel/debug/hwpoison/``
114 corrupt-pfn
118 unpoison-pfn
119 Software-unpoison page at PFN echoed into this file. This way
127 corrupt-filter-dev-major, corrupt-filter-dev-minor
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | style.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 example, non-deterministically producing false positives or negatives, or
29 ----------
59 ``linear-ranges``
62 ``qos-kunit-test``
63 This name should use underscores, and not have "kunit-test" as a
77 ------
122 ----------
149 the *fully-qualified* name of a test should be the suite name followed by the
162 tested, or be under [Kernel Hacking]->[Kernel Testing and Coverage]
[all …]
|