May 2018 - U-Boot

[U-Boot] [PATCH v5 0/9] Add support for DM_USB for TI's DRA7 EVMs and AM57 EVMs platforms
by Jean-Jacques Hiblot 17 May '18

17 May '18

Supporting DM USB is required to support DM_ETH and USB network adapters with the same binary. This series adds support for DM_USB for the DRA7/AM57 families. As a bonus it adds support for USB3. limitation: - only Host mode is supported. The Device mode can be added later. Tested on: - dra7 evm - dra71 evm - dra72 evm - dra72 evm rev C - dra76 evm - AM572 evm Changes in v5: - Rebased on latest u-boot - Removed patches that have already been merged Changes in v4: - Fix word missing in commit log - Remove dependency on MISC - Renamed the commit (DM_USB is already enabled, the only missing option is for the USB2 phy driver) - Remove dependency on MISC - Remove omap specific glue layer and use dwc3-of-simple glue layer Changes in v3: - in syscon_regmap_lookup_by_phandle(), use dev_dbg() instead of printf() - added unit test for syscon_regmap_lookup_by_phandle() Changes in v2: - Add USB3 support to ti-pipe3-phy driver - omap-usb2-phy: Implement power_on and power_off callbacks - am57xx boards: when DM_USB is used, turn on the required USB clocks - split dts changes in 2 commits: one for binding the children of ocp2scp@4a080000, and one to disable USB1 on all DRA7 EVMs - Instead of disabling USB1 port in dts files, use *-u-boot.dtsi files - Enable DM_USB in am57xx_evm_defconfig. USB3 (super speed) is supported. Jean-Jacques Hiblot (7): syscon: dm: Add a new method to get a regmap from DTS phy: Add a new driver for OMAP's USB2 PHYs board: ti: dra7xx-evm: turn on USB clocks in late init stage dts: dra7x: make ocp2scp@4a080000 compatible with simple-bus dts: dra7x: Disable USB1 on all evms configs: enable OMAP_USB2_PHY for all DRA7 platforms configs: am57xx_evm: Enable DM_USB and dependencies Vignesh R (2): phy: ti-pip3-phy: Add support for USB3 PHY board; ti: am57xx: turn on USB clocks arch/arm/dts/dra7-evm-u-boot.dtsi | 8 ++ arch/arm/dts/dra71-evm-u-boot.dtsi | 9 ++ arch/arm/dts/dra72-evm-revc-u-boot.dtsi | 8 ++ arch/arm/dts/dra72-evm-u-boot.dtsi | 22 ++++ arch/arm/dts/dra76-evm-u-boot.dtsi | 9 ++ arch/arm/dts/omap5-u-boot.dtsi | 4 + arch/sandbox/dts/test.dts | 6 +- board/ti/am57xx/board.c | 19 ++++ board/ti/dra7xx/evm.c | 19 ++++ configs/am57xx_evm_defconfig | 4 + configs/dra7xx_evm_defconfig | 1 + configs/dra7xx_hs_evm_defconfig | 1 + drivers/core/syscon-uclass.c | 23 ++++ drivers/phy/Kconfig | 8 ++ drivers/phy/Makefile | 1 + drivers/phy/omap-usb2-phy.c | 196 ++++++++++++++++++++++++++++++++ drivers/phy/ti-pipe3-phy.c | 30 +++-- include/syscon.h | 13 +++ test/dm/syscon.c | 29 +++++ 19 files changed, 401 insertions(+), 9 deletions(-) create mode 100644 arch/arm/dts/dra72-evm-u-boot.dtsi create mode 100644 drivers/phy/omap-usb2-phy.c -- 2.7.4

4 25

[U-Boot] [PATCH 0/4] Updates for Turris Mox
by Marek Behún 17 May '18

17 May '18

