[U-Boot] [PATCH] keystone2: k2g: add env script to load firmware initramfs as part of boot flow

From: Murali Karicheri On K2G, the PCIe SerDes h/w is a re-use from other K2 devices and SerDes driver requires a firmware image to initialize the SerDes h/w device. This is firmware is part of the initramfs file that is loaded to memory in u-boot and passed to kernel as in

Re: [U-Boot] [PATCH] image-fit: switch ENOLINK to ENOENT

Hi Tom, Hi Jonathan, On 03.09.2016 00:30, Jonathan Gray wrote: > ENOLINK is not required by POSIX and does not exist on OpenBSD > and likely other systems. > > Signed-off-by: Jonathan Gray > --- > common/image-fit.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

Re: [U-Boot] [bug report] sunxi: booting from eMMC

Hi, On Wed, Sep 14, 2016 at 12:05:19PM +0200, Hans de Goede wrote: > Hi, > > On 13-09-16 13:50, Maxime Ripard wrote: > >Hi, > > > >On Mon, Sep 12, 2016 at 04:47:49PM +0200, Hans de Goede wrote: > >>On 12-09-16 15:56, Maxime Ripard wrote: > >>>Hi, > >>> > >>>On Mon, Sep 12, 2016 at 01:53:24PM

Re: [U-Boot] [PATCH] image-fit: switch ENOLINK to ENOENT

Hi Stefan, I also see the same error on our Armada board. It stems from the fact that boot_get_ramdisk in common/image.c treats a ENOLINK different from all other errors (which the patch changed into a ENOENT). The following patch fixes the problem on our board: diff --git a/common/image.c

Re: [U-Boot] [PATCH v2] apalis_t30: colibri_imx7: colibri_t30: fix ethernet functionality

On Wed, Sep 14, 2016 at 5:54 PM, Marcel Ziswiler wrote: > Since commit aa7a648747d8c704a9a81c9e493d386930724e9d > ("net: Stop including NFS overhead in defragment max") the following > has been reproducibly observed while trying to transfer data over TFTP: > > Load

Re: [U-Boot] U-Boot memory allocation problems with ast2500

Hi Maxim, On 14 September 2016 at 09:50, Maxim Sloyko wrote: > > > > On Fri, Sep 9, 2016 at 4:18 PM, Simon Glass wrote: >> >> Hi Maxim, >> >> On 9 September 2016 at 15:53, Maxim Sloyko wrote: >> > >> > Hi all, >> > >> > First,

Re: [U-Boot] does it make sense to define misc_init_r() not conditional on CONFIG_MISC_INIT_R?

Hi Robert, On 14 September 2016 at 07:16, Robert P. J. Day wrote: > > another oddity i noted in my travels ... in common/board_r.c, this: > > #ifdef CONFIG_MISC_INIT_R > misc_init_r,/* miscellaneous platform-dependent init */ > #endif > > suggests

Re: [U-Boot] [PATCH v3 4/5] colibri_t20: fix display configuration

On 09/15/2016 01:27 AM, Marcel Ziswiler wrote: Without this patch the following error will be shown: stdio_add_devices: Video device failed (ret=-22) As commit ec5507707a1d1e84056a6c864338f95f6118d3ca (video: tegra: Move to using simple-panel and pwm-backlight) states the Colibri T20 needs

Re: [U-Boot] [PATCH] net: smsc95xx: fix DM MAC address reading

On Thu, Sep 15, 2016 at 1:53 PM, Stephen Warren wrote: > From: Stephen Warren > > eth-uclass.c expects DM-capable Ethernet adapters to implement ops-> > read_rom_hwaddr(), or for some other mechanism to set pdata->enetaddr, or > for the user to set

[U-Boot] [PATCH 3/3] ARM: tegra: fix ULPI PHY on Ventana and Seaboard

From: Stephen Warren Commit ce02a71c2374 "tegra: dts: Sync tegra20 device tree files with Linux" enabled the ULPI USB port on Ventana, but made no attempt to ensure that U-Boot code could handle this. In practice, various code is missing, and various configuration options are

