| /linux-6.15/Documentation/input/ |
| H A D | gamepad.rst | 12 document defines how gamepads are supposed to report their data.
44 4 buttons in diamonds-shape (on the right side). The buttons are
103 of the labels on the buttons, the codes are sent according to the
111 If only 2 action-buttons are present, they are reported as BTN_SOUTH and
117 If only 3 action-buttons are present, they are reported as (from left
119 If the buttons are aligned perfectly vertically, they are reported as
136 both are reported.
138 - Digital buttons are reported as:
142 - Analog buttons are reported as:
174 Menu buttons are always digital and are mapped according to their location
[all …]
|
| /linux-6.15/Documentation/ |
| H A D | atomic_bitops.txt | 5 While our bitmap_{}() functions are non-atomic, we have a number of operations
6 operating on single bits in a bitmap that are atomic.
12 The single bit operations are:
55 - non-RMW operations are unordered;
57 - RMW operations that have no return value are unordered;
59 - RMW operations that have a return value are fully ordered.
61 - RMW operations that are conditional are fully ordered.
68 the same barriers as for atomic_t are used, see atomic_t.txt.
|
| H A D | atomic_t.txt | 5 RMW operations between CPUs (atomic operations on MMIO are not supported and
82 The non-RMW ops are (typically) regular LOADs and STOREs and are canonically
86 and are doing it wrong.
91 C Atomic-RMW-ops-are-atomic-WRT-atomic_set
142 these are limited to the arithmetic operations because those are
165 - non-RMW operations are unordered;
167 - RMW operations that have no return value are unordered;
169 - RMW operations that have a return value are fully ordered;
171 - RMW operations that are conditional are unordered on FAILURE,
181 not defeated. Conditional operations are still unordered on FAILURE.
[all …]
|
| /linux-6.15/Documentation/core-api/ |
| H A D | tracepoint.rst | 11 Tracepoints are static probe points that are located in strategic points
13 a callback mechanism. The 'probes' are strictly typed functions that are
17 debug, and understand kernel behavior. There are a number of tools that
21 Tracepoints are defined in a number of header files via various macros.
24 tracepoints are available but also to understand where future
28 ``trace_tracepointname(function parameters)``. These are the tracepoints
29 callbacks that are found throughout the code. Registering and
|
| /linux-6.15/Documentation/fb/ |
| H A D | api.rst | 13 buffer core are not described.
24 Device and driver capabilities are reported in the fixed screen information
39 When supported, formats are configured using a FOURCC instead of manually
56 types and visuals are supported.
73 Planes are located contiguously in memory.
98 are packed together in a byte.
109 are packed together in a byte.
117 are device-dependent, and provide linear or non-linear ramps.
141 Pixels are encoded and interpreted as described by the format FOURCC
268 Pixel values are bits_per_pixel wide and are split in non-overlapping red,
[all …]
|
| /linux-6.15/Documentation/usb/ |
| H A D | functionfs-desc.rst | 5 Some of the descriptors that can be written to the FFS gadget are
6 described below. Device and configuration descriptors are handled
7 by the composite gadget and are not written by the user to the
10 Descriptors are written to the "ep0" file in the FFS gadget
21 descriptors are accepted.
26 Class-specific descriptors are accepted only for the class/subclass of the
27 most recent interface descriptor. The following are some of the
28 class-specific descriptors that are supported.
|
| /linux-6.15/Documentation/devicetree/bindings/ |
| H A D | writing-schema.rst | 6 Devicetree bindings are written using json-schema vocabulary. Schema files are
18 top-level json-schema properties used are:
50 parsed correctly, but are important when the text blocks are rendered to
51 another form. The options are as follows.
54 line breaks and leading whitespace are stripped. Paragraphs are delimited by
58 restrictions are on what the first character can be.
63 breaks on indented lines are also maintained.
109 being objects, are supposed to have one as well.
130 Unless noted otherwise, all properties are required.
137 vocabulary for that property. The properties schemas are what are used for
[all …]
|
| /linux-6.15/Documentation/networking/ |
| H A D | ipv6.rst | 8 Options for the ipv6 module are supplied as parameters at load time.
11 or modprobe command, but are usually specified in either
15 The available ipv6 module parameters are listed below. If a parameter
18 The parameters are as follows:
25 IPv6 addresses or operations are desired.
27 The possible values and their effects are:
49 The possible values and their effects are:
65 This might be used when no IPv6 addresses are desired.
67 The possible values and their effects are:
|
| /linux-6.15/Documentation/rust/ |
| H A D | testing.rst | 9 There are three sorts of tests:
18 These are the tests that come from the examples in the Rust documentation. They
43 KUnit tests are documentation tests
46 These documentation tests are typically examples of usage of any item (e.g.
49 They are very convenient because they are just written alongside the
63 In userspace, the tests are collected and run via ``rustdoc``. Using the tool
94 operator are also supported as usual, e.g.:
126 Since these tests are examples, i.e. they are part of the documentation, they
136 Additionally, there are the ``#[test]`` tests. These can be run using the
149 The kernel config options required for the tests are listed in the
[all …]
|
| /linux-6.15/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 20 the human eye has color receptors that are sensitive to three different
22 color. Be glad you are not a mantis shrimp as those are sensitive to 12
27 color receptors are stimulated. This is based on the Spectral Power
43 After some further mathematical transforms these stimuli are known as
59 colors are specified with lower case 'x' and 'y', then the CIE xyY
64 will find reading resources that go into much more detail if you are
76 This has resulted in a variety of colorspaces that are used for
91 Both the CIE XYZ and the RGB colorspace that are derived from the
99 values are denoted RGB, non-linear are denoted as R'G'B'. In general
100 colors used in graphics are all R'G'B', except in openGL which uses
[all …]
|
| H A D | colorspaces-details.rst | 18 are:
66 The luminance (Y') and color difference (Cb and Cr) are obtained with
95 and the white reference are:
168 that are outside the range [0…1]. The resulting Y', Cb and Cr values are
181 that are outside the range [0…1]. The resulting Y', Cb and Cr values are
242 These chromaticities are identical to the Rec. 709 colorspace.
510 and the white reference are:
535 These chromaticities are identical to the SMPTE 170M colorspace.
578 reference are:
655 are:
[all …]
|
| H A D | metafmt-intel-ipu3.rst | 16 an input Bayer frame. Those statistics are obtained from the "ipu3-imgu [01] 3a
18 interface. They are formatted as described by the :c:type:`ipu3_uapi_stats_3a`
21 The statistics collected are AWB (Auto-white balance) RGBS (Red, Green, Blue and
46 The pipeline parameters are passed to the "ipu3-imgu [01] parameters" metadata
47 output video nodes, using the :c:type:`v4l2_meta_format` interface. They are
50 Both 3A statistics and pipeline parameters described here are closely tied to
51 the underlying camera sub-system (CSS) APIs. They are usually consumed and
59 /* Flags which of the settings below are to be applied */
|
| /linux-6.15/Documentation/misc-devices/ |
| H A D | tps6594-pfsm.rst | 43 All device resources are powered down. The processor is off, and
44 no voltage domains are energized.
47 The digital and analog functions of the PMIC, which are not
48 required to be always-on, are turned off (low-power).
55 The PMICs are fully functional and supply power to all PDN loads.
56 All voltage domains are energized in both MCU and Main processor
61 Only the power resources assigned to the MCU Safety Island are on.
66 remain energized, while all other domains are off to minimize
|
| /linux-6.15/Documentation/i2c/ |
| H A D | i2c-topology.rst | 5 There are a couple of reasons for building more complex I2C topologies
8 Some example use cases are:
22 These components are represented as I2C adapter trees by Linux, where
48 adapter are locked. Mux-locked muxes are mostly interesting if the
75 These transfers are normal I2C transfers that locks the parent
100 mux-locked muxes that are not siblings, when there are address
233 are locked). But accesses to D3 and D4 are possibly interleaved at
288 When D1 is accessed, accesses to D2 are locked out for the full
290 are locked). Accesses to D3 and D4 are possibly interleaved at
366 When D1 or D2 are accessed, accesses to D3 and D4 are locked out while
[all …]
|
| /linux-6.15/Documentation/driver-api/soundwire/ |
| H A D | stream.rst | 20 interface. Below are some ways a stream can be represented in SoundWire.
57 Slaves are using single port. ::
79 Master. Both of the L and R channels are received by two different
80 Slaves. Master and both Slaves are using single port handling
285 After all above operations are successful, stream state is set to
315 After all above operations are successful, stream state is set to
365 After all above operations are successful, stream state is set to
395 associated with current stream are enabled.
397 After all above operations are successful, stream state is set to
423 with current stream are disabled.
[all …]
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-sx9324 | 15 (PH0, PH1, PH2, PH3), where the inputs are configured
19 while CS1 and CS2 are used as shields.
21 [PH1], CS1 is measured, CS0 and CS2 are shield:
23 [PH2], CS2 is measured, CS0 and CS1 are shield:
25 [PH3], CS1 and CS2 are measured (combo mode):
28 Note, these are the chip default. Hardware layout will most
|
| /linux-6.15/Documentation/devicetree/bindings/clock/ |
| H A D | stericsson,u8500-clks.yaml | 13 description: While named "U8500 clocks" these clocks are inside the
16 itself, not off-chip clocks. There are four different on-chip
52 which PRCC block the consumer wants to use, possible values are 1, 2, 3,
54 wants, possible values are 0 thru 31.
66 block the consumer wants to use, possible values are 1, 2, 3, 5, 6. The
68 values are 0 thru 31.
82 it wants to control, possible values are 0 thru 31.
121 The first cell indicates which output clock we are using,
122 possible values are 0 (CLKOUT1) and 1 (CLKOUT2).
124 possible values are 0 thru 7, see the defines for the different
[all …]
|
| /linux-6.15/Documentation/arch/arm/nwfpe/ |
| H A D | netwinder-fpe.rst | 17 Note: items enclosed in {} are optional.
28 These instructions are fully implemented.
58 FLT/FIX are fully implemented.
60 RFS/WFS are fully implemented.
62 RFC/WFC are fully implemented. RFC/WFC are supervisor only instructions, and
73 These are fully implemented.
87 These are fully implemented.
110 These are fully implemented.
116 These are fully implemented.
141 These are not implemented. They are not currently issued by the compiler,
[all …]
|
| /linux-6.15/Documentation/admin-guide/device-mapper/ |
| H A D | statistics.rst | 6 regions of a DM device. If no regions are defined no statistics are
8 devices are currently supported.
24 reported times are in nanoseconds.
65 The following optional arguments are supported:
77 times are in milliseconds, otherwise they are in
122 are returned.
123 If it is not specified, all regions are returned.
140 If omitted, all lines are returned.
144 If omitted, all lines are returned.
184 If omitted, all lines are printed and then cleared.
[all …]
|
| /linux-6.15/Documentation/livepatch/ |
| H A D | livepatch.rst | 15 There are many situations where users are reluctant to reboot a system. It may
26 There are multiple mechanisms in the Linux kernel that are directly related
39 are in any way modified.
71 or no data are stored in the modified structures at the moment.
135 are stuck in the initial patch state.
188 structures are in a well-defined state.
214 Livepatches are distributed using kernel modules, see
272 only when they are available.
280 symbols are found. The only exception are symbols from objects
303 in the module_init() callback. There are two main reasons:
[all …]
|
| /linux-6.15/Documentation/devicetree/bindings/pinctrl/ |
| H A D | pinctrl-rk805.txt | 11 Following properties are required if default setting of pins are required
17 The pin configurations are defined as child of the pinctrl states node. Each
27 - pins: List of pins. Valid values of pins properties are: gpio0, gpio1.
34 Following are optional properties defined as pinmux DT binding document
41 Valid values for function properties are: gpio.
43 There are also not customised properties for any GPIO.
|
| /linux-6.15/Documentation/hid/ |
| H A D | hid-transport.rst | 15 drivers on top of it. The transport drivers are responsible for raw data
18 and quirks are handled by all layers depending on the quirk.
68 this struct are used by HID core to communicate with the device.
103 send their input events on this channel. Outgoing events are normally
111 Outgoing reports are usually sent on the ctrl channel via synchronous
137 this is rarely done as OUTPUT reports are normally quite scarce. But devices are
143 allowed on the intr channel and are the only means of data there.
151 Note that data reports which are sent as answer to a GET_REPORT request are
175 Other ctrl-channel requests are supported by USB-HID but are not available
232 The available HID callbacks are:
[all …]
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | squashfs.rst | 10 directories. Inodes in the system are very small and all blocks are packed to
11 minimise data overhead. Block sizes greater than 4K are supported up to a
51 directory data are highly compacted, and packed on byte boundaries. Each
158 Compressed data blocks are written to the filesystem as files are read from
161 xattr tables are written.
168 these are stored here.
178 Inodes are packed into the metadata blocks, and are not aligned to block
184 To maximise compression there are different inodes for each file type
201 Directories are organised in a slightly complex way, and are not simply
205 Directories are therefore organised in a two level list, a directory
[all …]
|
| H A D | gfs2-glocks.rst | 17 are completed.
20 just the holders) associated with the glock. If there are any
23 are queued.
82 some progress before the pages are unmapped.
143 The per-glock counters are initialised to zero when the
144 glock is created. The per-glock statistics are lost when
147 The statistics are divided into three pairs of mean and
148 variance, plus two counters. The mean/variance pairs are
155 not scaled, but are in units of integer nanoseconds.
203 as possible. There are always inaccuracies in any
[all …]
|
| /linux-6.15/Documentation/admin-guide/pm/ |
| H A D | suspend-flows.rst | 26 different sleep states of the system are quite similar, but there are some
36 states are mostly identical, so they both together will be referred to as
58 Tasks are frozen primarily in order to avoid unchecked hardware accesses
69 specific reasons are frozen subsequently, but they are not intercepted.
79 Devices are suspended in four phases called *prepare*, *suspend*,
90 Interrupts are still handled after that, but they are only acknowledged to
123 The following steps are taken in order to transition the system from the
153 transition are "thawed", which means that they are woken up from the
155 are allowed to exit the kernel.
215 This means that all tasks are migrated away from those CPUs and all IRQs are
[all …]
|