| /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/linux/Documentation/devicetree/bindings/display/ |
| H A D | lvds.yaml | 38 LVDS data mappings are defined as follows.
41 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
52 specifications. Data are transferred as follows on 4 LVDS lanes.
64 Data are transferred as follows on 4 LVDS lanes.
75 Control signals are mapped as follows.
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | sigframe.h | 38 /* fp state follows here */
53 /* fp state follows here */
63 /* fp state follows here */
81 /* fp state follows here */
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | EventDestination.v1_15_1.json | 469 "Kafka": "The destination follows the Kafka protocol for event notifications.",
470 "OEM": "The destination follows an OEM protocol for event notifications.",
471 … "Redfish": "The destination follows the Redfish Specification for event notifications.",
472 "SMTP": "The destination follows the SMTP specification for event notifications.",
473 "SNMPv1": "The destination follows the SNMPv1 protocol for event notifications.",
474 "SNMPv2c": "The destination follows the SNMPv2c protocol for event notifications.",
475 "SNMPv3": "The destination follows the SNMPv3 protocol for event notifications.",
476 "SyslogRELP": "The destination follows syslog RELP for event notifications.",
477 … "SyslogTCP": "The destination follows syslog TCP-based transport for event notifications.",
478 … "SyslogTLS": "The destination follows syslog TLS-based transport for event notifications.",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | EventDestination.v1_15_1.json | 469 "Kafka": "The destination follows the Kafka protocol for event notifications.",
470 "OEM": "The destination follows an OEM protocol for event notifications.",
471 … "Redfish": "The destination follows the Redfish Specification for event notifications.",
472 "SMTP": "The destination follows the SMTP specification for event notifications.",
473 "SNMPv1": "The destination follows the SNMPv1 protocol for event notifications.",
474 "SNMPv2c": "The destination follows the SNMPv2c protocol for event notifications.",
475 "SNMPv3": "The destination follows the SNMPv3 protocol for event notifications.",
476 "SyslogRELP": "The destination follows syslog RELP for event notifications.",
477 … "SyslogTCP": "The destination follows syslog TCP-based transport for event notifications.",
478 … "SyslogTLS": "The destination follows syslog TLS-based transport for event notifications.",
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | iqs626a.yaml | 42 Specifies the power mode during suspend as follows:
64 updated during ultra-low-power mode as follows:
88 represents touch state as follows:
104 long-term average) of an associated channel as follows:
199 Specifies how inactive CRX pins are to be terminated as follows:
226 Specifies the channel's ATI mode as follows:
269 sensing as follows:
281 Specifies the channel's sensing frequency as follows (parenthesized
364 Specifies the capacitance to be added to the channel as follows:
377 Specifies the channel's sensing mode as follows:
[all …]
|
| H A D | iqs269a.yaml | 47 Specifies the power mode during suspend as follows:
172 Specifies the inductive sensing excitation frequency as follows (paren-
189 long-term average) of an associated channel as follows:
274 Specifies the capacitance to be added to the channel as follows:
291 sensing as follows:
302 Specifies the channel's sensing mode as follows:
314 Specifies the channel's sensing frequency as follows (parenthesized
330 Specifies the channel's ATI mode 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/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/drivers/gpu/drm/gma500/ |
| H A D | oaktrail.h | 77 u16 Panel_Backlight_Inverter_Descriptor;/* 16 bits, as follows */
81 /*16 bits, Defined as follows: */
106 u16 Panel_Backlight_Inverter_Descriptor;/*16 bits, as follows*/
111 /*16 bits, Defined as follows: */
147 union { /*8 bits,Defined as follows: */
164 union { /*8 bits,Defined as follows: */
|
| /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:
|
| /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/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/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 | rcubarrier.rst | 13 as follows::
19 IRQ context. The function p_callback() might be defined as follows::
61 Pseudo-code using rcu_barrier() is as follows:
83 in its exit function as follows::
194 The original code for rcu_barrier() was roughly as follows::
233 to post an RCU callback, as follows::
255 reaches zero, as follows::
|
| /openbmc/linux/include/linux/sunrpc/ |
| H A D | rpc_rdma.h | 135 * Pointer to the XDR position that follows the encoded RDMA segment
154 * Pointer to the XDR position that follows the encoded Read segment
172 * Pointer to the XDR item that follows the RDMA segment
191 * Pointer to the XDR item that follows the Read segment
|
| /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/linux/arch/powerpc/kernel/ptrace/ |
| H A D | ptrace-tm.c | 80 * The userspace interface buffer layout is as follows.
128 * The userspace interface buffer layout is as follows.
222 * The userspace interface buffer layout is as follows.
266 * FPR registers. The userspace interface buffer layout is as follows.
334 * layout is as follows.
385 * layout is as follows.
463 * The userspace interface buffer layout is as follows.
506 * FPR registers. The userspace interface buffer layout is as follows.
566 * The userspace interface buffer layout is as follows.
608 * The userspace interface buffer layout is as follows.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | hwmon-kernel-api.rst | 106 The hwmon_chip_info structure looks as follows::
146 defined as follows::
223 The remaining declarations are as follows.
237 is defined in include/linux/hwmon.h. Definition prefixes are as follows.
256 and return values for those functions are as follows::
365 variable, which is defined 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/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/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/linux/arch/loongarch/kernel/ |
| H A D | mcount_dyn.S | 14 * are as follows:
18 * modules trampoline is as follows:
26 * follows the LoongArch's psABI as well.
|
| /openbmc/linux/drivers/clk/sunxi/ |
| H A D | clk-sun9i-core.c | 19 * PLL4 rate is calculated as follows
95 * GT rate is calculated as follows
150 * AHB rate is calculated as follows
230 * APB1 rate is calculated 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:
|