/u-boot/tools/ |
A D | gpimage-common.c | 32 int gph_verify_header(struct gp_header *gph, int be) in gph_verify_header() argument 37 if (be) in gph_verify_header() 46 void gph_print_header(const struct gp_header *gph, int be) in gph_print_header() argument 50 if (be) in gph_print_header() 67 int be) in gph_set_header() argument 71 if (be) in gph_set_header()
|
A D | gpheader.h | 34 int gph_verify_header(struct gp_header *gph, int be); 35 void gph_print_header(const struct gp_header *gph, int be); 37 int be);
|
/u-boot/doc/ |
A D | README.POST | 28 2) The results of tests shall be saved so that it will be possible to 135 argument) will be executed. This routine will be called at least 171 be as follows: 287 A new command, diag, will be added to U-Boot. This command will be 530 be used: 582 scenarios will be used: 668 section "Hazardous tests") will be used. Namely, this test will be 680 features will be verified: 707 packets will be transmitted. These tests may be enhanced in future to 719 will be transmitted. These tests may be enhanced to make to perform [all …]
|
A D | README.watchdog | 4 This enables hw_watchdog_reset to be called during various loops, 9 new code, so it must be serviced, but the board would rather it 10 was off. And, it cannot always be turned off once on. 13 Can be used to change the timeout for i.mx31/35/5x/6x. 15 be 128000 msec for i.mx31/35/5x/6x. 24 Can be used to change the timeout for FTWDT010. 30 TODO: vision2 is removed now, so perhaps this can be changed.
|
A D | README.plan9 | 3 confaddr must be defined with the same value as CONFADDR (see mem.h). 4 Use of this facility is optional, but should be preferable to manual 7 When booting an image, arguments supplied to the bootm command will be 9 bootargs environment variable will be copied. 13 configuration could be simulated by issuing a fatload in bootcmd:
|
A D | README.serial_multi | 7 At the moment, the ports must be split on a SMC and a SCC port on a 17 *) The console can be switched to SCC by any of the following commands: 23 *) The console can be switched to SMC by any of the following commands: 30 will be used which, in turn, can be switched by above commands. 32 *) The baudrate is the same for all serial devices. But it can be switched 46 *) The console can be switched to UART1 by any of the following commands: 51 *) The console can be switched to UART0 by any of the following commands:
|
A D | README.silent | 1 The config option CONFIG_SILENT_CONSOLE can be used to quiet messages 2 on the console. If the option has been enabled, the output can be 16 - Until the console devices have been initialized, output has to be 25 the argument "console=" will be in the command line, no matter how 27 line to be affected, define CONFIG_SILENT_U_BOOT_ONLY in your board 28 config file as well, and this part of the feature will be disabled.
|
/u-boot/doc/device-tree-bindings/serial/ |
A D | omap_serial.txt | 4 - compatible : should be "ti,omap2-uart" for OMAP2 controllers 5 - compatible : should be "ti,omap3-uart" for OMAP3 controllers 6 - compatible : should be "ti,omap4-uart" for OMAP4 controllers 7 - compatible : should be "ti,am4372-uart" for AM437x controllers 8 - compatible : should be "ti,am3352-uart" for AM335x controllers 9 - compatible : should be "ti,dra742-uart" for DRA7x controllers 15 - ti,hwmods : Must be "uart<n>", n being the instance number (1-based)
|
/u-boot/arch/x86/include/asm/arch-apollolake/acpi/ |
A D | soc_int.asl | 10 #define SDCARD_INT 3 /* Need to be shared by PMC and SCC only*/ 11 #define UART0_INT 4 /* Need to be shared by PMC and SCC only*/ 12 #define UART1_INT 5 /* Need to be shared by PMC and SCC only*/ 13 #define UART2_INT 6 /* Need to be shared by PMC and SCC only*/ 14 #define UART3_INT 7 /* Need to be shared by PMC and SCC only*/ 15 #define XDCI_INT 13 /* Need to be shared by PMC and SCC only*/ 24 #define XHCI_INT 17 /* Need to be shared by PMC and SCC only*/
|
/u-boot/doc/android/ |
A D | ab.rst | 12 partitions in the unused slot can be updated [1]_. 17 The A/B updates support can be activated by specifying next options in 23 The disk space on target device must be partitioned in a way so that each 24 partition which needs to be updated has two or more instances. The name of 25 each instance must be formed by adding suffixes: ``_a``, ``_b``, ``_c``, etc. 31 special partition (e.g. ``misc``) and determines which slot should be used for 54 Based on this slot information, the current boot partition should be defined, 55 and next kernel command line parameters should be generated: 66 the default A/B metadata will be created and written to ``misc`` partition.
|
/u-boot/include/configs/ |
A D | bcm_ep_board.h | 18 #error CONFIG_SYS_TEXT_BASE must be defined! 21 #error CONFIG_SYS_SDRAM_BASE must be defined! 24 #error CONFIG_SYS_SDRAM_SIZE must be defined!
|
/u-boot/doc/device-tree-bindings/power/ |
A D | ti,sci-pm-domain.txt | 14 this relies on the TI SCI protocol to communicate with the SYSFW it must be a 19 - compatible: Must be "ti,sci-pm-domain" 20 - #power-domain-cells: Can be one of the following: 22 2: First entry should be device id 23 Second entry should be one of the floowing: 24 TI_SCI_PD_EXCLUSIVE: To allow device to be 27 TI_SCI_PD_SHARED: To allow device to be shared 45 along with an index representing the device id to be passed to the PMMC
|
/u-boot/doc/device-tree-bindings/mfd/ |
A D | kendryte,k210-sysctl.txt | 5 be reference by other bindings which need a phandle to the K210 sysctl regmap. 8 - compatible: should be 11 - reg-io-width: must be <4> 18 - compatible: should be "kendryte,k210-clk" 20 - #clock-cells: must be <1>
|
/u-boot/doc/device-tree-bindings/usb/ |
A D | dwc3-st.txt | 8 - compatible : must be "st,stih407-dwc3" 10 - reg-names : should be "reg-glue" and "syscfg-reg" 11 - st,syscon : should be phandle to system configuration node which 13 - resets : list of phandle and reset specifier pairs. There should be two entries, one 15 - reset-names : list of reset signal names. Names should be "powerdown" and "softreset" 17 - #address-cells, #size-cells : should be '1' if the device has sub-nodes 20 - pinctl-names : A pinctrl state named "default" must be defined 28 The dwc3 core should be added as subnode to ST DWC3 glue as shown in the
|
A D | tegra-usb.txt | 9 - compatible : Should be "nvidia,tegra20-ehci" for USB controllers 11 - phy_type : Should be one of "ulpi" or "utmi". 12 - nvidia,vbus-gpio : If present, specifies a gpio that needs to be 13 activated for the bus to be powered. 17 nvidia,tegra20-ehci compatible controllers. Can be "host", "peripheral",
|
/u-boot/doc/imx/ahab/guides/ |
A D | mx8_mx8x_encrypted_boot.txt | 11 step-by-step procedure can be found in mx8_mx8x_secure_boot.txt and 15 concept can be applied to others processors in i.MX8/8X family devices. 25 functions, the image must be encrypted by CST and the resulting DEK (Data 67 Details in API usage can be found in SCFW API guide [1]. 73 please be sure to have the following features enabled, this can be achieved 127 Secret Key command that must be added after Authenticate Data command. 137 2nd container will be encrypted. 160 The DEK must be encapsulated into a CAAM blob so it can be included into the 227 be commented or set to 0xFFFFFFFF. 254 be included into the final encrypted binary. [all …]
|
/u-boot/doc/device-tree-bindings/spi/ |
A D | spi-qup.txt | 5 - compatible : Should be "qcom,spi-qup-v1.1.1", "qcom,spi-qup-v2.1.1" 10 address on the SPI bus. Should be set to 1. 11 - #size-cells : Should be zero. 12 - pinctrl-names : Must be "default" 15 The gpios will be referred to as reg = <index> in the
|
/u-boot/doc/device-tree-bindings/memory/ |
A D | memory.txt | 5 Optional subnodes can be used defining the memory layout for different board 8 that the result should have for the match to be considered valid. The mask 13 - #address-cells: should be 1. 14 - #size-cells: should be 0. 23 match-mask - A mask to apply to the board id. This must be accompanied by 26 node to be considered a match. 28 each bank is probed to determine its actual size, which may be 65 * Default of 2GB of memory, auto-sized, so could be smaller
|
/u-boot/doc/usage/ |
A D | pstore.rst | 30 Ramoops parameters can be passed as kernel parameters or through Device Tree, 35 The same values should be set in U-Boot to be able to retrieve the records. 36 This values can be set at build time in U-Boot configuration file, or at runtime. 54 Records sizes should be a power of 2. 55 The memory size and the record/console size must be non-zero. 57 Multiple 'dump' records can be stored in the memory reserved for PStore. 58 The memory size has to be larger than the sum of the record sizes, i.e.:: 81 and match kernel ramoops parameters, it needs to be set using 'pstore set', e.g.:: 85 Then all available dumps can be displayed
|
/u-boot/doc/device-tree-bindings/gpio/ |
A D | gpio-samsung.txt | 4 - compatible: Compatible property value should be "samsung,exynos4-gpio>". 9 - #gpio-cells: Should be 4. The syntax of the gpio specifier used by client nodes 10 should be the following with values derived from the SoC user manual. 29 - #address-cells: should be 1. 30 - #size-cells: should be 1.
|
/u-boot/doc/device-tree-bindings/adc/ |
A D | st,stm32-adc.txt | 4 It has several multiplexed input channels. Conversions can be performed 7 Conversions can be launched in software or using hardware triggers. 16 - regular conversion can be done in sequence, running in background 24 - compatible: Should be one of: 39 - clock-names: Must be "adc" and/or "bus" depending on part used. 56 - compatible: Should be one of: 75 Both properties can be used together. Some channels can be used as 84 - dma-names: Must be "rx" when dmas property is being used. 87 * can be 6, 8, 10 or 12 on stm32f4 88 * can be 8, 10, 12, 14 or 16 on stm32h7 [all …]
|
/u-boot/doc/driver-model/ |
A D | fs_firmware_loader.rst | 11 File system firmware loader can be used to load whatever(firmware, image, 16 To enable firmware loader, CONFIG_FS_LOADER need to be set at 39 device, it can be described in FDT as shown in below: 53 The value of the firmware-loader property should be set with phandle 59 firmware-loader property can be added under /chosen node instead of 71 loaded instance should be created by DT phandle. 96 variables, so all these data from FDT can be overwritten 102 Storage interface, it can be "mmc", "usb", "sata" or "ubi". 104 Block device number and its partition, it can be "0:1". 106 UBI device mtd partition, it can be "UBI". [all …]
|
A D | soc-framework.rst | 13 from a set of identification information from an array. This can be useful for 30 soc_ops need not be defined and can be left as NULL, in which case the 36 identifying information. Information returned must be in the form of a NULL 40 meaning of the values that can be returned. See drivers/soc/soc_sandbox.c for 50 An array of 'struct soc_attr' can be defined, each containing ID information 52 for each entry in the list will be compared against the values provided by the 54 non-null values will be returned by soc_device_match. 56 An example of various uses of the framework can be found at test/dm/soc.c.
|
/u-boot/drivers/power/ |
A D | Kconfig | 113 On A31 boards dcdc2 is used for VDD-GPU and should be 1.2V. 115 On A80 boards dcdc2 powers the GPU and can be left off. 117 On R40 boards dcdc2 is VDD-CPU and should be 1.1V 131 should be 1.25V. 164 should be 1.5V, 1.35V if DDR3L is used. 179 should be 1.8V. 193 On A31 boards aldo2 may be used for LPDDR2 then it should be 1.8V. 197 LPDDR2, and the codec. It should be 1.8V. 207 On A10(s) / A13 / A20 boards aldo3 should be 2.8V. 209 be 3.0V. [all …]
|
/u-boot/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
A D | README.pci_iommu_extra | 9 This feature can be enabled through the PCI_IOMMU_EXTRA_MAPPINGS Kconfig option. 11 The "pci_iommu_extra" env var or "pci-iommu-extra" device tree property (to be 15 of VFs that will ever be created for it 30 <action> can be: 35 - "hp" to specify that on this <bdf> there will be a hot-plugged device so 37 The device tree property must be placed under the correct pci controller node 38 and only the bdf and action pairs need to be specified, like this: 57 For the device tree case, this would be specified like this: 65 For the device tree case, this would be specified like this:
|