March 2016 - U-Boot

[U-Boot] [PATCH] arm: mx5: Enable NAND TrimFFS on M53EVK
by Marek Vasut 20 Mar '16

20 Mar '16

Enable NAND TrimFFS support in M53EVK, since it is convenient when installing UBI images to NAND. Signed-off-by: Marek Vasut <marex(a)denx.de> Cc: Stefano Babic <sbabic(a)denx.de> --- include/configs/m53evk.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/configs/m53evk.h b/include/configs/m53evk.h index fbaa600..c247c2a 100644 --- a/include/configs/m53evk.h +++ b/include/configs/m53evk.h @@ -43,6 +43,7 @@ #define CONFIG_CMD_MII #define CONFIG_CMD_MMC #define CONFIG_CMD_NAND +#define CONFIG_CMD_NAND_TRIMFFS #define CONFIG_CMD_PING #define CONFIG_CMD_SATA #define CONFIG_CMD_USB -- 2.7.0

1 0

[U-Boot] Linux hangs due to commit v2015.10-15-g02cc27c on loading i2c-mv64xx
by Michael Haas 20 Mar '16

20 Mar '16

Hello all, I'm running Debian Jessie with Linux 4.3.0-0.bpo.1-armmp-lpae on my a20-olinuxino-lime2. I have noticed that my board hangs with my recent u-boot versions when I load the i2c module. git-bisect narrowed the problem down to the following commit: 02cc27c74f9b884b538bcd1b93342a4c05b5d608 is the first bad commit commit 02cc27c74f9b884b538bcd1b93342a4c05b5d608 Author: Hans de Goede <hdegoede(a)redhat.com> Date: Sat Oct 3 15:29:24 2015 +0200 sunxi: power: Change axp209 LDO3 and LDO4 default to disabled LDO3 and LDO4 are normally either unused, or used to power csi attached camera sensors, and as such do not need to be enabled at boot time. Signed-off-by: Hans de Goede <hdegoede(a)redhat.com> Acked-by: Ian Campbell <ijc(a)hellion.org.uk> :040000 040000 9ff2e54e613a4386473cdf66c3bc5dc830a31bc7 d5330c13ef2c86643499f476b7042748969fd523 MT>>>>>drivers The axp209 is attached to the i2c bus, so that is likely the real culprit. In my setup, the axp209 drivers are loaded before I insert i2c-mv64xxx. What would be the best course of action here? * Revert the commit * Enable LDO3 and LDO4 for the a20-olinuxino-lime2 only? * Fix linux Best, Michael

1 0

[U-Boot] [PATCH] sunxi: Support SID e-fuses on A83T and H3
by Chen-Yu Tsai 20 Mar '16

20 Mar '16

On the A83T and H3, the SID block is at a different address. Furthurmore, the e-fuses are at an offset of 0x200 within the hardware's address space. Signed-off-by: Chen-Yu Tsai <wens(a)csie.org> --- arch/arm/include/asm/arch-sunxi/cpu_sun4i.h | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h b/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h index 0cdefdc..f797649 100644 --- a/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h +++ b/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h @@ -74,7 +74,14 @@ #define SUNXI_AD_DA_BASE 0x01c22c00 #define SUNXI_KEYPAD_BASE 0x01c23000 #define SUNXI_TZPC_BASE 0x01c23400 + +#if defined(CONFIG_MACH_SUN8I_A83T) || defined(CONFIG_MACH_SUN8I_H3) +/* SID address space starts at 0x01c1400, but e-fuse is at offset 0x200 */ +#define SUNXI_SID_BASE 0x01c14200 +#else #define SUNXI_SID_BASE 0x01c23800 +#endif + #define SUNXI_SJTAG_BASE 0x01c23c00 #define SUNXI_TP_BASE 0x01c25000 -- 2.7.0

3 5

[U-Boot] Please pull u-boot-dm
by Simon Glass 20 Mar '16

20 Mar '16