Here are some updates for Turris Mox board. The first patch updates Marvell's comphy driver to call function board_update_comphy_map. The comphy driver contains a weak definition of this function, which does nothing. Board file can then define this function to update the serdes map before comphy lanes are initialized. This is needed because on Turris Mox serdes lane 0 has to be initialized to different speed when Topaz module is connected and when SFP module is connected. This is a temporary solution. Once comphy driver for Armada 3720 is in kernel, the comphy driver in u-boot shall also be rewritten to support changing the speed even after the comphy lane is initialized. The second patch changes the turris_mox board file to switch SERDES speed according to module topology. The third patch adds support for differentiating whether the board is with eMMC card or with SD card slot. The fourth patch adds the gpio command to turris_mox_defconfig. Signed-off-by: Marek Behun <marek.behun(a)nic.cz>

3 6

[U-Boot] [PATCH] arm: kirkwood: openrd: Change environment location
by Stefan Roese 17 May '18

17 May '18

With GCC 7.3 and the addition of device-tree to Kirkwood, the U-Boot image does not fit any more into its 0x60000 area. Let's move the environment so that U-Boot will fit also with the upcoming changes for Kirkwood (add DM support etc). Signed-off-by: Stefan Roese <sr(a)denx.de> Cc: Tom Rini <trini(a)konsulko.com> Cc: Chris Packham <judge.packham(a)gmail.com> Cc: Albert ARIBAUD <albert-u-boot(a)aribaud.net> Cc: Clint Adams <clint(a)debian.org> --- include/configs/openrd.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/configs/openrd.h b/include/configs/openrd.h index dfdad56dcc..3fe0a32a55 100644 --- a/include/configs/openrd.h +++ b/include/configs/openrd.h @@ -42,8 +42,8 @@ * it has to be rounded to sector size */ #define CONFIG_ENV_SIZE 0x20000 /* 128k */ -#define CONFIG_ENV_ADDR 0x60000 -#define CONFIG_ENV_OFFSET 0x60000 /* env starts here */ +#define CONFIG_ENV_ADDR 0x80000 +#define CONFIG_ENV_OFFSET 0x80000 /* env starts here */ /* * Environment is right behind U-Boot in flash. Make sure U-Boot * doesn't grow into the environment area. -- 2.17.0

2 2

[U-Boot] Please pull u-boot-marvell/master
by Stefan Roese 17 May '18

17 May '18

