| /openbmc/linux/Documentation/driver-api/ |
| H A D | vme.rst | 189 an item to a list. This is due to the diverse attributes required for each type
269 :c:func:`vme_lm_detach` allows on to be detached from each location monitor
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | watch_queue.rst | 200 (``WATCH_META_REMOVAL_NOTIFICATION``) is sent to the watch queue of each
221 note in each individual queue according to the credentials of that queue
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | ktap.rst | 17 can have subtests), each of which can contain both diagnostic data -- e.g., log
79 have the number 1 and the number then must increase by 1 for each additional
|
| /openbmc/linux/LICENSES/dual/ |
| H A D | copyleft-next-0.3.1 | 147 ** of using it. To the extent permitted by applicable law, each **
207 includes each entity that controls, is controlled by, or is under
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | hwmon-kernel-api.rst | 134 Pointer to a function to return the file mode for each supported
174 Pointer to a 0-terminated list of configuration values for each
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | gpio-properties.rst | 156 describes each line/pin of a GPIO controller/expander. This list, contained in
240 array of struct acpi_gpio_mapping objects that each contains a name, a pointer
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-fbuf.rst | 173 following each line as the Y plane. To avoid ambiguities drivers
315 and :ref:`osd`. Both chroma-keying are mutual exclusive to each
|
| /openbmc/linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_overview.rst | 42 The following section provides a brief overview of each phase in the BPF life
82 each of them prefixed with the specific object name:
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | vas-api.rst | 53 can establish multiple windows, but one window for each file descriptor.
217 co-processor Status Block (CSB) flags. NX updates status in CSB after each
|
| /openbmc/linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588s-indiedroid-nova.dts | 145 * Add labels for each GPIO pin exposed on the 40 pin header. Note that
146 * voltage of each GPIO pin could be either 3.3v or 1.8v (as noted by
|
| /openbmc/docs/security/ |
| H A D | network-security-considerations.md | 15 here is an example of each:
82 Transport layer security (TLS) protocols are configured for each service at
|
| /openbmc/qemu/target/arm/tcg/ |
| H A D | neon-dp.decode | 396 # each subgroup accidentally overlap each other. Note that all the
|
| /openbmc/qemu/qapi/ |
| H A D | block-export.json | 103 # @bitmaps: Also export each of the named dirty bitmaps reachable from
106 # each bitmap. Since 7.1 bitmap may be specified by node/name
|
| H A D | misc.json | 104 # Returns a list of information about each iothread.
110 # Returns: a list of @IOThreadInfo for each iothread
|
| /openbmc/linux/Documentation/sound/ |
| H A D | alsa-configuration.rst | 137 controlling enabling and disabling of each one of the devices if there
701 Number of PCM devices assigned to each card (default = 1, up to 4)
710 behavior to each PCM device:
1016 [Multiple options for each card instance]
2296 * bit 8: Add a delay of 20ms at each control message handling
2297 * bit 9: Add a delay of 1-2ms at each control message handling
2299 * bit 11: Add a delay of 50ms at each interface setup
2380 each channel.
2613 number for each card via module option, too, so that the order of
2642 the second (#1) for snd-ens1371. You can omit index option in each
[all …]
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight.rst | 17 developed a HW assisted tracing solution by means of different components, each
177 perform base operations related to the components, each component having
636 found in sysfs with more information on each entry being found in [#first]_::
673 Furthermore, components can be programmed to interact with each other across the
|
| /openbmc/linux/Documentation/userspace-api/netlink/ |
| H A D | intro.rst | 100 In addition to the Netlink fixed metadata header each Netlink protocol
157 matter in practice, but setting it to an increasing value for each
517 meaning that each message must be received in its entirety by a single
605 without breaking each member into an attribute of its own.
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | stallwarn.rst | 217 And continues with the output of sched_show_task() for each
238 will normally be followed by stack dumps for each CPU. Please note that
399 is supplied with each RCU CPU stall warning::
484 trace each interrupt, for example, by referring to show_interrupts().
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_systeminfo_parameters.robot | 585 [Documentation] Adding prefix '0x' to each list object and join the string.
590 # Prefix Bytes with 0x for each data bytes and makes a string of request bytes.
601 ... prefix each byte with 0x and make them a suite variable.
603 # Get Default Values of each parameters.
|
| /openbmc/ipmi-fru-parser/ |
| H A D | LICENSE | 199 appropriately publish on each copy an appropriate copyright notice;
205 You may charge any price or no price for each copy that you convey,
230 d) If the work has interactive user interfaces, each must display
456 work results from an entity transaction, each party to that
630 to attach them to the start of each source file to most effectively
631 state the exclusion of warranty; and each file should have at least
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | cpufreq.rst | 60 As a rule, each governor implements one, possibly parametrized, scaling
185 to register per-CPU utilization update callbacks for each policy. These
210 in :file:`/sys/devices/system/cpu/cpufreq` each contain policy-specific
337 scaling drivers. As stated before, each of them implements a single, possibly
351 per-policy, they are located in a subdirectory of each policy directory.
475 for each policy this governor is attached to (but since the unit here
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | GPL-3.0-only | 74 … any medium, provided that you conspicuously and appropriately publish on each copy an appropriate…
76 You may charge any price or no price for each copy that you convey, and you may offer support or wa…
84 …* d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; how…
144 …ons. If propagation of a covered work results from an entity transaction, each party to that trans…
194 …afest to attach them to the start of each source file to most effectively state the exclusion of w…
|
| H A D | AGPL-3.0-or-later | 176 on each copy an appropriate copyright notice; keep intact all notices stating
181 You may charge any price or no price for each copy that you convey, and you
204 d) If the work has interactive user interfaces, each must display Appropriate
407 each party to that transaction who receives a copy of the work also receives
581 them to the start of each source file to most effectively state the exclusion
582 of warranty; and each file should have at least the "copyright" line and a
|
| H A D | AGPL-3.0-only | 187 appropriately publish on each copy an appropriate copyright notice;
193 You may charge any price or no price for each copy that you convey,
218 d) If the work has interactive user interfaces, each must display
444 work results from an entity transaction, each party to that
628 to attach them to the start of each source file to most effectively
629 state the exclusion of warranty; and each file should have at least
|
| H A D | GPL-3.0-or-later | 187 on each copy an appropriate copyright notice; keep intact all notices stating
192 You may charge any price or no price for each copy that you convey, and you
215 d) If the work has interactive user interfaces, each must display Appropriate
418 each party to that transaction who receives a copy of the work also receives
580 them to the start of each source file to most effectively state the exclusion
581 of warranty; and each file should have at least the "copyright" line and a
|