Searched refs:sequence (Results 1 – 25 of 81) sorted by relevance
1234
/u-boot/doc/device-tree-bindings/video/ |
A D | intel-gma.txt | 15 - intel,panel-power-cycle-delay : T4 time sequence (6 = 500ms) 18 - intel,panel-power-up-delay : T1+T2 time sequence 19 - intel,panel-power-down-delay : T3 time sequence 20 - intel,panel-power-backlight-on-delay : T5 time sequence 21 - intel,panel-power-backlight-off-delay : Tx time sequence
|
/u-boot/lib/zstd/ |
A D | decompress.c | 875 size_t const sequenceLength = sequence.litLength + sequence.matchLength; in ZSTD_execSequenceLast7() 913 sequence.matchLength -= length1; in ZSTD_execSequenceLast7() 1002 size_t const sequenceLength = sequence.litLength + sequence.matchLength; in ZSTD_execSequence() 1018 if (sequence.litLength > 8) in ZSTD_execSequence() 1039 sequence.matchLength -= length1; in ZSTD_execSequence() 1052 if (sequence.offset < 8) { in ZSTD_execSequence() 1258 size_t const sequenceLength = sequence.litLength + sequence.matchLength; in ZSTD_execSequenceLong() 1274 if (sequence.litLength > 8) in ZSTD_execSequenceLong() 1294 sequence.matchLength -= length1; in ZSTD_execSequenceLong() 1307 if (sequence.offset < 8) { in ZSTD_execSequenceLong() [all …]
|
/u-boot/tools/buildman/ |
A D | test.py | 120 sequence = 0 126 if sequence < 6: 128 comm.sequence = sequence 129 sequence += 1 167 if ((boardnum >= 1 and boardnum >= commit.sequence) or 168 boardnum == 4 and commit.sequence == 6): 172 elif commit.sequence < 6:
|
/u-boot/doc/ |
A D | I2C_Edge_Conditions | 25 The device will interpret this sequence as a WRITE command and 39 the I2C bus reset sequence.
|
A D | README.autoboot | 68 entered before the specified time the boot delay sequence is 130 sequence to be interrupted by ctrl-c, in addition to the 132 provides an escape sequence from the limited "password"
|
A D | README.cfi | 18 Some flash chips seem to have trouble with this reset sequence.
|
A D | README.splashprepare | 6 sequence. It gives the board an opportunity to prepare the splash
|
A D | README.arm-caches | 49 - The following sequence is advisable while disabling d-cache:
|
/u-boot/lib/crypto/ |
A D | pkcs7.asn1 | 79 -- sequence of attributes and then reuse encoded 80 -- sequence in aaSequence.
|
/u-boot/doc/device-tree-bindings/i2c/ |
A D | i2c-gpio.txt | 20 Run deblocking sequence when the driver gets probed.
|
/u-boot/doc/device-tree-bindings/adc/ |
A D | st,stm32-adc.txt | 15 own configurable sequence and trigger: 16 - regular conversion can be done in sequence, running in background 18 interrupt regular conversion sequence (either triggered in SW or HW). 19 Regular sequence is resumed, in case it has been interrupted.
|
/u-boot/doc/usage/ |
A D | bootefi.rst | 30 sequence to: 36 command sequence to run a UEFI application might look like 66 *BootOrder* specifies in which sequence boot options shalled be tried.
|
A D | loady.rst | 35 After entering the loady command the key sequence <CTRL-A><CTRL-S> is used to
|
/u-boot/fs/btrfs/ |
A D | conv-funcs.h | 140 nlink, uid, gid, mode, rdev, flags, sequence, atime, ctime, mtime, 148 DEFINE_CONV(btrfs_root_ref, dirid, sequence, name_len)
|
/u-boot/net/ |
A D | ping.c | 35 icmp->un.echo.sequence = htons(ping_seq_number++); in set_icmp_header()
|
/u-boot/doc/api/ |
A D | efi.rst | 30 The UEFI specification foresees to define boot entries and boot sequence via UEFI 41 * BootOrder specifies in which sequence the boot options shall be tried if
|
/u-boot/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
A D | README.lsch3 | 157 command sequence. Below is one example for PBI commands for LS2085AQDS which 210 PBI command sequence. Below is one example for PBI commands for RDB 329 more deployed during u-boot boot-sequence. 337 1. Command sequence for u-boot ethernet: 349 2. Command sequence for Linux boot: 365 3. Command sequence for AIOP boot:
|
A D | README.qspi | 18 command sequence for setting the boot location pointer. It's should point
|
/u-boot/board/freescale/mpc8323erdb/ |
A D | README | 40 which is a shorter version of the manual sequence:
|
/u-boot/doc/device-tree-bindings/remoteproc/ |
A D | k3-rproc.txt | 6 remoteproc driver should communicate to SYSFW with a specific sequence.
|
/u-boot/arch/arm/mach-sunxi/ |
A D | rmr_switch.S | 2 @ ARMv8 RMR reset sequence on Allwinner SoCs.
|
/u-boot/doc/board/toradex/ |
A D | verdin-imx8mm.rst | 73 Boot sequence is:
|
/u-boot/board/technexion/pico-imx7d/ |
A D | README.pico-imx7d_BL33 | 3 The boot sequence is ATF -> OPTEE -> U-Boot -> Linux. U-Boot is in non-secure
|
/u-boot/doc/SPL/ |
A D | README.omap3 | 13 On these platforms the ROM supports trying a sequence of boot devices. Once
|
/u-boot/doc/android/ |
A D | boot-image.rst | 96 Then next command sequence can be used to boot Android: 125 This sequence should be used for Android 10 boot. Of course, the whole Android
|
Completed in 18 milliseconds
1234