February 2018 - U-Boot

[U-Boot] [RFC 00/14] bmips: add bcm6348-enet support
by Álvaro Fernández Rojas 11 Mar '18

11 Mar '18

In order to add bcm6348-enet support, dma-uclass must be extended to support dma channels and rewordked to operate like the other dm uclass (clk, reset...). This is an RFC, so please give you feedback on the things that I should fix or rework. Álvaro Fernández Rojas (14): dma: add dma channels support and improve uclass dma: add bcm6348-iudma support bmips: bcm6338: add bcm6348-iudma support bmips: bcm6348: add bcm6348-iudma support bmips: bcm6358: add bcm6348-iudma support phy: add support for internal phys net: add support for bcm6348-enet bmips: bcm6338: add support for bcm6348-enet bmips: enable f@st1704 enet support bmips: bcm6348: add support for bcm6348-enet bmips: enable ct-5361 enet support bmips: bcm6358: add support for bcm6348-enet bmips: enable hg556a enet support bmips: enable nb4-ser enet support arch/mips/dts/brcm,bcm6338.dtsi | 29 ++ arch/mips/dts/brcm,bcm6348.dtsi | 42 +++ arch/mips/dts/brcm,bcm6358.dtsi | 46 +++ arch/mips/dts/comtrend,ct-5361.dts | 12 + arch/mips/dts/huawei,hg556a.dts | 12 + arch/mips/dts/sagem,f(a)st1704.dts | 12 + arch/mips/dts/sfr,nb4-ser.dts | 24 ++ configs/comtrend_ct5361_ram_defconfig | 8 +- configs/huawei_hg556a_ram_defconfig | 8 +- configs/sagem_f@st1704_ram_defconfig | 9 +- configs/sfr_nb4-ser_ram_defconfig | 8 +- drivers/dma/Kconfig | 8 + drivers/dma/Makefile | 1 + drivers/dma/bcm6348-iudma.c | 498 ++++++++++++++++++++++++++++++++ drivers/dma/dma-uclass.c | 212 +++++++++++--- drivers/mtd/spi/sf-uclass.c | 17 ++ drivers/mtd/spi/spi_flash.c | 11 +- drivers/net/Kconfig | 9 + drivers/net/Makefile | 1 + drivers/net/bcm6348-eth.c | 517 ++++++++++++++++++++++++++++++++++ include/configs/bmips_common.h | 5 +- include/dma-uclass.h | 110 ++++++++ include/dma.h | 226 +++++++++++---- include/dt-bindings/dma/bcm6338-dma.h | 15 + include/dt-bindings/dma/bcm6348-dma.h | 17 ++ include/dt-bindings/dma/bcm6358-dma.h | 17 ++ include/phy.h | 2 + include/spi_flash.h | 3 + 28 files changed, 1780 insertions(+), 99 deletions(-) create mode 100644 drivers/dma/bcm6348-iudma.c create mode 100644 drivers/net/bcm6348-eth.c create mode 100644 include/dma-uclass.h create mode 100644 include/dt-bindings/dma/bcm6338-dma.h create mode 100644 include/dt-bindings/dma/bcm6348-dma.h create mode 100644 include/dt-bindings/dma/bcm6358-dma.h -- 2.11.0

6 105

[U-Boot] [PATCH] mx6sabresd: Select the CONFIG_EFI_PARTITION option
by Fabio Estevam 10 Mar '18

10 Mar '18

