| /u-boot/arch/arm/dts/ |
| A D | zynqmp-p-a2197-00-revA.dts | 138 reg_vcc_fmc: tps544@7 { /* u80 - FIXME name - don't know what it does */
146 reg_vcc_ram: tps544@8 { /* u83 - FIXME name - don't know what it does */
150 reg_vcc_pslp: tps544@9 { /* u85 - FIXME name - don't know what it does */
154 reg_vcc_psfp: tps544@a { /* u86 - FIXME name - don't know what it does */
195 reg_vccaus: tps544@d { /* u88 - FIXME name - don't know what it does */
203 reg_vcco_500: tps544@f { /* u93 - FIXME name - don't know what it does */
207 reg_vcco_501: tps544@10 { /* u95 - FIXME name - don't know what it does */
211 reg_vcco_502: tps544@11 { /* u97 - FIXME name - don't know what it does */
215 reg_vcco_503: tps544@12 { /* u99 - FIXME name - don't know what it does */
219 reg_vcc1v8: tps544@13 { /* u101 - FIXME name - don't know what it does */
[all …]
|
| /u-boot/examples/standalone/ |
| A D | smc91111_eeprom.c | 37 int c, i, j, done, line, reg, value, start, what; in smc91111_eeprom() local
61 what = UNKNOWN; in smc91111_eeprom()
150 what = EEPROM; in smc91111_eeprom()
153 what = MAC; in smc91111_eeprom()
156 what = UNKNOWN; in smc91111_eeprom()
183 what = UNKNOWN; in smc91111_eeprom()
196 switch (what) { in smc91111_eeprom()
|
| /u-boot/doc/driver-model/ |
| A D | debugging.rst | 8 not doing what you expect.
55 what the driver expects (in the struct udevice_id array).
62 drivers/core/lists.c should show you what is going on.
|
| /u-boot/scripts/ |
| A D | coreboot.sed | 4 # Script to convert coreboot code to something similar to what U-Boot uses
|
| /u-boot/doc/device-tree-bindings/misc/ |
| A D | esm-k3.txt | 5 handling of safety events somewhat similar to what interrupt controller
|
| /u-boot/drivers/usb/mtu3/ |
| A D | Kconfig | 14 If you don't know what this is, please say N.
|
| /u-boot/doc/develop/ |
| A D | logging.rst | 17 But for digging into what is happening in a particular area, or for debugging
18 a problem it is often useful to see what U-Boot is doing in more detail than
154 Filters are attached to log drivers to control what those drivers emit. FIlters
233 Code size impact depends largely on what is enabled. The following numbers are
269 Figure out what to do with BUG(), BUG_ON() and warn_non_spl()
|
| A D | testing.rst | 5 tested and what tests you should write when adding a new feature.
|
| /u-boot/arch/x86/cpu/ |
| A D | u-boot-spl.lds | 52 * The alignment of BSS depends on what is in it, so can range
|
| /u-boot/doc/ |
| A D | README.multi-dtb-fit | 16 The selection is done using board_fit_config_name_match() (same as what the SPL
37 FIT (same as what the SPL uses to select the DTB for U-Boot).
|
| A D | feature-removal-schedule.txt | 2 removed from the U-Boot source tree. Every entry should contain what
|
| A D | README.cfi | 7 * We do not yet know what kind of commandset to use, so we issue
|
| A D | README.LED | 75 TBD : Describe older board dependent macros similar to what is done for
|
| A D | README.mpc83xx.ddrecc | 8 * define inject mask (which tells the DDR controller what type of errors
|
| /u-boot/doc/device-tree-bindings/nand/ |
| A D | nvidia,tegra20-nand.txt | 4 (there isn't yet a generic binding in Linux, so this describes what is in
|
| /u-boot/doc/device-tree-bindings/cpu/ |
| A D | nios2.txt | 3 This binding specifies what properties available in the device tree
|
| /u-boot/scripts/coccinelle/null/ |
| A D | kmerr.cocci | 4 /// in determining what the error handling code for the call to malloc etc
|
| /u-boot/doc/device-tree-bindings/video/ |
| A D | tegra20-dc.txt | 4 (there isn't yet a generic binding in Linux, so this describes what is in
|
| /u-boot/arch/arm/cpu/armv7/ |
| A D | cache_v7_asm.S | 37 cmp r1, #2 @ see what cache we have at this level
107 cmp r1, #2 @ see what cache we have at this level
|
| /u-boot/doc/board/google/ |
| A D | chromebook_samus.rst | 64 You can extract what you need::
|
| /u-boot/ |
| A D | Kconfig | 75 do what it thinks is best, which is desirable in some cases for size
85 do what it thinks is best, which is desirable in some cases for size
95 do what it thinks is best, which is desirable in some cases for size
250 Use this only if you really know what you are doing.
|
| /u-boot/drivers/mmc/ |
| A D | sunxi_mmc.c | 334 uint timeout_msecs, uint done_bit, const char *what) in mmc_rint_wait() argument
343 debug("%s timeout %x\n", what, in mmc_rint_wait()
|
| /u-boot/Licenses/ |
| A D | gpl-2.0.txt | 46 want its recipients to know that what they have is not the original, so
77 Whether that is true depends on what the Program does.
226 This section is intended to make thoroughly clear what is believed to
293 <one line to give the program's name and a brief idea of what it does.>
338 library. If this is what you want to do, use the GNU Lesser General
|
| /u-boot/arch/arm/lib/ |
| A D | div64.S | 150 8: @ Division by a power of 2: determine what that divisor order is
|
| /u-boot/tools/patman/ |
| A D | README | 208 branch against patchwork to see what new reviews your series has
273 keep track of what happened. When you amend a commit, remember
371 your series on patchwork it can show you what new reviews have appears since
381 and patman will show you each patch and what review tags have been collected,
568 to remember what version you are up to, who you sent the last lot of patches
575 compare change and see what you did, you can either create a new branch for
|