- Feb 13, 2014
-
-
Holger Brunck authored
CONFIG_BOOTCOUNT_LIMIT is used on all boards from this board series. So remove this unneeded define. Signed-off-by:
Holger Brunck <holger.brunck@keymile.com> Acked-by:
Valentin Longchamp <valentin.longchamp@keymile.com>
-
Michal Simek authored
This patch is here because of: "arm: keep all sections in ELF file" (sha1: 47ed5dd0) Our tools expect to have elf with only LOAD header. Without this fix also PHDR, INTERP and DYNAMIC headers are available in ELF. Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
Michal Simek authored
The reason is enabling tftpput command where tftp shorcut stops to work for tftpboot. Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
Masahiro Yamada authored
Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Scott Wood <scottwood@freescale.com> Cc: David Feng <fenghua@phytium.com.cn> Acked-by:
Scott Wood <scottwood@freescale.com>
-
Stephen Warren authored
The entries in config.mk were needed so that U-Boot could be built with an old version of the Raspberry Pi Foundation's toolchain. Without them, the build would error out with: ...-ld: error: .../libgcc.a(_bswapsi2.o) uses VFP register arguments, u-boot does not However, none of the 3 toolchains in the latest version of their tools.git, nor the Ubuntu/Linaro ARM compilers in at least Ubuntu Quantal or Saucy, need these options set in order to compile a working U-Boot. Hence, remove the options for simplicity. Reported-by:
Tom Rini <trini@ti.com> Signed-off-by:
Stephen Warren <swarren@wwwdotorg.org> Reviewed-by:
Andreas Färber <afaerber@suse.de>
-
Stephen Warren authored
U-Boot names the Raspberry Pi board rpi_b. This means that the common expression for DTB filename ${soc}-${board}.dtb expands to bcm2835-rpi_b.dtb. However, the DTB generated by the Linux kernel is bcm2835-rpi-b.dtb. Set $fdtfile in U-Boot's environment so that scripts look for the correct DTB filename. An alternative would be to rename the U-Boot board to rpi-b. However, that change would be far more invasive, and end up affecting users (i.e they'd have to change their U-Boot build commands). Signed-off-by:
Stephen Warren <swarren@wwwdotorg.org>
-
Albert ARIBAUD authored
-
- Feb 10, 2014
-
-
Inha Song authored
Use setbits/clrbits macro instead of readl/writel function. (Suggested by Wolfgang) Signed-off-by:
Inha Song <ideal.song@samsung.com> Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Inha Song authored
This patch fixed that cfg value is set to wrong value. Because it didn't read the related register. Signed-off-by:
Inha Song <ideal.song@samsung.com> Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- Feb 07, 2014
-
-
Piotr Wilczek authored
This patch modifies envs to enable dual kernel boot - with separated DTB if the DTB file is loaded successfully; - with DTB apppended to uImage if DTB file is not found; This is neccesssary for backward compatibilty. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Cc: Lukasz Majewski <l.majewski@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch adds variables describing platform (soc, board, vendor) to default environment. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch adds variables describing platform (soc, board, vendor) to default environment. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Cc: Lukasz Majewski <l.majewski@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch adds variables describing platform (soc, board, vendor) to default environment. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Cc: Przemyslaw Marczak <p.marczak@samsung.com> Acked-by:
Przemyslaw Marczak <p.marczak@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch adds variables describing platform (soc, board, vendor) to default environment. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Cc: Mateusz Zalega <m.zalega@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch sets envs that describe board information. The following envs are set: soc_id, soc_rev, board_rev. Based on this information, if CONFIG_OF_LIBFDT is enabled, the 'fdtfile' env is set as: fdtfile=${soc_family}${soc_id}-${board}.dtb The generated envs are intenionally not saved to persistent storage. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch adds s5p_cpu_rev. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch enables to read cpu revision on Exynos CPU. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- Feb 05, 2014
-
-
Inha Song authored
This patch fix the u-boot shell problem on TRATS2 board. - If hold the key while booting is in progress, white spaces are written in u-boot shell. Set Automatically clears after resetting Rx FIFO. Signed-off-by:
Inha Song <ideal.song@samsung.com> Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com> Acked-by:
Lukasz Majewski <l.majewski@samsung.com> Tested-by:
Lukasz Majewski <l.majewski@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Minkyu Kang authored
Because of the list of peripherals is not sequential, such a routine does not check for valid correctly. Error check will be done when call the exynos_pinmux_config function. Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com> Acked-by:
Jaehoon Chung <jh80.chung@samsung.com> Acked-by:
Rajeshwari Shinde <rajeshwari.s@samsung.com>
-
Minkyu Kang authored
The value of PERIPH_ID_COUNT was wrong, and unnecessary. Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Minkyu Kang authored
Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com> Acked-by:
Rajehswari Shinde <rajeshwari.s@samsung.com>
-
- Feb 03, 2014
-
-
Jim Lin authored
Fix the timeout issue after running "bootp" command in U-Boot console. TXFIFOTHRES bits of TXFILLTUNING register should be set to 0x10 after a controller reset and before RUN bit is set (per technical reference manual). Signed-off-by:
Jim Lin <jilin@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
These are the board files for Venice2 (Tegra124), plus the AS3722 PMIC files. PMIC init will be moved to pmic_common_init later. This builds/boots on Venice2, SPI/MMC/USB/I2C all work. Audio, display and WB/LP0 are not supported yet. Signed-off-by:
Tom Warren <twarren@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
These are fairly complete, and near-clones of Tegra114 Venice, with an additional I2C port, and MMC address changes for Tegra124. Signed-off-by:
Tom Warren <twarren@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
These files are used by both SPL and main U-Boot. Signed-off-by:
Tom Warren <twarren@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
These files are for code that runs on the CPU (A15) on Tegra124 boards. At this time, there is no A15-specific code here. The warmboot/LP0 files aren't included as that code hasn't been ported yet. Signed-off-by:
Tom Warren <twarren@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
This provides SPL support for Tegra124 boards - AVP early init, plus CPU (A15) init/jump to main U-Boot. Signed-off-by:
Tom Warren <twarren@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
These headers define the Tegra124 hardware. Add them to the usual place. Add Tegra124 chip ID/SKU ID definitions to common headers. There's no real HW change on Tegra124 for 90% of the toys, so it might make sense for a future patch to unify some of the content of these files in a common location. Signed-off-by:
Tom Warren <twarren@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
The reg property for node spi@7000d800 was wrong. Fix it to match the HW. This change was verified against the Linux kernel. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
__pinmux_nand() won't compile if PERIPH_ID_NDFLASH isn't defined. Prevent this from causing build problems on newer SoCs without NAND support (or without SW support for NAND yet), but preventing compilation unless the function will actually be used, i.e. when CONFIG_TEGRA_NAND is defined. Signed-off-by:
Tom Warren <twarren@nvidia.com> [swarren, rewrote commit description, moved ifdef around whole function rather than just body] Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
There's already an SoC-specific conditional in cpu.h to determine the PLLP rate. Define the CSITE clock rate inside the same conditional, so that we can remove a conditional from clock_enable_coresight(). This means one less place to update the code for new SoCs. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
This programming sequence is correct per Jimmy Zhang, and makes sense too! Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
Pass just the partition ID to power_partition(), rather than also passing the partition's status register mask too. This makes it simpler to get call-sites correct, since they don't need to pass two different values that define the same thing and must match. Consequently, we can remove the mask definitions from pmc.h. Suggested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
Use a named constant for the PLL lock bit in enable_cpu_clocks(). Construct the complete value of pmc_pwrgate_toggle, rather than doing a read-modify-write; the register is simple enough and doesn't need to maintain state between operations. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
Tegra124's MMC controller is very similar to earlier SoC generations, and can be supported by the same driver. However, there are some non-backwards-compatible HW differences, and hence a new DT compatible value must be used to describe the HW. This patch updates the driver to support that new compatible value. That said, the HW differences are only relevant when enabling certain high-performance transfer modes. Since the driver is currently very simple and doesn't enable those modes, we don't actually need to address any of these HW differences in the code yet, hence the simple nature of this patch. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Acked-by:
Pantelis Antoniou <panto@antoniou-consulting.com> Tested-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Jimmy Zhang authored
Based on the Tegra TRM, the system clock (which is the AVP clock) can run up to 275MHz. On power on, the default sytem clock source is set to PLLP_OUT0. In function clock_early_init(), PLLP_OUT0 will be set to 408MHz which is beyond system clock's upper limit. The fix is to set the system clock to CLK_M before initializing PLLP, and then switch back to PLLP_OUT4, which has an appropriate divider configured, after PLLP has been configured Implement this logic in new function tegra30_set_up_pllp(), which sets up PLLP and all PLLP_OUT* dividers, and handles the AVP clock switching. Remove the duplicate PLLP setup from pllx_set_rate() and adjust_pllp_out_freqs(). Signed-off-by:
Jimmy Zhang <jimmzhang@nvidia.com> [swarren, significantly refactored the change] Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Thierry Reding <treding@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
Tegra114 and later's PMC module removes the pwrgate_timer_on register and replaces it with a clamp_status register. Adjust pmc.h to reflect this, and update any code affected by the change. The cpu.c change in this patch was extracted from a much larger patch by Jimmy Zhang. The pmc.h change was written from scratch, but inspired by related changes made by Tom Warren. There could well be other differences in the PMC register set for chips after Tegra20/30. However, they don't affect the code in U-Boot at present, so I haven't attempted an exhaustive update of pmc.h. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Thierry Reding <treding@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Tom Warren authored
Some clock sources have 3-bit muxes in bits 31:29. Implement core support for this mux field. Signed-off-by:
Tom Warren <twarren@nvidia.com> [swarren, extracted from a larger patch by Tom] Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Thierry Reding <treding@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
Since all code that sets or interprets MASK_BITS_* now uses the enums to define/compare the values, there is no need for MASK_BITS_* to have a specific integer value. In fact, having a specific integer value may encourage people to hard-code those values, or interpret the values in incorrect ways. As such, remove the logic that assigns a specific value to the enum values in order to make it completely clear that it's just an enum, not something that directly represents some integer value. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Thierry Reding <treding@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Stephen Warren authored
Not all code that set or interpreted "mux_bits" was using the named macros, but rather some was simply using hard-coded integer constants. This makes it hard to determine which pieces of code are affected by changes to those constants. Replace the integer constants with the equivalent macro definitions so that everything is nicely tied together. Note that I'm not convinced all the code was using the correct integer constants, and hence I'm not convinced that all the code is now using the desired macros. However, this change is a purely mechanical replacement and should have no functional change. Fixing any bugs will come later, separately. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Thierry Reding <treding@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-