Hi Tom, Here is the rest of the block device stuff as well as a few buildman improvements and a few other things. The following changes since commit f23baa572f96e1e13d7f1a3c8addb61b5d0dbd29: cmd_dhry.c: Use lldiv for vax_mips calculation as well (2016-03-17 10:14:25 -0400) are available in the git repository at: git://git.denx.de/u-boot-dm.git for you to fetch changes up to e4fb863f6dec0002069d57422ebe3ce3af69a273: dm: blk: Add tests for block devices (2016-03-17 21:27:39 -0600) ---------------------------------------------------------------- Michal Simek (1): dm: ns16550: Add support for reg-offset property Przemyslaw Marczak (2): dts:exynos:update pinctrl size-cells and fix child regs Revert "fdt: fix address cell count checking in fdt_translate_address()" Simon Glass (8): gpio: Report errors when GPIOs cannot be read buildman: Allow branch names which conflict with directories buildman: Add a way to specific a full toolchain prefix buildman: Clarify the use of -V dm: usb: Unbind old block devices when shutting down USB dm: sandbox: Switch over to use DM for block devices dm: sandbox: Drop the pre-DM host implementation dm: blk: Add tests for block devices arch/arm/dts/exynos4210-pinctrl-uboot.dtsi | 8 +- arch/arm/dts/exynos4x12-pinctrl-uboot.dtsi | 18 +-- arch/arm/dts/exynos5250-pinctrl-uboot.dtsi | 16 +-- arch/arm/dts/exynos54xx-pinctrl-uboot.dtsi | 12 +- arch/arm/dts/s5pc110-pinctrl.dtsi | 4 +- cmd/gpio.c | 34 ++++-- common/fdt_support.c | 7 +- configs/sandbox_defconfig | 1 + drivers/block/sandbox.c | 90 -------------- drivers/serial/ns16550.c | 6 +- drivers/usb/host/usb-uclass.c | 6 +- include/ns16550.h | 1 + test/dm/Makefile | 1 + test/dm/blk.c | 96 +++++++++++++++ tools/buildman/README | 299 ++++++++++++++++++++++++++++----------------- tools/buildman/cmdline.py | 2 +- tools/buildman/func_test.py | 2 + tools/buildman/toolchain.py | 40 +++++- tools/patman/gitutil.py | 5 + 19 files changed, 404 insertions(+), 244 deletions(-) create mode 100644 test/dm/blk.c Regards, Simon

2 1

[U-Boot] [PATCH] spl: Print from which mmc slot spl is trying to boot
by Hans de Goede 20 Mar '16

20 Mar '16

