Home
last modified time | relevance | path

Searched refs:parameters (Results 1 – 25 of 107) sorted by relevance

12345

/u-boot-v2022.01-rc1/doc/usage/
A Dpstore.rst30 Ramoops parameters can be passed as kernel parameters or through Device Tree,
37 U-Boot automatically patches the Device Tree to pass the Ramoops parameters to
40 The PStore configuration parameters are:
80 First of all, unless PStore parameters as been set during U-Boot configuration
81 and match kernel ramoops parameters, it needs to be set using 'pstore set', e.g.::
A Daskenv.rst36 Value of a environment variable env1 without message and size parameters:
46 Value of a environment variable env2 with message and size parameters:
/u-boot-v2022.01-rc1/doc/device-tree-bindings/video/
A Ddisplaymode.txt9 parameters in pixels
11 parameters in lines
25 not allow for inconsistent parameters. Unlike the Framebuffer framework
A Ddisplay-timing.txt19 - hfront-porch, hback-porch, hsync-len: horizontal display timing parameters
21 vfront-porch, vback-porch, vsync-len: vertical display timing parameters in
49 The parameters are defined as:
/u-boot-v2022.01-rc1/doc/
A DREADME.falcon22 from SPL. A new command is added to U-Boot to prepare the parameters that SPL
25 In normal mode, these parameters are generated each time before
27 the parameters can be read.
35 well, if used), use the "spl export" command to generate the kernel parameters
44 the parameters which are saved in the persistent area to the required address.
62 CONFIG_SYS_SPL_ARGS_ADDR Address in RAM where the parameters must be
68 CONFIG_CMD_SPL_NAND_OFS Offset in NAND where the parameters area was saved.
70 CONFIG_CMD_SPL_NOR_OFS Offset in NOR where the parameters area was saved.
72 CONFIG_CMD_SPL_WRITE_SIZE Size of the parameters area to be copied
187 The parameters generated with this step can be saved into NAND at the offset
[all …]
A DREADME.fsl-ddr149 Hwconfig can be combined with multiple parameters, for example, on a supported
292 type command "compute" to calculate the parameters from the default
314 dimmparms - DIMM parameters, calculated from SPD
315 commonparms - lowest common parameters for all DIMMs
324 dimmparms - DIMM parameters, calculated from SPD
325 commonparms - lowest common parameters for all DIMMs
362 DIMM parameters: Controller=0 DIMM=0
363 DIMM organization parameters:
A DREADME.atmel_pmecc43 CONFIG_SPL_GENERATE_ATMEL_PMECC_HEADER. The required parameters are taken from
46 type. The mkimage tool has intentionally _not_ compiled in those parameters.
/u-boot-v2022.01-rc1/arch/arm/mach-omap2/omap3/
A Dboard.c357 static void omap3_emu_romcode_call(u32 service_id, u32 *parameters) in omap3_emu_romcode_call() argument
359 u32 i, num_params = *parameters; in omap3_emu_romcode_call()
367 __raw_writel(*parameters, sram_scratch_space); in omap3_emu_romcode_call()
368 parameters++; in omap3_emu_romcode_call()
/u-boot-v2022.01-rc1/arch/arm/mach-uniphier/
A DKconfig102 bool "Enable dump command of DDR PHY parameters"
107 The command "ddrphy" shows the resulting parameters of DDR PHY
111 bool "Enable dump command of DDR Multi PHY parameters"
115 The command "ddrmphy" shows the resulting parameters of DDR Multi PHY
/u-boot-v2022.01-rc1/doc/device-tree-bindings/clock/
A Drockchip,rk3288-dmc.txt27 rockchip,ddr-speed-bin: DDR3 type,AC timing parameters from the memory data-sheet
50 rockchip,trcd: tRCD,AC timing parameters from the memory data-sheet
51 rockchip,trp: tRP,AC timing parameters from the memory data-sheet
53 -rockchip,pctl-timing: parameters for the SDRAM setup, in this order:
94 will be set up the same. The parameters are in this order:
103 - rockchip,sdram-params: SDRAM base parameters, in this order:
/u-boot-v2022.01-rc1/arch/arm/dts/
A Darmada-xp-crs305-1g-4s.dtsi51 /* Device Bus parameters are required */
53 /* Read parameters */
62 /* Write parameters */
A Darmada-xp-crs328-4c-20s-4s.dtsi51 /* Device Bus parameters are required */
53 /* Read parameters */
62 /* Write parameters */
A Darmada-xp-db-xc3-24g4xg.dts50 /* Device Bus parameters are required */
52 /* Read parameters */
61 /* Write parameters */
A Darmada-xp-crs326-24g-2s.dtsi51 /* Device Bus parameters are required */
53 /* Read parameters */
62 /* Write parameters */
A Darmada-xp-gp.dts72 /* Device Bus parameters are required */
74 /* Read parameters */
83 /* Write parameters */
/u-boot-v2022.01-rc1/arch/arm/
A DKconfig.debug20 to provide the parameters for the 8250 UART rather than
22 you know the parameters for the port.
/u-boot-v2022.01-rc1/lib/crypto/
A Dpkcs7.asn137 parameters ANY OPTIONAL
120 parameters ANY OPTIONAL
A Dx509.asn125 parameters ANY OPTIONAL ({ x509_note_params })
/u-boot-v2022.01-rc1/drivers/serial/
A DKconfig237 You will need to provide parameters to make this work. The
246 You will need to provide parameters to make this work. The
255 will need to provide parameters to make this work. The driver will
263 will need to provide parameters to make this work. The driver will
271 will need to provide parameters to make this work. The driver will
364 PL010 UART type. You will need to provide parameters to make this
373 PL011 UART type. You will need to provide parameters to make this
415 You will need to provide parameters to make this work.
433 You will need to provide parameters to make this work. The driver
442 You will need to provide parameters to make this work. The
[all …]
/u-boot-v2022.01-rc1/board/nokia/rx51/
A Drx51.c373 static void omap3_emu_romcode_call(u32 service_id, u32 *parameters) in omap3_emu_romcode_call() argument
375 u32 i, num_params = *parameters; in omap3_emu_romcode_call()
383 __raw_writel(*parameters, sram_scratch_space); in omap3_emu_romcode_call()
384 parameters++; in omap3_emu_romcode_call()
/u-boot-v2022.01-rc1/arch/arm/include/asm/arch-omap3/
A Dsys_proto.h70 void do_omap3_emu_romcode_call(u32 service_id, u32 parameters);
/u-boot-v2022.01-rc1/doc/mvebu/cmd/
A Dbubt.txt5 The bubt command gets the following parameters: ATF file name, destination device and source device.
18 by parameters CONFIG_SYS_MMC_ENV_DEV and CONFIG_SYS_MMC_ENV_PART.
/u-boot-v2022.01-rc1/board/freescale/mx6memcal/
A DREADME17 DDR parameters for U-Boot?).
18 3. It doesn't prompt for parameters, so it's much faster to gather
/u-boot-v2022.01-rc1/doc/build/
A Dgcc.rst103 Build parameters
106 A list of available parameters for the make command can be obtained via
118 Further important build parameters are
/u-boot-v2022.01-rc1/doc/device-tree-bindings/gpio/
A Dnvidia,tegra20-gpio.txt10 second cell is used to specify optional parameters:

Completed in 54 milliseconds

12345