| /openbmc/linux/tools/memory-model/litmus-tests/ |
| H A D | CoWW+poonceonce.litmus | 6 * Test of write-write coherence, that is, whether or not two successive
|
| H A D | CoRR+poonceonce+Once.litmus | 6 * Test of read-read coherence, that is, whether or not two successive
|
| H A D | README | 7 successive reads from the same variable are ordered.
21 successive writes to the same variable are ordered.
|
| /openbmc/linux/drivers/memory/tegra/ |
| H A D | tegra20.c | 84 unsigned int successive; member
588 &stats[clienta].successive, in tegra20_mc_collect_stats()
589 &stats[clientb].successive); in tegra20_mc_collect_stats()
669 tegra20_mc_printf_percents(s, "%-13s", stats[i].successive); in tegra20_mc_stats_show()
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | mcp3021.rst | 31 The Microchip Technology Inc. MCP3021 is a successive approximation A/D
|
| H A D | adm9240.rst | 57 high speed successive approximation ADC allows frequent sampling of all
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | field-order.rst | 36 two successive top and bottom, or bottom and top fields yield a valid
125 ``V4L2_FIELD_TOP`` or ``V4L2_FIELD_BOTTOM``. Any two successive
126 fields pair to build a frame. If fields are successive, without
|
| H A D | vidioc-g-parm.rst | 107 - This is the desired period between successive frames captured by
166 - This is the desired period between successive frames output by the
250 successive fields or frames to remove color edge artifacts and
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | qcom,pm8xxx-keypad.txt | 63 Definition: time in microseconds to pause between successive scans
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | efficiently-fetching-sources.rst | 52 Another technique you can use to ready yourself for a successive string
|
| /openbmc/linux/Documentation/translations/it_IT/doc-guide/ |
| H A D | sphinx.rst | 305 colonne successive
308 righe successive
325 * ``:cspan:`` [int] colonne successive (*morecols*)
326 * ``:rspan:`` [int] righe successive (*morerows*)
|
| H A D | kernel-doc.rst | 120 funzione può continuare su righe successive e termina con la descrizione di
222 funzione può continuare su righe successive e termina con la descrizione di
|
| /openbmc/linux/arch/m68k/fpsp040/ |
| H A D | decbin.S | 24 | A1. Convert the bcd exponent to binary by successive adds and muls.
30 | A2. Convert the bcd mantissa to binary by successive
|
| /openbmc/u-boot/doc/ |
| H A D | README.bloblist | 19 sometimes TPL). It is passed through to each successive part of the boot and
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | omfs.rst | 50 sysblock, and may be mirrored in successive blocks on the disk. A sysblock may
|
| /openbmc/linux/Documentation/accounting/ |
| H A D | delay-accounting.rst | 55 Taking the difference of two successive readings of a given
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | license-rules.rst | 114 dell'opzione 'o successive' si formano aggiungendo alla fine il simbolo "+"
115 per indicare l'opzione 'o successive'.::
202 licenze che permettono l'opzione 'o successive' hanno due identificatori
|
| H A D | changes.rst | 235 XFS nel kernel (sono raccomandate le versioni 2.6.0 o successive per via
250 formato quota. La versione 3.07 e successive di quota-tools supportano
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | amd-memory-encryption.rst | 26 successive level of page tables can also be encrypted by setting the encryption
|
| /openbmc/u-boot/doc/device-tree-bindings/adc/ |
| H A D | st,stm32-adc.txt | 3 STM32 ADC is a successive approximation analog-to-digital converter.
|
| /openbmc/linux/Documentation/driver-api/fpga/ |
| H A D | fpga-mgr.rst | 110 case, this function is called multiple times for successive chunks. This interface
|
| /openbmc/linux/Documentation/networking/ |
| H A D | netdev-features.rst | 82 stateless). It can be called multiple times between successive
|
| /openbmc/linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-dqevent.rst | 42 possible to read two successive events that have the same value (e.g.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest/ |
| H A D | userfaultfd.patch | 208 + value of the rear pointer; this is so successive calls to initstate won't
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | recipes.txt | 528 based on the relation between the accesses linking successive CPUs in a
564 between each successive pair of non-write-to-read links. This
|