From: Fabio Estevam <fabio.estevam(a)nxp.com> With fastboot support enabled, it is useful to be able to list the eMMC EFI partitions, so select the CONFIG_EFI_PARTITION option. Signed-off-by: Fabio Estevam <fabio.estevam(a)nxp.com> --- Hi Stefano, It seems you picked the v1 of my fastboot patch instead of v2. Hence I am sending a new patch that only selects CONFIG_EFI_PARTITION. configs/mx6sabresd_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/configs/mx6sabresd_defconfig b/configs/mx6sabresd_defconfig index feb385d..55709e8 100644 --- a/configs/mx6sabresd_defconfig +++ b/configs/mx6sabresd_defconfig @@ -48,6 +48,7 @@ CONFIG_CMD_EXT4=y CONFIG_CMD_EXT4_WRITE=y CONFIG_CMD_FAT=y CONFIG_CMD_FS_GENERIC=y +CONFIG_EFI_PARTITION=y CONFIG_ENV_IS_IN_MMC=y CONFIG_SPI_FLASH=y CONFIG_SPI_FLASH_STMICRO=y -- 2.7.4

3 4

[U-Boot] [PATCH] arm: socfpga: gen5: Enabling cache and TLB maintenance broadcast
by chin.liang.see＠intel.com 08 Mar '18

08 Mar '18

From: Chin Liang See <chin.liang.see(a)intel.com> Enabling cache and TLB maintenance broadcast through ACTLR as required by Linux. Signed-off-by: Chin Liang See <chin.liang.see(a)intel.com> --- arch/arm/mach-socfpga/misc_gen5.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-socfpga/misc_gen5.c b/arch/arm/mach-socfpga/misc_gen5.c index a7dcacc..7c7a708 100644 --- a/arch/arm/mach-socfpga/misc_gen5.c +++ b/arch/arm/mach-socfpga/misc_gen5.c @@ -239,7 +239,7 @@ static u32 iswgrp_handoff[8]; int arch_early_init_r(void) { - int i; + int i, val; /* * Write magic value into magic register to unlock support for @@ -285,6 +285,15 @@ int arch_early_init_r(void) socfpga_per_reset(SOCFPGA_RESET(NAND), 0); #endif + /* Enable cache and TLB maintainance broadcast as required by Linux */ + /* Read auxiliary control register */ + asm volatile ("mrc p15, 0, %0, c1, c0, 1\n\t" : "=r"(val)); + val |= (1 << 0); + /* Write auxiliary control register */ + asm volatile ("mcr p15, 0, %0, c1, c0, 1\n\t" : : "r"(val)); + CP15DSB; + CP15ISB; + return 0; } -- 2.2.2

4 3

[U-Boot] [RFC] ns16550: Add support for AUX regs usage on some ARC SoCs
by Alexey Brodkin 08 Mar '18

08 Mar '18

