| /rk3399_rockchip-uboot/doc/ |
| H A D | README.fec_mxc | 27 Optional, selects the exact phy address that should be connected
|
| H A D | README.power-framework | 114 how they handle the exact charging. Trats uses polling (MAX8997) and trats2
|
| H A D | README.fdt-control | 14 with the exact configuration of each board controlled by a flat device
|
| H A D | README.drivers.eth | 101 The exact arguments needed to initialize your device are up to you. If you
|
| H A D | README.pxe | 28 held in memory at once. The exact number and size of the files varies with
|
| H A D | README.ti-secure | 185 The exact details of the how the images are secured is handled by the
|
| /rk3399_rockchip-uboot/board/toradex/common/ |
| H A D | Kconfig | 11 address is generated) and the exact module type.
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/pwm/ |
| H A D | pwm.txt | 16 PWM properties should be named "pwms". The exact meaning of each pwms
|
| /rk3399_rockchip-uboot/fs/ubifs/ |
| H A D | tnc.c | 1174 int err, exact; in ubifs_lookup_level0() local 1193 exact = ubifs_search_zbranch(c, znode, key, n); in ubifs_lookup_level0() 1215 if (exact || !is_hash_key(c, key) || *n != -1) { in ubifs_lookup_level0() 1216 dbg_tnc("found %d, lvl %d, n %d", exact, znode->level, *n); in ubifs_lookup_level0() 1217 return exact; in ubifs_lookup_level0() 1310 int err, exact; in lookup_level0_dirty() local 1332 exact = ubifs_search_zbranch(c, znode, key, n); in lookup_level0_dirty() 1359 if (exact || !is_hash_key(c, key) || *n != -1) { in lookup_level0_dirty() 1360 dbg_tnc("found %d, lvl %d, n %d", exact, znode->level, *n); in lookup_level0_dirty() 1361 return exact; in lookup_level0_dirty()
|
| /rk3399_rockchip-uboot/board/davinci/da8xxevm/ |
| H A D | README.da850 | 9 depending on the exact board and pin configurations will initialize another 30 The exact build target you need will depend on the board you have. For
|
| /rk3399_rockchip-uboot/lib/ |
| H A D | slre.c | 195 exact(struct slre *r, const char **re) in exact() function 406 exact(r, re); in compile()
|
| /rk3399_rockchip-uboot/drivers/video/ |
| H A D | Kconfig | 328 anything in the 8MHz-30MHz range and the exact value should be 357 working LCD configuration. The exact role of SPI may differ for 367 working LCD configuration. The exact role of SPI may differ for 377 working LCD configuration. The exact role of SPI may differ for 387 working LCD configuration. The exact role of SPI may differ for
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | remoteproc-framework.txt | 68 NOTE: It depends on the remote processor as to the exact behavior
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/gpio/ |
| H A D | gpio.txt | 27 The exact purpose of each gpios property must be documented in the device tree 77 value at the device. The exact definition of logically asserted should be
|
| /rk3399_rockchip-uboot/arch/arm/cpu/armv8/ |
| H A D | Kconfig | 131 System with multi-cluster should difine their own exact value.
|
| /rk3399_rockchip-uboot/board/Barix/ipam390/ |
| H A D | README.ipam390 | 8 depending on the exact board and pin configurations will initialize another
|
| /rk3399_rockchip-uboot/arch/x86/dts/microcode/ |
| H A D | m0220661105_cv.dtsi | 15 * which is a reversible, bit-exact translation of binary representation to ASCII or
|
| H A D | m12206a7_00000029.dtsi | 15 * which is a reversible, bit-exact translation of binary representation to ASCII or
|
| H A D | m12306a9_0000001b.dtsi | 15 * which is a reversible, bit-exact translation of binary representation to ASCII or
|
| H A D | mc0306d4_00000018.dtsi | 15 * which is a reversible, bit-exact translation of binary representation to ASCII or
|
| /rk3399_rockchip-uboot/common/ |
| H A D | dlmalloc.src | 2049 (All fits are considered `exact' if they are within MINSIZE bytes.) 2058 the absence of exact fits. Runs of consecutive requests use 2126 /* Check for exact match in a bin */ 2171 else if (remainder_size >= 0) /* exact fit */
|
| /rk3399_rockchip-uboot/doc/uImage.FIT/ |
| H A D | beaglebone_vboot.txt | 20 for them to use the exact same binary from the same place. More typically,
|
| /rk3399_rockchip-uboot/arch/x86/ |
| H A D | Kconfig | 668 which in turns forms a table of exact 4KiB. The default value 128
|
| /rk3399_rockchip-uboot/tools/buildman/ |
| H A D | README | 123 behaviour is a superset of exact or substring matching. Examples are: 201 This tells buildman that you want to use this exact toolchain for the arm
|
| /rk3399_rockchip-uboot/arch/arm/dts/ |
| H A D | dra7.dtsi | 365 * the data manual for the exact part number in use
|