| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/panel/ |
| H A D | lvds.yaml | 49 LVDS data mappings are defined as follows.
52 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
63 specifications. Data are transferred as follows on 4 LVDS lanes.
75 Data are transferred as follows on 4 LVDS lanes.
86 Control signals are mapped as follows.
|
| /OK3568_Linux_fs/kernel/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 */
|
| /OK3568_Linux_fs/kernel/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: */
|
| /OK3568_Linux_fs/kernel/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 specicfication as described in the document at https://refspecs.linuxb…
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/soc/bcm/ |
| H A D | brcm,bcm2835-pm.txt | 17 - #reset-cells: Should be 1. This property follows the reset controller
19 - #power-domain-cells: Should be 1. This property follows the power domain
26 system power. This node follows the power controller bindings[3].
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/input/ |
| 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:
|
| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | rcubarrier.rst | 38 context might then be as follows::
44 IRQ context. The function p_callback() might be defined as follows::
85 Pseudo-code using rcu_barrier() is as follows:
104 as follows::
214 The original code for rcu_barrier() was as follows::
240 to post an RCU callback, as follows::
262 reaches zero, as follows::
|
| 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 | listRCU.rst | 78 implementation of ``audit_filter_task()`` might be as follows::
102 This means that RCU can be easily applied to the read side, as follows::
127 might be used as follows for deletion and insertion::
212 if it did, the reader-writer-locked code to do so might look as follows
241 RCU (*read-copy update*) its name. The RCU code is as follows::
305 audit_entry structure, and modify ``audit_filter_task()`` as follows::
336 spinlock as follows::
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | customize-patches.txt | 18 follows:
22 follows:
31 follows:
|
| /OK3568_Linux_fs/kernel/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:
|
| /OK3568_Linux_fs/kernel/arch/powerpc/kernel/ptrace/ |
| H A D | ptrace-tm.c | 80 * The userspace interface buffer layout is as follows.
127 * The userspace interface buffer layout is as follows.
221 * The userspace interface buffer layout is as follows.
265 * FPR registers. The userspace interface buffer layout is as follows.
333 * layout is as follows.
384 * layout is as follows.
462 * The userspace interface buffer layout is as follows.
505 * FPR registers. The userspace interface buffer layout is as follows.
565 * The userspace interface buffer layout is as follows.
607 * The userspace interface buffer layout is as follows.
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/ |
| H A D | locale.h | 88 2 The sign string follows the quantity and currency_symbol.
90 4 The sign string immediately follows the currency_symbol. */
105 2 The sign string follows the quantity and int_curr_symbol.
107 4 The sign string immediately follows the int_curr_symbol. */
|
| /OK3568_Linux_fs/kernel/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::
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/ |
| H A D | locale.h | 88 2 The sign string follows the quantity and currency_symbol.
90 4 The sign string immediately follows the currency_symbol. */
105 2 The sign string follows the quantity and int_curr_symbol.
107 4 The sign string immediately follows the int_curr_symbol. */
|
| /OK3568_Linux_fs/kernel/Documentation/hwmon/ |
| H A D | hwmon-kernel-api.rst | 116 The hwmon_chip_info structure looks as follows::
156 defined as follows::
233 The remaining declarations are as follows.
247 is defined in include/linux/hwmon.h. Definition prefixes are as follows.
266 and return values for those functions are as follows::
377 variable, which is defined as follows::
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/Documentation/kbuild/ |
| H A D | kconfig-macro-language.rst | 14 can write a makefile like follows::
24 and handles as if the source file were input like follows::
156 to make "info" function print " hello", you can write like follows::
241 Instead, you can do like follows so that any function call is statically
|
| /OK3568_Linux_fs/kernel/security/tomoyo/ |
| H A D | util.c | 432 * Check whether the given string follows the naming rules.
433 * Returns true if @string follows the naming rules, false otherwise.
510 * Check whether the given string follows the naming rules.
511 * Returns true if @string follows the naming rules, false otherwise.
519 * tomoyo_correct_path2 - Check whether the given pathname follows the naming rules.
524 * Returns true if @filename follows the naming rules, false otherwise.
539 * Check whether the given pathname follows the naming rules.
540 * Returns true if @filename follows the naming rules, false otherwise.
548 * tomoyo_correct_domain - Check whether the given domainname follows the naming rules.
552 * Returns true if @domainname follows the naming rules, false otherwise.
|
| /OK3568_Linux_fs/kernel/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 90 65,536 CPUs, RCU would configure the ``rcu_node`` tree as follows:
152 The general role of each of these data structures is as follows:
209 This portion of the ``rcu_state`` structure is declared as follows:
268 This portion of the ``rcu_state`` structure is declared as follows:
292 This portion of the ``rcu_state`` structure is declared as follows:
329 This portion of the ``rcu_node`` structure is declared as follows:
362 This field of the ``rcu_node`` structure is declared as follows:
379 This portion of the ``rcu_node`` structure is declared as follows:
421 This portion of the ``rcu_node`` structure has fields as follows:
542 expressions as follows:
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v1/ |
| H A D | README.md | 100 follows GlobalPlatform standards. The exceptions are as follows:
116 the Linux kernel is at `$HOME/devel/linux`, then you have to export like follows:
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/gpio/ |
| H A D | board.rst | 145 A lookup table can then be defined as follows, with an empty entry defining its
163 And the table can be added by the board code as follows::
167 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows::
195 And the table can be added to the board code as follows::
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Writing-an-Xmethod.html | 103 defined as follows:
157 above is as follows:
184 <small>GDB</small> globally as follows:
191 code as follows:
233 of the xmethod workers and xmethod matchers is as follows:
|