[U-Boot] [PATCH 1/3] ARM: tegra: fix USB ULPI PHY reset signal inversion confusion

From: Stephen Warren USB ULPI PHY reset signals are typically active low. Consequently, they should be marked as GPIO_ACTIVE_LOW in device tree, and indeed they are in the Linux kernel DTs, and in DT properties that U-Boot doesn't yet use. However, in DT properties that

[U-Boot] [PATCH] net: smsc95xx: fix DM MAC address reading

From: Stephen Warren eth-uclass.c expects DM-capable Ethernet adapters to implement ops-> read_rom_hwaddr(), or for some other mechanism to set pdata->enetaddr, or for the user to set environment variable $usbethaddr. Without any of these, it will refuse to initialize the

[U-Boot] [PATCH 2/3] ARM: tegra: fix USB controller aliases

From: Stephen Warren Some boards have a different set of USB controllers enabled in DT than the set referenced by /alias entries. This patch fixes that. For example, this avoids the following message while booting on Ventana, which is caused by the fact that the USB0

Re: [U-Boot] [PATCH v3 3/5] regulator: fixed: honour optionality of enable gpio

On 09/15/2016 03:30 AM, John Keeping wrote: On Thu, 15 Sep 2016 09:27:22 +0200, Marcel Ziswiler wrote: According to the binding documentation the fixed regulator enable GPIO is optional. However so far registration thereof failed if no enable GPIO was specified. Fix this by making it entirely

Re: [U-Boot] [PATCH v2] drivers: usb: fsl-dt-fixup: Fix the dt for multiple USB nodes in single traversal of device tree

On 09/15/2016 12:29 AM, york sun wrote: > On 09/14/2016 02:35 PM, Marek Vasut wrote: >> On 09/14/2016 07:22 AM, Sriram Dash wrote: From: Sriram Dash [mailto:sriram.d...@nxp.com] >>> >>> Hello Marek, >>> >>> Any comments? >> >> Waiting for York to review this. >> >> It's a bulky patch V2

Re: [U-Boot] [PATCH v3] drivers: usb: xhci-fsl: Implement Erratum A-010151 for FSL USB3 controller

On 09/15/2016 08:31 AM, Sriram Dash wrote: >> From: Marek Vasut [mailto:ma...@denx.de] >> On 09/14/2016 07:15 AM, Sriram Dash wrote: >>> Currently the controller by default enables the Receive Detect feature >>> in P3 mode in USB 3.0 PHY. However, USB 3.0 PHY does not reliably >>> support receive

Re: [U-Boot] [PATCH v2] apalis_t30: colibri_imx7: colibri_t30: fix ethernet functionality

On 09/15/2016 12:54 AM, Marcel Ziswiler wrote: > Since commit aa7a648747d8c704a9a81c9e493d386930724e9d > ("net: Stop including NFS overhead in defragment max") the following > has been reproducibly observed while trying to transfer data over TFTP: > > Load address: 0x80408000 > Loading: EHCI

Re: [U-Boot] [PATCH] imx: mx6: fix USB bmode to use reserved value

On 9/15/2016 3:04 PM, Stefan Agner wrote: > From: Stefan Agner > > Currently the bmode "usb" uses BOOT_CFG1 to 0x01, -which means > BOOT_CFG1[7:4] is set to b. According to Table 8-7 Boot > Device Selection this is NOR/OneNAND and not Reserved. > > Use 0x10 which

[U-Boot] [PATCH 2/2] ti_armv7_keystone2: Update addr_mon variable

As boot monitor contains a mkimage header, it can be loaded at any location. So, have a common addr_mon address across all keystone2 SoCs. And also making sure that boot monitor is installed early during default boot to avoid any overlapping with other images. Signed-off-by: Lokesh Vutla

[U-Boot] [PATCH 1/2] ARM: keystone2: Add support for parsing monitor header

Given that boot monitor image is being generated to a specific target location depending on the SoC and U-boot relies on addr_mon env variable to be aligned with boot monitor target location. When ever the target address gets updated in boot monitor, it is difficult to sync between u-boot and boot

