| /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-6.6/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
67 # patches.Figure only landed in Sphinx 1.4
68 from sphinx.directives.patches import Figure # pylint: disable=C0413
70 Figure = images.Figure variable
144 # figure handling
145 app.add_directive("kernel-figure", KernelFigure)
470 # figure handling
481 class kernel_figure(nodes.figure):
[all …]
|
| /kernel/linux/linux-6.6/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:: peer-states-8.dot
|
| /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-6.6/Documentation/devicetree/ |
| D | of_unittest.rst | 97 Figure 1, describes a generic structure of machine's un-flattened device tree
126 Figure 1: Generic structure of un-flattened device tree
144 in Figure 2 is attached to the live tree described in Figure 1::
155 Figure 2: Example test data tree to be attached to live tree.
164 data node is attached to the live tree above (Figure 1), the final structure is
165 as shown in Figure 3::
200 Figure 3: Live device tree structure after attaching the testcase-data.
204 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-6.6/Documentation/translations/zh_CN/doc-guide/ |
| D | sphinx.rst | 328 如果要添加图片，应该使用 ``kernel-figure`` 和 ``kernel-image`` 指令。例如，
331 .. kernel-figure:: ../../../doc-guide/svg_image.svg
338 .. kernel-figure:: ../../../doc-guide/svg_image.svg
350 .. kernel-figure:: ../../../doc-guide/hello.dot
357 .. kernel-figure:: ../../../doc-guide/hello.dot
385 *render* 指令包含 *figure* 指令中已知的所有选项，以及选项 ``caption`` 。如果
386 ``caption`` 有值，则插入一个 *figure* 节点，若无，则插入一个 *image* 节点。
|
| /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-6.6/Documentation/translations/it_IT/doc-guide/ |
| D | sphinx.rst | 409 Figure ed immagini
412 Se volete aggiungere un'immagine, utilizzate le direttive ``kernel-figure``
416 .. kernel-figure:: ../../../doc-guide/svg_image.svg
423 .. kernel-figure:: ../../../doc-guide/svg_image.svg
428 Le direttive del kernel per figure ed immagini supportano il formato **DOT**,
436 .. kernel-figure:: ../../../doc-guide/hello.dot
443 .. kernel-figure:: ../../../doc-guide/hello.dot
473 La direttiva *render* ha tutte le opzioni della direttiva *figure*, con
475 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-6.6/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-6.6/Documentation/userspace-api/media/v4l/ |
| 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**
|
| /kernel/linux/linux-6.6/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/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-6.6/Documentation/doc-guide/ |
| D | sphinx.rst | 443 If you want to add an image, you should use the ``kernel-figure`` and
444 ``kernel-image`` directives. E.g. to insert a figure with a scalable
447 .. kernel-figure:: svg_image.svg
454 .. kernel-figure:: svg_image.svg
459 The kernel figure (and image) directive supports **DOT** formatted files, see
466 .. kernel-figure:: hello.dot
473 .. kernel-figure:: hello.dot
503 The *render* directive has all the options known from the *figure* directive,
504 plus option ``caption``. If ``caption`` has a value, a *figure* node is
|
| /kernel/linux/linux-6.6/Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 10 .. kernel-figure:: dc_pipeline_overview.svg
142 .. kernel-figure:: pipeline_4k_no_split.svg
164 .. kernel-figure:: pipeline_4k_split.svg
220 .. kernel-figure:: global_sync_vblank.svg
230 .. kernel-figure:: config_example.svg
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/devicetree/ |
| D | of_unittest.rst | 101 Figure 1: 未扁平化的设备树的通用结构
127 Figure 2: 将测试数据树附在实时树上的例子。
169 Figure 3: 附加测试案例数据后的实时设备树结构。
|
| /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-6.6/drivers/gpu/drm/i915/gt/ |
| D | intel_gt_clock_utils.c | 65 * First figure out the reference frequency. There are 2 ways in gen11_read_clock_frequency()
78 * Now figure out how the command stream's timestamp in gen11_read_clock_frequency()
100 * Now figure out how the command stream's timestamp in gen9_read_clock_frequency()
|