June 2019 - U-Boot

[U-Boot] [PATCH v2 0/5] SiFive SPI MMC Support
by Anup Patel 05 Jul '19

05 Jul '19

This patchset adds: 1. SiFive SPI driver 2. New MMC SPI driver based on DM_MMC and DM_SPI 3. Enables SiFive SPI driver and MMC SPI driver for SiFive Unleashed board With this patch series, we can now load files from SD card on SiFive Unleashed board. Many thanks to Bhargav for porting SiFive SPI driver and updating MMC SPI driver for us. These patches can be also found in riscv_unleashed_mmc_spi_v2 branch of: https//github.com/avpatel/u-boot.git Changes since v1: - Make response matching part belongs to mmc_spi_sendcmd() - Match response to zero for SEND_STATUS (CMD13) - Add separate patch for updating SiFive FU540 Documentation Anup Patel (2): mmc: skip select_mode_and_width for MMC SPI host doc: sifive-fu540: Update README for SiFive SPI and MMC SPI drivers Bhargav Shah (3): spi: Add SiFive SPI driver mmc: mmc_spi: Re-write driver using DM framework riscv: sifive: fu540: Enable SiFive SPI and MMC SPI drivers board/sifive/fu540/Kconfig | 8 + doc/README.sifive-fu540 | 4 +- drivers/mmc/Kconfig | 18 ++ drivers/mmc/mmc.c | 14 ++ drivers/mmc/mmc_spi.c | 469 ++++++++++++++++++++++++------------- drivers/spi/Kconfig | 8 + drivers/spi/Makefile | 1 + drivers/spi/spi-sifive.c | 405 ++++++++++++++++++++++++++++++++ 8 files changed, 757 insertions(+), 170 deletions(-) create mode 100644 drivers/spi/spi-sifive.c -- 2.17.1

4 15

[U-Boot] [PATCH] mips: mt76xx: Implement new d-cache fix in last_stage_init()
by Stefan Roese 05 Jul '19

05 Jul '19

With commit 06985289d452 ("watchdog: Implement generic watchdog_reset() version") the init sequence has changed in arch_misc_init(), resulting in a re-appearance of the d-cache issue on MT7688 boards (e.g. gardena). When this happens, the first (or sometimes later ones as well) TFTP command hangs and does not complete correctly. This leads to the assumption that the d-cache is not in a clean state once the ethernet driver is called (d-cache is used here for the buffers). The old work- around with the cache flush somehow does not work any more now with the new code change. Unfortunately adding CONFIG_SYS_MALLOC_CLEAR_ON_INIT also did not fix this issue. With v2019.07-rc3 it shows again. The time of accessing the data seems to be very important here. It needs to be "very late" in the boot process. Testing has shown, that copying a 64KiB area in DDR at a very late bootup time, directly before calling into the prompt, fixes this issue. Flushing of the complete d-cache does not seem to necessary, as this copy alone seems to fix this problem. Signed-off-by: Stefan Roese <sr(a)denx.de> Cc: Daniel Schwierzeck <daniel.schwierzeck(a)gmail.com> --- arch/mips/Kconfig | 2 +- arch/mips/mach-mtmips/cpu.c | 26 ++++++++++++++++++++++++++ 2 files changed, 27 insertions(+), 1 deletion(-) diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig index 5cb9bdf2ee..e3e7945567 100644 --- a/arch/mips/Kconfig +++ b/arch/mips/Kconfig @@ -84,13 +84,13 @@ config ARCH_MTMIPS select DM_SERIAL imply DM_SPI imply DM_SPI_FLASH + select LAST_STAGE_INIT select MIPS_TUNE_24KC select OF_CONTROL select ROM_EXCEPTION_VECTORS select SUPPORTS_CPU_MIPS32_R1 select SUPPORTS_CPU_MIPS32_R2 select SUPPORTS_LITTLE_ENDIAN - select SYS_MALLOC_CLEAR_ON_INIT select SYSRESET config ARCH_JZ47XX diff --git a/arch/mips/mach-mtmips/cpu.c b/arch/mips/mach-mtmips/cpu.c index b0a6397d68..7afc2c5940 100644 --- a/arch/mips/mach-mtmips/cpu.c +++ b/arch/mips/mach-mtmips/cpu.c @@ -68,3 +68,29 @@ int print_cpuinfo(void) return 0; } + +int last_stage_init(void) +{ + void *src, *dst; + + src = malloc(SZ_64K); + dst = malloc(SZ_64K); + if (!src || !dst) { + printf("Can't allocate buffer for cache cleanup copy!\n"); + return 0; + } + + /* + * It has been noticed, that sometimes the d-cache is not in a + * "clean-state" when U-Boot is running on MT7688. This was + * detected when using the ethernet driver (which uses d-cache) + * and a TFTP command does not complete. Copying an area of 64KiB + * in DDR at a very late bootup time in U-Boot, directly before + * calling into the prompt, seems to fix this issue. + */ + memcpy(dst, src, SZ_64K); + free(src); + free(dst); + + return 0; +} -- 2.21.0

