| /openbmc/linux/Documentation/powerpc/ |
| H A D | elfnote.rst | 5 The PowerPC namespace in an ELF Note of the kernel binary is used to store
24 Indicate that the powerpc kernel binary knows how to run in an
27 In an ultravisor-enabled system, some machine resources are now controlled
33 In an ultravisor-enabled system, a bootloader could warn the user or prevent
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-delay.yaml | 13 This binding describes an electrical setup where setting an GPIO output
32 If the input on the consumer is controlled by an open-drain signal
33 attached to an RC circuit the ramp-up delay is not under control
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | brcm,bcm6345-l1-intc.txt | 10 - Most onchip peripherals are wired directly to an L1 input
29 - interrupt-controller: identifies the node as an interrupt controller
30 - #interrupt-cells: specifies the number of cells needed to encode an interrupt
35 If multiple reg ranges and interrupt-parent entries are present on an SMP
41 specifying an alternative endianness.
|
| H A D | marvell,orion-intc.txt | 8 - interrupt-controller: identifies the node as an interrupt controller
9 - #interrupt-cells: number of cells to encode an interrupt source, shall be 1
32 - interrupt-controller: identifies the node as an interrupt controller
33 - #interrupt-cells: number of cells to encode an interrupt source, shall be 1
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-trigger-sysfs | 6 driver. Writing this file with any value triggers an event
8 into an in kernel buffer. This approach can be valuable during
18 trigger. In order to associate the trigger with an IIO device
31 in the system, an invalid argument message will be returned.
41 to be removed. If the trigger can't be found, an invalid
|
| /openbmc/linux/Documentation/driver-api/firmware/ |
| H A D | request_firmware.rst | 16 an error is returned.
47 until the firmware or an error is returned. Function callbacks are
48 provided so that when the firmware or an error is found the driver is
60 Some devices have an optimization in place to enable the firmware to be
74 Once an API call returns you process the firmware and then release the
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-priority.rst | 33 Pointer to an enum :c:type:`v4l2_priority` type.
39 :ref:`VIDIOC_G_PRIORITY <VIDIOC_G_PRIORITY>` ioctl with a pointer to an enum v4l2_priority
42 To request an access priority applications store the desired priority in
43 an enum v4l2_priority variable and call :ref:`VIDIOC_S_PRIORITY <VIDIOC_G_PRIORITY>` ioctl
72 controls. This is the default priority unless an application
|
| H A D | vidioc-subscribe-event.rst | 63 event source, then set this to 0. Whether or not an event needs an
85 - When this event is subscribed an initial event will be sent
91 - If set, then events directly caused by an ioctl will also be sent
96 where an application changes a control to a one value and then
97 another, and then receives an event telling it that that control
|
| H A D | vidioc-qbuf.rst | 38 Applications call the ``VIDIOC_QBUF`` ioctl to enqueue an empty
67 the ``V4L2_BUF_FLAG_DONE`` flag in the ``flags`` field, or it returns an
78 ``flags`` field, or it returns an error code. This ioctl locks the
93 ``flags`` field, or it returns an error code. This ioctl locks the
95 access (usually DMA). If an application accesses (reads/writes) a locked
128 fills all remaining fields or returns an error code. The driver may also
146 immediately with an ``EAGAIN`` error code when no buffer is available.
167 an invalid DMABUF file descriptor.
170 ``VIDIOC_DQBUF`` failed due to an internal error. Can also indicate
175 The driver might dequeue an (empty) buffer despite returning
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/syslinux/syslinux/ |
| H A D | 0001-linux-syslinux-support-ext2-3-4-device.patch | 7 * The open_ext2_fs() checks whether it is an ext2/3/4 device,
30 + * Check whether the device contains an ext2, ext3 or ext4 fs and open it if
34 + * 1: Not an ext2, ext3 or ext4
50 die("can't combine an offset with a block device");
54 + * Check if it is an ext2, ext3 or ext4
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | inlinedata.rst | 11 attribute space, then it might be found as an extended attribute
13 constrains the amount of extended attributes one can attach to an inode.
22 The inline data feature requires the presence of an extended attribute
29 directory. Following that is a 56-byte space for an array of directory
31 attribute in the inode body, the EA value is an array of
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | net_prio.rst | 5 The Network priority cgroup provides an interface to allow an administrator to
9 Nominally, an application would set the priority of its traffic via the
14 decision rather than an application defined one.
16 This cgroup allows an administrator to assign a process to a group which defines
30 integer value that the kernel uses as an internal representation of this
|
| /openbmc/linux/lib/crypto/ |
| H A D | Kconfig | 26 Declares whether the architecture provides an arch-specific
42 Declares whether the architecture provides an arch-specific
62 by either the generic implementation or an arch-specific one, if one
68 Declares whether the architecture provides an arch-specific
88 fulfilled by either the generic implementation or an arch-specific
104 Declares whether the architecture provides an arch-specific
123 by either the generic implementation or an arch-specific one, if one
|
| /openbmc/linux/Documentation/devicetree/ |
| H A D | overlay-notes.rst | 18 in an active device should have it created while if the device node is either
21 Lets take an example where we have a foo board with the following base tree::
111 1) Call of_overlay_fdt_apply() to create and apply an overlay changeset. The
112 return value is an error or a cookie identifying this overlay.
115 previously created via the call to of_overlay_fdt_apply(). Removal of an
132 returns an error.
135 that could be triggered by applying or removing an overlay. These notifiers
147 pointers to the overlay nodes or data. Any example of an inadvertent use
148 of such pointers is if a driver or subsystem module is loaded after an
|
| /openbmc/qemu/docs/devel/ |
| H A D | control-flow-integrity.rst | 13 function calls have not been altered by an attacker.
46 If desired, an additional flag to increase the verbosity of the output in case
53 violation, the binary will terminate with an illegal instruction signal.
76 3. Plugins, since a plugin is implemented as an external library
78 4. Modules, since they are implemented as an external library
81 signal handler may have been provided by an external library or even plugged
87 If you are working on function that is performing a call using an
90 definition, and add an explanation on why the function is not compatible
96 * A TB is a blob of binary code, created at runtime and called with an
117 an assertion. However, other sanitizers such as address and ub sanitizers
[all …]
|
| /openbmc/qemu/docs/interop/ |
| H A D | qed_spec.txt | 9 …ut the image file. A regular cluster may be a '''data cluster''', an '''L2''', or an '''L1 table'…
45 …ed within the first ''header_size'' clusters. The backing filename may be an absolute path or rel…
50 …This should be used to ensure that raw backing files are never detected as an image format if they…
80 …ontiguous clusters. The table_size header field determines table size for an image file. For exa…
94 …ay wish to store per-offset information. The least significant 12 bits of an offset are reserved …
97 Reads to an unallocated area of the image file access the backing file. If there is no backing fil…
99 Writes to an unallocated area cause a new data clusters to be allocated, and a new L2 table if that…
104 Reads to a zero data cluster produce zeroes. Note that the difference between an unallocated and a…
131 …QED_F_NEED_CHECK bit is used to mark an image as dirty before starting an operation that could lea…
134 # Each cluster is referenced once and only once. It is an inconsistency to have a cluster referenc…
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | maple_tree.rst | 17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
20 the lock to an external lock of a different type.
64 given index. You can use mtree_erase() to erase an entire range by only
72 You can search for an entry from an index upwards by using mt_find().
100 The Maple Tree uses RCU and an internal spinlock to synchronise access:
125 freed memory, but an explanation of that is beyond the scope of this
134 cost of an interface which can be harder to use and has fewer safeguards.
136 You can use the ma_lock, RCU or an external lock for protection.
158 You can use mas_erase() to erase an entire range by setting index and
184 There are a few extra interfaces provided when using an allocation tree.
[all …]
|
| H A D | xarray.rst | 12 The XArray is an abstract data type which behaves like a very large array
32 objects, as long as those objects have an alignment of at least 4.
35 You must first convert it into an entry using xa_mk_value().
38 an integer by calling xa_to_value().
61 Start by initialising an XArray, either with DEFINE_XARRAY()
74 You can conditionally replace an entry at an index by using
110 Finally, you can remove all entries from an XArray by calling
122 You can enquire whether a mark is set on an entry by using
147 You can call xa_alloc() to store the entry at an unused index
155 To free an entry, use xa_erase() (or xa_release() if
[all …]
|
| /openbmc/linux/drivers/net/wireless/ath/ath9k/ |
| H A D | main.c | 357 struct ath_node *an; in ath_node_attach() local
360 an->sc = sc; in ath_node_attach()
361 an->sta = sta; in ath_node_attach()
362 an->vif = vif; in ath_node_attach()
363 memset(&an->key_idx, 0, sizeof(an->key_idx)); in ath_node_attach()
1368 an->sc = sc; in ath9k_add_interface()
1369 an->sta = NULL; in ath9k_add_interface()
1370 an->vif = vif; in ath9k_add_interface()
1624 if (!an->ps_key) in ath9k_del_ps_key()
1628 an->ps_key = 0; in ath9k_del_ps_key()
[all …]
|
| /openbmc/webui-vue/docs/guide/components/alerts/ |
| H A D | index.md | 3 An alert is an inline message that contains a short description that a user
14 <alert show variant="danger">This is an error message</alert>
15 <alert show variant="info">This is an info message</alert>
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | map_array.rst | 13 storage. The key type is an unsigned 32-bit integer (4 bytes) and the map is
60 To clear an array element, you may use ``bpf_map_update_elem()`` to insert a
106 This snippet shows how to declare an array in a BPF program.
118 This example BPF program shows how to access an array element.
145 This snippet shows how to create an array, using ``bpf_map_create_opts`` to
167 This snippet shows how to initialize the elements of an array.
187 This snippet shows how to retrieve an element value from an array.
232 This snippet shows how to access the per CPU elements of an array value.
259 in userspace, each value is an array with ``ncpus`` elements.
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | extcon-intel-int3496.rst | 6 devices with an acpi-id of INT3496, such as found for example on
12 between an USB host and an USB peripheral controller.
14 The ACPI devices exposes this functionality by returning an array with up
|
| /openbmc/u-boot/arch/arm/mach-meson/ |
| H A D | Kconfig | 26 Select this if your SoC is an S905
32 Select this if your SoC is an S905X/D or S805X
38 Select this if your SoC is an S912
44 Select this if your SoC is an A113X/D
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | overview.rst | 10 This document provides an overview of the Freescale DPAA2 architecture
27 interfaces, an L2 switch, or accelerator instances.
31 The diagram below shows an overview of the DPAA2 resource management
121 A DPRC has a mappable MMIO region (an MC portal) that can be used
122 to send MC commands. It has an interrupt for status events (like
132 DPAA2 Objects for an Ethernet Network Interface
177 Represents an Ethernet MAC, a hardware device that connects to an Ethernet
223 Provides an MC command portal.
266 bus, 2) an address, 3) a data value.
337 - creates an MSI IRQ domain
[all …]
|
| /openbmc/docs/architecture/code-update/ |
| H A D | emmc-storage-design.md | 11 Proposal to define an initial storage design for an eMMC device. This includes
25 - Updatable: Ensure that the filesystem design allows for an effective and
45 partitioning due to the lack of offline tools to build an LVM image (see
50 tool does not currently support building an image of a specified size and
64 by the image, so it is an overlayfs to have the ability to restore its
86 SOCs such as the AST2500 do not support executing U-Boot from an eMMC. In
111 - Filesystem: f2fs (Flash-Friendly File System). The f2fs is an up-and-coming
122 This provides simple code maintenance where an image is intact or not, and
158 moved into an extended partition in a future code update.
197 - Provisioning: Since the LVM userspace tools don't offer an offline mode,
[all …]
|