Home
last modified time | relevance | path

Searched full:figure (Results 1 – 25 of 1097) sorted by relevance

12345678910>>...44

/linux-6.12.1/Documentation/sphinx/
Dkfigure.py4 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
64 Figure = images.Figure variable
138 # figure handling
139 app.add_directive("kernel-figure", KernelFigure)
464 # figure handling
475 class kernel_figure(nodes.figure):
476 """Node for ``kernel-figure`` directive."""
478 class KernelFigure(Figure):
[all …]
/linux-6.12.1/Documentation/admin-guide/blockdev/drbd/
Dfigures.rst8 .. 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
/linux-6.12.1/Documentation/devicetree/
Dof_unittest.rst97 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
/linux-6.12.1/Documentation/translations/zh_CN/doc-guide/
Dsphinx.rst328 如果要添加图片,应该使用 ``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* 节点。
/linux-6.12.1/Documentation/translations/it_IT/doc-guide/
Dsphinx.rst409 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*.
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Ddev-raw-vbi.rst220 .. 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**
/linux-6.12.1/Documentation/timers/
Dhighres.rst14 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.
/linux-6.12.1/drivers/hwmon/
Dads7871.c16 /*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*/
/linux-6.12.1/Documentation/doc-guide/
Dsphinx.rst452 If you want to add an image, you should use the ``kernel-figure`` and
453 ``kernel-image`` directives. E.g. to insert a figure with a scalable
456 .. kernel-figure:: svg_image.svg
463 .. kernel-figure:: svg_image.svg
468 The kernel figure (and image) directive supports **DOT** formatted files, see
475 .. kernel-figure:: hello.dot
482 .. kernel-figure:: hello.dot
512 The *render* directive has all the options known from the *figure* directive,
513 plus option ``caption``. If ``caption`` has a value, a *figure* node is
/linux-6.12.1/Documentation/gpu/amdgpu/display/
Ddcn-overview.rst10 .. 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
Dmpo-overview.rst89 .. kernel-figure:: mpo-cursor.svg
126 .. kernel-figure:: single-display-mpo.svg
188 .. kernel-figure:: multi-display-hdcp-mpo.svg
223 .. kernel-figure:: multi-display-hdcp-mpo-less-pipe-ex.svg
/linux-6.12.1/Documentation/translations/zh_CN/devicetree/
Dof_unittest.rst101 Figure 1: 未扁平化的设备树的通用结构
127 Figure 2: 将测试数据树附在实时树上的例子。
169 Figure 3: 附加测试案例数据后的实时设备树结构。
/linux-6.12.1/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.rst45 .. 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 …]
/linux-6.12.1/Documentation/RCU/Design/Memory-Ordering/
DTree-RCU-Memory-Ordering.rst245 .. kernel-figure:: rcu_node-lock.svg
276 figure:
278 .. kernel-figure:: TreeRCU-callback-registry.svg
344 .. kernel-figure:: TreeRCU-gp-init-1.svg
366 .. kernel-figure:: TreeRCU-gp-init-2.svg
373 .. kernel-figure:: TreeRCU-gp-init-3.svg
413 .. kernel-figure:: TreeRCU-qs.svg
488 .. kernel-figure:: TreeRCU-dyntick.svg
511 .. kernel-figure:: TreeRCU-hotplug.svg
532 .. kernel-figure:: TreeRCU-gp-fqs.svg
[all …]
/linux-6.12.1/drivers/gpu/drm/i915/gt/
Dintel_gt_clock_utils.c66 * First figure out the reference frequency. There are 2 ways in gen11_read_clock_frequency()
79 * Now figure out how the command stream's timestamp in gen11_read_clock_frequency()
101 * Now figure out how the command stream's timestamp in gen9_read_clock_frequency()
/linux-6.12.1/drivers/usb/dwc3/
Ddrd.c114 * 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()
/linux-6.12.1/sound/soc/codecs/
Dak4458.h51 * x 1 0 MSB justified Figure 3 (default)
52 * x 1 1 I2S Compliment Figure 4
/linux-6.12.1/arch/s390/include/asm/
Duser.h49 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 */
/linux-6.12.1/drivers/thermal/st/
Dstm_thermal.c202 /* Figure out prescaler value for PCLK during calibration */ in stm_thermal_calibration()
275 /* Figure out the CLK_PTAT frequency for a given temperature */ in stm_thermal_calculate_threshold()
279 /* Figure out the threshold sample number */ in stm_thermal_calculate_threshold()
366 /* Figure out the CLK_PTAT frequency */ in stm_thermal_get_temp()
371 /* Figure out the temperature in mili celsius */ in stm_thermal_get_temp()
/linux-6.12.1/include/linux/pinctrl/
Dpinmux.h31 * called by the core to figure out which mux setting it shall map a
39 * driver does not need to figure out whether enabling this function
/linux-6.12.1/include/linux/
Dreciprocal_div.h29 * 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
/linux-6.12.1/Documentation/driver-api/acpi/
Dlinuxized-acpica.rst33 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
/linux-6.12.1/arch/m68k/include/asm/
Duser.h55 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 */
/linux-6.12.1/Documentation/i2c/
Dsummary.rst36 .. kernel-figure:: i2c_bus.svg
61 For the example configuration in the figure above, you will need one driver for
/linux-6.12.1/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt99 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

12345678910>>...44