- Apr 08, 2013
-
-
SRICHARAN R authored
The omap5-uevm is the reference board name for OMAP5 soc based platform. So rename it accordingly. Acked-by:
Nishanth Menon <nm@ti.com> Signed-off-by:
Sricharan R <r.sricharan@ti.com> Tested-by:
Nishanth Menon <nm@ti.com>
-
Hunter, Jon authored
The function get_timer() should return time in ms and CONFIG_SYS_HZ should be set to 1000 by default. Fix both of these items. Signed-off-by:
Jon Hunter <jon-hunter@ti.com>
-
Hunter, Jon authored
Enable device-tree support for the omap2420-h4 board. Signed-off-by:
Jon Hunter <jon-hunter@ti.com>
-
Hunter, Jon authored
The omap2420-h4 board is using a RAM based address as the linker location for code. This is causing several problems when attempting to run the latest u-boot code base on this board from flash. Update the default linker location for code to be in NOR flash. Please note that OMAP maps the NOR flash to address 0x08000000 by default and so use this as the default address for the NOR flash. Also remove legacy code that attempts to calculate where in flash the sdata structure, that holds the memory interface configuration data, is located. By changing the default linker location for code to flash this is no longer necessary. Signed-off-by:
Jon Hunter <jon-hunter@ti.com>
-
Hunter, Jon authored
The size of the DRAM for the omap2420-h4 board is getting setup in the dram_init() function. However, for the current u-boot release this is too late and needs to be done in dram_init_banksize(). Therefore, add a dram_init_banksize() function for the omap2420-h4 board and setup the DRAM size there. Signed-off-by:
Jon Hunter <jon-hunter@ti.com>
-
Andreas Bießmann authored
Signed-off-by:
Andreas Bießmann <andreas.devel@googlemail.com> Cc: Tom Rini <trini@ti.com> Cc: Thomas Weber <weber@corscience.de> Cc: Ilya Yanok <ilya.yanok@cogentembedded.com> Cc: Scott Wood <scottwood@freescale.com>
-
Andreas Bießmann authored
The kernel states: ---8<--- The OMAP3 GPMC hardware BCH engine computes remainder polynomials, it does not provide automatic error location and correction: this step is implemented using the BCH library. --->8--- And we do so in u-boot. This implementation uses the same layout for BCH8 but it is fix. The current provided layout does only work with 64 Byte OOB. Signed-off-by:
Andreas Bießmann <andreas.devel@googlemail.com> Cc: Tom Rini <trini@ti.com> Cc: Ilya Yanok <ilya.yanok@cogentembedded.com> Cc: Scott Wood <scottwood@freescale.com> Cc: Mansoor Ahamed <mansoor.ahamed@ti.com> Cc: Thomas Weber <thomas.weber.linux@googlemail.com>
-
Andreas Bießmann authored
With uppcoming BCH support on OMAP devices we need to decide between differnt algorithms when switching the ECC engine. Currently we support 1-bit hammign and 8-bit BCH on HW backend. In order to switch between differnet ECC algorithms we need to change the interface of omap_nand_switch_ecc() also. Signed-off-by:
Andreas Bießmann <andreas.devel@googlemail.com> Cc: Tom Rini <trini@ti.com> Cc: Thomas Weber <thomas.weber.linux@googlemail.com>
-
Andreas Bießmann authored
This patch adds BCH8 ooblayout for NAND as provided by 0e618ef0a6a33cf7ef96c2c824402088dd8ef48c in linux kernel. This Layout is currently only provided for 64 byte OOB. Signed-off-by:
Andreas Bießmann <andreas.devel@googlemail.com> Cc: Tom Rini <trini@ti.com> Cc: Ilya Yanok <ilya.yanok@cogentembedded.com> Cc: Scott Wood <scottwood@freescale.com> Reviewed-by:
Tom Rini <trini@ti.com>
-
Andreas Bießmann authored
arch/arm/include/asm/arch-am33xx/omap_gpmc.h and arch/arm/include/asm/arch-omap3/omap_gpmc.h are almost the same, consolidate the common parts into a new header. Introduce a new asm/omap_gpmc.h which defines the command part and pulls in the architecture specific one. Signed-off-by:
Andreas Bießmann <andreas.devel@googlemail.com> Cc: Tom Rini <trini@ti.com> Reviewed-by:
Tom Rini <trini@ti.com>
-
Andreas Bießmann authored
This patch adds the BCH result registers to register mapping for OMAP3 gpmc. Signed-off-by:
Andreas Bießmann <andreas.devel@googlemail.com> Cc: Tom Rini <trini@ti.com> Cc: Ilya Yanok <ilya.yanok@cogentembedded.com> Cc: Scott Wood <scottwood@freescale.com> Reviewed-by:
Tom Rini <trini@ti.com>
-
Manfred Huber authored
Flush UART3 xmit on enable if TEMT is broken On some OMAP3 devices when UART3 is configured for boot mode before SPL starts only THRE bit is set. We have to empty the transmitter before initialization starts. This patch avoids the use of CONFIG_SYS_NS16550_BROKEN_TEMT. Signed-off-by:
Manfred Huber <man.huber@arcor.de> Tested-by:
Javier Martinez Canillas <javier@dowhile0.org> Tested-by:
Andreas Bießmann <andreas.devel@googlemail.com>
-
Tom Rini authored
We must not assume ROM has enabled the clock for MMC1. Reported-by:
Koen Kooi <koen@dominion.thruhere.net> Signed-off-by:
Tom Rini <trini@ti.com> Acked-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Lars Poeschel authored
This is done already for am335x in 59dcf970 and also applies for pcm051. It powers down the IO receiver when not performing read which helps reducing the overall power consuption in low power states (suspend/standby). Signed-off-by:
Lars Poeschel <poeschel@lemonage.de>
-
Bin Liu authored
Do not config MUSB to highspeed mode if CONFIG_USB_GADGET_DUALSPEED is not set, in which case Ether gadget only operates in fullspeed. Reviewed-by:
Tom Rini <trini@ti.com> Signed-off-by:
Bin Liu <b-liu@ti.com>
-
Bin Liu authored
On TI AM335x devices, MUSB has bulk split/combine feature enabled in the ConfigData register, but the current MUSB driver does not support it yet. Therefore, disable the feature for now, until the driver adds the support. One usecase which is broken because of this feature is that Ether gadget stops working in Fullspeed mode (by un-defining CONFIG_USB_GADGET_DUALSPEED) After desabled this feature, MUSB driver send packets in proper size (no more than 64 bytes) in Fullspeed mode. This has been validated with Ether gadget in Fullspeed mode on AM335x EVM. Signed-off-by:
Bin Liu <b-liu@ti.com>
-
- Apr 05, 2013
-
-
Josh Wu authored
Atmel change to new logo since 2012. This patch update the logo to new one. Signed-off-by:
Josh Wu <josh.wu@atmel.com> Signed-off-by:
Andreas Bießmann <andreas.devel@googlemail.com>
-
- Apr 04, 2013
-
-
Albert ARIBAUD authored
-
Minkyu Kang authored
Fix the indentation of some defines by tab. Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Albert ARIBAUD authored
-
Dirk Behme authored
Reviewing the ECSPI reset handling shows two issues: 1. For the enable/reset bit (MXC_CSPICTRL_EN) in the control reg (ECSPIx_CONGREG) the i.MX6 technical reference manual states: -- cut -- ECSPIx_CONREG[0]: EN: Writing zero to this bit disables the block and resets the internal logic with the exception of the ECSPI_CONREG. -- cut -- Note the exception mentioned: The CONREG itself isn't reset. Fix this by manually writing the reset value 0 to the whole register. This sets the EN bit to zero, too (i.e. includes the old ~MXC_CSPICTRL_EN). 2. We want to reset the whole SPI block here. So it makes no sense to first read the old value of the CONREG and write it back, later. This will give us the old (historic/random) value of the CONREG back. And doesn't reset the CONREG. To get a clean CONREG after the reset of the block, too, don't use the old (historic/random) value of the CONREG while doing the reset. And read the clean CONREG after the reset. This was found while working on a SPI boot device where the i.MX6 boot ROM has already initialized the SPI block. The initialization by the boot ROM might be different to what the U-Boot driver wants to configure. I.e. we need a clean reset of SPI block, including the CONREG. Signed-off-by:
Dirk Behme <dirk.behme@de.bosch.com> CC: Stefano Babic <sbabic@denx.de> CC: Fabio Estevam <fabio.estevam@freescale.com>
-
Stephen Warren authored
Apparently, CONFIG_SYS_HZ must be 1000. Change this, and fix the timer driver to conform to this. Have the timer implementation export a custom API get_timer_us() for use by the BCM2835 MMC API, which needs us resolution for a HW workaround. Signed-off-by:
Stephen Warren <swarren@wwwdotorg.org>
-
- Apr 03, 2013
-
-
Javier Martinez Canillas authored
board/freescale/mx6qsabrelite/README explain a procedure to update the SPI-NOR on the SabreLite board without Freescale manufacturing tool but following this procedure leads to both "sf erase" and "sf write" failing on a mx6qsabrelite board: MX6QSABRELITE U-Boot > sf probe 1 MX6QSABRELITE U-Boot > sf erase 0 0x40000 SPI flash erase failed MX6QSABRELITE U-Boot > sf write 0x10800000 0 0x40000 SPI flash write failed This is because the chip-select 1 is wrong and the correct value is 0x7300. Since commit c1173bd0 ("sf command: allow default bus and chip selects") the chip-select and bus arguments for the sf probe command are optional so let's just remove it and use "sf probe" instead. Signed-off-by:
Javier Martinez Canillas <javier.martinez@collabora.co.uk>
-
Fabio Estevam authored
CONFIG_SYS_FSL_USDHC_NUM is not used for wandboard. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Acked-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Fabio Estevam authored
No need to call 'mmc dev' twice. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Acked-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Fabio Estevam authored
No need to call 'mmc dev' twice. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Acked-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Fabio Estevam authored
When booting a Freescale kernel 3.0.35 on a Wandboard solo, the get_board_rev() returns 0x62xxx, which is not a value understood by the VPU (Video Processing Unit) library in the kernel and causes the video playback to fail. The expected values for get_board_rev are: 0x63xxx: For mx6quad/dual 0x61xxx: For mx6dual-lite/solo So adjust get_board_rev() accordingly and make it as weak function, so that we do not need to define it in every mx6 board file. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Acked-by:
Dirk Behme <dirk.behme@de.bosch.com> Acked-by:
Eric Nelson <eric.nelson@boundarydevices.com>
-
Alexandre Pereira da Silva authored
The netargs variable was referencing the non-existing variable console_mainline. Change that to console variable instead. Signed-off-by:
Alexandre Pereira da Silva <aletes.xgr@gmail.com> Acked-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Abbas Raza authored
Maximum bus width supported by some i.MX6 boards is not 8bit like others. In case where both host controller and card support 8bit transfers, they agree to communicate on 8bit interface while some boards support only 4bit interface. Due to this reason the mmc 8bit default mode fails on these boards. To rectify this, define maximum bus width supported by these boards (4bit). If max_bus_width is not defined, it is 0 by default and 8bit width support will be enabled in host capabilities otherwise host capabilities are modified accordingly. It is tested with a MMCplus card. Signed-off-by:
Abbas Raza <Abbas_Raza@mentor.com> cc: stefano Babic <sbabic@denx.de> cc: Andy Fleming <afleming@gmail.com> Acked-by:
Dirk Behme <dirk.behme@de.bosch.com> Acked-by:
Andrew Gabbasov <andrew_gabbasov@mentor.com>
-
Otavio Salvador authored
Change all "#define/ifdef<TAB>" sequences into "#define/ifdef<SPACE>". Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Benoît Thébaudeau authored
The mx25pdk board supports the i.MX25 DryIce RTC (imxdi), so enable it. This allows to compile-test the imxdi driver in the mainline tree. Signed-off-by:
Benoît Thébaudeau <benoit.thebaudeau@advansee.com> Acked-by:
Fabio Estevam <fabio.estevam@freescale.com>
-
Fabio Estevam authored
The u-boot.imx binary is generated by default, so no need to pass it in the 'make' line. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com>
-
Fabio Estevam authored
Introduce 'mx28evk_nand' target for saving environment variables into NAND. The mx28evk board does not come with a NAND flash populated from the factory. It comes with an empty slot (U23), which allows the insertion of a 48-pin TSOP flash device. Tested with a K9LBG08U0D. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Reviewed-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Otavio Salvador authored
Adds support for 'bmode' command which let user to choose where to boot from; this allows U-Boot to load system from another storage without messing with jumpers. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Otavio Salvador authored
This changes the code so in case an unkown value is passed it will return as invalid. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Otavio Salvador authored
This documents the SD card identifier so it is easier for user to spot which card number will be used, if need. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
- Apr 01, 2013
-
-
Akshay Saraswat authored
As we shall now be using clock_get_periph_rate function. We find no reason for keeping code in function exynos5_get_pwm_clk. Hence, removing it. Signed-off-by:
Akshay Saraswat <akshay.s@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Padmavathi Venna authored
Use generic api to get the pwm clock frequency Test with command "sf probe 1:0; time sf read 40008000 0 1000". Try with different numbers of bytes and see that sane values are obtained Build and boot U-boot with this patch, backlight works properly. Signed-off-by:
Padmavathi Venna <padma.v@samsung.com> Signed-off-by:
Akshay Saraswat <akshay.s@samsung.com> Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Padmavathi Venna authored
MPLL is selected as the source clk of pwm by default Test with command "sf probe 1:0; time sf read 40008000 0 1000". Try with different numbers of bytes and see that sane values are obtained Build and boot U-boot with this patch, backlight works properly. Signed-off-by:
Padmavathi Venna <padma.v@samsung.com> Signed-off-by:
Akshay Saraswat <akshay.s@samsung.com> Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Padmavathi Venna authored
Add generic api to get the frequency of the required peripherial. This API gets the source clock frequency and returns the required frequency by dividing with first and second dividers based on the requirement. Test with command "sf probe 1:0; time sf read 40008000 0 1000". Try with different numbers of bytes and see that sane values are obtained Build and boot U-boot with this patch, backlight works properly. Signed-off-by:
Padmavathi Venna <padma.v@samsung.com> Signed-off-by:
Akshay Saraswat <akshay.s@samsung.com> Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-