- 17 11月, 2017 9 次提交
-
-
由 Baruch Siach 提交于
Fixes: 4984de2b ("dm: core: Add ofnode to represent device tree nodes") Cc: Simon Glass <sjg@chromium.org> Signed-off-by: NBaruch Siach <baruch@tkos.co.il> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 André Draszik 提交于
While commit 36d35345 ("tpm: add missing va_end") added some missing calls to va_end(), it missed a few places. Signed-off-by: NAndré Draszik <adraszik@tycoint.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 André Draszik 提交于
TPM_NV_PER_PPREAD: physical presence needed for reading TPM_NV_PER_WRITEDEFINE: persistent write lock by writing size 0 TPM_NV_PER_WRITEALL: write in one go Signed-off-by: NAndré Draszik <adraszik@tycoint.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 André Draszik 提交于
Add a function to obtain random data from the TPM. Signed-off-by: NAndré Draszik <adraszik@tycoint.com> Added commit message, add cast to min() Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 André Draszik 提交于
The offset of the permanent flags structure is in a different place in the response compared to what the code is doing, which gives us a completely useless result. Fix by replacing hand-crafted code with generic parser infrastructure. Signed-off-by: NAndré Draszik <adraszik@tycoint.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 André Draszik 提交于
The maximum length of the name of the image is obviously not sizeof(), which is just the length of a pointer, but IH_NMLEN. fixes: 62cf11c0 ("SPL: Limit image name print length") Signed-off-by: NAndré Draszik <adraszik@tycoint.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Tom Rini 提交于
We borrow the macros for these functions from ARM and remove references to '__raw_'. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
This currently causes a warning in sandbox and will not do the right thing: drivers/core/read.c: In function ‘dev_read_addr_ptr’: drivers/core/read.c:64:44: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] return (addr == FDT_ADDR_T_NONE) ? NULL : (void *)addr; Use map_sysmem() which is the correct way to convert an address to a pointer. Fixes: c131c8bc (dm: core: add dev_read_addr_ptr()) Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NBin Meng <bmeng.cn@gmail.com> Tested-by: NBin Meng <bmeng.cn@gmail.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Bernhard Messerklinger 提交于
Since the compiler is free to place a char array to any address in memory (in this case the stack), also to a non word aligned address the function "fdt_prop_parse" runs into troubles upon it wants to write some (fdt32_t *) to such a variable (if it has been placed to a none word aligned address). To avoid this we tell the compiler to always align this scratchpad to a word aligned address. Signed-off-by: NBernhard Messerklinger <bernhard.messerklinger@br-automation.com> Reviewed-by: NHannes Schmelzer <oe5hpm@oevsv.at> Tested-by: NHannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
- 14 11月, 2017 1 次提交
-
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 13 11月, 2017 3 次提交
-
-
由 Soeren Moch 提交于
This reverts commit c61d0009. A tbs2910 board user reported a very slow console frambuffer as regression in current u-boot. I could bisect this down to the above mentioned commit. This revert brings back the fast framebuffer console (one cache flush per string in puts(), not after each char). Reported-by: NUwe Scheffler <scheffler.u@web.de> Signed-off-by: NSoeren Moch <smoch@web.de> Tested-by: NUwe Scheffler <scheffler.u@web.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Angelo Dureghello 提交于
Signed-off-by: NAngelo Dureghello <angelo@sysam.it>
-
由 Marek Vasut 提交于
The eMMC is 1V8 device only and the signaling is always 1V8, fix the DT for Salvator-X/XS to describe the hardware correctly. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
- 10 11月, 2017 7 次提交
-
-
-
由 Werner Böllmann 提交于
After updating u-boot from v2016.01 to 2017.09, issue with "SATA link 0 timeout." on my Cubietruck board. mdelay milled after moving satapwr code to board. "sunxi: Turn satapwr on from board_init" (sha1: 9fbb0c3a) After adding the "mdelay(500);" line that was lost in the path the error is gone. Signed-off-by: NWerner Böllmann <Werner.Boellmann@fh-dortmund.de> [Rebased and updated change and commit message] Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
由 Chen-Yu Tsai 提交于
Only the H3/H5 SoCs have an internal PHY and its related clock and reset controls. Use an #ifdef to guard the internal PHY control code block so it can be built for other SoCs, such as the A83T or A64. Signed-off-by: NChen-Yu Tsai <wens@csie.org> Acked-by: NMaxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by: NJoe Hershberger <joe.hershberger@ni.com> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
-
由 Jagan Teki 提交于
Update the falcon offsets for args to 16MB and kernel to 17MB Since the below commit updated U-Boot proper location along with rockchip boot image offsets "spl: set SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR to 0x4000 for rockchip" (sha1: 8f4d62b4) Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Jagan Teki 提交于
This patch fixed U-Boot proper location has been missed to update in bewlo commit "rockchip: doc: update U-Boot location info" (sha1: 73e6dbe8) Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Goldschmidt Simon 提交于
The U-Boot location has been moved to block 16384. This is 8MB, not 4MB. Signed-off-by: NSimon Goldschmidt <sgoldschmidt@de.pepperl-fuchs.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
- 09 11月, 2017 10 次提交
-
-
-
-
由 Lukasz Majewski 提交于
Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Lukasz Majewski 提交于
Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Lukasz Majewski 提交于
Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Lukasz Majewski 提交于
This commit provides support for LWN's IMX6Q based DISPLAY5 board. Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Lukasz Majewski 提交于
This commit provides generic function to set the RGMII/HSIC IO voltage level on iMX6 devices. Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Lukasz Majewski 提交于
The sys_proto.h file has been included earlier in this file. Signed-off-by: NLukasz Majewski <lukma@denx.de>
-
由 Artturi Alm 提交于
due misnaming of CONFIG_SUN4I_EMAC in include/configs/sunxi-common.h, likely missed in: commit 3146f0c0 ("Move PHYLIB to Kconfig") Signed-off-by: NArtturi Alm <artturi.alm@gmail.com> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
由 Artturi Alm 提交于
fixes CONFIG_SUNXI_EMAC references from drivers/net/Makefile and include/configs/sunxi-common.h likely forgotten in: commit abc3e4df ("sunxi: Convert SUNXI_EMAC to Kconfig") Signed-off-by: NArtturi Alm <artturi.alm@gmail.com> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
- 07 11月, 2017 10 次提交
-
-
由 Benoît Thébaudeau 提交于
The following error has been observed on i.MX25 with a high-speed SDSC card: Data Write Failed in PIO Mode. It was caused by the timeout set on PRSSTAT.BWEN, which was triggered because this bit takes 15 ms to be set after writing the first block to DATPORT with this card. Without this timeout, all the blocks are properly written. This timeout was implemented by decrementing a variable, so it was depending on the CPU frequency. Fix this issue by setting this timeout to a long enough absolute duration (500 ms). Signed-off-by: NBenoît Thébaudeau <benoit.thebaudeau.dev@gmail.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
由 Jagan Teki 提交于
- Update newly added include/configs file in MAINTAINERS - Update newly added defconfig file in README Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Fabio Estevam 提交于
When a high speed card is connected to mx51evk the following error is seen: U-Boot 2017.11-rc2 (Oct 18 2017 - 13:49:26 -0200) CPU: Freescale i.MX51 rev3.0 at 800 MHz Reset cause: POR Board: MX51EVK DRAM: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - read failed, using default environment In: serial Out: serial Err: serial Net: FEC Hit any key to stop autoboot: 0 => saveenv Saving Environment to MMC... Writing to MMC(0)... failed The root cause for the failure is the eSDHC-A001 erratum: "eSDHC-A001 : Data timeout counter (SYSCTL[DTOCV]) is not reliable for values of 0x4,0x8, and 0xC" that is listed on some PowerArchitecture chips: https://www.nxp.com/files-static/32bit/doc/errata/MPC8379ECE.pdf Even though eSDHC-A001 is not documented on the i.MX51 errata document, I have confirmed with the NXP design team that this erratum does affect i.MX51, so fix the problem by selecting SYS_FSL_ERRATUM_ESDHC_A001 at SoC level. The i.MX51 ts4800 board already selects this option, but it is better to move this selection to the i.MX51 SoC level instead. Successfully tested with a high speed SD card on a mx51evk board. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com> Acked-by: NSebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
-
由 Fabio Estevam 提交于
When a high speed card is connected to mx25 the following error is seen: U-Boot 2017.11-rc2-00104-gb79372ae (Oct 31 2017 - 11:02:22 -0200) CPU: Freescale i.MX25 rev1.2 at 399 MHz Reset cause: POR Board: MX25PDK I2C: ready DRAM: 64 MiB No arch specific invalidate_icache_all available! MMC: FSL_SDHC: 0 *** Warning - read failed, using default environment In: serial Out: serial Err: serial Net: FEC Hit any key to stop autoboot: 0 => saveenv Saving Environment to MMC... Writing to MMC(0)... failed , which prevents any usage of the SD card. The root cause for the failure is the eSDHC-A001 erratum: "eSDHC-A001 : Data timeout counter (SYSCTL[DTOCV]) is not reliable for values of 0x4,0x8, and 0xC" that is listed on some PowerArchitecture chips: https://www.nxp.com/files-static/32bit/doc/errata/MPC8379ECE.pdf Even though eSDHC-A001 is not documented on the i.MX25 errata document, I have confirmed with the NXP design team that this erratum does affect i.MX25, so fix the problem by selecting SYS_FSL_ERRATUM_ESDHC_A001 at SoC level. Successfully tested with a high speed SD card on a mx25pdk board. Suggested-by: NBenoît Thébaudeau <benoit@wsystem.com> Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com> Acked-by: NSebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com> Acked-by: NOtavio Salvador <otavio@ossystems.com.br> Tested-by: Otavio Salvador <otavio@ossystems.com.br> # mx25pdk
-
由 Fabio Estevam 提交于
The motivation for moving MX25 selection to Kconfig is to be able to better handle MX25 specific errata, so that an errata option can be selected at SoC level instead of board level. This selection method also aligns with the way other i.MX SoCs are selected in U-Boot. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com> Acked-by: NSebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com> Reviewed-by: NBenoît Thébaudeau <benoit.thebaudeau.dev@gmail.com>
-
由 Kever Yang 提交于
Use default value 0x4000 for SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR instead of define a new one. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Kever Yang 提交于
Update rockchip U-Boot location to 0x4000/16384. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Kever Yang 提交于
Rockchip use a 'loader2' partition for U-Boot, so u-boot.bin or u-boot.itb load by SPL need to locate at0x4000. Detail here: http://opensource.rock-chips.com/wiki_Boot_optionSigned-off-by: NKever Yang <kever.yang@rock-chips.com> Acked-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Klaus Goger 提交于
The environment storage location is selectable via Kconfig. We support eMMC, SD and SPI-NOR as location for U-Boot. This adds support to store the environment in the SPI-NOR additional to the default eMMC location. Signed-off-by: NKlaus Goger <klaus.goger@theobroma-systems.com> Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
由 Klaus Goger 提交于
The VCC_SD and VCC_SDIO rail should only be powered up to 3.0V on RK3399 platforms. Signed-off-by: NKlaus Goger <klaus.goger@theobroma-systems.com> Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-