| /kernel/linux/linux-5.10/Documentation/sphinx/ |
| D | kfigure.py | 4 scalable figure and image handling
14 handling from the author's POV. Directives like ``kernel-figure`` implement
21 * ``.. kernel-figure``: for figure handling / a ``.. figure::`` replacement
75 # patches.Figure only landed in Sphinx 1.4
76 from sphinx.directives.patches import Figure # pylint: disable=C0413
78 Figure = images.Figure variable
142 # figure handling
143 app.add_directive("kernel-figure", KernelFigure)
372 # figure handling
383 class kernel_figure(nodes.figure):
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/drbd/ |
| D | figures.rst | 8 .. kernel-figure:: DRBD-8.3-data-packets.svg
12 .. kernel-figure:: DRBD-data-packets.svg
20 .. kernel-figure:: conn-states-8.dot
24 .. kernel-figure:: disk-states-8.dot
28 .. kernel-figure:: node-states-8.dot
|
| /kernel/linux/linux-5.10/Documentation/devicetree/ |
| D | of_unittest.rst | 76 Figure 1, describes a generic structure of machine's un-flattened device tree
105 Figure 1: Generic structure of un-flattened device tree
123 in Figure 2 is attached to the live tree described in Figure 1::
134 Figure 2: Example test data tree to be attached to live tree.
143 data node is attached to the live tree above (Figure 1), the final structure is
144 as shown in Figure 3::
179 Figure 3: Live device tree structure after attaching the testcase-data.
183 sibling compared to the earlier structure (Figure 2). After attaching first
|
| /kernel/linux/linux-5.10/arch/mips/sgi-ip27/ |
| D | TODO | 1 1. Need to figure out why PCI writes to the IOC3 hang, and if it is okay
3 2. Need to figure out RRB allocation in bridge_startup().
4 3. Need to figure out why address swaizzling is needed in inw/outw for
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-nv12mt.rst | 31 Layout of macroblocks in memory is presented in the following figure.
36 .. kernel-figure:: nv12mt.svg
53 .. kernel-figure:: nv12mt_example.svg
|
| D | dev-raw-vbi.rst | 220 .. kernel-figure:: vbi_hsync.svg
224 **Figure 4.1. Line synchronization**
228 .. kernel-figure:: vbi_525.svg
232 **Figure 4.2. ITU-R 525 line numbering (M/NTSC and M/PAL)**
236 .. kernel-figure:: vbi_625.svg
240 **Figure 4.3. ITU-R 625 line numbering**
|
| D | dev-subdev.rst | 107 .. kernel-figure:: pipeline.dot
452 .. kernel-figure:: subdev-image-processing-crop.svg
456 **Figure 4.5. Image processing in subdevs: simple crop example**
469 .. kernel-figure:: subdev-image-processing-scaling-multi-source.svg
473 **Figure 4.6. Image processing in subdevs: scaling with multiple sources**
485 .. kernel-figure:: subdev-image-processing-full.svg
489 …**Figure 4.7. Image processing in subdevs: scaling and composition with multiple sinks and sources…
|
| /kernel/linux/linux-5.10/Documentation/doc-guide/ |
| D | sphinx.rst | 362 If you want to add an image, you should use the ``kernel-figure`` and
363 ``kernel-image`` directives. E.g. to insert a figure with a scalable
366 .. kernel-figure:: svg_image.svg
373 .. kernel-figure:: svg_image.svg
378 The kernel figure (and image) directive support **DOT** formated files, see
385 .. kernel-figure:: hello.dot
392 .. kernel-figure:: hello.dot
422 The *render* directive has all the options known from the *figure* directive,
423 plus option ``caption``. If ``caption`` has a value, a *figure* node is
|
| /kernel/linux/linux-5.10/Documentation/translations/it_IT/doc-guide/ |
| D | sphinx.rst | 369 Figure ed immagini
372 Se volete aggiungere un'immagine, utilizzate le direttive ``kernel-figure``
376 .. kernel-figure:: ../../../doc-guide/svg_image.svg
383 .. kernel-figure:: ../../../doc-guide/svg_image.svg
388 Le direttive del kernel per figure ed immagini supportano il formato **DOT**,
396 .. kernel-figure:: ../../../doc-guide/hello.dot
403 .. kernel-figure:: ../../../doc-guide/hello.dot
433 La direttiva *render* ha tutte le opzioni della direttiva *figure*, con
435 un nodo *figure* viene aggiunto. Altrimenti verrà aggiunto un nodo *image*.
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | highres.rst | 14 changes in the time(r) related Linux subsystems. Figure #1 (p. 2) shows the
35 also figure #2 (OLS slides p. 15)
49 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
66 Figure #3 (OLS slides p.18) illustrates the transformation.
139 Figure #4 (OLS slides p.20) illustrates the transformation.
205 Figure #5 (OLS slides p.22) illustrates the transformation.
|
| /kernel/linux/linux-5.10/drivers/hwmon/ |
| D | ads7871.c | 16 /*From figure 18 in the datasheet*/
30 * From figure 17 in the datasheet
39 /*From figure 18 in the datasheet*/
46 /*From figure 18 in the datasheet*/
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 221 .. kernel-figure:: rcu_node-lock.svg
252 figure:
254 .. kernel-figure:: TreeRCU-callback-registry.svg
320 .. kernel-figure:: TreeRCU-gp-init-1.svg
342 .. kernel-figure:: TreeRCU-gp-init-1.svg
349 .. kernel-figure:: TreeRCU-gp-init-1.svg
389 .. kernel-figure:: TreeRCU-qs.svg
464 .. kernel-figure:: TreeRCU-dyntick.svg
487 .. kernel-figure:: TreeRCU-hotplug.svg
508 .. kernel-figure:: TreeRCU-gp-fqs.svg
[all …]
|
| /kernel/linux/linux-5.10/sound/soc/codecs/ |
| D | ak4458.h | 51 * x 1 0 MSB justified Figure 3 (default)
52 * x 1 1 I2S Compliment Figure 4
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 45 .. kernel-figure:: ExpRCUFlow.svg
119 .. kernel-figure:: ExpSchedFlow.svg
305 .. kernel-figure:: Funnel0.svg
314 .. kernel-figure:: Funnel1.svg
320 .. kernel-figure:: Funnel2.svg
349 .. kernel-figure:: Funnel3.svg
356 .. kernel-figure:: Funnel4.svg
363 .. kernel-figure:: Funnel5.svg
370 .. kernel-figure:: Funnel6.svg
377 .. kernel-figure:: Funnel7.svg
[all …]
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | summary.rst | 37 .. kernel-figure:: i2c_bus.svg
57 For the example configuration in figure, you will need a driver for your
|
| /kernel/linux/linux-5.10/drivers/usb/dwc3/ |
| D | drd.c | 114 * Figure 11-4 OTG Driver Overall Programming Flow in dwc3_otgregs_init()
172 * As per Figure 11-4 OTG Driver Overall Programming Flow, in dwc3_otg_init()
199 /* As per Figure 11-10 A-Device Flow Diagram */ in dwc3_otg_host_init()
250 * Figure 11-4 OTG Driver Overall Programming Flow in dwc3_otg_host_exit()
271 /* As per Figure 11-20 B-Device Flow Diagram */ in dwc3_otg_device_init()
309 * Figure 11-4 OTG Driver Overall Programming Flow in dwc3_otg_device_exit()
|
| /kernel/linux/linux-5.10/drivers/thermal/st/ |
| D | stm_thermal.c | 205 /* Figure out prescaler value for PCLK during calibration */ in stm_thermal_calibration()
278 /* Figure out the CLK_PTAT frequency for a given temperature */ in stm_thermal_calculate_threshold()
282 /* Figure out the threshold sample number */ in stm_thermal_calculate_threshold()
369 /* Figure out the CLK_PTAT frequency */ in stm_thermal_get_temp()
374 /* Figure out the temperature in mili celsius */ in stm_thermal_get_temp()
|
| /kernel/linux/linux-5.10/include/linux/pinctrl/ |
| D | pinmux.h | 32 * called by the core to figure out which mux setting it shall map a
40 * driver does not need to figure out whether enabling this function
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | reciprocal_div.h | 29 * version of the algorithm described in Figure 4.1 of the paper.
46 * described in Figure 4.2 of the paper except when "divisor > (1U << 31)" whose
|
| /kernel/linux/linux-5.10/arch/h8300/include/asm/ |
| D | user.h | 47 this will be used by gdb to figure out where the data and stack segments
54 /* The rest of this junk is to help gdb figure out what goes where */
|
| /kernel/linux/linux-5.10/arch/s390/include/asm/ |
| D | user.h | 49 this will be used by gdb to figure out where the data and stack segments
55 /* The rest of this junk is to help gdb figure out what goes where */
|
| /kernel/linux/linux-5.10/Documentation/driver-api/acpi/ |
| D | linuxized-acpica.rst | 33 The following figure depicts the Linux ACPI subsystem where the ACPICA
78 Figure 1. Linux ACPI Software Components
130 illustrated in the following figure::
169 Figure 2. ACPICA -> Linux Upstream Process
205 reduced, but there still are several ones and it takes time to figure
|
| /kernel/linux/linux-5.10/arch/m68k/include/asm/ |
| D | user.h | 55 this will be used by gdb to figure out where the data and stack segments
65 /* The rest of this junk is to help gdb figure out what goes where */
|
| /kernel/linux/linux-5.10/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 99 Figure 1. CIPSO Format
177 Figure 2: Standard Tag Format
218 Figure 3. Tag Type 1 Format
253 by the least significant bit of the second byte. Figure 4 graphically
276 Figure 4. Ordering of Bits in Tag 1 Bit Map
304 Figure 5. Tag Type 2 Format
367 Figure 6. Tag Type 5 Format
|
| /kernel/linux/linux-5.10/scripts/mod/ |
| D | empty.c | 1 /* empty file to figure out endianness / word size */
|