Synopsys Data Fusion subsystem (DFSS) is targeted to deeply built-in use-cases and so to save some silicon area decision was made to escape usage of any busses and use instead directly wired to CPU peripherals. And one of those is DW APB UART. Later DFSS became a part of larger and more complicated SoCs with some other peripherals connected via common buses but default UART is still used via ARC core's auxulary registers which are not mapped to "normal" address space and we use very special instructions to access them, thus we cannot simply reuse whatever accessor we have in 16550 UART as of now. Also we cannot just switch inb()/outb() to access ARC AUX regs always for DFSS because other peripherals have normal memory-mapped control registers and we need to use normal accessors for them. Frankly I don't like a lot what I did here but otherwise if I create a special driver for this I'll need to reimplement ns16550_serial_ops.putc()/getc() which will be pure copy-paseted from ns16550.c because the only difference is only in ns16550_{read|write}b(). As mentioned above we cannot remap those auxiliary registers to normal memory address-space and thus we have to use very special accessors write_aux_reg()/read_aux_reg() that directly use special CPU intructions (namely LR/SR) for dealing with ARC AUX regs. Also note here I just use a check for a particular SoC being selected (CONFIG_ARCH_DFSS will be introduced shortly) but that is done just for simplicity, otherwise it might be a slecial Kconfig option for NS16550 or anything else. I'd like to know what people think about possible colutions here. And as always any comments are much appreciated! Signed-off-by: Alexey Brodkin <abrodkin(a)synopsys.com> Cc: Simon Glass <sjg(a)chromium.org> Cc: Tom Rini <trini(a)konsulko.com> Cc: Stefan Roese <sr(a)denx.de> --- drivers/serial/ns16550.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/serial/ns16550.c b/drivers/serial/ns16550.c index 6f9ce689cfff..75f342f337f1 100644 --- a/drivers/serial/ns16550.c +++ b/drivers/serial/ns16550.c @@ -13,6 +13,9 @@ #include <watchdog.h> #include <linux/types.h> #include <asm/io.h> +#ifdef CONFIG_ARCH_DFSS +#include <asm/arcregs.h> +#endif DECLARE_GLOBAL_DATA_PTR; @@ -53,7 +56,9 @@ DECLARE_GLOBAL_DATA_PTR; static inline void serial_out_shift(void *addr, int shift, int value) { -#ifdef CONFIG_SYS_NS16550_PORT_MAPPED +#ifdef CONFIG_ARCH_DFSS + write_aux_reg((int)addr, value); +#elif defined(CONFIG_SYS_NS16550_PORT_MAPPED) outb(value, (ulong)addr); #elif defined(CONFIG_SYS_NS16550_MEM32) && !defined(CONFIG_SYS_BIG_ENDIAN) out_le32(addr, value); @@ -70,7 +75,9 @@ static inline void serial_out_shift(void *addr, int shift, int value) static inline int serial_in_shift(void *addr, int shift) { -#ifdef CONFIG_SYS_NS16550_PORT_MAPPED +#ifdef CONFIG_ARCH_DFSS + return read_aux_reg((int)addr); +#elif defined(CONFIG_SYS_NS16550_PORT_MAPPED) return inb((ulong)addr); #elif defined(CONFIG_SYS_NS16550_MEM32) && !defined(CONFIG_SYS_BIG_ENDIAN) return in_le32(addr); -- 2.14.3

3 10

[U-Boot] [RFC 1/1] dm: video: tegra124: incorrect logical condition
by Heinrich Schuchardt 07 Mar '18

07 Mar '18

