- Dec 10, 2013
-
-
git://git.denx.de/u-boot-x86Tom Rini authored
-
git://git.denx.de/u-boot-mmcTom Rini authored
-
git://git.denx.de/u-boot-i2cTom Rini authored
-
- Dec 09, 2013
-
-
Mike Frysinger authored
We want to test SPI flash code in the sandbox, so enable the new drivers and the 'sf test' command. This command is used to validate the sandbox SPI / SPI flash implementation, so enable it. Signed-off-by:
Mike Frysinger <vapier@gentoo.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Mike Frysinger authored
This adds a SPI flash driver which simulates SPI flash clients. Currently supports the bare min that U-Boot requires: you can probe, read, erase, and write. Should be easy to extend to make it behave more exactly like a real SPI flash, but this is good enough to merge now. sjg@chromium.org added a README and tidied up code a little. Added a required map_sysmem() for sandbox. Signed-off-by:
Mike Frysinger <vapier@gentoo.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Mike Frysinger authored
This adds a SPI framework for people to hook up simulated SPI clients. Signed-off-by:
Mike Frysinger <vapier@gentoo.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This was obtained from Linux 3.12 commit 5e01dc7b26. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This allows us to put the SPI flash chip inside the SPI interface node, with U-Boot finding the correct bus and chip select automatically. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
The new name is longer but more clearly related to sandbox. This is in a separate patch within the same series since some comments on the SPI series rely on it. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Hung-ying Tyan <tyanh@chromium.org>
-
- Dec 08, 2013
-
-
Kuo-Jung Su authored
Faraday FTSDC021 is a controller which is compliant with SDHCI v3.0, SDIO v2.0 and MMC v4.3. However this driver is only verified with SD memory cards. Signed-off-by:
Kuo-Jung Su <dantesu@faraday-tech.com> Acked-by:
Pantelis Antoniou <panto@antoniou-consulting.com> CC: Andy Fleming <afleming@gmail.com>
-
Priyanka Jain authored
Existing eSDHC SPL framework assumes booting from sd-image with boot_format header which contains final u-boot Image offset and size. No such header is present in case of corenet devices like T1040 as corenet deivces use PBI-RCW based intialization. So, for corenet deives, SPL bootloader use values provided at compilation time. These values can be defined in board specific config file. Signed-off-by:
Priyanka Jain <Priyanka.Jain@freescale.com> Acked-by:
Pantelis Antoniou <panto@antoniou-consulting.com>
-
Alexey Brodkin authored
If platform provides "host->fifoth_val" it will be used for initialization of DWMCI_FIFOTH register. Otherwise default value will be used. This implementation allows: * escape unclear and recursive calculations that are currently in use * use whatever custom value for DWMCI_FIFOTH initialization if any particular SoC requires it Signed-off-by:
Alexey Brodkin <abrodkin@synopsys.com> Cc: Mischa Jonker <mjonker@synopsys.com> Cc: Alim Akhtar <alim.akhtar@samsung.com> Cc: Rajeshwari Shinde <rajeshwari.s@samsung.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: Amar <amarendra.xt@samsung.com> Cc: Kyungmin Park <kyungmin.park@samsung.com> Cc: Minkyu Kang <mk7.kang@samsung.com> Cc: Simon Glass <sjg@chromium.org> Cc: Pantelis Antoniou <panto@antoniou-consulting.com> Cc: Andy Fleming <afleming@freescale.com> Acked-by:
Jaehoon Chung <jh80.chung@samsung.com> Acked-by:
Pantelis Antoniou <panto@antoniou-consulting.com>
-
Jaehoon Chung authored
dw-mmc.c is the general driver file. So, remove the exynos specific code at dw-mmc.c. Instead, exynos specific cod can be move into exynos-dw_mmc.c. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com> Acked-by:
Alexey Brodkin <abrodkin@synopsys.com> Acked-by:
Pantelis Antoniou <panto@antoniou-consulting.com> Acked-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- Dec 06, 2013
-
-
Masahiro Yamada authored
Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com>
-
Axel Lin authored
For invalid bus number, current code returns NULL in the default case of switch-case statements. In additional, pins[bus] is always not NULL because it is the address of specific row of the two-dimensional array. Thus this patch removes these unnecessary test. Signed-off-by:
Axel Lin <axel.lin@ingics.com> Acked-by:
Scott Jiang <scott.jiang.linux@gmail.com> Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com>
-
Axel Lin authored
For invalid bus number, current code returns NULL in the default case of switch-case statements. In additional, pins[bus] is always not NULL because it is the address of specific row of the two-dimensional array. Thus this patch removes these unnecessary test. Signed-off-by:
Axel Lin <axel.lin@ingics.com> Acked-by:
Scott Jiang <scott.jiang.linux@gmail.com> Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com>
-
Sonic Zhang authored
Use default GPIO operations. Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com> Acked-by:
Heiko Schocher <hs@denx.de>
-
Sonic Zhang authored
Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com>
-
Sonic Zhang authored
Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com>
-
Sonic Zhang authored
Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com>
-
Naveen Krishna Ch authored
This patch adds the U_BOOT_I2C_ADAP_COMPLETE defines for channels on Exynos5420 and Exynos5250 and also adds support for init function for hsi2c channels Signed-off-by:
Naveen Krishna Chatradhi <ch.naveen@samsung.com>
- Dec 05, 2013
-
-
Nikita Kiryanov authored
Writing zero into I2Ci.I2C_CNT register causes random I2C failures in OMAP3 based devices. This seems to be related to the following advisory which apears in multiple erratas for OMAP3 SoCs (OMAP35xx, DM37xx), as well as OMAP4430 TRM: Advisory: I2C Module Does Not Allow 0-Byte Data Requests Details: When configured as the master, the I2C module does not allow 0-byte data transfers. Note: Programming I2Ci.I2C_CNT[15:0]: DCOUNT = 0 will cause undefined behavior. Workaround(s): No workaround. Do not use 0-byte data requests. The writes in question are unnecessary from a functional point of view. Most of them are done after I/O has finished, and the only one that preceds I/O (in i2c_probe()) is also unnecessary because a stop bit is sent before actual data transmission takes place. Therefore, remove all writes that zero the cnt register. Cc: Heiko Schocher <hs@denx.de> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Tom Rini <trini@ti.com> Cc: Lubomir Popov <lpopov@mm-sol.com> Cc: Enric Balletbo Serra <eballetbo@gmail.com> Signed-off-by:
Nikita Kiryanov <nikita@compulab.co.il> Tested-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by:
Lubomir Popov <lpopov@mm-sol.com>
-
Kuo-Jung Su authored
The local pointer of address (i.e., addr) only gets referenced under SPI mode, and it won't be appropriate to pass only 1-byte addr[1] to i2c_read/i2c_write while CONFIG_SYS_I2C_EEPROM_ADDR_LEN > 1. 1. In U-boot's I2C model, the address would be re-assembled to a byte string in MSB order inside I2C controller drivers. 2. The 'CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW' option which could be found at soft_i2c.c is always turned on in cmd_eeprom.c, the addr[0] always contains the device address with overflowed MSB address bits. Signed-off-by:
Kuo-Jung Su <dantesu@faraday-tech.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> cc: Peter Tyser <ptyser@xes-inc.com> Cc: Heiko Schocher <hs@denx.de> Cc: Wolfgang Denk <wd@denx.de> Cc: Stefan Roese <sr@denx.de> Cc: Mischa Jonker <mjonker@synopsys.com>
-
Kuo-Jung Su authored
For a eeprom with a 2-bytes address (e.g., Ateml AT24C1024B), the r/w address should be serial out in MSB order. Signed-off-by:
Kuo-Jung Su <dantesu@faraday-tech.com> Cc: Heiko Schocher <hs@denx.de>
-
Kuo-Jung Su authored
Replace the legacy i2c model with the new one. Signed-off-by:
Kuo-Jung Su <dantesu@faraday-tech.com> Cc: Heiko Schocher <hs@denx.de>
-
Kuo-Jung Su authored
Coding style cleanup Signed-off-by:
Kuo-Jung Su <dantesu@faraday-tech.com> Cc: Heiko Schocher <hs@denx.de>
-
Piotr Wilczek authored
Fix clock value initialisation for Exynos other than Exynos5 for hsi2c. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Cc: Minkyu Kang <mk7.kang@samsung.com> Cc: Heiko Schocher <hs@denx.de>
-
Piotr Wilczek authored
This patch adapts the s3c24x0 driver to the new i2c framework. Config file is modified for all the boards that use the driver. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> CC: Minkyu Kang <mk7.kang@samsung.com> CC: Heiko Schocher <hs@denx.de> CC: Inderpal Singh <inderpal.singh@linaro.org> CC: David Müller <d.mueller@elsoft.ch> CC: Chander Kashyap <k.chander@samsung.com> CC: Lukasz Majewski <l.majewski@samsung.com> Tested-by:
Naveen Krishna Chatradhi <ch.naveen@samsung.com> Reviewed-by:
Naveen Krishna Chatradhi <ch.naveen@samsung.com>
-
- Dec 04, 2013
-
-
York Sun authored
MPC8349 has been using mpc85xx DDR driver through a symbolic link to mpc85xx_ddr_gen2.c. After consolidating the drivers to a single set under driver/ddr/fsl/, the link is replaced by referring driver directly. We now can simply enable the macro and use the driver. Other mpc83xx SoCs still use their own driver. Signed-off-by:
York Sun <yorksun@freescale.com>
-
Shengzhou Liu authored
Usually CONFIG_FSL_DDR_INTERACTIVE feature is used for debug. we would not enable this by default to save the limited space of u-boot. This avoid following compiling error: section .bootpg loaded at [00000000effff000,00000000effff577] overlap ssection .data loaded at [00000000efff31b8,00000000f00010c7] u-boot: section .bootpg lma 0xeffff000 adjusted to 0xf00010c8 Signed-off-by:
Shengzhou Liu <Shengzhou.Liu@freescale.com> Acked-by:
York Sun <yorksun@freescale.com>
-
Zang Roy-R61911 authored
MEM_PLL_RAT on T4240/T4160 Rev2.0 uses a value which is half of Rev1.0. It's 12 in Rev1.0, for Rev2.0 it uses 6. Signed-off-by:
Roy Zang <tie-fei.zang@freescale.com> Signed-off-by:
Shaohui Xie <Shaohui.Xie@freescale.com> Acked-by:
York Sun <yorksun@freescale.com>
-
Priyanka Jain authored
Existing eSPI SPL framework assumes booting from spi-image with boot_format header which contains final u-boot Image offset and size. No such header is present in case of corenet devices like T1040 as corenet deivces use PBI-RCW based intialization. So, for corenet deives, SPL bootloader use values provided at compilation time. These values can be defined in board specific config file. Signed-off-by:
Priyanka Jain <Priyanka.Jain@freescale.com> Acked-by:
York Sun <yorksun@freescale.com>
-
Po Liu authored
Currently, there is only one EEPROM on c29xpcie board which is AT24C1024. We program the SPD data at beginning of the AT24C1024.But the AT24C1024 has a 16-bit sub-address mode. This patch is tomake it work when getting SPD in a 16-bit sub-address EEPROM. Signed-off-by:
Po Liu <Po.Liu@freescale.com> Acked-by:
York Sun <yorksun@freescale.com>
-
Zhao Qiang authored
In new board P1010RDB-PB, the interrupt vector table is at the start of memory. So if the start_address needs to be set a proper value. Signed-off-by:
Zhao Qiang <B45475@freescale.com> Acked-by:
York Sun <yorksun@freescale.com>
-
Dave Liu authored
In PBL RAMBOOT(SPI/SD/NAND boot) mode, CPC1 used as SRAM, should disable CPC1 speculation and keep it till relocation. Otherwise, speculation transactions will go to DDR controller, it will cause problem. Signed-off-by:
Dave Liu <daveliu@freescale.com> Signed-off-by:
Shaohui Xie <Shaohui.Xie@freescale.com> Acked-by:
York Sun <yorksun@freescale.com>
-
- Dec 02, 2013
-
-
git://git.denx.de/u-boot-mipsTom Rini authored
-
Masahiro Yamada authored
Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
git://git.denx.de/u-boot-mpc85xxTom Rini authored