- Jan 24, 2017
-
-
Tony O'Brien authored
Commit ac337168 unified functions to flush and invalidate dcache by range. These two functions were no-ops for SoCs other than 4xx and MPC86xx. Adding these functions seemed to be correct but introduced issues in some drivers when the dcache was flushed. While the root cause was under investigation, these functions were disabled in Commit cb1629f9 for affected SoCs, including the MPC85xx, to make the various drivers work. On the T208x USB stopped working after v2016.07 was pulled. After re-enabling the dcache functions for the MPC85xx it started working again. The USB and DPPA Ethernet drivers have been seen as operational after this change but other drivers cannot be tested. Reviewed-by:
Chris Packham <chris.packham@alliedtelesis.co.nz> Signed-off-by:
Tony O'Brien <tony.obrien@alliedtelesis.co.nz> Cc: Marek Vasut <marex@denx.de> Cc: York Sun <york.sun@nxp.com> Reviewed-by: York Sun <york.sun>
-
Tony O'Brien authored
The read-only-write-enable bit is set by default and must be cleared to prevent overwriting read-only registers. This should be done immediately after resetting the PCI Express controller. Reviewed-by:
Hamish Martin <hamish.martin@alliedtelesis.co.nz> Signed-off-by:
Tony O'Brien <tony.obrien@alliedtelesis.co.nz> [York S: Move SYS_FSL_ERRATUM_A007815 to Kconfig] Reviewed-by:
York Sun <york.sun@nxp.com>
-
Darwin Dingel authored
Core hang occurs when using L1 stashes. Workaround is to disable L1 stashes so software uses L2 cache for stashes instead. Reviewed-by:
Chris Packham <chris.packham@alliedtelesis.co.nz> Signed-off-by:
Darwin Dingel <darwin.dingel@alliedtelesis.co.nz> Cc: York Sun <york.sun@nxp.com> [York S: Move SYS_FSL_ERRATUM_A007907 to Kconfig] Reviewed-by:
York Sun <york.sun@nxp.com>
-
- Jan 22, 2017
-
-
git://git.denx.de/u-boot-uniphierTom Rini authored
- Allow to disable SPL (mainly for ATF) - Refactor SoC init code - Update DRAM settings - Add PXs3 SoC support (DT, pinctrl driver, SoC code)
-
Masahiro Yamada authored
Initial support for PXs3 SoC. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
Initial commit for the PXs3 SoC DT. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
Add pin configuration and pinmux support for UniPhier PXs3 SoC. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
All the UniPhier DT files are compiled if CONFIG_ARCH_UNIPHIER is enabled, but not all of them actually work. For example, when U-Boot is compiled for ARM 32 bit, 64 bit DT files are also built, and vice versa. Compile only the combination that makes sense. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
There are similar functions that look up SoC data by the SoC ID. The new macro UNIPHIER_DEFINE_SOCDATA_FUNC will be helpful to avoid the code duplication. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
Currently, uniphier_get_soc_type() converts the SoC ID (this is read from the revision register) to an enum symbol to use it for SoC identification. Come to think of it, there is no need for the conversion in the first place. Using the SoC ID from the register as-is a straightforward way. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
The <common.h> includes too many headers. Actually, these files needed to include it for udelay() declaration. Now we can replace it with <linux/delay.h> thanks to commit 5bc516ed ("delay: collect {m, n, u}delay declarations to include/linux/delay.h"). Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
These files only need error number macros. Actually, IS_ERR(), PTR_ERR(), ERR_PTR(), etc. are not useful for U-Boot. Avoid unnecessary header includes. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
This defconfig does not support SPL. If you use this, the basic SoC initialization must be done in firmware that runs before U-Boot. (Generally, ARM Trusted Firmware is expected to do this job). Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
We may want to run different firmware before running U-Boot. For example, ARM Trusted Firmware runs before U-Boot, making U-Boot a non-secure world boot loader. In this case, the SoC might be initialized there, which enables us to skip SPL entirely. This commit removes "select SPL" to make it configurable. This also enables the Multi SoC support for the UniPhier ARMv8 SoCs. (CONFIG_ARCH_UNIPHIER_V8_MULTI) Thanks to the driver model and Device Tree, the U-Boot proper part is now written in a generic way. The board/SoC parameters reside in DT. The Multi SoC support increases the memory footprint a bit, but the U-Boot proper does not have strict memory constraint. This will mitigate the per-SoC (sometimes per-board) defconfig burden. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
These are file-internal and constant. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Kotaro Hayashi authored
The ddrphy_shift_rof_hws() never writes back the shifted delay value to the register, which makes this function non-effective. Signed-off-by:
Kotaro Hayashi <hayashi.kotaro@socionext.com> [masahiro: add git log] Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Wataru Okoshi authored
Change bnk_typ's value from 8 to 0 (for G1's performance). Signed-off-by:
Wataru Okoshi <okoshi.wataru@socionext.com> Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
- Jan 21, 2017
-
-
Tom Rini authored
On occasion the job that does these two build types will hit the time limit so split this in two. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Uri Mashiach authored
Move all of the status LED feature to drivers/led/Kconfig. The LED status definitions were moved from the board configuration files to the defconfig files. TBD: Move all of the definitions in the include/status_led.h to the relevant board's defconfig files. Tested boards: CL-SOM-AM57x, CM-T335 Signed-off-by:
Uri Mashiach <uri.mashiach@compulab.co.il>
-
Uri Mashiach authored
Move all of the status LED feature to drivers/led/Kconfig. doc/README.LED updated to reflect the Kconfig implementation. Tested boards: CL-SOM-AM57x, CM-T335 Signed-off-by:
Uri Mashiach <uri.mashiach@compulab.co.il>
-
Jagan Teki authored
Cc: Tom Rini <trini@konsulko.com> Signed-off-by:
Jagan Teki <jagan@openedev.com>
-
Jagan Teki authored
This patch add Kconfig entry for CONFIG_BOARD_LATE_INIT Cc: Tom Rini <trini@konsulko.com> Signed-off-by:
Jagan Teki <jagan@openedev.com>
-
Tom Rini authored
When falcon mode support was added, it was right around when SPL_OS_BOOT was migrated to Kconfig. So first we must move the enablement to the defconfig file. Next, it turned off EXT support rather than add the information to allow for falcon mode from EXT. Add this information so that the board compiles after 5d28b930. Fixes: d96796ca ("mx6sabresd: Add Falcon mode support") Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Jan 20, 2017
-
-
Emmanuel Vadot authored
Instead of disabling the data cache in the bootelf command, disabling it in the do_bootm_qnxelf function. Some ELF binary might want the cache enabled. Signed-off-by:
Emmanuel Vadot <manu@bidouilliste.com>
-
Sven Ebenfeld authored
Reported-by: Coverity (CID: 155214) Signed-off-by:
Sven Ebenfeld <sven.ebenfeld@gmail.com>
-
Lokesh Vutla authored
Latest gcc compile strted complaining about defined structure definition that are not used. Remove the unused sturctures. Reported-by:
Dan Murphy <dmurphy@ti.com> Signed-off-by:
Lokesh Vutla <lokeshvutla@ti.com>
-
Lokesh Vutla authored
Latest gcc 6.2 compiler is throwing the below warning for omap4_panda_defconfig arch/arm/mach-omap2/omap4/hw_data.c:136:3: warning: 'abe_dpll_params_sysclk_196608khz' defined but not used [-Wunused-const-variable=] abe_dpll_params_sysclk_196608khz[NUM_SYS_CLKS] = { Fix this by guarding it with CONFIG_SYS_OMAP_ABE_SYSCK Reported-by:
Dan Murphy <dmurphy@ti.com> Signed-off-by:
Lokesh Vutla <lokeshvutla@ti.com>
-
Emmanuel Vadot authored
The built _libfdt.so is placed in the /tools dir and need to say here as it contains relative paths. Add the directory to the python path so binman can use this module. Signed-off-by:
Emmanuel Vadot <manu@bidouilliste.com>
-
Emmanuel Vadot authored
Do not rely on CONFIG_SPL_OF_PLATDATA to build the libfdt python module. If swig is present, this will be build Signed-off-by:
Emmanuel Vadot <manu@bidouilliste.com>
-
Lukasz Majewski authored
Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
Andreas Färber authored
Use the generic "distro" boot framework to enable automatic DHCP boot. MMC and USB are not yet implemented, so this is the only boot option. The fdt and kernel addresses are adopted from downstream; ramdisk and scriptaddr addresses were chosen arbitrarily. Signed-off-by:
Andreas Färber <afaerber@suse.de> Reviewed-by:
Alexander Graf <agraf@suse.de>
-
Andreas Färber authored
Move it from meson-gxbb-common.h to odroid-c2.h to allow new boards not to implement it. Signed-off-by:
Andreas Färber <afaerber@suse.de>
-
Tom Rini authored
We can make the code read more easily here by simply using memset() always as when we don't have an optimized version of the function we will still have a version of this function around anyhow. Cc: Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Tom Rini authored
We have long had available optimized versions of the memset and memcpy functions that are borrowed from the Linux kernel. We should use these in normal conditions as the speed wins in many workflows outweigh the relatively minor size increase. However, we have a number of places where we're simply too close to size limits in SPL and must be able to make the size vs performance trade-off in those cases. Cc: Philippe Reynes <tremyfr@yahoo.fr> Cc: Eric Jarrige <eric.jarrige@armadeus.org> Cc: Heiko Schocher <hs@denx.de> Cc: Magnus Lilja <lilja.magnus@gmail.com> Cc: Lokesh Vutla <lokeshvutla@ti.com> Cc: Chander Kashyap <k.chander@samsung.com> Cc: Akshay Saraswat <akshay.s@samsung.com> Cc: Simon Glass <sjg@chromium.org> Cc: Stefan Roese <sr@denx.de> Signed-off-by:
Tom Rini <trini@konsulko.com> Acked-by:
Stefan Roese <sr@denx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Andrew F. Davis authored
While moving OMAP related files to mach-omap2 the functionality relating to generating secure boot files was modified. This change prevents secure platforms other than AM33xx and OMAP54XX from correctly building files for all needed media types. Fixes: 983e3700 ("arm: Introduce arch/arm/mach-omap2 for OMAP2 derivative platforms") Signed-off-by:
Andrew F. Davis <afd@ti.com> Acked-by:
Lokesh Vutla <lokeshvutla@ti.com>
-
Andrew F. Davis authored
Signed-off-by:
Andrew F. Davis <afd@ti.com> Acked-by:
Lokesh Vutla <lokeshvutla@ti.com> Acked-by:
Michal Simek <michal.simek@xilinx.com>
-
Andrew F. Davis authored
These files are only included for build by the make system when CONFIG_SPL_{EXT,FAT}_SUPPORT is enabled, remove the unneed checks for these in the source files. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
xypron.glpk@gmx.de authored
IEC 80000-13:2008 Quantities and units Part 13: Information science and technology defines the prefixes to use for binary multiples. So instead of writing Data Size: 6726132 Bytes = 6568.49 kB = 6.41 MB in dumpimage we should write Data Size: 6726132 Bytes = 6568.49 KiB = 6.41 MiB. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
Emmanuel Vadot authored
In a config with one MMC at device id '1' and no MMC at device id '0' (a BeagleBone Black with no sd inserted for example), the current code will first test to access the MMC 0 (sd port), seeing that no device is present it will simply return that no more device are present for this class. This patch fixes this by testing all devices for each class. Signed-off-by:
Emmanuel Vadot <manu@bidouilliste.com>
-
Emmanuel Vadot authored
The current code can loop undefinitly as it doesn't parse correctly the env data. Since the env is an hashtable, use the hashtable function for the API_ENV_ENUM api call. Signed-off-by:
Emmanuel Vadot <manu@bidouilliste.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-