Searched refs:references (Results 1 – 10 of 10) sorted by relevance
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.ARM-memory-map | 7 >I still see references to _armboot_start, _armboot_end_data, and
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/adc/ |
| H A D | adc.txt | 31 Example of supply phandle usage, for the ADC's VDD/VSS references as below:
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/ |
| H A D | chosen.txt | 56 in the order they are listed: references (i.e. implicit paths), a full
|
| /rk3399_rockchip-uboot/fs/ubifs/ |
| H A D | debug.c | 1810 int references; member
2130 fscki->references += 1; in check_leaf()
2209 fscki->references != 1) { in check_inodes()
2212 fscki->references); in check_inodes()
2216 fscki->references != 0) { in check_inodes()
2219 fscki->references); in check_inodes()
2235 if (fscki->references != fscki->nlink) { in check_inodes()
2238 fscki->nlink, fscki->references); in check_inodes()
|
| /rk3399_rockchip-uboot/Licenses/ |
| H A D | README | 44 If a "SPDX-License-Identifier:" line references more than one Unique
|
| /rk3399_rockchip-uboot/arch/arm/dts/ |
| H A D | tegra186.dtsi | 319 * In theory, these references, and the configuration in the
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 91 | changes made to the device tree either, its references |
|
| H A D | README.txt | 498 More commonly you can use node references, which expand to the full path:
|
| /rk3399_rockchip-uboot/ |
| H A D | Kconfig | 441 This option currently references CONFIG_CONS_INDEX, which is
|
| H A D | README | 5199 information and associated file and directory references.
|