Skip to content

imx: vybrid: Update BK4 and PCM052 boards to only use DM/DTS

Stefan Agner u-boot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v2 Latest6 of 21 patches 0 repliesNew

6 of 21 patches are in this archive. The cover letter announces 21.

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/21net: FEC: Add compatible for vybrid (vf610) to reuse fec_mxc.c driver+0 -00 replies
2/21net: Kconfig: FEC: Add dependency on VF610+0 -00 replies
3/21vybrid: ddr: Extend vf610-pinfunc.h with DDR pads definitions+0 -00 replies
4/21vybrid: clock: Provide enable_i2c_clk() function for Vybrid+0 -01 reply
4/21vybrid: clock: Provide enable_i2c_clk() function for Vybrid+0 -01 reply
8/21ARM: DTS: vybrid: Update vf.dtsi file to descibe more vf610 hardware+0 -00 replies

Reviews trailers per patch

4 of 6 patches have a Reviewed-by or Acked-by.

PatchStefan Agner
1/21R-b
2/21R-b
3/21R-b
4/21
4/21
8/21R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [U-Boot] [PATCH v2 00/21] imx: vybrid: Update BK4 and PCM052 boards to only use DM/DTS
Quoted 64 lines · Lukasz Majewski
Quoted 51 lines · On Mon, 21 Jan 2019 09:33:23 +0100 Lukasz Majewski <[email protected]> wrote:

Hi Stefan,

Quoted 26 lines

This patch series converts PCM052 and BK4 to use Driver Model and Device Tree.

Some notable changes:
- The way how MAC address is read from fuses can now be adjusted
- DTS improvement/sync with kernel (also extract u-boot specific properties)
- Using generic code instead of one from board

The output of u-boot boot:
U-Boot 2019.01-rc3-00076-gc149229be0 (Jan 14 2019 - 08:38:48 +0100)

CPU: Freescale Vybrid VF610 at 396 MHz
Reset cause: POWER ON RESET
Model: Liebherr (LVF) BK4 Vybrid Board
Board: BK4r1 (L333)
DRAM:  512 MiB
NAND:  1024 MiB
MMC:   FSL_SDHC: 0
Loading Environment from NAND... OK
In:    serial at 40028000
Out:   serial at 40028000
Err:   serial at 40028000
Net:   eth0: fec at 400d0000, eth1: fec at 400d1000

Enter passphrase to stop autoboot, booting in 3 seconds

Quoted 7 lines

Buildman CI:
./tools/buildman/buildman.py --branch=HEAD~4 vf610 mx6 vybrid --detail --verbose --show_errors --force-build --count=21 --output-dir=../BUILD/

Travis-CI:
https://travis-ci.org/lmajewski/u-boot-dfu/jobs/481963146

I've bisected this error, and it turned out that the following patch is the culprit (on top of which I've rebased my work):

"fs: fat: dynamically allocate memory for temporary buffer"

Without this patch applied:
https://travis-ci.org/lmajewski/u-boot-dfu/builds/482301236

With:
https://travis-ci.org/lmajewski/u-boot-dfu/builds/482297604

Test: test/py qemu_arm

Error is in: "test_efi_selftest"

Quoted 9 lines

Executing 'block device' /home/travis/build/lmajewski/u-boot-dfu/lib/efi_selftest/efi_selftest_block_device.c(386):
TODO: Wrong volume label 'xxa1', expected 'U-BOOT TEST' /home/travis/build/lmajewski/u-boot-dfu/lib/efi_selftest/efi_selftest_block_device.c(413):
ERROR: Unexpected file content /home/travis/build/lmajewski/u-boot-dfu/lib/efi_selftest/efi_selftest.c(110):
ERROR: Executing 'block device' failed

Quoted 4 lines

And the full travis-ci build without the above patch (all "green"):

https://travis-ci.org/lmajewski/u-boot-dfu/builds/482308817

I skimmed through the rest of the patchset but did not do a full review. But I am ok with the rest of the patches.

I also tested the patchset on our Colibri VF50, and U-Boot seems to work fine!

Thanks for your work!

--
Stefan