Hi Tom, please pull the Kirkwood DT patches from Chris. Thanks, Stefan The following changes since commit 0315d6959fdd9d2a4d89016c311e9c8c8d239a10: ARM: mvebu: a38x: Add missing SPDX license identfier (2018-05-15 09:08:00 -0400) are available in the Git repository at: git://www.denx.de/git/u-boot-marvell.git for you to fetch changes up to a7925926dc7f81fb5c137d2b4b7c6457694b1ac0: ARM: kirkwood: Add device-tree for sheevaplug (2018-05-16 10:29:53 +0200) ---------------------------------------------------------------- Chris Packham (11): ARM: add devicetree files for kirkwood SoC ARM: kirkwood: Add device-tree for dns325 ARM: kirkwood: Add device-tree for dockstar ARM: kirkwood: Add device-tree for goflexhome ARM: kirkwood: Add device-tree for guruplug ARM: kirkwood: Add device-tree for ib62x0 ARM: kirkwood: Add device-tree for iconnect ARM: kirkwood: Add device-tree for nas220 ARM: kirkwood: Add device-tree for openrd ARM: kirkwood: Add device-tree for pogo_e02 ARM: kirkwood: Add device-tree for sheevaplug arch/arm/dts/kirkwood-6192.dtsi | 88 ++++++ arch/arm/dts/kirkwood-6281.dtsi | 90 ++++++ arch/arm/dts/kirkwood-98dx4122.dtsi | 53 ++++ arch/arm/dts/kirkwood-blackarmor-nas220.dts | 172 +++++++++++ arch/arm/dts/kirkwood-dns325.dts | 63 ++++ arch/arm/dts/kirkwood-dnskw.dtsi | 235 +++++++++++++++ arch/arm/dts/kirkwood-dockstar.dts | 110 +++++++ arch/arm/dts/kirkwood-goflexnet.dts | 190 ++++++++++++ arch/arm/dts/kirkwood-guruplug-server-plus.dts | 133 +++++++++ arch/arm/dts/kirkwood-ib62x0.dts | 146 +++++++++ arch/arm/dts/kirkwood-iconnect.dts | 195 ++++++++++++ arch/arm/dts/kirkwood-openrd-base.dts | 39 +++ arch/arm/dts/kirkwood-openrd-client.dts | 73 +++++ arch/arm/dts/kirkwood-openrd-ultimate.dts | 55 ++++ arch/arm/dts/kirkwood-openrd.dtsi | 122 ++++++++ arch/arm/dts/kirkwood-pogo_e02.dts | 132 +++++++++ arch/arm/dts/kirkwood-sheevaplug-common.dtsi | 104 +++++++ arch/arm/dts/kirkwood-sheevaplug.dts | 42 +++ arch/arm/dts/kirkwood.dtsi | 393 +++++++++++++++++++++++++ configs/dns325_defconfig | 3 +- configs/dockstar_defconfig | 3 +- configs/goflexhome_defconfig | 3 +- configs/guruplug_defconfig | 3 +- configs/ib62x0_defconfig | 3 +- configs/iconnect_defconfig | 3 +- configs/nas220_defconfig | 3 +- configs/openrd_base_defconfig | 3 +- configs/openrd_client_defconfig | 3 +- configs/openrd_ultimate_defconfig | 3 +- configs/pogo_e02_defconfig | 3 +- configs/sheevaplug_defconfig | 3 +- 31 files changed, 2459 insertions(+), 12 deletions(-) create mode 100644 arch/arm/dts/kirkwood-6192.dtsi create mode 100644 arch/arm/dts/kirkwood-6281.dtsi create mode 100644 arch/arm/dts/kirkwood-98dx4122.dtsi create mode 100644 arch/arm/dts/kirkwood-blackarmor-nas220.dts create mode 100644 arch/arm/dts/kirkwood-dns325.dts create mode 100644 arch/arm/dts/kirkwood-dnskw.dtsi create mode 100644 arch/arm/dts/kirkwood-dockstar.dts create mode 100644 arch/arm/dts/kirkwood-goflexnet.dts create mode 100644 arch/arm/dts/kirkwood-guruplug-server-plus.dts create mode 100644 arch/arm/dts/kirkwood-ib62x0.dts create mode 100644 arch/arm/dts/kirkwood-iconnect.dts create mode 100644 arch/arm/dts/kirkwood-openrd-base.dts create mode 100644 arch/arm/dts/kirkwood-openrd-client.dts create mode 100644 arch/arm/dts/kirkwood-openrd-ultimate.dts create mode 100644 arch/arm/dts/kirkwood-openrd.dtsi create mode 100644 arch/arm/dts/kirkwood-pogo_e02.dts create mode 100644 arch/arm/dts/kirkwood-sheevaplug-common.dtsi create mode 100644 arch/arm/dts/kirkwood-sheevaplug.dts create mode 100644 arch/arm/dts/kirkwood.dtsi

3 5

[U-Boot] [PATCH 0/6] Convert Xilinx ZynqMP to DM_USB with generic DWC3 glue logic driver
by Michal Simek 17 May '18

17 May '18

