July 2018 - U-Boot

[U-Boot] [PATCH 1/4] x86: quark: acpi: Add full reset bit to the reset register value in FADT
by Bin Meng 19 Jul '18

19 Jul '18

This adds full reset bit in the reset register value in the ACPI FADT table, so that kernel can do a thorough reboot. Signed-off-by: Bin Meng <bmeng.cn(a)gmail.com> --- arch/x86/cpu/quark/acpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/cpu/quark/acpi.c b/arch/x86/cpu/quark/acpi.c index 4a02720..7b6fc2f 100644 --- a/arch/x86/cpu/quark/acpi.c +++ b/arch/x86/cpu/quark/acpi.c @@ -67,7 +67,7 @@ void acpi_create_fadt(struct acpi_fadt *fadt, struct acpi_facs *facs, fadt->reset_reg.access_size = ACPI_ACCESS_SIZE_BYTE_ACCESS; fadt->reset_reg.addrl = IO_PORT_RESET; fadt->reset_reg.addrh = 0; - fadt->reset_value = SYS_RST | RST_CPU; + fadt->reset_value = SYS_RST | RST_CPU | FULL_RST; fadt->x_firmware_ctl_l = (u32)facs; fadt->x_firmware_ctl_h = 0; -- 2.7.4

4 12

[U-Boot] [PATCH v2] sysreset: Add support for gpio-restart
by Michal Simek 19 Jul '18

19 Jul '18

The Linux kernel has binding for gpio-restart node. This patch is adding basic support without supporting any optional properties. This driver was tested on Microblaze system where gpio is connected to SoC reset logic. Output value is handled via gpios cells values. In gpio_reboot_request() set_value is writing 1 because dm_gpio_set_value() is capable to changing it when it is ACTIVE_LOW. ... if (desc->flags & GPIOD_ACTIVE_LOW) value = !value; ... Signed-off-by: Michal Simek <michal.simek(a)xilinx.com> Reviewed-by: Philipp Tomsich <philipp.tomsich(a)theobroma-systems.com> Reviewed-by: Simon Glass <sjg(a)chromium.org> --- Changes in v2: - Record file in MAINTAINERS - Fix comment reported by Simon - Kconfig fragment fix - use reset instead of restart --- MAINTAINERS | 1 + drivers/sysreset/Kconfig | 8 ++++++ drivers/sysreset/Makefile | 1 + drivers/sysreset/sysreset_gpio.c | 59 ++++++++++++++++++++++++++++++++++++++++ 4 files changed, 69 insertions(+) create mode 100644 drivers/sysreset/sysreset_gpio.c diff --git a/MAINTAINERS b/MAINTAINERS index 570bc6d1a525..91e4ad7c75a1 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -419,6 +419,7 @@ F: drivers/net/xilinx_axi_emac.c F: drivers/net/xilinx_emaclite.c F: drivers/serial/serial_xuartlite.c F: drivers/spi/xilinx_spi.c +F: drivers/sysreset/sysreset_gpio.c F: drivers/watchdog/xilinx_tb_wdt.c N: xilinx diff --git a/drivers/sysreset/Kconfig b/drivers/sysreset/Kconfig index a6d48e8a662c..cec612ed50dd 100644 --- a/drivers/sysreset/Kconfig +++ b/drivers/sysreset/Kconfig @@ -15,6 +15,14 @@ config SYSRESET if SYSRESET +config SYSRESET_GPIO + bool "Enable support for GPIO reset driver" + select GPIO + help + Reset support via GPIO pin connected reset logic. This is used for + example on Microblaze where reset logic can be controlled via GPIO + pin which triggers cpu reset. + config SYSRESET_PSCI bool "Enable support for PSCI System Reset" depends on ARM_PSCI_FW diff --git a/drivers/sysreset/Makefile b/drivers/sysreset/Makefile index 0da58a1cf6ad..ca533cfefaad 100644 --- a/drivers/sysreset/Makefile +++ b/drivers/sysreset/Makefile @@ -3,6 +3,7 @@ # (C) Copyright 2016 Cadence Design Systems Inc. obj-$(CONFIG_SYSRESET) += sysreset-uclass.o +obj-$(CONFIG_SYSRESET_GPIO) += sysreset_gpio.o obj-$(CONFIG_SYSRESET_PSCI) += sysreset_psci.o obj-$(CONFIG_SYSRESET_SYSCON) += sysreset_syscon.o obj-$(CONFIG_SYSRESET_WATCHDOG) += sysreset_watchdog.o diff --git a/drivers/sysreset/sysreset_gpio.c b/drivers/sysreset/sysreset_gpio.c new file mode 100644 index 000000000000..ed9a49ad08c8 --- /dev/null +++ b/drivers/sysreset/sysreset_gpio.c @@ -0,0 +1,59 @@ +// SPDX-License-Identifier: GPL-2.0 +/* + * Copyright (C) 2018 Xilinx, Inc. - Michal Simek + */ + +#include <common.h> +#include <dm.h> +#include <errno.h> +#include <sysreset.h> +#include <asm/gpio.h> + +struct gpio_reboot_priv { + struct gpio_desc gpio; +}; + +static int gpio_reboot_request(struct udevice *dev, enum sysreset_t type) +{ + struct gpio_reboot_priv *priv = dev_get_priv(dev); + + /* + * When debug log is enabled please make sure that chars won't end up + * in output fifo. Or you can append udelay(); to get enough time + * to HW to emit output fifo. + */ + debug("GPIO reset\n"); + + /* Writing 1 respects polarity (active high/low) based on gpio->flags */ + return dm_gpio_set_value(&priv->gpio, 1); +} + +static struct sysreset_ops gpio_reboot_ops = { + .request = gpio_reboot_request, +}; + +int gpio_reboot_probe(struct udevice *dev) +{ + struct gpio_reboot_priv *priv = dev_get_priv(dev); + + /* + * Linux kernel DT binding contain others optional properties + * which are not supported now + */ + + return gpio_request_by_name(dev, "gpios", 0, &priv->gpio, GPIOD_IS_OUT); +} + +static const struct udevice_id led_gpio_ids[] = { + { .compatible = "gpio-restart" }, + { } +}; + +U_BOOT_DRIVER(gpio_reboot) = { + .id = UCLASS_SYSRESET, + .name = "gpio_restart", + .of_match = led_gpio_ids, + .ops = &gpio_reboot_ops, + .priv_auto_alloc_size = sizeof(struct gpio_reboot_priv), + .probe = gpio_reboot_probe, +}; -- 1.9.1

2 1

[U-Boot] [PATCH v5 0/5] Add support for reading memory configuration from DT at run-time
by Michal Simek 19 Jul '18

19 Jul '18

Hi, this is series which was send by Siva. I have just put there missing Tom's tag which we got and adding more people to TO. Thanks, Michal Changes in v5: - Add Tom's tag - https://lists.denx.de/pipermail/u-boot/2018-June/332810.html - Add Tom's tag - https://lists.denx.de/pipermail/u-boot/2018-June/332810.html Changes in v4: - Rebased on latest master and used available ram_base - Separate the rename patch - Rebased on latest master - None, rebased on latest master Changes in v3: - Used new varibale ram_start - Rename fdtdec_setup_memory_size Changes in v2: - Removed commit reference from description as per comment - Update memory node as per comment - Removed intc and fclk as per comment Siva Durga Prasad Paladugu (5): lib: fdtdec: Update ram_base to store ram start adddress lib: fdtdec: Rename routine fdtdec_setup_memory_size() arm: zynq: Dont define SDRAM_BASE and SDRAM_SIZE in .h arm: zynq: Add Nand flash mini u-boot configuration for zynq arm: zynq: Add parallel NOR flash mini u-boot configuration for zynq arch/arm/dts/Makefile | 2 + arch/arm/dts/zynq-cse-nand.dts | 80 ++++++++++++++++++++ arch/arm/dts/zynq-cse-nor.dts | 88 ++++++++++++++++++++++ arch/arm/mach-mvebu/arm64-common.c | 2 +- board/emulation/qemu-arm/qemu-arm.c | 2 +- board/renesas/alt/alt.c | 2 +- board/renesas/blanche/blanche.c | 2 +- board/renesas/draak/draak.c | 2 +- board/renesas/eagle/eagle.c | 2 +- board/renesas/gose/gose.c | 2 +- board/renesas/koelsch/koelsch.c | 2 +- board/renesas/lager/lager.c | 2 +- board/renesas/porter/porter.c | 2 +- board/renesas/salvator-x/salvator-x.c | 2 +- board/renesas/silk/silk.c | 2 +- board/renesas/stout/stout.c | 2 +- board/renesas/ulcb/ulcb.c | 2 +- board/st/stm32f429-discovery/stm32f429-discovery.c | 2 +- .../st/stm32f429-evaluation/stm32f429-evaluation.c | 2 +- board/st/stm32f469-discovery/stm32f469-discovery.c | 2 +- board/st/stm32h743-disco/stm32h743-disco.c | 2 +- board/st/stm32h743-eval/stm32h743-eval.c | 2 +- board/xilinx/zynq/board.c | 2 +- board/xilinx/zynqmp/zynqmp.c | 2 +- board/xilinx/zynqmp_r5/board.c | 2 +- common/board_f.c | 4 +- configs/zynq_cse_nand_defconfig | 50 ++++++++++++ configs/zynq_cse_nor_defconfig | 50 ++++++++++++ include/configs/zynq_cse.h | 3 - include/fdtdec.h | 16 ++-- lib/fdtdec.c | 3 +- tools/patman/func_test.py | 2 +- tools/patman/test/0000-cover-letter.patch | 2 +- ...-cast-for-sandbox-in-fdtdec_setup_memory_.patch | 4 +- tools/patman/test/test01.txt | 2 +- 35 files changed, 310 insertions(+), 40 deletions(-) create mode 100644 arch/arm/dts/zynq-cse-nand.dts create mode 100644 arch/arm/dts/zynq-cse-nor.dts create mode 100644 configs/zynq_cse_nand_defconfig create mode 100644 configs/zynq_cse_nor_defconfig -- 1.9.1

2 6

[U-Boot] [RFC] Make U-Boot log great again
by Sam Protsenko 18 Jul '18

18 Jul '18

Hi guys, TL;DR This is a suggestion about fixing U-Boot log, which has got worse recently. Right now U-Boot and SPL logs are cluttered with bogus warnings like these (on X15 board, but I'm pretty sure it should appear on many others): Loading Environment from FAT... *** Warning - bad CRC, using default environment Failed (-5) Those are the consequences of next commit: fb69464eae1e ("env: Allow to build multiple environments in Kconfig") Because of this commit, I can see following changes in my .config file: +CONFIG_ENV_IS_IN_FAT=y +CONFIG_ENV_FAT_INTERFACE="mmc" +CONFIG_ENV_FAT_DEVICE_AND_PART="0:1" +CONFIG_ENV_FAT_FILE="uboot.env" which led U-Boot to try and load the environment from different sources. I agree that it's good thing to do and can be useful, but the problem is that the code for loading the environment wasn't changed to handle errors properly. How I suggest to handle that case: 1. If we have two sources for the environment (e.g. FAT partition on SD card and some raw partition on eMMC), we shouldn't print error messages if we were unable to load the environment from one source 2. We should probably print some human-readable information that we didn't find the environment there, let's skip and look for next source (but don't print those warnings/failed messages) 3. And only print the error message in case when U-Boot environment wasn't found at all (on all possible sources). I don't have enough time to fix this by my own right now. But let's discuss how to approach this issue in a best way possible. And if someone wants to step forward and do that -- would be really nice. If no -- I can look into that later. But let's collect some opinions here, first. Thanks.

8 22

[U-Boot] [RESEND PATCH v2 0/2] Add bootlimit to Kconfig
by Alex Kiernan 18 Jul '18

18 Jul '18

3 5

[U-Boot] Commit d233ccb1d84b90 broke MMC access on BeagleBoard xM
by Guillaume GARDET 18 Jul '18

18 Jul '18

Hi, commit d233ccb1d84b901f7e23e6d9b4f2c6a57198b23b (HEAD, refs/bisect/bad) Author: Derald D. Woods <woods.technical(a)gmail.com> Date: Mon Feb 26 17:52:58 2018 -0600 ARM: omap3: beagle: Enable DM_SERIAL, update distro usage and NAND layout broke MMC access on Beagleboard xM (rev. B). For my SD card with 2 partitions, I get the following errors: * 'ls mmc 0:1' returns: ** Unrecognized filesystem type ** * 'ls mmc 0:2' returns: ** Invalid partition 2 ** Not sure which part of this patch cause this bug. Guillaume

2 3

[U-Boot] [PATCH 1/3] bmips: ram: add an option to force the size of the ram
by Philippe Reynes 18 Jul '18

18 Jul '18

This adds an option to force the size of the ram, and avoid the detection of ram size. Signed-off-by: Philippe Reynes <philippe.reynes(a)softathome.com> --- drivers/ram/bmips_ram.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drivers/ram/bmips_ram.c b/drivers/ram/bmips_ram.c index cc37dfa..b5f19c9 100644 --- a/drivers/ram/bmips_ram.c +++ b/drivers/ram/bmips_ram.c @@ -43,6 +43,7 @@ struct bmips_ram_hw { struct bmips_ram_priv { void __iomem *regs; + u32 force_size; const struct bmips_ram_hw *hw; }; @@ -104,7 +105,10 @@ static int bmips_ram_get_info(struct udevice *dev, struct ram_info *info) const struct bmips_ram_hw *hw = priv->hw; info->base = 0x80000000; - info->size = hw->get_ram_size(priv); + if (priv->force_size) + info->size = priv->force_size; + else + info->size = hw->get_ram_size(priv); return 0; } @@ -155,6 +159,8 @@ static int bmips_ram_probe(struct udevice *dev) if (!priv->regs) return -EINVAL; + dev_read_u32(dev, "force-size", &priv->force_size); + priv->hw = hw; return 0; -- 2.7.4

2 5

[U-Boot] [RFC 00/35] sunxi: Add initial CLK, RESET support
by Jagan Teki 18 Jul '18

18 Jul '18

This is series is trying to add initial support for CLK and RESET drivers for Allwinner SoC's with USB as a starting IP. Linux handle both clock and reset as ccu with common DT bindings, but besides that U-Boot handle them separately with individual generic uclass functions. So we need have a separate drivers for CLK and RESET with common DT binding. This series is trying to resolve this by binding the reset driver from CLK driver .bind call. First of all the CLK driver will probe based on DT compatible and the .bind call of CLK driver will bind the respective reset driver based on uclass driver name. I would prefer USB can be initial IP to go, since it doesn't rely on dm pinctrl or any other dm stuff require. Tested this on A64, H5, H3 but I still need to have closer look on other SoCs. All these changes available at u-boot-sunxi/clk Suggestions, Jagan. Andre Przywara (1): sunxi: clk: add DM clock driver template for the A64 SoC Jagan Teki (34): clk: Kconfig: Ascending order to sub directiory kconfigs net: sun8i_emac: Make proper order for include files mtd: sunxi_nand_spl: Make proper order for include files dt-bindings: reset: Sync sun4i-a10-ccu.h from Linux dt-bindings: clock: Sync sun5i-ccu.h from Linux dt-bindings: reset: Sync sun5i-ccu.h from Linux dt-bindings: clock: Sync sun6i-a31-ccu.h from Linux dt-bindings: reset: Sync sun6i-a31-ccu.h from Linux clk: sunxi: Add Kconfig entry clk: sunxi: a64: Add disable function clk: sunxi: a64: Implement USB clocks reset: sunxi: Add DM reset driver template for the A64 SoC reset: sunxi: a64: Bind reset from clock driver reset: Add default request ops reset: sunxi: a64: Implement USB resets clk: sunxi: Add initial CLK driver for H3_H5 reset: sunxi: Add initial RESET driver for H3_H5 clk: sunxi: Add initial CLK driver for A10/A20 reset: sunxi: Add initial RESET driver for A10/A20 clk: sunxi: Add initial CLK driver for A10s/A13 reset: sunxi: Add initial RESET driver for A10s/A13 clk: sunxi: Add initial CLK driver for A31/A31s reset: sunxi: Add initial RESET driver for A31/A31s clk: sunxi: Add initial CLK driver for A23 reset: sunxi: Add initial RESET driver for A23 clk: sunxi: a23: Add CLK support for A33 reset: sunxi: a23: Add RESET support A33 clk: sunxi: Add initial CLK driver for A83T reset: sunxi: Add initial RESET driver for A83T sunxi: Enable CLK and RESET musb-new: sunxi: Use CLK and RESET support phy: sun4i-usb: Use CLK and RESET support sunxi: usb: Switch to Generic host controllers usb: host: Drop [e-o]hci-sunxi drivers arch/arm/include/asm/arch-sunxi/clock.h | 8 + arch/arm/mach-sunxi/Kconfig | 18 ++ configs/A10-OLinuXino-Lime_defconfig | 1 + configs/A10s-OLinuXino-M_defconfig | 1 + configs/A13-OLinuXinoM_defconfig | 1 + configs/A13-OLinuXino_defconfig | 1 + configs/A20-OLinuXino-Lime2-eMMC_defconfig | 1 + configs/A20-OLinuXino-Lime2_defconfig | 1 + configs/A20-OLinuXino-Lime_defconfig | 1 + configs/A20-Olimex-SOM204-EVB_defconfig | 2 + configs/Auxtek-T003_defconfig | 1 + configs/Auxtek-T004_defconfig | 1 + configs/Bananapi_defconfig | 1 + configs/Bananapi_m2m_defconfig | 1 + configs/Bananapro_defconfig | 1 + configs/CHIP_defconfig | 1 + configs/CHIP_pro_defconfig | 1 + configs/CSQ_CS908_defconfig | 1 + configs/Colombus_defconfig | 1 + configs/Cubieboard2_defconfig | 1 + configs/Cubieboard_defconfig | 1 + configs/Cubietruck_plus_defconfig | 1 + configs/Hummingbird_A31_defconfig | 1 + configs/Itead_Ibox_A20_defconfig | 1 + configs/Linksprite_pcDuino3_Nano_defconfig | 1 + configs/Linksprite_pcDuino3_defconfig | 1 + configs/Linksprite_pcDuino_defconfig | 1 + configs/MK808C_defconfig | 1 + configs/Marsboard_A10_defconfig | 1 + configs/Mele_A1000G_quad_defconfig | 1 + configs/Mele_A1000_defconfig | 1 + configs/Mele_I7_defconfig | 1 + configs/Mele_M3_defconfig | 1 + configs/Mele_M5_defconfig | 1 + configs/Mele_M9_defconfig | 1 + configs/Mini-X_defconfig | 1 + configs/Orangepi_defconfig | 1 + configs/Orangepi_mini_defconfig | 1 + configs/Sinlinx_SinA31s_defconfig | 1 + configs/Sinlinx_SinA33_defconfig | 1 + configs/Sinovoip_BPI_M2_Plus_defconfig | 1 + configs/Sinovoip_BPI_M2_defconfig | 1 + configs/Sinovoip_BPI_M3_defconfig | 1 + configs/Wexler_TAB7200_defconfig | 1 + configs/Wobo_i5_defconfig | 1 + configs/a64-olinuxino_defconfig | 1 + configs/ba10_tv_box_defconfig | 1 + configs/bananapi_m1_plus_defconfig | 1 + configs/bananapi_m64_defconfig | 1 + configs/ga10h_v1_1_defconfig | 1 + configs/h8_homlet_v2_defconfig | 1 + configs/i12-tvbox_defconfig | 1 + configs/icnova-a20-swac_defconfig | 1 + configs/inet1_defconfig | 1 + configs/inet_q972_defconfig | 1 + configs/jesurun_q5_defconfig | 1 + configs/libretech_all_h3_cc_h2_plus_defconfig | 1 + configs/libretech_all_h3_cc_h3_defconfig | 1 + configs/libretech_all_h3_cc_h5_defconfig | 1 + configs/mixtile_loftq_defconfig | 1 + configs/mk802_a10s_defconfig | 1 + configs/mk802_defconfig | 1 + configs/mk802ii_defconfig | 1 + configs/nanopi_a64_defconfig | 1 + configs/nanopi_m1_defconfig | 1 + configs/nanopi_m1_plus_defconfig | 1 + configs/nanopi_neo2_defconfig | 1 + configs/nanopi_neo_air_defconfig | 1 + configs/nanopi_neo_defconfig | 1 + configs/nanopi_neo_plus2_defconfig | 1 + configs/orangepi_2_defconfig | 1 + configs/orangepi_lite_defconfig | 1 + configs/orangepi_one_defconfig | 1 + configs/orangepi_pc2_defconfig | 1 + configs/orangepi_pc_defconfig | 1 + configs/orangepi_pc_plus_defconfig | 1 + configs/orangepi_plus2e_defconfig | 1 + configs/orangepi_plus_defconfig | 1 + configs/orangepi_prime_defconfig | 1 + configs/orangepi_r1_defconfig | 1 + configs/orangepi_win_defconfig | 1 + configs/orangepi_zero_defconfig | 1 + configs/orangepi_zero_plus2_defconfig | 1 + configs/orangepi_zero_plus_defconfig | 1 + configs/parrot_r16_defconfig | 1 + configs/pine64_plus_defconfig | 1 + configs/r7-tv-dongle_defconfig | 1 + configs/sopine_baseboard_defconfig | 1 + configs/sun8i_a23_evb_defconfig | 1 + configs/sunxi_Gemei_G9_defconfig | 1 + configs/tbs_a711_defconfig | 1 + drivers/clk/Kconfig | 9 +- drivers/clk/Makefile | 1 + drivers/clk/sunxi/Kconfig | 60 +++++ drivers/clk/sunxi/Makefile | 15 ++ drivers/clk/sunxi/clk_a10.c | 105 ++++++++ drivers/clk/sunxi/clk_a10s.c | 105 ++++++++ drivers/clk/sunxi/clk_a23.c | 113 +++++++++ drivers/clk/sunxi/clk_a31.c | 130 ++++++++++ drivers/clk/sunxi/clk_a64.c | 141 +++++++++++ drivers/clk/sunxi/clk_a83t.c | 120 +++++++++ drivers/clk/sunxi/clk_h3.c | 131 ++++++++++ drivers/clk/sunxi/clk_sunxi.c | 39 +++ drivers/mtd/nand/sunxi_nand_spl.c | 4 +- drivers/net/sun8i_emac.c | 8 +- drivers/phy/allwinner/phy-sun4i-usb.c | 63 +++-- drivers/reset/Kconfig | 2 + drivers/reset/Makefile | 1 + drivers/reset/reset-uclass.c | 10 +- drivers/reset/sunxi/Kconfig | 61 +++++ drivers/reset/sunxi/Makefile | 13 + drivers/reset/sunxi/reset_a10.c | 95 +++++++ drivers/reset/sunxi/reset_a10s.c | 93 +++++++ drivers/reset/sunxi/reset_a23.c | 111 +++++++++ drivers/reset/sunxi/reset_a31.c | 123 +++++++++ drivers/reset/sunxi/reset_a64.c | 115 +++++++++ drivers/reset/sunxi/reset_a83t.c | 117 +++++++++ drivers/reset/sunxi/reset_h3.c | 121 +++++++++ drivers/usb/host/Kconfig | 2 + drivers/usb/host/Makefile | 2 - drivers/usb/host/ehci-sunxi.c | 204 --------------- drivers/usb/host/ohci-sunxi.c | 233 ------------------ drivers/usb/musb-new/sunxi.c | 82 +++--- include/configs/sun4i.h | 4 - include/configs/sun50i.h | 5 - include/configs/sun5i.h | 4 - include/configs/sun6i.h | 4 - include/configs/sun7i.h | 4 - include/configs/sun8i.h | 4 - include/configs/sunxi-common.h | 1 - include/dt-bindings/clock/sun5i-ccu.h | 106 ++++++++ include/dt-bindings/clock/sun6i-a31-ccu.h | 191 ++++++++++++++ include/dt-bindings/reset/sun4i-a10-ccu.h | 69 ++++++ include/dt-bindings/reset/sun5i-ccu.h | 32 +++ include/dt-bindings/reset/sun6i-a31-ccu.h | 106 ++++++++ scripts/config_whitelist.txt | 2 - 136 files changed, 2549 insertions(+), 528 deletions(-) create mode 100644 drivers/clk/sunxi/Kconfig create mode 100644 drivers/clk/sunxi/Makefile create mode 100644 drivers/clk/sunxi/clk_a10.c create mode 100644 drivers/clk/sunxi/clk_a10s.c create mode 100644 drivers/clk/sunxi/clk_a23.c create mode 100644 drivers/clk/sunxi/clk_a31.c create mode 100644 drivers/clk/sunxi/clk_a64.c create mode 100644 drivers/clk/sunxi/clk_a83t.c create mode 100644 drivers/clk/sunxi/clk_h3.c create mode 100644 drivers/clk/sunxi/clk_sunxi.c create mode 100644 drivers/reset/sunxi/Kconfig create mode 100644 drivers/reset/sunxi/Makefile create mode 100644 drivers/reset/sunxi/reset_a10.c create mode 100644 drivers/reset/sunxi/reset_a10s.c create mode 100644 drivers/reset/sunxi/reset_a23.c create mode 100644 drivers/reset/sunxi/reset_a31.c create mode 100644 drivers/reset/sunxi/reset_a64.c create mode 100644 drivers/reset/sunxi/reset_a83t.c create mode 100644 drivers/reset/sunxi/reset_h3.c delete mode 100644 drivers/usb/host/ehci-sunxi.c delete mode 100644 drivers/usb/host/ohci-sunxi.c create mode 100644 include/dt-bindings/clock/sun5i-ccu.h create mode 100644 include/dt-bindings/clock/sun6i-a31-ccu.h create mode 100644 include/dt-bindings/reset/sun4i-a10-ccu.h create mode 100644 include/dt-bindings/reset/sun5i-ccu.h create mode 100644 include/dt-bindings/reset/sun6i-a31-ccu.h -- 2.17.1

4 44

[U-Boot] [PATCH v4 0/6] Generic file system firmware loader DM
by tien.fong.chee＠intel.com 18 Jul '18

18 Jul '18

From: Tien Fong Chee <tien.fong.chee(a)intel.com> This patchset contains generic file system loader DM which is very close to Linux firmware loader but for U-Boot framework. Generic file system firmware loader can be used load whatever into target location, and then consumer driver would use it to program whatever, ie. the FPGA. This version mainly resolved comments from Simon and Anatolij in [v3]. Patch set for sandbox will be sent out separately. This series is working on top of u-boot-socfpga.git - http://git.denx.de/u-boot.git . [v3]: https://www.mail-archive.com/u-boot@lists.denx.de/msg290433.html [v2]: https://www.mail-archive.com/u-boot@lists.denx.de/msg286979.html [v1]: https://www.mail-archive.com/u-boot@lists.denx.de/msg286294.html v3 -> v4 changes ---------------- - Adding mounting and unmounting for UBI. - Adding some new enviroment variables. - Removed storage_device from FDT. - devpart from fdt changed to phandlepart for supporting block device node pointer and partition. - Adding new function for getting block device description based on device. - Adding new function for freeing firmware buffer. - Update firmware doc and device tree binding doc. Tien Fong Chee (6): cmd: ubifs: Move ubifs_initialized checking into cmd_ubifs_umount() cmd: ubifs: Factor out some checking codes into cmd_ubifs_mount() block: Add a function to find block device descriptor doc: Add new doc for file system firmware loader driver model doc: dtbinding: Add file system firmware loader binding document common: Generic loader for file system cmd/ubifs.c | 40 ++-- doc/device-tree-bindings/chosen.txt | 21 ++ doc/device-tree-bindings/misc/fs_loader.txt | 48 +++++ doc/driver-model/fs_firmware_loader.txt | 133 +++++++++++++ drivers/block/blk-uclass.c | 23 +++ drivers/misc/Kconfig | 10 + drivers/misc/Makefile | 1 + drivers/misc/fs_loader.c | 295 ++++++++++++++++++++++++++++ include/blk.h | 9 + include/dm/uclass-id.h | 1 + include/fs_loader.h | 79 ++++++++ include/ubi_uboot.h | 2 + 12 files changed, 645 insertions(+), 17 deletions(-) create mode 100644 doc/device-tree-bindings/misc/fs_loader.txt create mode 100644 doc/driver-model/fs_firmware_loader.txt create mode 100644 drivers/misc/fs_loader.c create mode 100644 include/fs_loader.h -- 2.2.0

2 1

[U-Boot] Clarification ECC bytes
by Fernando AE 18 Jul '18

18 Jul '18

Hello all, I'm rebasing our internal code over v2017.11 and I found an unexpected change in drivers/mtd/nand/nand_base.c: In the function nand_scan_tail: ----- (...) case NAND_ECC_SOFT_BCH: (...) /* * Board driver should supply ecc.size and ecc.strength values * to select how many bits are correctable. Otherwise, default * to 4 bits for large page devices. */ if (!ecc->size && (mtd->oobsize >= 64)) { ecc->size = 512; ecc->strength = 4; } /* See nand_bch_init() for details. */ ecc->bytes = 0; ecc->priv = nand_bch_init(mtd); ----- This means that ecc->bytes = 0 is overwritting the board driver supplied value. Actually, back in v2014.03, that specific line (ecc->bytes = 0) did not exit. I also checked today in v2018.07 and master, and this potential bug is still there. Could someone kindly help me here? Removing this line is safe? Or I'm missing something? Thanks in advance, Fernando

2 2