| /openbmc/linux/drivers/staging/greybus/ |
| H A D | Kconfig | 8 Select this option if you have a device that follows the
29 Select this option if you have a device that follows the
39 Select this option if you have a device that follows the
49 Select this option if you have a device that follows the
59 Select this option if you have a device that follows the
69 Select this option if you have a device that follows the
78 Select this option if you have a device that follows the
87 Select this option if you have a device that follows the
97 Select this option if you have a device that follows the
106 Select this option if you have a device that follows the
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lvgl/files/ |
| H A D | 0006-Add-SDL2-example-support.patch | 10 To use legacy fbdev support, adjust lv_conf.h as follows:
15 To use DRM/KMS support, adjust lv_conf.h as follows:
20 To use SDL2 support, adjust lv_conf.h as follows:
|
| H A D | 0005-Add-DRM-KMS-example-support.patch | 8 To use legacy fbdev support, adjust lv_conf.h as follows:
12 To use DRM/KMS support, adjust lv_conf.h as follows:
|
| /openbmc/linux/Documentation/devicetree/bindings/scsi/ |
| H A D | hisilicon-sas.txt | 6 - compatible : value should be as follows:
22 sources; the interrupts are ordered in 3 groups, as follows:
35 Fatal interrupts : the fatal interrupts are ordered as follows:
39 the interrupts are ordered in 3 groups, as follows:
|
| /openbmc/qemu/docs/system/ |
| H A D | multi-process.rst | 43 - Example command-line for the remote process is as follows:
55 memory-backend-memfd is required to facilitate this, as follows:
64 - Example commandline for QEMU is as follows:
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | lockdep-splat.rst | 68 Line 2776 of block/cfq-iosched.c in v3.0-rc5 is as follows::
78 which would permit us to invoke rcu_dereference_protected as follows::
93 add rcu_read_lock() and rcu_read_unlock() as follows::
110 by rcu_access_pointer() as follows::
|
| H A D | rcuref.rst | 52 in this scenario as follows:
89 as follows:
140 delete(), so that el_free() can be subsumed into delete as follows::
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | sodaville.txt | 13 The interrupt specifier consists of two cells encoded as follows:
15 - <2nd cell>: The level-sense information, encoded as follows:
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | code_update.md | 12 https://jenkins.openbmc.org/job/latest-master/ and run as follows:
29 https://openpower.xyz/job/openpower-op-build/ and run as follows:
54 https://jenkins.openbmc.org/job/latest-master/ and run as follows:
64 https://openpower.xyz/job/openpower-op-build/ and run as follows:
76 https://jenkins.openbmc.org/job/latest-master/ and run as follows:
86 https://openpower.xyz/job/openpower-op-build/ and run as follows:
|
| /openbmc/u-boot/doc/device-tree-bindings/nand/ |
| H A D | nvidia,tegra20-nand.txt | 9 The device node for a NAND flash device is as follows:
20 The device node for a NAND flash controller is as follows:
|
| /openbmc/u-boot/doc/device-tree-bindings/adc/ |
| H A D | adc.txt | 42 For the above PMIC, the node can be defined as follows:
54 For the above ADC, the node can be defined as follows:
|
| /openbmc/linux/Documentation/pcmcia/ |
| H A D | locking.rst | 69 The "main" struct pcmcia_socket is protected as follows (read-only fields
112 The "main" struct pcmcia_device is protected as follows (read-only fields
|
| /openbmc/qemu/tests/qapi-schema/ |
| H A D | doc-interleaved-section.err | 1 doc-interleaved-section.json:15:1: description of '@foobar:' follows a section
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | jitdump-specification.txt | 48 The flags currently defined are as follows:
53 …ollowed by records. Each record starts with a fixed size header describing the record that follows.
55 The record header is specified in order as follows:
126 The debug_entry describes the source line information. It is defined as follows in order:
164 The EH Frame header follows the Linux Standard Base (LSB) specification as described in the documen…
167 The EH Frame follows the LSB specification as described in the document at https://refspecs.linuxba…
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | s390.rst | 36 Once on Debian, the build prerequisites can be installed as follows::
62 Latest Clang targeting BPF can be installed as follows::
130 The virtual machine can be started as follows::
153 need to be mounted as follows::
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | remoteproc-framework.txt | 40 Overall, the driver statemachine transitions are typically as follows:
82 The driver follows a standard UCLASS DM.
122 a simplified definition of a device is as follows:
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | blocks.rst | 17 For 32-bit filesystems, limits are as follows:
79 For 64-bit filesystems, limits are as follows:
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A D | pops-clicks.rst | 23 shutdown and follows some basic rules:-
38 ADC until all the pops have occurred. This follows similar power rules to
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | x32-psabi.rst | 27 follows:
42 configuration file as follows::
|
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/leds/ |
| H A D | phosphor-led-manager_%.bbappend | 10 # Harma power led is follows the host status.
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | control-dependencies.txt | 23 as follows:
50 the original example by eliminating the "if" statement as follows:
60 identical stores on both branches of the "if" statement as follows:
73 Unfortunately, current compilers will transform this as follows at high
146 make sure that MAX is greater than one, perhaps as follows:
171 always true, the compiler can transform this example as follows, again
|
| /openbmc/docs/architecture/ |
| H A D | redfish-logging-in-bmcweb.md | 27 If an appropriate message does not exist, new messages can be added as follows:
83 be logged to the journal as follows:
133 this message can be logged to the journal as follows:
|
| /openbmc/u-boot/board/Barix/ipam390/ |
| H A D | ipam390-ais-uart.cfg | 34 ; the input args is as follows:
45 ; is as follows:
157 ; the input args is as follows:
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | vduse.rst | 23 VDUSE devices are created as follows:
36 VDUSE devices are destroyed as follows:
109 module as follows:
155 able to start the dataplane processing as follows:
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ti/ |
| H A D | mux.txt | 15 results in programming the register as follows:
24 "index-starts-at-one" modified the scheme as follows:
|