2 2

[U-Boot] pull request: raspberry pi updates
by Matthias Brugger 05 Jul '19

05 Jul '19

Hi Tom, Please have a look on the following patches. Regards, Matthias --- The following changes since commit fc6c0e29a28f6b71dfb728b7f78e9e770f2cd218: Prepare v2019.07-rc4 (2019-06-10 21:27:46 -0400) are available in the Git repository at: https://github.com/mbgg/u-boot.git tags/rpi-next-2019.07 for you to fetch changes up to 38e58ff2b785b45e8c8ade8e23f916a1984016c6: ARM: bcm283x: Fix definition of MBOX_TAG_TEST_PIXEL_ORDER (2019-06-12 12:23:46 +0200) ---------------------------------------------------------------- - fix complation error for CONFIG_USB - update RPi3 DTBs to v5.1-rc6 state - add defconfig for RPi3 B+ - Fix BCM2835_MBOX_TAG_TEST_PIXEL_ORDER define ---------------------------------------------------------------- Berkus Decker (1): ARM: bcm283x: Fix definition of MBOX_TAG_TEST_PIXEL_ORDER Heinrich Schuchardt (2): fdt: update bcm283x device tree sources to Linux 5.1-rc6 state ARM: defconfig: add Raspberry Pi 3 Model B+ akaher (1): Fix compilation error if CONFIG_USB is disabled arch/arm/dts/Makefile | 13 +- arch/arm/dts/bcm2835-rpi-a-plus.dts | 15 ++- arch/arm/dts/bcm2835-rpi-a.dts | 9 +- arch/arm/dts/bcm2835-rpi-b-plus.dts | 15 ++- arch/arm/dts/bcm2835-rpi-b-rev2.dts | 11 +- arch/arm/dts/bcm2835-rpi-b.dts | 9 +- arch/arm/dts/bcm2835-rpi-cm1-io1.dts | 88 ++++++++++++++ arch/arm/dts/bcm2835-rpi-cm1.dtsi | 34 ++++++ arch/arm/dts/bcm2835-rpi-zero-w.dts | 123 +++++++++++++++++-- arch/arm/dts/bcm2835-rpi-zero.dts | 105 ++++++++++++++++ arch/arm/dts/bcm2835-rpi.dtsi | 22 ++-- arch/arm/dts/bcm2835.dtsi | 7 +- arch/arm/dts/bcm2836-rpi-2-b.dts | 81 ++++++++++++- arch/arm/dts/bcm2836-rpi.dtsi | 6 + arch/arm/dts/bcm2836.dtsi | 25 ++-- arch/arm/dts/bcm2837-rpi-3-a-plus.dts | 175 +++++++++++++++++++++++++++ arch/arm/dts/bcm2837-rpi-3-b-plus.dts | 178 ++++++++++++++++++++++++++++ arch/arm/dts/bcm2837-rpi-3-b.dts | 128 +++++++++++++++++++- arch/arm/dts/bcm2837-rpi-cm3-io3.dts | 87 ++++++++++++++ arch/arm/dts/bcm2837-rpi-cm3.dtsi | 52 ++++++++ arch/arm/dts/bcm2837.dtsi | 20 ++-- arch/arm/dts/bcm283x-rpi-lan7515.dtsi | 41 +++++++ arch/arm/dts/bcm283x-rpi-smsc9512.dtsi | 1 + arch/arm/dts/bcm283x-rpi-usb-otg.dtsi | 11 ++ arch/arm/dts/bcm283x.dtsi | 57 +++++++-- arch/arm/mach-bcm283x/include/mach/mbox.h | 2 +- configs/rpi_3_b_plus_defconfig | 43 +++++++ include/configs/rpi.h | 36 +++++- include/dt-bindings/clock/bcm2835-aux.h | 10 +- include/dt-bindings/clock/bcm2835.h | 10 +- include/dt-bindings/net/microchip-lan78xx.h | 21 ++++ include/dt-bindings/pinctrl/bcm2835.h | 8 +- include/dt-bindings/soc/bcm2835-pm.h | 28 +++++ 33 files changed, 1365 insertions(+), 106 deletions(-) create mode 100644 arch/arm/dts/bcm2835-rpi-cm1-io1.dts create mode 100644 arch/arm/dts/bcm2835-rpi-cm1.dtsi create mode 100644 arch/arm/dts/bcm2835-rpi-zero.dts create mode 100644 arch/arm/dts/bcm2836-rpi.dtsi create mode 100644 arch/arm/dts/bcm2837-rpi-3-a-plus.dts create mode 100644 arch/arm/dts/bcm2837-rpi-3-b-plus.dts create mode 100644 arch/arm/dts/bcm2837-rpi-cm3-io3.dts create mode 100644 arch/arm/dts/bcm2837-rpi-cm3.dtsi create mode 100644 arch/arm/dts/bcm283x-rpi-lan7515.dtsi create mode 100644 arch/arm/dts/bcm283x-rpi-usb-otg.dtsi create mode 100644 configs/rpi_3_b_plus_defconfig create mode 100644 include/dt-bindings/net/microchip-lan78xx.h create mode 100644 include/dt-bindings/soc/bcm2835-pm.h

