| /openbmc/u-boot/doc/ |
| H A D | README.trace | 105 calls on the left and little marks representing the start and end of each
233 update profoffset each time. This allows successive commands to append data
|
| /openbmc/linux/Documentation/usb/ |
| H A D | ehci.rst | 125 and bulk transfers. Shows each active qh and the qtds
182 so that it's only trying six (or maybe seven) USB transactions each
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-v4l2.rst | 68 padding bytes at the end of each line. Drivers however may ignore
84 following each line as the Y plane. To avoid ambiguities drivers
|
| 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/networking/ |
| H A D | nexthop-group-resilient.rst | 16 hashes to each next hop in the group, and then selects the next hop by
251 only), each bucket will be considered idle when no traffic hits it for at
|
| H A D | pktgen.rst | 9 running, pktgen creates a thread for each CPU with affinity to that CPU.
59 Pktgen creates a thread for each CPU with affinity to that CPU.
|
| /openbmc/linux/Documentation/PCI/ |
| H A D | acpi-info.rst | 11 host bridges, so the ACPI namespace must describe each host bridge, the
103 system firmware must supply an _HID object ... for each device to
|
| /openbmc/qemu/docs/system/ppc/ |
| H A D | pseries.rst | 215 As noticed in the sections above, each module can run in a different
216 environment. The following table shows with which environment each module can
|
| /openbmc/openbmc/poky/meta/recipes-extended/shadow/files/ |
| H A D | login.defs_shadow-sysroot | 86 # If defined, this file will be output before each login prompt.
191 # better for privacy. There is no One True Answer here: each sysadmin
|
| /openbmc/qemu/qapi/ |
| H A D | block-export.json | 102 # @bitmaps: Also export each of the named dirty bitmaps reachable from
105 # each bitmap. Since 7.1 bitmap may be specified by node/name
|
| /openbmc/docs/designs/ |
| H A D | bmc-health-monitor.md | 199 interface for each metric would need to be associated with the appropriate
225 AIX, etc) and applications, the amount of code for each Collected plugin is
|
| /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/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/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/qemu/docs/devel/ |
| H A D | writing-monitor-commands.rst | 42 The following sections will demonstrate each of the steps above. We will start
160 Notice the new 'data' member in the schema. It's an JSON object whose each
365 fields corresponding to each distinct data item. This should be the
572 # Returns: a list of @TimerAlarmMethod for each method
|
| /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.
|