[U-Boot] [PATCH 0/2] ARM: keystone2: Add support for parsing monitor header

This series adds support for parsing mkimage header on boot monitor image. Update boot-monitor code is available here[1] [1] git://git.ti.com/processor-firmware/ks2-boot-monitor.git Lokesh Vutla (2): ARM: keystone2: Add support for parsing monitor header ti_armv7_keystone2: Update addr_mon

[U-Boot] [PATCH] imx: mx6: fix USB bmode to use reserved value

From: Stefan Agner Currently the bmode "usb" uses BOOT_CFG1 to 0x01, -which means BOOT_CFG1[7:4] is set to b. According to Table 8-7 Boot Device Selection this is NOR/OneNAND and not Reserved. Use 0x10 which leads to b0001, which is a Reserved boot device. With

Re: [U-Boot] [PATCH 00/12] sh: change arch and boards code to generic board

Hi, Sorry, reply is late.. I will check your patches this weekend. Best regards, Nobuhiro 2016-08-31 18:44 GMT+09:00 Vladimir Zapolskiy : > On 06.08.2016 21:21, Vladimir Zapolskiy wrote: >> The changeset implements initial support of relocatable U-Boot code >> for SH2/SH3/SH4

[U-Boot] [PATCH] power: regulator: Add support for gpio regulators

Add support for gpio regulators. As of now this driver caters to gpio regulators with one gpio. Supports setting voltage values to gpio regulators and retrieving the values. Signed-off-by: Keerthy --- drivers/power/regulator/Kconfig | 8 ++

Re: [U-Boot] [PATCH 1/5] power: regulator: Add ctrl_reg and volt_reg fields for pmic

Hello Keerthy, On 09/14/2016 10:24 AM, Keerthy wrote: Hi Marczak, On Wednesday 14 September 2016 01:33 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/14/2016 06:28 AM, Keerthy wrote: The ctrl reg contains bit fields to enable and disable regulators, and volt_reg has the bit fields to

[U-Boot] [PATCH] arm: imx6: configure NoC on i.MX6DQP

The i.MX6DP and i.MX6QP incorporate NoC interconnect logic which needs to be configured in order to use external DDR memory. This patch enables the SPL to configure the necessary registers in accordance with the NXP engineering bulletin EB828. Signed-off-by: Filip Brozovic

[U-Boot] [PATCH] imx: iomux-v3: fix pad setup on i.MX6DQP when CONFIG_MX6QDL is defined

The CPU detection macro is_mx6dq returns 0 on an i.MX6DQP, so we need to check for it explicitly in order to correctly initialize the pads when CONFIG_MX6QDL is defined. Signed-off-by: Filip Brozovic --- arch/arm/imx-common/iomux-v3.c | 2 +- 1 file changed, 1 insertion(+),

[U-Boot] [PATCH v3 0/5] various fixes mainly for colibri_t20

This series addresses various issues as seen on Colibri T20. Please note that for successful Ethernet operation not only on Colibri T20 but also on Colibri T30 the following patch will still be required already waiting in Marek's usb tree: [PATCH v2] net: asix: Fix ASIX 88772B with driver model

[U-Boot] [PATCH v3 1/5] tegra: usb gadget: fix ci udc operation if not hostpc capable

The Tegra 2 aka T20 is not host PC capable. Therefore gate the define CONFIG_CI_UDC_HAS_HOSTPC in tegra-common-usb-gadget.h in case of CONFIG_TEGRA20. Signed-off-by: Marcel Ziswiler Acked-by: Stephen Warren --- Changes in v3: - Add Stephen's

[U-Boot] [PATCH v3 4/5] colibri_t20: fix display configuration

Without this patch the following error will be shown: stdio_add_devices: Video device failed (ret=-22) As commit ec5507707a1d1e84056a6c864338f95f6118d3ca (video: tegra: Move to using simple-panel and pwm-backlight) states the Colibri T20 needs updating too which this patch finally attempts

