| /openbmc/u-boot/Documentation/sphinx/ |
| H A 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
73 # patches.Figure only landed in Sphinx 1.4
74 from sphinx.directives.patches import Figure # pylint: disable=C0413
76 Figure = images.Figure
140 # figure handling
141 app.add_directive("kernel-figure", KernelFigure)
366 # figure handling
377 class kernel_figure(nodes.figure):
[all …]
|
| /openbmc/linux/Documentation/sphinx/ |
| H A 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
144 # figure handling
145 app.add_directive("kernel-figure", KernelFigure)
470 # figure handling
481 class kernel_figure(nodes.figure):
[all …]
|
| /openbmc/linux/Documentation/admin-guide/blockdev/drbd/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/ |
| H A 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
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | KeyPolicy.v1_0_1.json | 293 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
294 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
295 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
296 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
297 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
315 …hash function as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base S…
316 …hash function as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base S…
317 …hash function as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base S…
353 …'Transport Specific Address Subtype `Definition` for NVMe/TCP Transport' figure in the NVMe TCP Tr…
354 …'Transport Specific Address Subtype `Definition` for NVMe/TCP Transport' figure in the NVMe TCP Tr…
|
| /openbmc/linux/Documentation/translations/zh_CN/doc-guide/ |
| H A 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* 节点。
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | KeyPolicy_v1.xml | 151 …hash function as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base S…
155 …hash function as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base S…
159 …hash function as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base S…
168 …'Transport Specific Address Subtype `Definition` for NVMe/TCP Transport' figure in the NVMe TCP Tr…
172 …'Transport Specific Address Subtype `Definition` for NVMe/TCP Transport' figure in the NVMe TCP Tr…
194 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
198 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
202 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
206 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
210 … group as defined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base S…
|
| /openbmc/linux/Documentation/translations/it_IT/doc-guide/ |
| H A 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*.
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A 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**
|
| /openbmc/linux/Documentation/timers/ |
| H A 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.
|
| /openbmc/linux/drivers/hwmon/ |
| H A 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*/
|
| /openbmc/openbmc/poky/meta-selftest/recipes-extended/hello-rs/hello-rs/ |
| H A D | 0001-Greet-OE-Core.patch | 22 let figure = standard_font.convert(&greeting);
23 println!("{}", figure.unwrap());
|
| /openbmc/linux/Documentation/doc-guide/ |
| H A 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
|
| /openbmc/linux/Documentation/gpu/amdgpu/display/ |
| H A 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
|
| /openbmc/linux/Documentation/translations/zh_CN/devicetree/ |
| H A D | of_unittest.rst | 101 Figure 1: 未扁平化的设备树的通用结构
127 Figure 2: 将测试数据树附在实时树上的例子。
169 Figure 3: 附加测试案例数据后的实时设备树结构。
|
| /openbmc/linux/drivers/gpu/drm/i915/gt/ |
| H A 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()
|
| /openbmc/linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A 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 …]
|
| /openbmc/linux/sound/soc/codecs/ |
| H A D | ak4458.h | 51 * x 1 0 MSB justified Figure 3 (default)
52 * x 1 1 I2S Compliment Figure 4
|
| /openbmc/linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 245 .. 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 …]
|
| /openbmc/linux/drivers/usb/dwc3/ |
| H A 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()
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | var_stack.py | 109 … parameter is normally unnecessary as this function can figure out the
115 # The caller has not passed a var_name so we will try to figure it out.
|
| /openbmc/linux/arch/s390/include/asm/ |
| H A 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 */
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | summary.rst | 39 .. kernel-figure:: i2c_bus.svg
59 For the example configuration in figure, you will need a driver for your
|
| /openbmc/openbmc/poky/documentation/overview-manual/ |
| H A D | concepts.rst | 204 The following figure shows an expanded representation of the "User
206 figure <overview-manual/concepts:openembedded build system concepts>`:
329 Configuration Edits" box in the figure.
356 figure <overview-manual/concepts:openembedded build system concepts>`:
367 "BSP Layer" in the following figure) providing machine-specific
375 the following figure) providing top-level or general policies for the
384 The following figure shows an expanded representation of these three
385 layers from the :ref:`general workflow figure
479 While the figure shows several
499 figure <overview-manual/concepts:openembedded build system concepts>`
[all …]
|
| /openbmc/linux/drivers/thermal/st/ |
| H A D | stm_thermal.c | 202 /* 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()
|