| /openbmc/linux/Documentation/input/devices/ |
| H A D | xpad.rst | 25 - if you are using a known controller
26 - if you are using a known dance pad
27 - if using an unknown device (one not listed below), what you set in the
31 If you set dpad_to_buttons to N and you are using an unknown device
66 When using a known dance pad, jstest will report 6 axes and 14 buttons.
76 If your dance pad is recognized by the driver but is using axes instead
194 If you're using a normal controller, there should be a single line showing
196 the sticks and push the buttons. If you're using a dance pad, it should
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | sync_file.rst | 19 driver that issued the fence is not using/processing the buffer anymore, so it
36 dma_fence_signal(), when it has finished using (or processing) that buffer.
41 we need to wait for the fence(s) to signal before using any buffer related to
81 afterwards using dma_fence_put(). In case of error, a NULL is returned instead.
|
| H A D | reset.rst | 98 Note that since multiple consumers may be using a shared reset control, there
101 Consumer drivers using shared reset controls should assume that the reset line
138 For this, reset controls can be requested as optional using
181 Reset consumers can control a reset line using an opaque reset control handle,
185 reset_control_deassert(), trigger a reset pulse using reset_control_reset(), or
186 query the reset line status using reset_control_status().
210 a struct :c:type:`reset_controller_dev`, and register it using
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | GPL-3.0-with-GCC-exception | 16 …later version) of the GNU General Public License (GPL) with the option of using any subsequent ver…
20 … it is done using GCC, alone or with other GPL-compatible software, or if it is done without using…
|
| H A D | CNRI-Python | 7 …, and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6, beta 1…
11 …using the following unique, persistent identifier (known as a handle): 1895.22/1011. This Agreemen…
23 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using…
|
| /openbmc/qemu/docs/devel/ |
| H A D | multiple-iothreads.txt | 12 QEMU is an event-driven program that can do several things at once using an
18 possible to create additional event loop threads using -object
84 The AioContext can be obtained from the IOThread using
85 iothread_get_aio_context() or for the main loop using qemu_get_aio_context().
91 AioContext is not thread-safe so some rules must be followed when using file
119 is associated with an AioContext using bdrv_try_change_aio_context() and
123 Block layer code must therefore expect to run in an IOThread and avoid using
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | virt.rst | 40 - running guests using the KVM accelerator on aarch64 hardware
41 - large amounts of RAM (at least 255GB, and more if using highmem)
42 - many CPUs (up to 512 if using a GICv3 and highmem)
129 Use the same GIC version the host provides, when using KVM
131 Use the best GIC version possible (same as host when using KVM;
149 using ACPI and guest external abort exceptions. The default is off.
202 - For guests using the Linux kernel boot protocol (this means any
|
| /openbmc/linux/Documentation/mm/ |
| H A D | zsmalloc.rst | 14 and links them together using various 'struct page' fields. These linked
30 is very small. So, before using the allocating memory, the object has to
31 be mapped using zs_map_object() to get a usable pointer and subsequently
32 unmapped using zs_unmap_object().
117 need to store an object of size, say, 1568 bytes, we end up using size class
138 objects of size 1568 in a single zspage, using a total of 5 physical pages.
255 Using larger zspage chains may result in using fewer physical pages, as seen
|
| /openbmc/u-boot/board/lego/ev3/ |
| H A D | README | 47 mode. The image can then be uploaded using the official LEGO MINDSTORMS EV3
51 to the flash. If you are not using a microSD card, you will need to create an
52 image file using the layout described above.
|
| /openbmc/phosphor-pid-control/ |
| H A D | ipmi.md | 6 to the BMC from the host, by using the IPMI SDR as shared storage.
36 | `01` | `command` | `0x04 (also using manual command)` |
62 | `01` | `command` | `0x04 (also using manual command)` |
|
| /openbmc/linux/Documentation/devicetree/bindings/watchdog/ |
| H A D | aspeed-wdt.txt | 53 single word defined using the AST2500_WDT_RESET_* macros;
55 word defined using the AST2600_WDT_RESET1_* macros and the
56 second word defined using the AST2600_WDT_RESET2_* macros.
|
| /openbmc/linux/drivers/mtd/nand/onenand/ |
| H A D | Kconfig | 40 (using command mapping method) and S5PC110/S5PC210 (using generic
51 The OTP block can be read, programmed and locked using the same
|
| /openbmc/linux/drivers/pps/clients/ |
| H A D | Kconfig | 32 tristate "PPS client using GPIO"
34 If you say yes here you get support for a PPS source using
|
| /openbmc/openbmc/meta-aspeed/ |
| H A D | README.md | 19 meta-aspeed patches are reviewed using the Gerrit instance at
22 Please submit patches to Gerrit. More information on using Gerrit can be found
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | rule.md | 9 For example, the following action sequences might be sharable using a rule:
13 - Actions that detect down-level hardware using version registers
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/dibbler/ |
| H A D | dibbler_git.bb | 13 file://0001-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
|
| /openbmc/openbmc/poky/meta/recipes-multimedia/gstreamer/gst-devtools/ |
| H A D | 0001-connect-has-a-different-signature-on-musl.patch | 6 On linux when not using glibc and using musl for C library, connect
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 182.out | 5 Starting a second QEMU using the same image should fail
7 Is another process using the image [TEST_DIR/t.qcow2]?
|
| /openbmc/linux/sound/soc/sof/mediatek/ |
| H A D | Kconfig | 31 using the mt8186 processors.
41 using the mt8195 processors.
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-consumer-common.yaml | 14 Pay attention to using proper GPIO flag (e.g. GPIO_ACTIVE_LOW) for the GPIOs
15 using inverted signal (e.g. RESETN).
|
| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A D | consumer.rst | 52 If a function is implemented by using several GPIOs together (e.g. a simple LED
159 A GPIO descriptor can be disposed of using the gpiod_put() function::
168 It is also not allowed to individually release descriptors (using gpiod_put())
235 Some GPIO controllers must be accessed using message based buses like I2C or
318 The active low state of a GPIO can also be queried and toggled using the
380 The descriptor array can be obtained using the gpiod_get_array() function
390 descriptors may be obtained using any combination of gpiod_get() and
415 corresponding to a given GPIO using the following call::
421 unchecked error to use a GPIO that wasn't set up as an input using
452 Many kernel subsystems and drivers still handle GPIOs using the legacy
[all …]
|
| /openbmc/u-boot/doc/imx/habv4/guides/ |
| H A D | mx6_mx7_secure_boot.txt | 2 + i.MX6, i.MX7 U-Boot Secure Boot guide using HABv4 +
160 - Program SRK_HASH[255:0] fuses, using i.MX6 series as example:
224 signed using the correct PKI tree.
226 - Program SEC_CONFIG[1] fuse, using i.MX6 series as example:
249 - Program SRK_LOCK, using i.MX6 series as example:
253 - Program DIR_BT_DIS, using i.MX6 series as example:
257 - Program SJC_DISABLE, using i.MX6 series as example:
261 - JTAG_SMODE, using i.MX6 series as example:
401 [1] AN4581: "Secure Boot on i.MX 50, i.MX 53, i.MX 6 and i.MX 7 Series using
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | platform.rst | 40 and shutdown notifications using the standard conventions::
106 will often provide additional information using the device's platform_data
134 tend to already have "normal" modes, such as ones using device nodes that
138 using these calls except with such hotplug-deficient drivers::
179 - When a driver is registered using platform_driver_register(), all
183 - Registering a driver using platform_driver_probe() works just like
184 using platform_driver_register(), except that the driver won't
199 The architecture code registers platform device data using the function
218 platform drivers belonging to a certain class using the function
|
| /openbmc/u-boot/doc/ |
| H A D | README.commands | 5 This is done by first including command.h, then using the U_BOOT_CMD() or the
34 Likewise an array of cmd_tbl_t holding sub-commands can be created using either
119 the linker in a special section using the linker lists mechanism
124 command array can be iterated over using the linker lists macros.
|
| /openbmc/qemu/docs/ |
| H A D | memory-hotplug.txt | 33 hotplugged by using any combination of the available memory slots.
50 Besides basic RAM hotplug, QEMU also supports using files as a memory
51 backend. This is useful for using hugetlbfs in Linux, which provides
63 but this allows for a lot of flexibility when using the file backend.
|