6 13

[U-Boot] [RESEND PATCH v3 00/18] Improvement for the DWC3 USB generic driver and fixes for the K2 platforms
by Jean-Jacques Hiblot 05 Jul '19

05 Jul '19

Resend after rebasing on top of latest u-boot The K2 platforms have shown boot issues after switching to the DWC3 generic driver. Those are due to the fact that the USB domains are not turned off before booting linux and the phy were not properly initialized. Fixing it by improving the DWC3-generic driver and handling the USB power domain in the PHY driver. At the same time this series introduce a new uclass (UCLASS_NOP) to replace usage of UCLASS_MISC in the USB wrapper because the MISC class now automatically binds all the child devices and that breaks the DWC3-generic driver. Improvements to the DWC3 generic driver are: - Fix it by switching to UCLASS_NOP - core: read quirks properties from DT and apply the fixes. - add a new host driver that uses the DWC3 core (more generic than xhci-dwc3). This should enable most platforms to drop their own version of the xhci-driver to use the generic one instead. This series also removes the now unused xhci-zynqmp driver and tries to better manage the Kconfig options related to DWC3 gadget/host mode selection. This has been tested with K2 and DRA7 platforms (host and device modes). Travis build: https://travis-ci.org/jjhiblot/u-boot/builds/515282720 Changes in v3: - updated log message when defaulting to super speed Changes in v2: Add a test for the NOP uclass Update commit log Select USB_GADGET_DUALSPEED if USB_DWC3_GADGET is selected Jean-Jacques Hiblot (18): usb: dwc3-generic: remove dm_scan_fdt_dev() from the remove() callback usb: host: remove the xhci-zynqmp driver dm: Add a No-op uclass usb: dwc3: Use UCLASS_NOP instead of UCLASS_MISC for the DWC3 generic glue usb: dwc3: switch to peripheral mode when exiting usb: xhci: move xhci.h to include usb usb: dwc3: always use the inlined version of dwc3_host_init/dwc3_host_exit usb: dwc3-generic: use platdata usb: dwc3-generic: factorize code usb: dwc3-generic: add a new host driver that uses the dwc3 core usb: dwc3-generic: if no max speed is specified in DT, assume super speed usb: dwc3: Add dwc3_of_parse() to get quirks information from DT usb: dwc3: Kconfig: get rid of obsolete mode selection ARM: keystone: increase PSC timeout ARM: keystone: Do not enable the USB power domains at the board level phy: keystone-usb: handle the transition of the USB power domain configs: k2g_evm_defconfig: disable XHCI_DWC3 and enable KEYSTONE_USB_PHY ARM: DTS: keystone: complete the description of the USB PHY devices MAINTAINERS | 1 + arch/arm/dts/keystone-k2e-evm-u-boot.dtsi | 32 ++++ arch/arm/dts/keystone-k2g-evm-u-boot.dtsi | 28 ++++ arch/arm/dts/keystone-k2hk-evm-u-boot.dtsi | 14 ++ arch/arm/dts/keystone-k2l-evm-u-boot.dtsi | 18 +++ .../arm/mach-keystone/include/mach/psc_defs.h | 2 +- arch/sandbox/dts/test.dts | 12 ++ board/ti/ks2_evm/board.c | 13 -- configs/avnet_ultra96_rev1_defconfig | 1 - configs/evb-rk3328_defconfig | 1 + configs/k2g_evm_defconfig | 3 +- .../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/core/uclass.c | 5 + drivers/phy/keystone-usb-phy.c | 22 +++ drivers/usb/dwc3/Kconfig | 18 +-- drivers/usb/dwc3/core.c | 84 +++++++++- drivers/usb/dwc3/core.h | 6 +- drivers/usb/dwc3/dwc3-generic.c | 150 ++++++++++++++---- drivers/usb/host/Kconfig | 7 - drivers/usb/host/Makefile | 1 - drivers/usb/host/xhci-dwc3.c | 2 +- drivers/usb/host/xhci-exynos5.c | 2 +- drivers/usb/host/xhci-fsl.c | 2 +- drivers/usb/host/xhci-mem.c | 2 +- drivers/usb/host/xhci-mvebu.c | 2 +- drivers/usb/host/xhci-omap.c | 2 +- drivers/usb/host/xhci-pci.c | 2 +- drivers/usb/host/xhci-rcar.c | 2 +- drivers/usb/host/xhci-ring.c | 2 +- drivers/usb/host/xhci-rockchip.c | 2 +- drivers/usb/host/xhci-zynqmp.c | 146 ----------------- drivers/usb/host/xhci.c | 2 +- drivers/usb/phy/omap_usb_phy.c | 2 +- include/dm/uclass-id.h | 1 + {drivers/usb/host => include/usb}/xhci.h | 0 test/dm/Makefile | 1 + test/dm/nop.c | 73 +++++++++ 47 files changed, 421 insertions(+), 253 deletions(-) create mode 100644 arch/arm/dts/keystone-k2l-evm-u-boot.dtsi delete mode 100644 drivers/usb/host/xhci-zynqmp.c rename {drivers/usb/host => include/usb}/xhci.h (100%) create mode 100644 test/dm/nop.c -- 2.17.1