Hi, this patchset is based on unfinished series send to ML 06/13/2017 by Vignesh "[U-Boot] [PATCH v2 00/13] driver model bring-up of dwc3 usb peripheral" We have taken some part of this to Xilinx tree and use it for a while but it is time to review it and upstream it. The patchset has 2 patches created by Mugunthan which are a little bit fixed. dwc3-generic driver was inspired by omap version. And the last 3 patches just doing conversion and enable DM_USB for our platform. Thanks, Michal Michal Simek (4): usb: dwc3: Add generic DWC3 glue logic driver usb: xhci: zynqmp: Add support for DM_USB arm64: zynqmp: Use DWC3 generic driver and DM_USB usb: xhci: zynqmp: Remove support for !DM_USB Mugunthan V N (2): usb: dwc3: Add dwc3_init/remove with DM_USB usb: common: add support to get maximum speed from dt board/xilinx/zynqmp/zynqmp.c | 46 ----- .../xilinx_zynqmp_zc1751_xm015_dc1_defconfig | 1 + .../xilinx_zynqmp_zc1751_xm016_dc2_defconfig | 1 + .../xilinx_zynqmp_zc1751_xm017_dc3_defconfig | 1 + configs/xilinx_zynqmp_zcu100_revC_defconfig | 1 + configs/xilinx_zynqmp_zcu102_rev1_0_defconfig | 1 + configs/xilinx_zynqmp_zcu102_revA_defconfig | 1 + configs/xilinx_zynqmp_zcu102_revB_defconfig | 1 + configs/xilinx_zynqmp_zcu104_revA_defconfig | 1 + configs/xilinx_zynqmp_zcu104_revC_defconfig | 1 + configs/xilinx_zynqmp_zcu106_revA_defconfig | 1 + configs/xilinx_zynqmp_zcu111_revA_defconfig | 1 + drivers/usb/common/common.c | 29 +++ drivers/usb/dwc3/Kconfig | 6 + drivers/usb/dwc3/Makefile | 1 + drivers/usb/dwc3/core.c | 57 ++++++ drivers/usb/dwc3/core.h | 6 + drivers/usb/dwc3/dwc3-generic.c | 165 ++++++++++++++++++ drivers/usb/host/Kconfig | 1 + drivers/usb/host/xhci-zynqmp.c | 85 +++++---- .../configs/xilinx_zynqmp_zc1751_xm015_dc1.h | 1 - .../configs/xilinx_zynqmp_zc1751_xm016_dc2.h | 2 - .../configs/xilinx_zynqmp_zc1751_xm017_dc3.h | 3 - include/configs/xilinx_zynqmp_zcu100.h | 3 - include/configs/xilinx_zynqmp_zcu102.h | 2 - include/configs/xilinx_zynqmp_zcu104.h | 2 - include/configs/xilinx_zynqmp_zcu106.h | 1 - include/configs/xilinx_zynqmp_zcu111.h | 2 - include/linux/usb/otg.h | 9 + scripts/config_whitelist.txt | 1 - 30 files changed, 339 insertions(+), 94 deletions(-) create mode 100644 drivers/usb/dwc3/dwc3-generic.c -- 2.17.0

4 14

[U-Boot] U-Boot/Linux and HYP mode on ARMv7 | falstaff - yet another tech...2018-05-17 15:24:28
by ashley 17 May '18

17 May '18

