Enable support for XIP (execute in place) of U-Boot or kernel image. There is
no need to copy image from flash to ram if flash supports execute in place.
Signed-off-by: Vikas Manocha
---
arch/arm/include/asm/spl.h | 1 +
With xip booting configuration, we don't need to copy the next image
(U-Boot or linux xipimage) from flash to sdram area.
Flash memory organization is like this:
spl-U-Boot: u-boot-spl.bin : 0x0800_
U-Boot :u-boot-dtb.bin : 0x0800_8000
linux :
This commit supports booting from stm32 internal nor flash. spl U-Boot
initializes the sdram memory, copies next image (e.g. standard U-Boot)
to sdram & then jumps to entry point.
Here are the flash memory addresses for U-Boot-spl & standard U-Boot:
- spl U-Boot: 0x0800_
Signed-off-by: Vikas Manocha
---
configs/stm32f746-disco_defconfig | 4
1 file changed, 4 deletions(-)
diff --git a/configs/stm32f746-disco_defconfig
b/configs/stm32f746-disco_defconfig
index 4322aad..a334d50 100644
--- a/configs/stm32f746-disco_defconfig
+++
This patchset adds support for XIP (execute in place) of U-Boot or kernel image
and enables it for stm32f7.
Vikas Manocha (6):
stm32f7: remove duplicate configs
stm32: stm32f7: add spl build support
SPL: Add XIP booting support
serial: stm32f7: disable overrun
spl: stm32f7: add kernel
Add the 'cdns,trigger-address' property to the cadence QSPI device
node for Texas Instruments K2G SoC devices.
Signed-off-by: Jason A. Rush
---
arch/arm/dts/keystone-k2g.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/keystone-k2g.dtsi
Add the 'cdns,trigger-address' property to the cadence QSPI device
node for the ST STV0991 application board.
Signed-off-by: Jason A. Rush
---
arch/arm/dts/stv0991.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/stv0991.dts b/arch/arm/dts/stv0991.dts
This patch series addresses an issue with the indaddrtrig
register on the Cadence QSPI device being programmed with
the wrong value for the socfpga arch. Adopting the
trigger-address DT bindings from the Linux kernel allows
the indaddrtrig register to be set independently from the
ahbbase as
The socfpga arch uses a different value for the indaddrtrig reg than
the ahbbase address. Adopting the cdns,trigger-address DT bindings
from the Linux kernel allows the trigger-address to be set correctly
on the socfpga arch.
Tested on Terasic SoCKit dev board (Altera Cyclone V)
Signed-off-by:
I missed this when I added support for BMIPS UART driver and it's needed to
achieve a real 115200 8N1 setup.
Signed-off-by: Álvaro Fernández Rojas
---
v2: fix commit title (missed bcm6345)
drivers/serial/serial_bcm6345.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
I missed this when I added support for BMIPS UART driver and it's needed to
achieve a real 115200 8N1 setup.
Signed-off-by: Álvaro Fernández Rojas
---
drivers/serial/serial_bcm6345.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/serial/serial_bcm6345.c
Hi Hector,
On Thu, May 18, 2017 at 2:06 PM, Palacios, Hector
wrote:
> Hi Fabio,
>
> On Thu, 18 May 2017 17:52, Fabio Estevam wrote:
>> I got very slow performance with MX6UL when U-Boot is loaded via
>> serial download mode.
>
> That's it, actually!
> I was booting the
Hi Fabio,
On Thu, 18 May 2017 17:52, Fabio Estevam wrote:
> I got very slow performance with MX6UL when U-Boot is loaded via
> serial download mode.
That's it, actually!
I was booting the target via USB, booting from the NAND shows normal
performance.
> This gets fixed by setting the SMP bit:
Hi Tom,
On 18 May 2017 at 10:33, Tom Warren wrote:
> Simon,
>
> What testing did you do?
This was tested on Nyan. I'd be grateful for any Tegra review /
testing that you can arrange. It seems mighty quiet around here :-)
>
> Tom
> --
> nvpublic
Regards,
Simon
Simon,
What testing did you do?
Tom
--
nvpublic
> -Original Message-
> From: s...@google.com [mailto:s...@google.com]
> Sent: Thursday, May 18, 2017 9:01 AM
> To: Simon Glass
> Cc: Alban Bedel ; Max Krummenacher
>
On 05/18/2017 01:23 AM, Michal Simek wrote:
Some tests depends on echo command to be present.
diff --git a/test/py/tests/test_hush_if_test.py
b/test/py/tests/test_hush_if_test.py
+@pytest.mark.buildconfigspec('cmd_echo')
@pytest.mark.parametrize('expr,result', subtests)
def
On 05/18/2017 01:23 AM, Michal Simek wrote:
All tests in test_hush_if_test depends on hush parser to be
present. This patch simplify test dependencies by using global
pytestmark.
Acked-by: Stephen Warren
___
U-Boot mailing list
When binding a new MMC device, make sure that it has the required
operations. Since for now we still support *not* having the operations
(with CONFIG_DM_MMC_OPS not enabled) it makes sense to add this check.
Signed-off-by: Simon Glass
---
drivers/mmc/mmc-uclass.c | 4
1
These support the flat device tree. We want to use the dev_read_..()
prefix for functions that support both flat tree and live tree. So rename
the existing functions to avoid confusion.
In the end we will have:
1. dev_read_addr...()- works on devices, supports flat/live tree
2.
On Sun, Apr 23, 2017 at 4:10 AM, Simon Glass wrote:
> We should not call out to board code from drivers. With driver model,
> mmc_power_init() already has code to use a named regulator, but the
> legacy code path remains. Update the code to make this clear.
>
I don't like this
Sometimes it is useful to be able to find a block device without also
probing it. Add a function for this as well as the associated test.
Signed-off-by: Simon Glass
---
drivers/block/blk-uclass.c | 15 +--
include/blk.h | 15 ++-
Enable CONFIG_DM_MMC_OPS and CONFIG_BLK for all Tegra devices. This moves
Tegra to use driver model fully for MMC.
Signed-off-by: Simon Glass
---
board/toradex/common/tdx-cfg-block.c | 2 +-
configs/apalis-tk1_defconfig | 2 -
configs/apalis_t30_defconfig |
On Wed, May 3, 2017 at 5:36 AM, Simon Glass wrote:
> Hi Andy,
>
> On 24 April 2017 at 02:04, Andy Shevchenko wrote:
>> On Mon, Apr 24, 2017 at 5:02 AM, Simon Glass wrote:
>>> At present this code is inline. Move it into a function
We do not need to probe the block device here, so avoid doing so. The MMC
device itself must be active, but the block device can come later.
Signed-off-by: Simon Glass
---
drivers/mmc/mmc-uclass.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
Applied to
The intention with block devices is that the device number (devnum field
in its descriptor) matches the alias of its parent device. For example,
with:
aliases {
mmc0 = "/sdhci@700b0600";
mmc1 = "/sdhci@700b0400";
}
we expect that the block devices
This function is called when the MMC block device is being probed. There
is a recursive call in this function since find_mmc_device() itself can
cause the MMC device to be probed.
Admittedly the MMC device should already be probed, since we would not be
probing its child otherwise, but the
Move this group of address-related functions into a new file. These use
the flat device tree. Future work will provide new versions of these which
can support the live tree.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/core/Makefile | 2
This function should not be used outside the core driver-model code.
Update it to use dm_scan_fdt_dev() instead.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/gpio/atmel_pio4.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Applied
This function is only used in one place. It is better to just declare it
internally since there is a simpler replacement for use outside the
driver-model core code.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/core/root.c | 17
At present devices use a simple integer offset to record the device tree
node associated with the device. In preparation for supporting a live
device tree, which uses a node pointer instead, refactor existing code to
access this field through an inline function.
Signed-off-by: Simon Glass
With live tree we need a struct device_node * to reference a node. With
the existing flat tree, we need an int offset. We need to unify these into
a single value which can represent both.
Add an ofnode union for this and adjust existing code to move to this.
Signed-off-by: Simon Glass
This core function will need to work with a live tree also. Update it to
accept an ofnode instead of an offset.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Cut the series down to only prepare the way for live tree
- Drop all live tree changes
- Adjust
On Thu, May 18, 2017 at 09:55:41AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On 17 May 2017 at 15:33, Tom Rini wrote:
> > On Wed, May 17, 2017 at 08:23:09AM -0600, Simon Glass wrote:
> >
> >> We should not have an arch-specific header file in common.h. Instead, use
> >> the
Hi Tom,
On 17 May 2017 at 15:33, Tom Rini wrote:
> On Wed, May 17, 2017 at 08:23:09AM -0600, Simon Glass wrote:
>
>> We should not have an arch-specific header file in common.h. Instead, use
>> the asm/hardware.h header to provide the required declarations, and drop
>> the
On 2017-05-18 17:37, Jagan Teki wrote:
> On Thu, May 18, 2017 at 9:04 PM, Manfred Schlaegl
> wrote:
>> On 2017-05-18 16:59, Lothar Waßmann wrote:
>>> Manfred Schlaegl wrote:
>>>
On 2017-05-17 06:13, Lokesh Vutla wrote:
>
Hi Hector,
On Thu, May 18, 2017 at 11:43 AM, Hector Palacios
wrote:
> In case I wasn't clear, I don't have any memory mapping problems. I have one
> single
> DDR chip, which internally uses two dies and two chip selects. Setting
> CONFIG_NR_DRAM_BANKS to 1 (and full
On Thu, May 18, 2017 at 5:47 PM, Fabio Estevam wrote:
> On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
>> From: Jagan Teki
>>
>> Fix to give space between of and bs of dd command.
>>
>> Cc: Stefano Babic
>>
On Thu, May 18, 2017 at 9:04 PM, Manfred Schlaegl
wrote:
> On 2017-05-18 16:59, Lothar Waßmann wrote:
>> Manfred Schlaegl wrote:
>>
>>> On 2017-05-17 06:13, Lokesh Vutla wrote:
On Tuesday 16 May 2017 07:59 PM, Manfred
On 2017-05-18 16:59, Lothar Waßmann wrote:
> Manfred Schlaegl wrote:
>
>> On 2017-05-17 06:13, Lokesh Vutla wrote:
>>>
>>>
>>> On Tuesday 16 May 2017 07:59 PM, Manfred Schlaegl wrote:
On 2017-05-11 08:53, Lokesh Vutla wrote:
>
>
> On Wednesday 10
Hi,
The original commit for the MCF54418TWR ColdFire development board
support defined a 'CONFIG_SYS_FAULT_ECCONFIG_SYS_NO_FLASHHO_LINK_DOWN'
which obviously has a rogue 'CONFIG_SYS_NO_FLASH' embedded in the
intended 'CONFIG_SYS_FAULT_ECHO_LINK_DOWN' define.
Signed-off-by: Lothar Waßmann
Hi Marcin,
On 18/05/2017 16:57, Marcin Niestroj wrote:
> Hi Stefano,
>
> On 18.05.2017 16:28, Stefano Babic wrote:
>> Hi Marcin,
>>
>> even if it was already merged (and maybe I am guilty of it because I
>> have not noted before), it is completely crazy that a board is stored
>> inside the SOC
Manfred Schlaegl wrote:
> On 2017-05-17 06:13, Lokesh Vutla wrote:
> >
> >
> > On Tuesday 16 May 2017 07:59 PM, Manfred Schlaegl wrote:
> >> On 2017-05-11 08:53, Lokesh Vutla wrote:
> >>>
> >>>
> >>> On Wednesday 10 May 2017 07:11 PM, Manfred Schlaegl wrote:
>
Hi Stefano,
On 18.05.2017 16:28, Stefano Babic wrote:
Hi Marcin,
even if it was already merged (and maybe I am guilty of it because I
have not noted before), it is completely crazy that a board is stored
inside the SOC directory. The litesom board is in fact in
Hi Fabio,
On 05/17/2017 11:08 PM, Fabio Estevam wrote:
> Hi Hector,
>
> On Wed, May 17, 2017 at 5:50 AM, Palacios, Hector
> wrote:
>
>> The code is on Github [1] (well, not the dual-die DDR3 yet) but there isn't
>> much to see for this issue other than:
>
> I looked
Hi Tim,
On 18/05/2017 16:22, Tim Harvey wrote:
> On Thu, May 18, 2017 at 2:12 AM, Stefano Babic wrote:
>> On 12/05/2017 21:58, Tim Harvey wrote:
>>> There is no dedicated reset signal wired up for the MX6QDL thus if the
>>> bootloader enables the link we need some special
Hi Marcin,
even if it was already merged (and maybe I am guilty of it because I
have not noted before), it is completely crazy that a board is stored
inside the SOC directory. The litesom board is in fact in
./arch/arm/cpu/armv7/mx6/litesom.c, and there is nothing that justify
this. The code has
On Thu, May 18, 2017 at 2:12 AM, Stefano Babic wrote:
> On 12/05/2017 21:58, Tim Harvey wrote:
>> There is no dedicated reset signal wired up for the MX6QDL thus if the
>> bootloader enables the link we need some special handling to get the core
>> back into a state where it is
On 2017-05-17 06:13, Lokesh Vutla wrote:
>
>
> On Tuesday 16 May 2017 07:59 PM, Manfred Schlaegl wrote:
>> On 2017-05-11 08:53, Lokesh Vutla wrote:
>>>
>>>
>>> On Wednesday 10 May 2017 07:11 PM, Manfred Schlaegl wrote:
Using u-boot-2017.05 on i.MX6UL we ran into following problem:
I have u-boot 2017.03 and 2017.05 detecting the keyboard in 32 bit
mode. But in 64 bit mode the keyboard is never detected.
Under the 32 bit mode, 4 items are detected using "usb tree". In 64
bit mode only 3 items are detected.
I have tried "usb start" and "usb reset".
Any suggestions would be
One can obtain those variables using next commands:
$ fastboot getvar cpu
$ fastboot getvar secure
$ fastboot getvar board_rev
$ fastboot getvar userdata_size
Those variables are needed for fastboot.sh script.
Signed-off-by: Sam Protsenko
---
This patch reuses new option, which allows us to expose variables
from environment to "fastboot getvar" command. Those variables must be
of "fastboot.%s" format.
Signed-off-by: Sam Protsenko
---
arch/arm/include/asm/omap_common.h | 2 +
arch/arm/mach-omap2/utils.c
One can obtain those variables using next commands:
$ fastboot getvar cpu
$ fastboot getvar secure
$ fastboot getvar board_rev
$ fastboot getvar userdata_size
Those variables are needed for fastboot.sh script.
Signed-off-by: Sam Protsenko
---
fastboot.sh is a script used for flashing Android images for TI boards
(and can be found in corresponding AOSP sources). This script relies on
some fastboot variables, which can be accessed with "fastboot getvar"
command.
This patch series exports those variables, which fastboot.sh script
relies
On Thu, May 18, 2017 at 9:22 AM, Fabio Estevam wrote:
> Last time I tested the pmic commands were gone. Were you able to
> access the PMIC via the 'pmic' commands?
Just tested your latest version and the 'pmic' command is gone, so
this needs to be fixed. Thanks
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> From: Jagan Teki
>
> Now, SabreSD support SPL for all cpu types and the only configuration
> option, So renamed mx6sabresd_spl_defconfig to mx6sabresd_defconfig
>
> Signed-off-by: Jagan Teki
Hi Jagan,
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> -static void setup_iomux_enet(void)
> -{
> - SETUP_IOMUX_PADS(enet_pads);
> -
> - /* Reset AR8031 PHY */
> - gpio_direction_output(IMX_GPIO_NR(1, 25) , 0);
> - mdelay(10);
> -
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> From: Jagan Teki
>
> Enable CONFIG_DM_REGULATOR for i.MX6 SabreSD boards.
>
> Signed-off-by: Jagan Teki
Reviewed-by: Fabio Estevam
Hi Jagan,
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> From: Jagan Teki
>
> (1) Enable
> DM_I2C
> DM_PMIC
> DM_PMIC_PFUZE100
> (2) Removed
> setup_i2c
> power_init_board
>
> I2C Log:
>
> => i2c bus
> Bus 0:
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> From: Jagan Teki
>
> Retrive imx6qdl-sabresd.dtsi from Linux with last commit
> "ARM: dts: imx6qdl-sabresd: Set LDO regulator supply"
> (sha1: c23568dbbda110a5c79c6537cc81ed7af5444b64)
Could you
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> From: Jagan Teki
>
> Fix to give space between of and bs of dd command.
>
> Cc: Stefano Babic
> Cc: Michael Trimarchi
> Signed-off-by: Jagan Teki
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> From: Jagan Teki
>
> I2C support not needed for SPL build, hence removed the
> CONFIG_SPL_I2C_SUPPORT from mx6sabresd_spl_defconfig
>
> Cc: Stefano Babic
> Cc: Fabio Estevam
Hi Jagan,
On Thu, May 18, 2017 at 8:00 AM, Jagan Teki wrote:
> From: Jagan Teki
>
> no-SPL target defconfigs are droped in below commit
> and forgot to update the same on MAINTAINERS F: list
> "mx6sabresd: Remove non-SPL targets"
> (sha1:
Hi Marek,
looks good, as small comment below...
On 12.05.2017 16:10, Marek Behún wrote:
> The DDR3 training code for Marvell A38X currently computes 1t timing
> when given board topology map of the Turris Omnia, but Omnia needs 2t.
>
> This patch adds support for enforcing the 2t timing in
Hi Marek,
On 13.05.2017 11:54, Andreas Färber wrote:
+/* Default boot environment. */
+#define CONFIG_BOOTCOMMAND \
+ "i2c dev 1; " \
+ "i2c read 0x2a 0x9 1 0x00F0; "\
+ "setexpr.b rescue *0x00F0; " \
+ "if
On 18 May 2017 at 14:20, Tom Rini wrote:
> On Thu, May 18, 2017 at 11:50:23AM +0300, Sam Protsenko wrote:
>> On 18 May 2017 at 01:20, Tom Rini wrote:
>> > On Wed, May 17, 2017 at 08:20:47PM +0300, Sam Protsenko wrote:
>> >
>> >> This patch adds support for
This patch adds support for flashing zImage to the Android boot
partition on eMMC.
Usage:
$ fastboot flash zImage
It's based on [1].
[1]
http://omapzoom.org/?p=repo/u-boot.git;a=commit;h=3393b908c1e848bba3706612cbe50aa8970720b3
Signed-off-by: Sam Protsenko
On Thu, May 18, 2017 at 11:50:23AM +0300, Sam Protsenko wrote:
> On 18 May 2017 at 01:20, Tom Rini wrote:
> > On Wed, May 17, 2017 at 08:20:47PM +0300, Sam Protsenko wrote:
> >
> >> This patch adds support for flashing zImage to the Android boot
> >> partition on eMMC.
> >
Previous to MC v10.x, port mac address was specified via DPL. Since
newer MC versions are compatible with old style DPLs, make the u-boot
env mac addresses visible there. This applies only to DPLs that have an
older version.
DPLs use 32 bit values for specifying MAC addresses. U-boot environment
DPAA2 platforms boot the Management Complex based on the u-boot env
variable "mcinitcmd". Instead of doing this step on each platform
individually, define a reset_phy function in the MC driver, since it's
semantically tied to it and it gets called at a later moment, when all
board PHY devices have
From: Fabio Estevam
mx6sabresd only supports SPL mode now, so update the README file
accordingly.
Signed-off-by: Fabio Estevam
---
board/freescale/mx6sabresd/README | 84 +--
1 file changed, 28 insertions(+), 56
From: Fabio Estevam
As mx6sabresd only supports SPL target now, there is no need to
keep the 'spl' in the name of the target, so simply rename it
to mx6sabresd_defconfig.
Signed-off-by: Fabio Estevam
---
configs/{mx6sabresd_spl_defconfig =>
From: Fabio Estevam
Only configs/mx6sabresd_defconfig is supported now, so update the
MAINTAINERS file accordingly.
Signed-off-by: Fabio Estevam
---
board/freescale/mx6sabresd/MAINTAINERS | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
From: Jagan Teki
Enable DM_USB and removed non-DM_USB related config options.
Signed-off-by: Jagan Teki
Reviewed-by: Fabio Estevam
---
arch/arm/cpu/armv7/mx6/Kconfig | 1 +
From: Jagan Teki
Add initial devicetree support for i.MX6 DualLite Sabresd board.
Signed-off-by: Jagan Teki
---
board/freescale/mx6sabresd/spl.c | 2 ++
configs/mx6sabresd_spl_defconfig | 2 +-
2 files changed, 3 insertions(+), 1
From: Jagan Teki
Since SabreSD is supporting fdt, there is no use
of printing the board name explicitly using checkboard
because dtb supported u-boot will print model like this
Model: Freescale i.MX6 Quad Plus SABRE Smart Device Board
Signed-off-by: Jagan Teki
From: Jagan Teki
Add initial devicetree support for i.MX6 Quad Sabresd board.
(1) Added config options
CONFIG_OF_CONTROL=y
CONFIG_DM_GPIO=y
CONFIG_DM_MMC=y
CONFIG_BLK is not set
CONFIG_DM_MMC_OPS is not set
CONFIG_PINCTRL=y
From: Jagan Teki
Add initial devicetree support for i.MX6 Quad Plus Sabresd board.
Signed-off-by: Jagan Teki
---
arch/arm/cpu/armv7/mx6/Kconfig | 3 +++
board/freescale/mx6sabresd/spl.c | 12
From: Jagan Teki
Now SabreSD board support SPL with U-Boot proper devicetree
enabled, so update the README according with images generated
with respective builds.
"Booting from eMMC" still need to test and update README.
Signed-off-by: Jagan Teki
From: Jagan Teki
Retrive imx6dl-sabresd.dts from Linux with last commit
"ARM: dts: imx: share pad macro names between imx6q and imx6dl"
(sha1: c56009b2f6134e5943a03cf26e4d7fce9745d56b)
Signed-off-by: Jagan Teki
---
arch/arm/dts/Makefile
From: Jagan Teki
Now, SabreSD support SPL for all cpu types and the only configuration
option, So renamed mx6sabresd_spl_defconfig to mx6sabresd_defconfig
Signed-off-by: Jagan Teki
---
board/freescale/mx6sabresd/MAINTAINERS
From: Jagan Teki
I2C support not needed for SPL build, hence removed the
CONFIG_SPL_I2C_SUPPORT from mx6sabresd_spl_defconfig
Cc: Stefano Babic
Cc: Fabio Estevam
Cc: Michael Trimarchi
From: Jagan Teki
Moved CONFIG_SYS_I2C_MXC from include/configs/mxsabresd.h
to imx6 sabresd defconfigs.
Signed-off-by: Jagan Teki
Reviewed-by: Fabio Estevam
---
configs/mx6sabresd_spl_defconfig | 1 +
From: Jagan Teki
(1) Enable
DM_I2C
DM_PMIC
DM_PMIC_PFUZE100
(2) Removed
setup_i2c
power_init_board
I2C Log:
=> i2c bus
Bus 0: i2c@021a
Bus 1: i2c@021a4000
08: pfuze100@08, offset len 1, flags 0
Bus 2: i2c@021a8000
=> i2c dev 1
From: Jagan Teki
Retrive imx6qp-sabresd.dts from Linux with last commit
"ARM: dts: imx6qp-sabresd: Set reg_arm regulator supply"
(sha1: 448548174caaa04ffe9da4da9326052eb8791a9b)
Signed-off-by: Jagan Teki
---
arch/arm/dts/Makefile
From: Jagan Teki
- Give proper tab alignment for display_info_t structure
- Add tab spaces UART_PAD_CTRL and SPI_PAD_CTRL
- Give proper alignment of reg init values on setup_display
- Add space and newline on board_init_f
- Add static qualifier for file scope
From: Jagan Teki
(1) Enable DM_ETH
(2) Droped board_eth_init
Signed-off-by: Jagan Teki
Reviewed-by: Fabio Estevam
---
arch/arm/cpu/armv7/mx6/Kconfig | 1 +
board/freescale/mx6sabresd/mx6sabresd.c | 45
From: Jagan Teki
Moved CONFIG_FEC_MXC from include/configs/mxsabresd.h
to imx6 sabresd and sabreauto defconfigs.
Signed-off-by: Jagan Teki
Reviewed-by: Fabio Estevam
---
configs/mx6dlsabreauto_defconfig | 2 ++
From: Jagan Teki
Enable CONFIG_DM_REGULATOR for i.MX6 SabreSD boards.
Signed-off-by: Jagan Teki
---
arch/arm/cpu/armv7/mx6/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/cpu/armv7/mx6/Kconfig
From: Jagan Teki
Retrive imx6q-sabresd.dts from Linux with last commit
"ARM: dtsi: enable ahci sata on imx6q platforms"
(sha1: 0fb1f804269e549b556b475c8655bc862c220622)
Signed-off-by: Jagan Teki
---
arch/arm/dts/Makefile | 1 +
From: Jagan Teki
Retrive imx6qdl-sabresd.dtsi from Linux with last commit
"ARM: dts: imx6qdl-sabresd: Set LDO regulator supply"
(sha1: c23568dbbda110a5c79c6537cc81ed7af5444b64)
Signed-off-by: Jagan Teki
---
From: Jagan Teki
Retrive imx6qp.dtsi from Linux with last commit
"ARM: dts: imx6qp: add PRG nodes and hook up to IPUs"
(sha1: 54458dac349f72dd9a4fd816619bde0bab40841d)
Signed-off-by: Jagan Teki
---
arch/arm/dts/imx6qp.dtsi | 149
From: Jagan Teki
Fix to give space between of and bs of dd command.
Cc: Stefano Babic
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
Reviewed-by: Fabio Estevam
---
From: Jagan Teki
no-SPL target defconfigs are droped in below commit
and forgot to update the same on MAINTAINERS F: list
"mx6sabresd: Remove non-SPL targets"
(sha1: e2bab4b9ea3c9ab59c1ba064263ee0863cba112e)
Signed-off-by: Jagan Teki
---
From: Jagan Teki
Compared to previous series, this series
- Add dts files directly from Linux
- Moved spl code in separate file spl.c
- Add patches ontop of 'Fabio' changes.
- Droped file/drirectory rename changes
Changes for v6:
- rebase on u-boot-imx/master
- Fixed
On Thu, May 18, 2017 at 2:58 AM, Jagan Teki wrote:
> Missing to update MAINTAINERS file, will change it here and send along
> with the series, is that OK?
Let me take care of it as I do have other changes as part of moving
mx6sabresd to SPL.
Will send these patches
The function mcs7830_recv_common() returns a negative value on error, 0
or positive value on success.
Fix the condition for calling the function
net_process_received_packet().
The function mcs7830_recv() is always returning 0.
Update the return value of mcs7830_recv() to reflect the function's
Hi Jagan,
On Thu, May 18, 2017 at 5:30 AM, Jagan Teki wrote:
> I think this backlight IMX_GPIO_NR(1, 21) gpio is related to board
> code here in U-boot, couldn't see the node related to this on dts.
In U-Boot MX6QDL_PAD_SD1_DAT3__GPIO1_IO21 is used to as GPIO and when
On 18/05/2017 12:28, Sébastien Szymanski wrote:
> Hi,
>
> On 05/18/2017 12:13 PM, Stefano Babic wrote:
>> On 18/05/2017 10:53, Stefano Babic wrote:
>>> On 24/04/2017 23:20, Alexey Ignatov wrote:
Aliases must be present for USB gadget with DM_USB. Without this,
usb_setup_ehci_gadget()
Hi,
On 05/18/2017 12:13 PM, Stefano Babic wrote:
> On 18/05/2017 10:53, Stefano Babic wrote:
>> On 24/04/2017 23:20, Alexey Ignatov wrote:
>>> Aliases must be present for USB gadget with DM_USB. Without this,
>>> usb_setup_ehci_gadget() fails because it can't find required devices
>>> in
Hi,
On Thu, 18 May 2017 11:15:08 +0200 Stefano Babic wrote:
> On 11/05/2017 11:34, Peng Fan wrote:
> > Each time set_state is called, a new piece memory will
> > be allocated for pin_data, but not freed, this will
> > incur memory leak.
> >
> > When error, the devm API could not free memory
101 - 200 of 230 matches
Mail list logo