4 31

[U-Boot] [RFC] env: ti: Handle reboot reason from BCB
by Sam Protsenko 04 Jul '19

04 Jul '19

*** PLEASE DO NOT MERGE. *** This is only RFC, a discussion thread. Patch is only for the *** reference here right now, to create a discussion context. There are 2 possible reboot use-cases: 1. User did "fastboot reboot bootloader" (we're setting "dofastboot" variable as an indicator in this case) 2. User did "adb reboot bootloader" or "reboot bootloader" from Linux shell (Android sets "bootonce-bootloader" string into command field of BCB area inside of 'misc' partition as an indicator in this case) We already had (1) handling implemented. This patch adds implementation of (2). Possible drawbacks are: - user is able to re-define 'preboot' variable and break this mechanism this way - performance penalty due to scripting usage in 'preboot' DISCUSSION ITEM 1: possible solution to those can be checking BCB area (and 'dofastboot' variable) in C code, somewhere in board file, like in late_init() function, and on;y set 'preboot' variable from there, if conditions are met, to something like this: preboot=fastboot 1; setenv preboot; so that next time 'preboot' variable will be empty. But this way also has its shortcomings, like the necessity of board file modification, need of BCB C API exposure, etc. DISCUSSION ITEM 2: this patch only implements reboot reason handling for TI platforms. I presume there could be another parties interested in this feature. Should we somehow provide some generic way for handling that (at least mechanism for checking), or is it a bad idea, and everyone should handle this in their own way? DISCUSSION ITEM 3: I didn't handle "reboot recovery" reason here. Does anyone have some ideas on that? This doc [1] a bit of confuses me, but as I understand, the 'recovery' partition will remain, so in case of "reboot recovery" we just need to load recovery partition into the RAM and run bootm for that. Is that correct or I'm missing something? [1] https://source.android.com/devices/tech/ota/ab/ab_implement Signed-off-by: Sam Protsenko <semen.protsenko(a)linaro.org> --- include/environment/ti/boot.h | 43 ++++++++++++++++++++++++++++++----- 1 file changed, 37 insertions(+), 6 deletions(-) diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h index 8ddb0416c4..943adcad40 100644 --- a/include/environment/ti/boot.h +++ b/include/environment/ti/boot.h @@ -126,13 +126,44 @@ "if test $fdtfile = undefined; then " \ "echo WARNING: Could not determine device tree to use; fi; \0" -#define CONFIG_PREBOOT \ +#define FASTBOOT_CMD \ + "echo Booting into fastboot ...; " \ + "fastboot " __stringify(CONFIG_FASTBOOT_USB_DEV) "; " + +/* Check we are booting from "fastboot reboot bootloader" */ +#define PREBOOT_CHECK_DOFASTBOOT \ "if test ${dofastboot} -eq 1; then " \ - "echo Boot fastboot requested, resetting dofastboot ...;" \ - "setenv dofastboot 0; saveenv;" \ - "echo Booting into fastboot ...; " \ - "fastboot " __stringify(CONFIG_FASTBOOT_USB_DEV) "; " \ - "fi;" \ + "echo Boot fastboot requested, resetting dofastboot ...; " \ + "setenv dofastboot 0; saveenv; " \ + FASTBOOT_CMD \ + "fi; " + +/* Check reboot reason in BCB area of 'misc' partition */ +#define PREBOOT_CHECK_BCB \ + "if bcb load " __stringify(CONFIG_FASTBOOT_FLASH_MMC_DEV) " misc; " \ + "then " \ + "if bcb test command = bootonce-bootloader; then " \ + "echo Boot fastboot requested, resetting BCB ...; " \ + "bcb clear command; bcb store; " \ + FASTBOOT_CMD \ + "elif bcb test command = boot-recovery; then " \ + "echo Boot recovery requested; resetting BCB ...; " \ + "bcb clear command; bcb store; " \ + "echo TODO: RECOVERY_CMD is not implemented; " \ + "fi; " \ + "else " \ + "echo Error: BCB/misc is corrupted or does not exist; " \ + "fi; " + +/* Enter fastboot mode if user requested it */ +#if CONFIG_IS_ENABLED(CMD_BCB) +# define CONFIG_PREBOOT \ + PREBOOT_CHECK_DOFASTBOOT \ + PREBOOT_CHECK_BCB +#else +# define CONFIG_PREBOOT \ + PREBOOT_CHECK_DOFASTBOOT +#endif #define CONFIG_BOOTCOMMAND \ "if test ${boot_fit} -eq 1; then " \ -- 2.20.1

2 2

[U-Boot] [PATCH] fastboot: Remove "bootloader-version" variable
by Sam Protsenko 04 Jul '19

04 Jul '19

As per [1], there is no such fastboot variable as "bootloader-version". Only "version-bootloader" is supported. Let's reflect this and not confuse users further. [1] https://android.googlesource.com/platform/system/core/+/master/fastboot/REA… Signed-off-by: Sam Protsenko <semen.protsenko(a)linaro.org> --- doc/README.android-fastboot | 4 ++-- drivers/fastboot/fb_getvar.c | 9 +++------ 2 files changed, 5 insertions(+), 8 deletions(-) diff --git a/doc/README.android-fastboot b/doc/README.android-fastboot index 431191c473..ce852a4fd1 100644 --- a/doc/README.android-fastboot +++ b/doc/README.android-fastboot @@ -169,8 +169,8 @@ On the client side you can fetch the bootloader version for instance: :: - $ fastboot getvar bootloader-version - bootloader-version: U-Boot 2014.04-00005-gd24cabc + $ fastboot getvar version-bootloader + version-bootloader: U-Boot 2014.04-00005-gd24cabc finished. total time: 0.000s or initiate a reboot: diff --git a/drivers/fastboot/fb_getvar.c b/drivers/fastboot/fb_getvar.c index fd0823b2bf..ebe5c8a104 100644 --- a/drivers/fastboot/fb_getvar.c +++ b/drivers/fastboot/fb_getvar.c @@ -12,7 +12,7 @@ #include <version.h> static void getvar_version(char *var_parameter, char *response); -static void getvar_bootloader_version(char *var_parameter, char *response); +static void getvar_version_bootloader(char *var_parameter, char *response); static void getvar_downloadsize(char *var_parameter, char *response); static void getvar_serialno(char *var_parameter, char *response); static void getvar_version_baseband(char *var_parameter, char *response); @@ -37,12 +37,9 @@ static const struct { { .variable = "version", .dispatch = getvar_version - }, { - .variable = "bootloader-version", - .dispatch = getvar_bootloader_version }, { .variable = "version-bootloader", - .dispatch = getvar_bootloader_version + .dispatch = getvar_version_bootloader }, { .variable = "downloadsize", .dispatch = getvar_downloadsize @@ -131,7 +128,7 @@ static void getvar_version(char *var_parameter, char *response) fastboot_okay(FASTBOOT_VERSION, response); } -static void getvar_bootloader_version(char *var_parameter, char *response) +static void getvar_version_bootloader(char *var_parameter, char *response) { fastboot_okay(U_BOOT_VERSION, response); } -- 2.20.1

4 7

[U-Boot] [PATCH 0/3] amlogic: add unique MAC address generatio
by Neil Armstrong 04 Jul '19

04 Jul '19

This patchset adds support for generating an unique MAC address per-SoC, and enables it on the q200 (VIM2) and P212 (libretech-cc, khadas-vim, libretech-ac) based boards. Neil Armstrong (3): ARM: meson: sm: Add secure monitor calls to retrieve SoC serial number ARM: meson: add unique MAC address generation board: amlogic: Generate unique MAC address for Q200 and P212 based boards arch/arm/include/asm/arch-meson/eth.h | 3 +++ arch/arm/include/asm/arch-meson/sm.h | 4 ++++ arch/arm/mach-meson/board-common.c | 31 +++++++++++++++++++++++++++ arch/arm/mach-meson/sm.c | 24 +++++++++++++++++++++ board/amlogic/p212/p212.c | 2 ++ board/amlogic/q200/q200.c | 2 ++ 6 files changed, 66 insertions(+) -- 2.21.0

1 4

[U-Boot] [PATCH 0/4] davinci: fix build warnings
by Bartosz Golaszewski 04 Jul '19

04 Jul '19

From: Bartosz Golaszewski <bgolaszewski(a)baylibre.com> There are several build warnings related to driver-model usage emitted when building u-boot for da850-evm and da850-lcdk. This series fixes them and - while we're at it - removes the i2c compatiblity layer as davinci was the last user of it. Bartosz Golaszewski (4): davinci: remove CONFIG_DM_I2C_COMPAT from defconfigs sandbox: remove CONFIG_DM_I2C_COMPAT from defconfigs i2c: remove i2c driver-model compatibility layer omapl138_lcdk_defconfig: don't build support for SPI Makefile | 7 -- configs/da850_am18xxevm_defconfig | 1 - configs/omapl138_lcdk_defconfig | 7 +- configs/sandbox64_defconfig | 1 - configs/sandbox_defconfig | 1 - configs/sandbox_flattree_defconfig | 1 - configs/sandbox_noblk_defconfig | 1 - configs/sandbox_spl_defconfig | 1 - configs/tools-only_defconfig | 1 - drivers/i2c/Kconfig | 13 +-- drivers/i2c/Makefile | 1 - drivers/i2c/i2c-uclass-compat.c | 128 ----------------------------- include/_exports.h | 3 +- include/configs/am3517_evm.h | 1 - include/configs/da850evm.h | 8 -- include/configs/omapl138_lcdk.h | 8 -- include/exports.h | 3 +- include/i2c.h | 80 ------------------ 18 files changed, 4 insertions(+), 262 deletions(-) delete mode 100644 drivers/i2c/i2c-uclass-compat.c -- 2.21.0

3 11

[U-Boot] [PATCH] env: ti: Improve "fastboot reboot bootloader" handling
by Sam Protsenko 04 Jul '19

04 Jul '19

Enter fastboot mode ASAP during the boot, when user performed "fastboot reboot bootloader" command, before starting the CONFIG_BOOTDELAY countdown. We don't want to allow user to get into U-Boot shell when we already know user wants to get into fastboot mode. Signed-off-by: Sam Protsenko <semen.protsenko(a)linaro.org> --- include/environment/ti/boot.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h index a6b245b1c7..8ddb0416c4 100644 --- a/include/environment/ti/boot.h +++ b/include/environment/ti/boot.h @@ -126,13 +126,15 @@ "if test $fdtfile = undefined; then " \ "echo WARNING: Could not determine device tree to use; fi; \0" -#define CONFIG_BOOTCOMMAND \ +#define CONFIG_PREBOOT \ "if test ${dofastboot} -eq 1; then " \ "echo Boot fastboot requested, resetting dofastboot ...;" \ "setenv dofastboot 0; saveenv;" \ "echo Booting into fastboot ...; " \ "fastboot " __stringify(CONFIG_FASTBOOT_USB_DEV) "; " \ "fi;" \ + +#define CONFIG_BOOTCOMMAND \ "if test ${boot_fit} -eq 1; then " \ "run update_to_fit;" \ "fi;" \ -- 2.20.1

1 1

[U-Boot] [PATCH] usb: gadget: f_dfu.c: fix memory leak
by Ralph Siemsen 04 Jul '19

04 Jul '19

dfu_prepare_function() allocates N+1 descriptor header structures, the last one being the "DFU Functional Descriptor". dfu_unbind() handles de-allocation, but failes to free the final one (eg. "DFU Functional Descriptor"), leading to memory leak. Fixed by incrementing counter, as in dfu_prepare_function(). Signed-off-by: Ralph Siemsen <ralph.siemsen(a)linaro.org> --- Notes: The array of pointers allocated in dfu_prepare_function() is larger than necessary. For some reason it is N+2 when N+1 would suffice. Not a memory leak, so did not address in this commit. drivers/usb/gadget/f_dfu.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/gadget/f_dfu.c b/drivers/usb/gadget/f_dfu.c index 30ece524a8..e27f146605 100644 --- a/drivers/usb/gadget/f_dfu.c +++ b/drivers/usb/gadget/f_dfu.c @@ -748,6 +748,7 @@ static void dfu_unbind(struct usb_configuration *c, struct usb_function *f) if (f_dfu->function) { i = alt_num; + i++; /* free DFU Functional Descriptor */ while (i) { free(f_dfu->function[--i]); f_dfu->function[i] = NULL; -- 2.17.1

2 3