Spam detection software, running on the system "lists.denx.de", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: U-Boot/Linux and HYP mode on ARMv7 | falstaff - yet another tech... As a full service custom injection molder, RayBo offers a complete range of services. Our engineers specialize in close-tolerance, mold building, mold tryout, scientific injection molding and assembly. [...] Content analysis details: (9.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.6 HTML_IMAGE_ONLY_12 BODY: HTML: images with 800-1200 bytes of words 1.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts 0.0 HTML_MESSAGE BODY: HTML included in message 3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [113.77.86.117 listed in zen.spamhaus.org] 1.6 RCVD_IN_BRBL_LASTEXT RBL: No description available. [113.77.86.117 listed in bb.barracudacentral.org] 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines 0.1 MISSING_MID Missing Message-Id: header 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 0

[U-Boot] [PATCH] sf: Add Macronix MX25U25645G ID
by Marek Vasut 17 May '18

17 May '18

Add ID for the Macronix MX25U25645G flash. Signed-off-by: Marek Vasut <marex(a)denx.de> Cc: Jagan Teki <jagan(a)openedev.com> --- drivers/mtd/spi/spi_flash_ids.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mtd/spi/spi_flash_ids.c b/drivers/mtd/spi/spi_flash_ids.c index a46227f172..3b8f254ca2 100644 --- a/drivers/mtd/spi/spi_flash_ids.c +++ b/drivers/mtd/spi/spi_flash_ids.c @@ -85,6 +85,7 @@ const struct spi_flash_info spi_flash_ids[] = { {"mx25u6435f", INFO(0xc22537, 0x0, 64 * 1024, 128, RD_FULL | WR_QPP) }, {"mx25l12855e", INFO(0xc22618, 0x0, 64 * 1024, 256, RD_FULL | WR_QPP) }, {"mx25u1635e", INFO(0xc22535, 0x0, 64 * 1024, 32, SECT_4K) }, + {"mx25u25645g", INFO(0xc22539, 0x0, 64 * 1024, 512, RD_FULL | WR_QPP) }, {"mx66u51235f", INFO(0xc2253a, 0x0, 64 * 1024, 1024, RD_FULL | WR_QPP) }, {"mx66l1g45g", INFO(0xc2201b, 0x0, 64 * 1024, 2048, RD_FULL | WR_QPP) }, #endif -- 2.16.2

2 1

[U-Boot] Which carrier card is targeted by the zynq picozed implementation?
by Ed Jubenville 17 May '18

17 May '18

I may have missed it, but I cannot determine which carrier card is targeted by "configs/zynq_picozed_defconfig" and "arch/arm/dts/zynq-picozed.dtb". Most of a picozed's multiplexed I/O (MIO) depends on its carrier card design, so any picozed-related files that are independent of a carrier card don't make sense. For example, a config name such as "zynq_picozed_carrierv2_defconfig" would make a lot more sense. 1) Which carrier card is targeted by the existing "picozed" configuration files? 2) What is the recommended procedure to adapt the picozed configuration to a custom carrier card. Ed

2 1

[U-Boot] [PATCH v2 0/2] efi_loader: adjust definitions of variable services
by Heinrich Schuchardt 17 May '18

17 May '18

The definitons of the variable services are adjusted: - use efi_uintn_t instead of unsigned long - use u16 * instead of s16 * for Unicode strings - correct definition of QueryVariableInfo - rename efi_get_next_variable to efi_get_next_variable_name A unit test for the variable services is supplied. v2: fix warning when building on 64bit architecture Heinrich Schuchardt (2): efi_loader: adjust definitions of variable services efi_selftest: unit test for variable services include/efi_api.h | 24 +-- include/efi_loader.h | 18 +-- lib/efi_loader/efi_bootmgr.c | 10 +- lib/efi_loader/efi_runtime.c | 10 +- lib/efi_loader/efi_variable.c | 24 +-- lib/efi_selftest/Makefile | 1 + lib/efi_selftest/efi_selftest_variables.c | 180 ++++++++++++++++++++++ 7 files changed, 224 insertions(+), 43 deletions(-) create mode 100644 lib/efi_selftest/efi_selftest_variables.c -- 2.17.0

1 2

[U-Boot] [PATCH] common: image-fit: add FIT data-position & data-offset property support
by Kelvin Cheung 17 May '18

17 May '18