On some sunxi boards (and presumably also non sunxi boards) u-boot can be either loaded from a sdcard in a micro-sd slot, or from eMMC. Print which MMC spl tries to boot from, to help debugging. Signed-off-by: Hans de Goede <hdegoede(a)redhat.com> --- common/spl/spl.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/common/spl/spl.c b/common/spl/spl.c index e5167bf..82e7f58 100644 --- a/common/spl/spl.c +++ b/common/spl/spl.c @@ -210,9 +210,9 @@ struct boot_device_name boot_name_table[] = { { BOOT_DEVICE_RAM, "RAM" }, #endif #ifdef CONFIG_SPL_MMC_SUPPORT - { BOOT_DEVICE_MMC1, "MMC" }, - { BOOT_DEVICE_MMC2, "MMC" }, - { BOOT_DEVICE_MMC2_2, "MMC" }, + { BOOT_DEVICE_MMC1, "MMC1" }, + { BOOT_DEVICE_MMC2, "MMC2" }, + { BOOT_DEVICE_MMC2_2, "MMC2_2" }, #endif #ifdef CONFIG_SPL_NAND_SUPPORT { BOOT_DEVICE_NAND, "NAND" }, -- 2.7.3

2 1

[U-Boot] How to run a new instance of u-boot from u-boot shell prompt
by Woody Wu 20 Mar '16

20 Mar '16

Hi list, in a running version of u-boot, assume i downloaded another version of u-boot into my RAM, then how can i jump to this new u-boot and run? I want to do this because the new version of u-boot that i hacked not yet stable so I don't want to actually flash it to my nand. BTW: my current u-boot version is quite old: 2009-11. -- Life is the only flaw in an otherwise perfect nonexistence -- Schopenhauer woody public key at http://subkeys.pgp.net:11371 (narkewoody(a)gmail.com)

1 0

Re: [U-Boot] [PATCH] Add CONFIG_GMAC_TX_DELAY=4 for OlinuXino Lime2
by Michael Haas 20 Mar '16

20 Mar '16

On 03/18/2016 08:02 PM, Karsten Merker wrote: > The installer supports a number of systems that can only load images > of limited size, therefore the installer includes only an > installation-related subset of all the kernel modules and i2c-mv64xxx > currently isn't among those. This hasn't been a practical problem up > to now, but being able to talk to the pmic is indeed something that > should be possible even in the installer. I'll try to address that in > the next days. Regards, Karsten Just an anecdote: I loaded i2c-mv64xx.ko which I had extracted from the deb and the olinuxino locked up. So now I'm trying to reproduce broken GBit, which is harder than expected. I managed to do it once right after the lockup in u-boot: tftp was slow and ran into timeouts. Then I typed 'reset' in the u-boot shell. u-boot started again and GBit was working again. Weird.

3 2

[U-Boot] [PATCH v3 0/4] dm: Add driver-model support for block drivers
by Simon Glass 20 Mar '16

20 Mar '16

Recent additions of the MMC and DISK uclasses have indicated that it is time to look at adding a uclass for block devices. This series does this and includes a few clean-ups to the partition code also. A block device is typically a child device of its storage parent. For example an MMC device will have a block-device child. A USB storage device may have multiple block-device children, one for each LUN. With this series only USB storage and 'host' are converted over to use the new support. Several more remain, including SCSI, IDE and MMC. Each of these should get its own uclass. The uclass implements only a few basic features. A few tests are added to check that things work as expected. The code size impact of switching to driver model for block devices is small. One benefit is that it becomes possible to enumerate all block devices, regardless of their type. Changes in v3: - Expand the commit message - Drop patches already applied Changes in v2: - Rename to blk_get_device_by_str() Simon Glass (4): dm: usb: Unbind old block devices when shutting down USB dm: sandbox: Switch over to use DM for block devices dm: sandbox: Drop the pre-DM host implementation dm: blk: Add tests for block devices configs/sandbox_defconfig | 1 + drivers/block/sandbox.c | 90 ---------------------------------------- drivers/usb/host/usb-uclass.c | 6 ++- test/dm/Makefile | 1 + test/dm/blk.c | 96 +++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 103 insertions(+), 91 deletions(-) create mode 100644 test/dm/blk.c -- 2.7.0.rc3.207.g0ac5344

1 8

[U-Boot] [PATCH v2 1/3] buildman: Allow branch names which conflict with directories
by Simon Glass 20 Mar '16

20 Mar '16

At present if you try to use buildman with the branch 'test' it will complain that it is unsure whether you mean the branch or the directory. This is a feature of the 'git log' command that buildman uses. Fix it by resolving the ambiguity. Signed-off-by: Simon Glass <sjg(a)chromium.org> Reviewed-by: Joe Hershberger <joe.hershberger(a)ni.com> --- Changes in v2: - Fix test breakage tools/buildman/func_test.py | 2 ++ tools/patman/gitutil.py | 5 +++++ 2 files changed, 7 insertions(+) diff --git a/tools/buildman/func_test.py b/tools/buildman/func_test.py index 75eb3a9..a0bd46c 100644 --- a/tools/buildman/func_test.py +++ b/tools/buildman/func_test.py @@ -255,6 +255,8 @@ class TestFunctional(unittest.TestCase): self.assertEqual(gitutil.use_no_decorate, True) def _HandleCommandGitLog(self, args): + if args[-1] == '--': + args = args[:-1] if '-n0' in args: return command.CommandResult(return_code=0) elif args[-1] == 'upstream/master..%s' % self._test_branch: diff --git a/tools/patman/gitutil.py b/tools/patman/gitutil.py index 5f1b4f6..e088bae 100644 --- a/tools/patman/gitutil.py +++ b/tools/patman/gitutil.py @@ -44,6 +44,11 @@ def LogCmd(commit_range, git_dir=None, oneline=False, reverse=False, cmd.append('-n%d' % count) if commit_range: cmd.append(commit_range) + + # Add this in case we have a branch with the same name as a directory. + # This avoids messages like this, for example: + # fatal: ambiguous argument 'test': both revision and filename + cmd.append('--') return cmd def CountCommitsToBranch(): -- 2.7.0.rc3.207.g0ac5344

2 7

[U-Boot] [PATCH] arm: socfpga: Nuke useless include
by Marek Vasut 20 Mar '16

20 Mar '16

The dwmmc.h include was forgotten during the migration of dwmmc probing to DM. Since the shiny DM is in place now, remove this relic of the past. Signed-off-by: Marek Vasut <marex(a)denx.de> Cc: Dinh Nguyen <dinguyen(a)opensource.altera.com> Cc: Chin Liang See <clsee(a)altera.com> --- arch/arm/mach-socfpga/misc.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm/mach-socfpga/misc.c b/arch/arm/mach-socfpga/misc.c index ce3ff0a..ebaa736 100644 --- a/arch/arm/mach-socfpga/misc.c +++ b/arch/arm/mach-socfpga/misc.c @@ -16,7 +16,6 @@ #include <asm/arch/reset_manager.h> #include <asm/arch/scan_manager.h> #include <asm/arch/system_manager.h> -#include <asm/arch/dwmmc.h> #include <asm/arch/nic301.h> #include <asm/arch/scu.h> #include <asm/pl310.h> -- 2.7.0

1 0