- Jan 02, 2014
-
-
Prabhakar Kushwaha authored
T1040QDS has 256KB SRAM. Comment is showing wrong information. So update the comment. Signed-off-by:
Prabhakar Kushwaha <prabhakar@freescale.com>
-
- Dec 20, 2013
-
-
Łukasz Majewski authored
Update boards.cfg entries for Samsung's GONI and Universal_C210 maintainers entry. Signed-off-by:
Lukasz Majewski <l.majewski@samsung.com> Acked-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- Dec 19, 2013
-
-
git://git.denx.de/u-boot-spiTom Rini authored
-
Poddar, Sourav authored
claim spi bus while doing memory copy, this will set up the spi controller device control register before doing a memory read. Signed-off-by:
Sourav Poddar <sourav.poddar@ti.com> Tested-by:
Yebio Mesfin <ymesfin@ti.com> Reviewed-by:
Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
Poddar, Sourav authored
Add config to support bank address register. Signed-off-by:
Sourav Poddar <sourav.poddar@ti.com> Tested-by:
Yebio Mesfin <ymesfin@ti.com> Reviewed-by:
Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
- Dec 18, 2013
-
-
git://git.denx.de/u-boot-usbTom Rini authored
-
Marek Vasut authored
Fix the register access in EHCI HCD. We need to use address of the register as an ehci_writel() argument. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Simon Glass <sjg@chromium.org>
-
Marek Vasut authored
In case the controller is not initialized, we shall not de-initialize it. As the control structure will not be filled, we will produce a null ptr dereference if the controller is not inited. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Simon Glass <sjg@chromium.org>
-
Marek Vasut authored
The detection function of the EHCI PCI controller was really cryptic, add a beefy comment and clean the portion of the code up a bit. No change in the logic of the code. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Simon Glass <sjg@chromium.org>
-
Łukasz Majewski authored
Provide default Poll Timeout value for Trats board. Signed-off-by:
Lukasz Majewski <l.majewski@samsung.com>
-
Łukasz Majewski authored
Code cleanup for dfu_bind_config function Signed-off-by:
Lukasz Majewski <l.majewski@samsung.com>
-
Łukasz Majewski authored
It is necessary to deter the host from sending subsequent DFU_GETSTATUS request in the case of e.g. writing the buffer to medium. Here the timeout is increased when we fill up the whole buffer. This delay allows eMMC memory to perform its internal operations. Otherwise we end up with HOST's error regarding GET_STATUS receive timeout. Signed-off-by:
Lukasz Majewski <l.majewski@samsung.com>
-
Łukasz Majewski authored
The method for exporting size of allocated buffer is provided. It is afterwards used by USB's dfu function code. Signed-off-by:
Lukasz Majewski <l.majewski@samsung.com>
-
Yen Lin authored
The RDY bit indicates that a transfer is complete. This needs to be cleared by SW before every single HW transaction, rather than only at the start of each SW transaction (those being made up of n HW transactions). It seems that earlier HW may have cleared this bit autonomously when starting a new transfer, and hence this code was not needed in practice. However, this is generally a good idea in all cases. In Tegra124, the HW behaviour appears to have changed, and SW must explicitly clear this bit. Otherwise, SW will believe that transfers have completed when they have not, and may e.g. read stale data from the RX FIFO. Signed-off-by:
Yen Lin <yelin@nvidia.com> [swarren, rewrote commit description, unified duplicate RDY clearing code and moved it right before the start of the HW transaction, unconditionally exit loop after reading RX data, rather than checking if TX FIFO is empty, since it is guaranteed to be] Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
Nobuhiro Iwamatsu authored
This patch adds a driver for Renesas SoC's Quad SPI bus. This supports with 8 bits per transfer to use with SPI flash. Signed-off-by:
Kouei Abe <kouei.abe.cp@renesas.com> Signed-off-by:
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com> Signed-off-by:
Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
Luka Perkov authored
Add support for Macronix MX25L2006E SPI flash. Signed-off-by:
Luka Perkov <luka@openwrt.org> Reviewed-by:
Jagannadha Sutradharudu Teki <jagannadh.teki@gmail.com>
-
Luka Perkov authored
All other hex values in sf_probe.c are in lower case so we should fix this one too. Signed-off-by:
Luka Perkov <luka@openwrt.org> Reviewed-by:
Jagannadha Sutradharudu Teki <jagannadh.teki@gmail.com>
-
Masahiro Yamada authored
Before this commit, a broken pipe error sometimes happened when building lcd4_lwmon5 board with Buildman. This commit re-writes build rules of u-boot.spr and u-boot-img-spl-at-end.bin more simply without using a pipe. Besides fixing a broken pipe error, this commit gives us other advantages: - Do not generate intermidiate files, spl/u-boot-spl.img and spl/u-boot-spl-pad.img for creating u-boot.spr - Do not generate an intermidiate file, u-boot-pad.img for creating u-boot-img-spl-at-end.bin Such intermidiate files were not deleted by "make clean" or "make mrpropr". Nor u-boot-pad.img was ignored by git. Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by:
Stefan Roese <sr@denx.de>
-
Bo Shen authored
Fix the typo error for mrproper from mkproper. Signed-off-by:
Bo Shen <voice.shen@atmel.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Yoshihiro Shimoda authored
Signed-off-by:
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Signed-off-by:
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
Yoshihiro Shimoda authored
SH7753 has two fast ethernet controllers and two gigabit ethernet controllers. It is similar to SH7757. Signed-off-by:
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Signed-off-by:
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
Yoshihiro Shimoda authored
The SH7753 EVB board has SH7753, 512MB DDR3-SDRAM, SPI ROM, Gigabit Ethernet, and eMMC. This patch support the following functions: - 512MB DDR3-SDRAM, SCIF4, SPI ROM, Gigabit Ethernet, eMMC Signed-off-by:
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Signed-off-by:
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
- Dec 17, 2013
-
-
Nikita Kiryanov authored
If we change to software ecc and then back to hardware ecc, the nand ecc ops pointers are populated with incorrect function pointers. This is related to the way nand_scan_tail() handles assigning functions to ecc ops: If we are switching to software ecc/no ecc, it assigns default functions to the ecc ops pointers unconditionally, but if we are switching to hardware ecc, the default hardware ecc functions are assigned to ops pointers only if these pointers are NULL (so that drivers could set their own functions). In the case of omap_gpmc.c driver, when we switch to sw ecc, sw ecc functions are assigned to ecc ops by nand_scan_tail(), and when we later switch to hw ecc, the ecc ops pointers are not NULL, so nand_scan_tail() does not overwrite them with hw ecc functions. The result: sw ecc functions used to write hw ecc data. Clear the ecc ops pointers in omap_gpmc.c when switching ecc types, so that ops which were not assigned by the driver will get the correct default values from nand_scan_tail(). Cc: Scott Wood <scottwood@freescale.com> Cc: Pekon Gupta <pekon@ti.com> Signed-off-by:
Nikita Kiryanov <nikita@compulab.co.il>
-
Nikita Kiryanov authored
When switching ecc mode, omap_select_ecc_scheme() assigns the appropriate values into the current nand chip's ecc.layout struct. This is done under the assumption that the struct exists only to store values, so it is OK to overwrite it, but there is at least one situation where this assumption is incorrect: When switching to 1 bit hamming code sw ecc, the job of assigning layout data is outsourced to nand_scan_tail(), which simply assigns into ecc.layout a pointer to an existing struct prefilled with the appropriate values. This struct doubles as both data and layout definition, and therefore shouldn't be overwritten, but on the next switch to hardware ecc, this is exactly what's going to happen. The next time the user switches to software ecc, they're going to get a messed up ecc layout. Prevent this and possible similar bugs by explicitly using the private-to-omap_gpmc.c omap_ecclayout struct when switching ecc mode. Cc: Scott Wood <scottwood@freescale.com> Cc: Pekon Gupta <pekon@ti.com> Signed-off-by:
Nikita Kiryanov <nikita@compulab.co.il>
-
Tom Rini authored
length is size_t so needs to be '%zd' not '%d' to avoid warnings. Cc: Scott Wood <scottwood@freescale.com> Signed-off-by:
Tom Rini <trini@ti.com>
-
Nikita Kiryanov authored
Commit "mtd: nand: omap: enable BCH ECC scheme using ELM for generic platform" (d016dc42) changed the way software ECC is configured, both during boot, and during ecc switch, in a way that is not backwards compatible with older systems: Older version of omap_gpmc.c always assigned ecc.size = 0 when configuring for software ecc, relying on nand_scan_tail() to select a default for ecc.size (256), while the new version of omap_gpmc.c assigns ecc.size = pagesize, which is likely to not be 256. Since 1 bit hamming sw ecc is only meant to be used by legacy devices, revert to the original behavior. Cc: Igor Grinberg <grinberg@compulab.co.il> Cc: Tom Rini <trini@ti.com> Cc: Scott Wood <scottwood@freescale.com> Cc: Pekon Gupta <pekon@ti.com> Signed-off-by:
Nikita Kiryanov <nikita@compulab.co.il> Acked-by:
Pekon Gupta <pekon@ti.com>
-
Stefan Roese authored
Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Pekon Gupta <pekon@ti.com> Cc: Scott Wood <scottwood@freescale.com> [scottwood@freescale.com: wrap some long lines] Signed-off-by:
Scott Wood <scottwood@freescale.com>
-
pekon gupta authored
As per OMAP3530 TRM referenced below [1] For large-page NAND, ROM code expects following ecc-layout for HAM1 ecc-scheme - OOB[1] (offset of 1 *byte* from start of OOB) for x8 NAND device - OOB[2] (offset of 1 *word* from start of OOB) for x16 NAND device Thus ecc-layout expected by ROM code for HAM1 ecc-scheme is: *for x8 NAND Device* +--------+---------+---------+---------+---------+---------+---------+ | xxxx | ECC[A0] | ECC[A1] | ECC[A2] | ECC[B0] | ECC[B1] | ECC[B2] | ... +--------+---------+---------+---------+---------+---------+---------+ *for x16 NAND Device* +--------+--------+---------+---------+---------+---------+---------+---------+ | xxxxx | xxxxx | ECC[A0] | ECC[A1] | ECC[A2] | ECC[B0] | ECC[B1] | ECC[B2] | +--------+--------+---------+---------+---------+---------+---------+---------+ This patch fixes ecc-layout *only* for HAM1, as required by ROM-code For other ecc-schemes like (BCH8) ecc-layout is same for x8 or x16 devices. [1] OMAP3530: http://www.ti.com/product/omap3530 TRM: http://www.ti.com/litv/pdf/spruf98x Chapter-25: Initialization Sub-topic: Memory Booting Section: 25.4.7.4 NAND Figure 25-19. ECC Locations in NAND Spare Areas Reported-by:
Stefan Roese <sr@denx.de> Signed-off-by:
Pekon Gupta <pekon@ti.com> Tested-by:
Stefan Roese <sr@denx.de>
-
- Dec 16, 2013
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@ti.com>
-
git://git.denx.de/u-boot-videoTom Rini authored
-
Masahiro Yamada authored
Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Masahiro Yamada authored
Commit fea25720 renamed arch/i386 to arch/x86. But it missed to modify examples/standalone/Makefile. Since then, examples/standalone/82559_eeprom has never compiled and nobody has noticed that. After some discussion on ML, we agreed to delete this example. Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Masahiro Yamada authored
Convert like follows: CPU mpc83xx -> CONFIG_MPC83xx CPU mpc85xx -> CONFIG_MPC85xx CPU mpc86xx -> CONFIG_MPC86xx CPU mpc5xxx -> CONFIG_MPC5xxx CPU mpc8xx -> CONFIG_8xx CPU mpc8260 -> CONFIG_8260 CPU ppc4xx -> CONFIG_4xx CPU x86 -> CONFIG_X86 ARCH x86 -> CONFIG_X86 ARCH powerpc -> CONFIG_PPC Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Masahiro Yamada authored
REMOTE_BUILD is not used any more. Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Miao Yan authored
Signed-off-by:
Miao Yan <miao.yan@windriver.com>
-
Miao Yan authored
fdt_fixup_memory_banks() will add and update /memory node in device tree blob. In the case that /memory node doesn't exist, after adding a new one, this function returns error. The correct behavior should be continuing to update its properties. Signed-off-by:
Miao Yan <miao.yan@windriver.com>
-
Miao Yan authored
The next version VxWorks adopts device tree (for PowerPC and ARM) as its hardware description mechanism. For PowerPC, the boot interface conforms to the ePAPR standard, which is: void (*kernel_entry)(ulong fdt_addr, ulong r4 /* 0 */, ulong r5 /* 0 */, ulong r6 /* EPAPR_MAGIC */, ulong r7 /* IMA size */, ulong r8 /* 0 */, ulong r9 /* 0 */) For ARM, the boot interface is: void (*kernel_entry)(void *fdt_addr) Signed-off-by:
Miao Yan <miao.yan@windriver.com> [trini: Fix build error when !CONFIG_OF_FDT is set, typo on PowerPC, missing extern ft_fixup_num_cores] Signed-off-by:
Tom Rini <trini@ti.com>
-
Sonic Zhang authored
Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com>
-