[U-Boot] [PATCH v3 2/5] simple panel: fix spelling of debug message

Fix spelling of debug message from cnnot to cannot. Signed-off-by: Marcel Ziswiler Acked-by: Anatolij Gustschin --- Changes in v3: - No change. Changes in v2: - Add Anatolij's ack. drivers/video/simple_panel.c | 2 +- 1 file changed, 1

Re: [U-Boot] interaction between CONFIG_CMD_SAVEENV and CONFIG_BOOTCOMMAND

Dear Wolfgang, Regarding your recommendations about U-Boot usage, I completely agree with that. In fact, In my description, I wouldn't give too many details, but your answer leads me to add some :-) As I told you, this "old" u-boot is used only as primary bootloader, and its main objective is

[U-Boot] [PATCH v3 5/5] colibri_t20: fix usb operation and controller order

Without this patch the following error will be shown: Colibri T20 # usb start starting USB... No controllers found This patch fixes USB operation and also the controller order as the CI UDC driver may only be instantiated on the first aka OTG port. Signed-off-by: Marcel Ziswiler

[U-Boot] [PATCH v3 3/5] regulator: fixed: honour optionality of enable gpio

According to the binding documentation the fixed regulator enable GPIO is optional. However so far registration thereof failed if no enable GPIO was specified. Fix this by making it entirely optional whether an enable GPIO is used. Signed-off-by: Marcel Ziswiler ---

[U-Boot] [PATCH 0/2] Add TOPIC Miami boards

These patches add support for the Miami range of boards from TOPIC. The boards are based on Xilinx Zynq SoCs, these two patches are for the 7-series, the Ultrascale MPSOC boards are to be added later. Please note that the "ps7_init_gpl" files are largely generated by a tool and as a result of

Re: [U-Boot] [PATCH v2] drivers: usb: fsl-dt-fixup: Fix the dt for multiple USB nodes in single traversal of device tree

>From: york sun >On 09/14/2016 02:35 PM, Marek Vasut wrote: >> On 09/14/2016 07:22 AM, Sriram Dash wrote: From: Sriram Dash [mailto:sriram.d...@nxp.com] >>> >>> Hello Marek, >>> >>> Any comments? >> >> Waiting for York to review this. >> >> It's a bulky patch V2 without changelog, shall

Re: [U-Boot] [PATCH 0/2] Add TOPIC Miami boards

Hi Mike, On 15.9.2016 08:02, Mike Looijmans wrote: > These patches add support for the Miami range of boards from TOPIC. > The boards are based on Xilinx Zynq SoCs, these two patches are for > the 7-series, the Ultrascale MPSOC boards are to be added later. > > Please note that the

Re: [U-Boot] [PATCH 1/5] power: regulator: Add ctrl_reg and volt_reg fields for pmic

On Wednesday 14 September 2016 05:26 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/14/2016 10:24 AM, Keerthy wrote: Hi Marczak, On Wednesday 14 September 2016 01:33 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/14/2016 06:28 AM, Keerthy wrote: The ctrl reg contains bit fields

Re: [U-Boot] [PATCH v3] drivers: usb: xhci-fsl: Implement Erratum A-010151 for FSL USB3 controller

>From: Marek Vasut [mailto:ma...@denx.de] >On 09/14/2016 07:15 AM, Sriram Dash wrote: >> Currently the controller by default enables the Receive Detect feature >> in P3 mode in USB 3.0 PHY. However, USB 3.0 PHY does not reliably >> support receive detection in P3 mode. >> Enabling the USB3

Re: [U-Boot] [PATCH 21/21] arm: imx: add i.MX6ULL 14x14 EVK board support