2 << 24 | A is always true. To use check against a bitmask we need &. Identified with cppcheck. Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- I do not have the hardware available. But the current coding is fishy. Please, clarify what should be coded here. --- drivers/video/tegra124/sor.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/tegra124/sor.c b/drivers/video/tegra124/sor.c index 700ab25d46..4b3381fae2 100644 --- a/drivers/video/tegra124/sor.c +++ b/drivers/video/tegra124/sor.c @@ -669,7 +669,7 @@ static void tegra_dc_sor_config_panel(struct tegra_dc_sor_data *sor, tegra_sor_write_field(sor, CSTM, CSTM_ROTCLK_DEFAULT_MASK | CSTM_LVDS_EN_ENABLE, - 2 << CSTM_ROTCLK_SHIFT | + 2 << CSTM_ROTCLK_SHIFT & is_lvds ? CSTM_LVDS_EN_ENABLE : CSTM_LVDS_EN_DISABLE); -- 2.15.1

2 2

[U-Boot] spi: Zapping non-dm drivers, deadline: v2018.09
by Jagan Teki 06 Mar '18

06 Mar '18

Due to adding various new functionalities with SPI and SPI-FLASH subsystems which are rounding in Mailing list for year+ [1] these long term supporting spi driver which never seen any update with driver-model conversion. We support to write another stack code for supporting these legacy stuff, but things become more difficult. So I'm finally giving deadlines for these drivers to respective driver or board developers to convert them as soon as possible. PS: We all agree some special platforms has some difficulties with dm-conversion let's discuss. No dm conversion yet: ---------------------------- drivers/spi/cf_spi.c drivers/spi/fsl_espi.c drivers/spi/lpc32xx_ssp.c drivers/spi/mpc8xx_spi.c drivers/spi/mpc8xxx_spi.c drivers/spi/mxs_spi.c drivers/spi/sh_qspi.c drivers/spi/sh_spi.c drivers/spi/soft_spi_legacy.c Partially converted: ------------------------- drivers/spi/atcspi200_spi.c drivers/spi/atmel_spi.c drivers/spi/davinci_spi.c drivers/spi/fsl_dspi.c drivers/spi/fsl_qspi.c drivers/spi/kirkwood_spi.c drivers/spi/mxc_spi.c drivers/spi/omap3_spi.c drivers/spi/ti_qspi.cM I would like to see these legacy drivers with full dm-conversion or zapped in v2018.09 version of U-Boot. [1] http://u-boot.10912.n7.nabble.com/PATCH-v10-00-27-dm-Generic-MTD-Subsystem-… Jagan. -- Jagan Teki Senior Linux Kernel Engineer | Amarula Solutions U-Boot, Linux | Upstream Maintainer Hyderabad, India.

6 10

[U-Boot] [UBOOT PATCH v2 0/2] eeprom: Moved eeprom u-boot headers to the Kconfig
by Vipul Kumar 06 Mar '18

06 Mar '18

This series of patch added Kconfig support for eeprom u-boot headers and enabled in respective defconfig. These are the configs: -CONFIG_ZYNQ_EEPROM_BUS -CONFIG_ZYNQ_GEM_EEPROM_ADDR -Changes in v2: - Removed CONFIG_ZYNQ_EEPROM for zynqmp - Enabled configs defined under CONFIG_ZYNQ_EEPROM for zynq - in defconfig and removed CONFIG_ZYNQ_EEPROM. - Added depends on ARCH_ZYNQ - Branch: u-boot-microblaze/kconfig Vipul Kumar (2): eeprom: Enabled eeprom u-boot headers in defconfig eeprom: Added Kconfig support for eeprom u-boot headers configs/syzygy_hub_defconfig | 1 + configs/xilinx_zynqmp_zcu102_rev1_0_defconfig | 2 ++ configs/xilinx_zynqmp_zcu102_revA_defconfig | 2 ++ configs/xilinx_zynqmp_zcu102_revB_defconfig | 2 ++ configs/zynq_zc702_defconfig | 6 ++++++ configs/zynq_zc706_defconfig | 6 ++++++ configs/zynq_zybo_defconfig | 1 + drivers/misc/Kconfig | 14 ++++++++++++++ include/configs/syzygy_hub.h | 1 - include/configs/xilinx_zynqmp_ep.h | 1 - include/configs/xilinx_zynqmp_zcu102.h | 2 -- include/configs/zynq-common.h | 9 --------- include/configs/zynq_zc70x.h | 2 -- include/configs/zynq_zybo.h | 1 - 14 files changed, 34 insertions(+), 16 deletions(-) -- 2.7.4 This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

2 4

[U-Boot] [PATCH] pwm-backlight: make power-supply as option
by Kever Yang 06 Mar '18

06 Mar '18

Some pwm backlight may not need 'power-supply', let's make it as option in pwm-backlight driver. Signed-off-by: Kever Yang <kever.yang(a)rock-chips.com> --- drivers/video/pwm_backlight.c | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/drivers/video/pwm_backlight.c b/drivers/video/pwm_backlight.c index fbd7bf7..f40e57b 100644 --- a/drivers/video/pwm_backlight.c +++ b/drivers/video/pwm_backlight.c @@ -32,16 +32,18 @@ static int pwm_backlight_enable(struct udevice *dev) uint duty_cycle; int ret; - plat = dev_get_uclass_platdata(priv->reg); - debug("%s: Enable '%s', regulator '%s'/'%s'\n", __func__, dev->name, - priv->reg->name, plat->name); - ret = regulator_set_enable(priv->reg, true); - if (ret) { - debug("%s: Cannot enable regulator for PWM '%s'\n", __func__, - dev->name); - return ret; + if (priv->reg) { + plat = dev_get_uclass_platdata(priv->reg); + debug("%s: Enable '%s', regulator '%s'/'%s'\n", __func__, + dev->name, priv->reg->name, plat->name); + ret = regulator_set_enable(priv->reg, true); + if (ret) { + debug("%s: Cannot enable regulator for PWM '%s'\n", + __func__, dev->name); + return ret; + } + mdelay(120); } - mdelay(120); duty_cycle = priv->period_ns * (priv->default_level - priv->min_level) / (priv->max_level - priv->min_level + 1); @@ -68,10 +70,8 @@ static int pwm_backlight_ofdata_to_platdata(struct udevice *dev) debug("%s: start\n", __func__); ret = uclass_get_device_by_phandle(UCLASS_REGULATOR, dev, "power-supply", &priv->reg); - if (ret) { + if (ret) debug("%s: Cannot get power supply: ret=%d\n", __func__, ret); - return ret; - } ret = gpio_request_by_name(dev, "enable-gpios", 0, &priv->enable, GPIOD_IS_OUT); if (ret) { -- 1.9.1

3 2

[U-Boot] [PATCH v4 0/4] dm: video: Correct color ANSI escape sequence support
by Heinrich Schuchardt 06 Mar '18

06 Mar '18

Support special rendition code 0 - reset attributes. Support special rendition code 1 - increased intensity (bold). Get RGB sequence in pixels right (swap blue and red). Do not set reserved bits. Use u32 instead of unsigned for color bit mask. qemu-system-i386 -display sdl -vga virtio and qemu-system-i386 -display sdl -vga cirrus now display the same colors as qemu-system-i386 -nographic Testing is possible via setenv efi_selftest test output bootefi selftest --- v4: Fix a build warning leading to a Travis error. Rename a variable. v3: Split single patch up into a series Use constants for colors v2: SGR 0 should reset the colors and the attributes. --- Heinrich Schuchardt (4): dm: video: show correct colors in graphical console dm: video: correctly clean background in 16bit mode dm: video: use constants to refer to colors dm: video: support increased intensity (bold) drivers/video/vidconsole-uclass.c | 86 ++++++++++++++++++++++++++------------- drivers/video/video-uclass.c | 38 +++++++++++++---- include/video.h | 13 +++++- include/video_console.h | 43 ++++++++++++++++++++ test/dm/video.c | 2 +- 5 files changed, 142 insertions(+), 40 deletions(-) -- 2.14.2

3 7

[U-Boot] [PATCH v10 00/27] dm: Generic MTD Subsystem, with SPI-NOR interface
by Jagan Teki 06 Mar '18

06 Mar '18

Compared to previous series’s [1], [2], [3] and [4] this patch set redefined most of the implementation suitable to fit into existing driver-model. MTD is generic subsystem for underlying flash devices like nand, parallel nor, spinor, dataflash etc. So to drive this theory with driver model(with an example of block layer) mtd is common device interaction for most of memory technology flashes like nand, parallel nor, spinor, dataflash etc, these are treated as interface types wrt u-boot driver model. Once the respective interface driver bind happen, the uclass driver will pass an 'interface type' to mtd layer to create device for it, for example once spinor ULASS_SPI_NOR driver bind happen, the uclass driver of spinor will pass MTD_IF_TYPE_SPI_NOR interface type to create mtd device for spinor devices. SPI-NOR: ======= Some of the SPI device drivers at drivers/spi not a real spi controllers, Unlike normal/generic SPI controllers they operates only with SPI-NOR flash devices. these were technically termed as SPI-NOR controllers, Ex: drivers/spi/fsl_qspi.c The problem with these were resides at drivers/spi is entire SPI layer becomes SPI-NOR flash oriented which is absolutely a wrong indication where SPI layer getting effected more with flash operations - So this SPI-NOR core will resolve this issue by separating all SPI-NOR flash operations from spi layer and creats a generic layer called SPI-NOR core which can be used to interact SPI-NOR to SPI driver interface layer and the SPI-NOR controller driver. ======================================= cmd/spinor.c ======================================= mtd-uclass.c ======================================= spi-nor-uclass.c ======================================= spi-nor.c ======================================= m25p80.c zynq_qspinor.c ======================================= spi-uclass.c ======================================= zynq_qspi.c ======================================= #####SPI NOR chip###### ======================================= Changes for v10: - Update Simon's R-B tag - Add mtd dm test case - implemented entire code wrt MTD, with interface type code size: ========== before: $ arm-linux-gnueabi-size u-boot text data bss dec hex filename 473712 15152 222568 711432 adb08 u-boot $ du -hs u-boot-dtb.img 488K u-boot-dtb.img after: $ arm-linux-gnueabi-size u-boot text data bss dec hex filename 470124 14352 222584 707060 ac9f4 u-boot $ du -hs u-boot-dtb.img 484K u-boot-dtb.img approximately 4KiB but DM_SPI_FLASH still there which can be removed once support added in SPL test log: ======== Zynq> spinor spinor - SPI-NOR Sub-system Usage: spinor list - show list of spinor devices spinor info - show current spinor device info spinor dev [devnum] - show or set current spinor device spinor erase offset len - erase 'len' bytes from 'offset' spinor write addr to len - write 'len' bytes to 'to' from 'addr' spinor read addr from len - read 'len' bytes from 'from' to 'addr' spinor protect lock/unlock sector len - protect/unprotect 'len' bytes starting at address 'sector' Zynq> spinor list flash@0: 0 spi-nor@e000d000: 1 Zynq> spinor dev 0 switch to dev #0, OK spinor0 is current device Zynq> spinor info bus: flash@0: 0 device: s25fl128s_64k page size: 256 B erase size: 64 KiB size: 16 MiB Zynq> spinor erase 0xE00000 0x100000 SPI-NOR: 1048576 bytes @ 0xe00000 Erased: OK Zynq> mw.b 0x100 0xcc 0x100000 Zynq> spinor write 0x100 0xE00000 0x100000 device 0 offset 0xe00000, size 0x100000 SPI-NOR: 1048576 bytes @ 0xe00000 Written: OK Zynq> spinor read 0x3000000 0xE00000 0x100000 device 0 offset 0xe00000, size 0x100000 SPI-NOR: 1048576 bytes @ 0xe00000 Read: OK Zynq> cmp.b 0x3000000 0x100 0x100000 Total of 1048576 byte(s) were the same Zynq> spinor dev 1 switch to dev #1, OK spinor1 is current device Zynq> spinor info bus: spi-nor@e000d000: 1 device: s25fl128s_64k page size: 256 B erase size: 64 KiB size: 16 MiB Zynq> spinor erase 0xE00000 0x100000 SPI-NOR: 1048576 bytes @ 0xe00000 Erased: OK Zynq> mw.b 0x100 0xbb 0x100000 Zynq> spinor write 0x100 0xE00000 0x100000 device 0 offset 0xe00000, size 0x100000 SPI-NOR: 1048576 bytes @ 0xe00000 Written: OK Zynq> spinor read 0x3000000 0xE00000 0x100000 device 0 offset 0xe00000, size 0x100000 SPI-NOR: 1048576 bytes @ 0xe00000 Read: OK Zynq> cmp.b 0x3000000 0x100 0x100000 Total of 1048576 byte(s) were the same WIP: === - to support non-dm code - to support spinor SPL Repo: ==== $ git clone git://git.denx.de/u-boot-spi.git $ cd u-boot-spi $ git checkout -b mtd-spinor-working origin/mtd-spinor-working [1] https://lists.denx.de/pipermail/u-boot/2016-October/271459.html [2] http://lists.denx.de/pipermail/u-boot/2016-March/249286.html [3] http://lists.denx.de/pipermail/u-boot/2016-February/245418.html [4] [PATCH RFC v8 00/16] SPI-NOR/MTD addition Jagan Teki (27): mtd: Add mtd core ops mtd: add mtd device create operations mtd: add SPI-NOR core support mtd: spi-nor: sync/modify sst write operations mtd: spi-nor: sync/modify lock operations mtd: spi-nor: Kconfig: Add MTD_SPI_NOR entry mtd: spi-nor: Kconfig: Add MTD_SPI_NOR_USE_4K_SECTORS mtd: spi-nor: Kconfig: Add SPI_NOR_MISC entry mtd: spi-nor: Kconfig: Add SPI_NOR_MACRONIX entry mtd: spi-nor: Kconfig: Add SPI_NOR_SPANSION entry mtd: spi-nor: Kconfig: Add SPI_NOR_STMICRO entry mtd: spi-nor: Kconfig: Add SPI_NOR_SST entry mtd: spi-nor: Kconfig: Add SPI_NOR_WINBOND entry mtd-uclass: use platdata_auto_alloc spi: Add spi_write_then_read mtd: spi-nor: Add m25p80 driver mtd: spi-nor: Kconfig: Add MTD_M25P80 entry mtd: spi-nor: Add zynq qspinor driver mtd: spi-nor: zynq_qspi: Kconfig: Add MTD_ZYNQ mtd: spi-nor: Add 4-byte addresswidth support cmd: add spinor cmd support cmd: spinor: sync/update protect command board_r: initialize spi_nor env: add spi-nor environment arm: dts: zynq: Add zynq-qspinor node dm: zynq: microzed: enable MTD/SPI-NOR framework test: dm: add tests for mtd devices Makefile | 1 + arch/arm/dts/zynq-7000.dtsi | 12 + arch/arm/dts/zynq-microzed.dts | 12 +- cmd/Kconfig | 5 + cmd/Makefile | 1 + cmd/nvedit.c | 1 + cmd/spinor.c | 326 ++++++++++++ common/board_r.c | 13 + configs/sandbox_defconfig | 8 +- configs/zynq_microzed_defconfig | 17 +- drivers/mtd/Kconfig | 2 + drivers/mtd/Makefile | 7 +- drivers/mtd/mtd-uclass.c | 203 +++++++- drivers/mtd/spi-nor/Kconfig | 89 ++++ drivers/mtd/spi-nor/Makefile | 15 + drivers/mtd/spi-nor/m25p80.c | 251 ++++++++++ drivers/mtd/spi-nor/spi-nor-ids.c | 184 +++++++ drivers/mtd/spi-nor/spi-nor-uclass.c | 160 ++++++ drivers/mtd/spi-nor/spi-nor.c | 940 +++++++++++++++++++++++++++++++++++ drivers/mtd/spi-nor/zynq_qspinor.c | 622 +++++++++++++++++++++++ drivers/spi/spi-uclass.c | 24 + env/Kconfig | 27 + env/Makefile | 1 + env/env.c | 2 + env/spinor.c | 113 +++++ include/dm/uclass-id.h | 1 + include/environment.h | 1 + include/linux/mtd/mtd.h | 14 + include/linux/mtd/spi-nor.h | 223 +++++++++ include/mtd.h | 176 +++++++ include/spi.h | 20 + test/dm/Makefile | 1 + test/dm/mtd.c | 33 ++ 33 files changed, 3493 insertions(+), 12 deletions(-) create mode 100644 cmd/spinor.c create mode 100644 drivers/mtd/spi-nor/Kconfig create mode 100644 drivers/mtd/spi-nor/Makefile create mode 100644 drivers/mtd/spi-nor/m25p80.c create mode 100644 drivers/mtd/spi-nor/spi-nor-ids.c create mode 100644 drivers/mtd/spi-nor/spi-nor-uclass.c create mode 100644 drivers/mtd/spi-nor/spi-nor.c create mode 100644 drivers/mtd/spi-nor/zynq_qspinor.c create mode 100644 env/spinor.c create mode 100644 include/linux/mtd/spi-nor.h create mode 100644 test/dm/mtd.c -- 2.7.4

10 54