| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/daemontools/ |
| H A D | daemontools_0.76.bb | 8 each line and, for each log, includes or excludes lines matching specified \
|
| /openbmc/phosphor-dbus-interfaces/yaml/org/open_power/OCC/ |
| H A D | PassThrough.interface.yaml | 16 array[byte]), so each entry in the array should pack as many
27 each entry in the array should pack as many bytes as possible.
|
| /openbmc/linux/Documentation/devicetree/bindings/interconnect/ |
| H A D | qcom,qdu1000-rpmh.yaml | 17 associated with each execution environment. Provider nodes must point to at
18 least one RPMh device child node pertaining to their RSC and each provider
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/zeroconf/ |
| H A D | zeroconf_0.9.bb | 7 are normally attached to each Ethernet device in your computer. \
8 Addresses are assigned randomly by each host and, in case of collision, \
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | tsi721.rst | 16 RapidIO messaging support uses dedicated messaging channels for each mailbox.
34 descriptors allocated for each registered Tsi721 DMA channel.
39 transaction requests that can be accepted by each DMA channel.
85 each BDMA channel of Tsi721 (by default - 128).
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | bitmain,bm1880-pinctrl.txt | 21 options. The name of each subnode is not important; all subnodes should be
29 - pins: An array of strings, each string containing the name of a pin.
34 - groups: An array of strings, each string containing the name of a pin
65 - function: An array of strings, each string containing the name of the
|
| /openbmc/linux/tools/testing/memblock/ |
| H A D | README | 20 each other, region arrays are reset in between.
58 allocation functions. Tests for each group are defined in dedicated files, as it
85 points to a block of memory allocated via malloc. For each group of allocation
102 called at the beginning of each test.
|
| /openbmc/linux/Documentation/devicetree/bindings/leds/ |
| H A D | leds-lp55xx.yaml | 103 Current setting at each LED channel (mA x10, 0 if LED is not connected)
109 description: Maximum current at each LED channel.
126 Current setting at each LED channel (mA x10, 0 if LED is not connected)
132 description: Maximum current at each LED channel.
|
| /openbmc/linux/Documentation/admin-guide/perf/ |
| H A D | hns3-pmu.rst | 7 On Hip09, each SICL(Super I/O cluster) has one PMU device.
27 The "filtermode" directory describes the supported filter modes of each
35 The "bdf_min" and "bdf_max" files show the supported bdf range of each
38 The "hw_clk_freq" file shows the hardware clock frequency of each pmu
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | method.md | 6 configured per fan and each supported method requires its own set of attributes
24 - `allowed_out_of_range_time` - Time(in seconds) that each fan sensor is allowed
28 - Time(in seconds) that each fan sensor must be calculated within range of a
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | spi.rst | 9 duplex protocol; for each bit shifted out the MOSI line (one per clock)
13 normally used for each peripheral, plus sometimes an interrupt.
41 :c:type:`struct spi_transfer <spi_transfer>` objects, each of
|
| /openbmc/linux/Documentation/driver-api/pldmfw/ |
| H A D | index.rst | 65 4. For each component that the record indicates, send the component data to
66 the device. For each component, the firmware may respond with an
69 5. For each component, send the binary data to the device firmware for
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-davinci.yaml | 36 description: strings describing the names of each gpio line.
49 banked then provide list of interrupts corresponding to each bank, else
50 provide the list of interrupts for each gpio.
|
| H A D | aspeed,sgpio.yaml | 17 - Support interrupt option for each input port and various interrupt
19 - Support reset tolerance option for each output port
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-jpeg.rst | 26 The chroma subsampling factors describe how each component of an
27 input image is sampled, in respect to maximum sample rate in each
40 - No chroma subsampling, each pixel has Y, Cr and Cb values.
|
| /openbmc/qemu/target/hexagon/ |
| H A D | README | 27 encode*.def Encoding patterns for each instruction
29 legal VLIW slots for each instruction
160 Notice that we also generate a variable named <operand>_off for each operand of
185 We also generate an analyze_<tag> function for each instruction. Currently,
187 gen_start_packet, we invoke the analyze_<tag> function for each instruction in
189 we initialize the result register for each of the predicated assignments.
203 runtime information for each thread and contains stuff like the GPR and
228 These files create a function for each instruction. It is mostly composed of
247 packet is committed. We record the results of each instruction in a side data
300 The helper function for each instruction is named helper_<TAG>, so here's
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | dynamic-debug-howto.rst | 27 - class name (as known/declared by each module)
92 You can also use wildcards in each query term. The match rule supports
132 The meanings of each keyword are:
136 of each callsite. Example::
143 pathname, or the basename of the source file of each callsite.
154 of each callsite. The module name is the string as
179 The given class_name is validated against each module, which may
190 against the line number of each ``pr_debug()`` callsite. A single
284 ``foo`` is extracted from the param-name, and applied to each query in
285 ``QUERY``, and only 1 match-spec of each type is allowed.
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/ |
| H A D | jquery-2.0.3.min.js | 4 …each:function(e,t){return x.each(this,e,t)},ready:function(e){return x.ready.promise().done(e),thi…
5 …each(function(){var n=x.queue(this,e,t);x._queueHooks(this,e),"fx"===e&&"inprogress"!==n[0]&&x.deq…
6 …each(e[a]||[],function(e,a){var l=a(t,n,r);return"string"!=typeof l||o||i[l]?o?!(u=l):undefined:(t…
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-design-CFS.rst | 18 power and which can run each task at precise equal speed, in parallel, each at
20 each at 50% physical power --- i.e., actually in parallel.
209 fair CPU time to each task. Sometimes, it may be desirable to group tasks and
210 provide fair CPU time to each such task group. For example, it may be
211 desirable to first provide fair CPU time to each user on the system and then to
212 each task belonging to a user.
227 When CONFIG_FAIR_GROUP_SCHED is defined, a "cpu.shares" file is created for each
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | qe_firmware.rst | 60 The QE architecture allows for only one microcode present in I-RAM for each
72 allows each processor to run a different microcode, effectively creating an
127 | 0 | General | Indicates that prior to each host command |
158 | | | for each SNUM of Ethernet TX thread. |
206 must be one and only one 'microcode' structure for each RISC processor.
237 'vtraps' is an array of 8 words that contain virtual trap values for each
242 For each RISC processor there is one 'microcode' structure. The first
249 for each of the 16 traps. If trap[i] is 0, then this particular
|
| /openbmc/linux/Documentation/timers/ |
| H A D | hpet.rst | 10 each of which can generate oneshot interrupts and at least one of which has
13 independent of each other ... these share a counter, complicating resets.
|
| /openbmc/linux/Documentation/usb/ |
| H A D | misc_usbsevseg.rst | 27 raw controls each segment manually,
49 To set multiple decimals points sum up each power.
|
| /openbmc/linux/drivers/phy/allwinner/ |
| H A D | Kconfig | 47 This driver controls each individual USB 2 host PHY.
59 This driver controls each individual USB 2+3 host PHY combo.
|
| /openbmc/linux/drivers/net/ethernet/microchip/vcap/ |
| H A D | Kconfig | 19 Besides this each VCAP has:
33 limitations that each VCAP has in terms of its supported keys and actions.
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | mediatek,mt6779-keypad.yaml | 18 A key can be placed at each intersection of a unique row and a unique column.
53 description: each (row, column) group has multiple keys
|