Hi Fabio, On Wed, Sep 14, 2016 at 1:13 AM, Fabio Estevam wrote: > Hi Jagan, > > On Tue, Sep 13, 2016 at 4:11 PM, Jagan Teki wrote: > > +int dram_init(void) > +{ > + gd->ram_size = imx_ddr_size(); >> >> Is this common call for all

Re: [U-Boot] [PATCH] image-fit: switch ENOLINK to ENOENT

On Thu, Sep 15, 2016 at 04:08:33PM +0200, Mario Six wrote: > Hi Stefan, > > I also see the same error on our Armada board. It stems from the fact that > boot_get_ramdisk in common/image.c treats a ENOLINK different from all other > errors (which the patch changed into a ENOENT). The following

Re: [U-Boot] [PATCH 0/2] Add TOPIC Miami boards

On 15-09-16 09:41, Mike Looijmans wrote: On 15-09-16 08:54, Michal Simek wrote: Hi Mike, On 15.9.2016 08:02, Mike Looijmans wrote: These patches add support for the Miami range of boards from TOPIC. The boards are based on Xilinx Zynq SoCs, these two patches are for the 7-series, the

Re: [U-Boot] [PATCH v3 3/5] regulator: fixed: honour optionality of enable gpio

Hello Marcel, On 09/15/2016 09:27 AM, Marcel Ziswiler wrote: According to the binding documentation the fixed regulator enable GPIO is optional. However so far registration thereof failed if no enable GPIO was specified. Fix this by making it entirely optional whether an enable GPIO is used.

Re: [U-Boot] [PATCH 0/2] Add TOPIC Miami boards

On 15-09-16 08:54, Michal Simek wrote: Hi Mike, On 15.9.2016 08:02, Mike Looijmans wrote: These patches add support for the Miami range of boards from TOPIC. The boards are based on Xilinx Zynq SoCs, these two patches are for the 7-series, the Ultrascale MPSOC boards are to be added later.

Re: [U-Boot] [PATCH] power: regulator: Add limits checking while setting voltage and current

Hello Keerthy, On 09/15/2016 10:54 AM, Keerthy wrote: Currently the specific set ops functions are directly called without any check for voltage/current limits for a regulator. Check for them and proceed. Signed-off-by: Keerthy ---

Re: [U-Boot] [PATCH] power: regulator: Add support for gpio regulators

Hello Keerthy, On 09/15/2016 10:25 AM, Keerthy wrote: Add support for gpio regulators. As of now this driver caters to gpio regulators with one gpio. Supports setting voltage values to gpio regulators and retrieving the values. Signed-off-by: Keerthy ---

[U-Boot] [PATCH] power: regulator: Add limits checking while setting voltage and current

Currently the specific set ops functions are directly called without any check for voltage/current limits for a regulator. Check for them and proceed. Signed-off-by: Keerthy --- drivers/power/regulator/regulator-uclass.c | 10 ++ 1 file changed, 10 insertions(+) diff

Re: [U-Boot] [PATCH] power: regulator: Add limits checking while setting voltage and current

On Thursday 15 September 2016 04:26 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/15/2016 10:54 AM, Keerthy wrote: Currently the specific set ops functions are directly called without any check for voltage/current limits for a regulator. Check for them and proceed. Signed-off-by:

Re: [U-Boot] [PATCH] power: regulator: Add limits checking while setting voltage and current

On Thursday 15 September 2016 04:38 PM, Keerthy wrote: On Thursday 15 September 2016 04:26 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/15/2016 10:54 AM, Keerthy wrote: Currently the specific set ops functions are directly called without any check for voltage/current limits for a

Re: [U-Boot] [PATCH v7 01/12] clk: Use dummy clk_get_by_* functions when CONFIG_CLK is disabled

Hi Paul, 2016-09-12 0:14 GMT+09:00 Paul Burton : > On 11/09/16 14:25, Masahiro Yamada wrote: >> Hi Paul, >> >> 2016-09-09 17:01 GMT+09:00 Paul Burton : >>> On 09/09/16 04:15, Masahiro Yamada wrote: 2016-09-08 15:47 GMT+09:00 Paul Burton

Re: [U-Boot] [PATCH 0/2] Add sdram capacity auto detect for rk3288

Hi Kever, With regards to the SPL size issue, I believe that the CONFIG_ROCKCHIP_SPL_BACK_TO_BROM option should work with all of the rk3288 boards. So if your patch causes unbootable SPL's because they're too big, then you should probably enable the BROM macro (and disable OF_PLATDATA). Firefly

[U-Boot] [PATCH] fixup! ARM: uniphier: fix DRAM size of LD21 SoC package

Signed-off-by: Masahiro Yamada --- arch/arm/mach-uniphier/boards.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-uniphier/boards.c b/arch/arm/mach-uniphier/boards.c index 1dececb..79b1d20 100644 ---

Re: [U-Boot] pull request: u-boot-uniphier/master

On Thu, Sep 15, 2016 at 05:40:52PM +0900, Masahiro Yamada wrote: > Hi Tom, > > I found a bug in this series. > If you have not pulled it in yet, > I'd like to cancel it > and do the 2nd round later. OK, thanks! > > Thanks, > > > > > 2016-09-14 23:13 GMT+09:00 Masahiro Yamada

[U-Boot] [PATCH] Revert "Increase default of CONFIG_SYS_MALLOC_F_LEN for SPL_OF_CONTROL"

This reverts commit 90c08d9e08c7a108ab904f3bbdeb558081757892. I took a closer look at this and found CONFIG_SYS_MALLOC_F_LEN=0x2000 was too much to enable SPL_OF_CONTROL. Perhaps 0x800 is enough, but the situation varies board by board. Postpone the decision until we come up with a good idea.

[U-Boot] [PATCH v2] power: regulator: Add support for gpio regulators

Add support for gpio regulators. As of now this driver caters to gpio regulators with one gpio. Supports setting voltage values to gpio regulators and retrieving the values. Signed-off-by: Keerthy --- Changes in v2: * Added states and voltages as part of plat data to have

Re: [U-Boot] [PATCH] power: regulator: Add support for gpio regulators

On Thursday 15 September 2016 03:04 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/15/2016 10:25 AM, Keerthy wrote: Add support for gpio regulators. As of now this driver caters to gpio regulators with one gpio. Supports setting voltage values to gpio regulators and retrieving the

Re: [U-Boot] [PATCH] power: regulator: Add support for gpio regulators

On 09/15/2016 12:34 PM, Keerthy wrote: On Thursday 15 September 2016 03:04 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/15/2016 10:25 AM, Keerthy wrote: Add support for gpio regulators. As of now this driver caters to gpio regulators with one gpio. Supports setting voltage values to

Re: [U-Boot] [PATCH] power: regulator: Add support for gpio regulators

On Thursday 15 September 2016 05:12 PM, Przemyslaw Marczak wrote: On 09/15/2016 12:34 PM, Keerthy wrote: On Thursday 15 September 2016 03:04 PM, Przemyslaw Marczak wrote: Hello Keerthy, On 09/15/2016 10:25 AM, Keerthy wrote: Add support for gpio regulators. As of now this driver caters

Re: [U-Boot] pull request: u-boot-uniphier/master

Hi Tom, I found a bug in this series. If you have not pulled it in yet, I'd like to cancel it and do the 2nd round later. Thanks, 2016-09-14 23:13 GMT+09:00 Masahiro Yamada : > Hi Tom, > > Here is the fist pull request from me > for the v2016.11 development

Re: [U-Boot] [PATCH v3 3/5] regulator: fixed: honour optionality of enable gpio

On Thu, 15 Sep 2016 09:27:22 +0200, Marcel Ziswiler wrote: > According to the binding documentation the fixed regulator enable GPIO > is optional. However so far registration thereof failed if no enable > GPIO was specified. Fix this by making it entirely optional whether an > enable GPIO is

Re: [U-Boot] [ANN] U-Boot v2016.09 is released

On Wed, Sep 14, 2016 at 11:32:07PM +0200, Daniel Schwierzeck wrote: > Hi Tom, > > Am 12.09.2016 um 18:21 schrieb Tom Rini: > > > > Another thing I'd like to call out, and ask for a little help with too > > is automated testing. The framework in test/py/test.py can be used on > > real hardware