Add FIT data-position & data-offset property support for bootm, which are already supported in SPL. Signed-off-by: Kelvin Cheung <keguang.zhang(a)gmail.com> --- common/image-fit.c | 82 +++++++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 78 insertions(+), 4 deletions(-) diff --git a/common/image-fit.c b/common/image-fit.c index 5b93dce..f21db4b 100644 --- a/common/image-fit.c +++ b/common/image-fit.c @@ -359,11 +359,14 @@ void fit_image_print(const void *fit, int image_noffset, const char *p) { char *desc; uint8_t type, arch, os, comp; - size_t size; + size_t size = 0; ulong load, entry; const void *data; int noffset; int ndepth; + bool external_data = false; + int offset; + int len; int ret; /* Mandatory properties */ @@ -391,7 +394,27 @@ void fit_image_print(const void *fit, int image_noffset, const char *p) fit_image_get_comp(fit, image_noffset, &comp); printf("%s Compression: %s\n", p, genimg_get_comp_name(comp)); - ret = fit_image_get_data(fit, image_noffset, &data, &size); + if (!fit_image_get_data_position(fit, image_noffset, &offset)) { + external_data = true; + } else if (!fit_image_get_data_offset(fit, image_noffset, &offset)) { + external_data = true; + /* + * For FIT with external data, figure out where + * the external images start. This is the base + * for the data-offset properties in each image. + */ + size = (fdt_totalsize(fit) + 3) & ~3; + offset += size; + } + + if (external_data) { + printf("%s External Data\n", p); + ret = fit_image_get_data_size(fit, image_noffset, &len); + data = fit + offset; + size = len; + } else { + ret = fit_image_get_data(fit, image_noffset, &data, &size); + } #ifndef USE_HOSTCC printf("%s Data Start: ", p); @@ -1151,9 +1174,35 @@ int fit_image_verify(const void *fit, int image_noffset) size_t size; int noffset = 0; char *err_msg = ""; + bool external_data = false; + int offset; + int len; + int ret; /* Get image data and data length */ - if (fit_image_get_data(fit, image_noffset, &data, &size)) { + if (!fit_image_get_data_position(fit, image_noffset, &offset)) { + external_data = true; + } else if (!fit_image_get_data_offset(fit, image_noffset, &offset)) { + external_data = true; + /* + * For FIT with external data, figure out where + * the external images start. This is the base + * for the data-offset properties in each image. + */ + size = (fdt_totalsize(fit) + 3) & ~3; + offset += size; + } + + if (external_data) { + debug("External Data\n"); + ret = fit_image_get_data_size(fit, image_noffset, &len); + data = fit + offset; + size = len; + } else { + ret = fit_image_get_data(fit, image_noffset, &data, &size); + } + + if (ret) { err_msg = "Can't get image data/size"; printf("error!\n%s for '%s' hash node in '%s' image node\n", err_msg, fit_get_name(fit, noffset, NULL), @@ -1750,6 +1799,9 @@ int fit_image_load(bootm_headers_t *images, ulong addr, uint8_t os_arch; #endif const char *prop_name; + bool external_data = false; + int offset; + int data_len; int ret; fit = map_sysmem(addr, 0); @@ -1875,7 +1927,29 @@ int fit_image_load(bootm_headers_t *images, ulong addr, bootstage_mark(bootstage_id + BOOTSTAGE_SUB_CHECK_ALL_OK); /* get image data address and length */ - if (fit_image_get_data(fit, noffset, &buf, &size)) { + if (!fit_image_get_data_position(fit, noffset, &offset)) { + external_data = true; + } else if (!fit_image_get_data_offset(fit, noffset, &offset)) { + external_data = true; + /* + * For FIT with external data, figure out where + * the external images start. This is the base + * for the data-offset properties in each image. + */ + size = (fdt_totalsize(fit) + 3) & ~3; + offset += size; + } + + if (external_data) { + debug("External Data\n"); + ret = fit_image_get_data_size(fit, noffset, &data_len); + buf = fit + offset; + size = data_len; + } else { + ret = fit_image_get_data(fit, noffset, &buf, &size); + } + + if (ret) { printf("Could not find %s subimage data!\n", prop_name); bootstage_error(bootstage_id + BOOTSTAGE_SUB_GET_DATA); return -ENOENT; -- 1.9.1

2 2