February 2018 - U-Boot

[U-Boot] [UBOOT PATCH v2 0/2] spi: Moved spi u-bbot headers to Kconfig
by Vipul Kumar 05 Mar '18

05 Mar '18

This seris of patch moved spi headers to Kconfig. These are the configs: -CONFIG_SYS_ZYNQ_SPI_WAIT -CONFIG_XILINX_SPI_IDLE_VAL -CONFIG_SYS_ZYNQ_QSPI_WAIT -Changes in V2: - Added depends on ZYNQ_QSPI - Added depends on XILINX_SPI - Branch: u-boot-microblaze/kconfig Vipul Kumar (2): qspi: Added Kconfig support for CONFIG_SYS_ZYNQ_QSPI_WAIT spi: Added Kconfig support for SYS_ZYNQ_SPI_WAIT and XILINX_SPI_IDLE_VAL drivers/spi/Kconfig | 21 +++++++++++++++++++++ drivers/spi/xilinx_spi.c | 4 ---- drivers/spi/zynq_qspi.c | 3 --- drivers/spi/zynq_spi.c | 3 --- 4 files changed, 21 insertions(+), 10 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.

3 4

[U-Boot] [PATCH v2] env: mmc/fat/ext4: make sure that the MMC sub-system is initialized before using it
by Faiz Abbas 05 Mar '18

05 Mar '18

When booting from a non-MMC device, the MMC sub-system may not be initialized when the environment is first accessed. We need to make sure that the MMC sub-system is ready in even a non-MMC boot case. Therefore, initialize mmc before loading environment from it. Signed-off-by: Faiz Abbas <faiz_abbas(a)ti.com> --- Dropped Lukasz's Reviewed-by because patch has changed. I have tested this with ENV_IS_IN_FAT and ENV_IS_IN_MMC. env/ext4.c | 3 +++ env/fat.c | 3 +++ env/mmc.c | 2 ++ 3 files changed, 8 insertions(+) diff --git a/env/ext4.c b/env/ext4.c index 3f3aac5..6c69a0a 100644 --- a/env/ext4.c +++ b/env/ext4.c @@ -87,6 +87,9 @@ static int env_ext4_load(void) int err; loff_t off; + if (!strcmp(CONFIG_ENV_EXT4_INTERFACE, "mmc")) + mmc_initialize(NULL); + part = blk_get_device_part_str(CONFIG_ENV_EXT4_INTERFACE, CONFIG_ENV_EXT4_DEVICE_AND_PART, &dev_desc, &info, 1); diff --git a/env/fat.c b/env/fat.c index 35f7ab5..fdf4b7a 100644 --- a/env/fat.c +++ b/env/fat.c @@ -89,6 +89,9 @@ static int env_fat_load(void) int dev, part; int err; + if (!strcmp(CONFIG_ENV_FAT_INTERFACE, "mmc")) + mmc_initialize(NULL); + part = blk_get_device_part_str(CONFIG_ENV_FAT_INTERFACE, CONFIG_ENV_FAT_DEVICE_AND_PART, &dev_desc, &info, 1); diff --git a/env/mmc.c b/env/mmc.c index 1058b8c..6f11dec 100644 --- a/env/mmc.c +++ b/env/mmc.c @@ -273,6 +273,8 @@ static int env_mmc_load(void) ALLOC_CACHE_ALIGN_BUFFER(env_t, tmp_env1, 1); ALLOC_CACHE_ALIGN_BUFFER(env_t, tmp_env2, 1); + mmc_initialize(NULL); + mmc = find_mmc_device(dev); errmsg = init_mmc_for_env(mmc); -- 2.7.4

4 13

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

05 Mar '18

This series of patch moved mmc u-boot headers to the Kconfig and enabled it in respective defconfig. These are the configs: -CONFIG_ZYNQ_SDHCI0 -CONFIG_ZYNQ_SDHCI1 -Changes in V2: - Added depends on MMC_SDHCI_ZYNQ - Branch: u-boot-microblaze/kconfig Vipul Kumar (2): arm64: zynqmp: mmc: Added Kconfig support for CONFIG_ZYNQ_SDHCI0 arm64: zynqmp: mmc: Added Kconfig support for CONFIG_ZYNQ_SDHCI1 arch/arm/cpu/armv8/zynqmp/Kconfig | 12 ++++++++++++ configs/xilinx_zynqmp_zc1751_xm015_dc1_defconfig | 2 ++ configs/xilinx_zynqmp_zc1751_xm019_dc5_defconfig | 1 + configs/xilinx_zynqmp_zcu102_rev1_0_defconfig | 1 + configs/xilinx_zynqmp_zcu102_revA_defconfig | 1 + configs/xilinx_zynqmp_zcu102_revB_defconfig | 1 + include/configs/xilinx_zynqmp_zc1751_xm015_dc1.h | 2 -- include/configs/xilinx_zynqmp_zc1751_xm019_dc5.h | 1 - include/configs/xilinx_zynqmp_zcu102.h | 1 - 9 files changed, 18 insertions(+), 4 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.

4 11

[U-Boot] Kernel panic - not syncing: VFS: Unable to mount rootfs on unknown-block (1, 0)
by Zoran S 03 Mar '18

03 Mar '18

Hello to U-Boot list, I have encountered an interesting problem which I do not entirely understand. I am trying to boot MLO and u-boot.bin from the SD Card, and rest from the initramfs. I tried several initramfs images, and so far I am always failing on the same place: [ 2.135533] No filesystem could mount root, tried: [ 2.135541] ext2 [ 2.140682] [ 2.144262] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) [ 2.153034] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) I have tried mostly .gz images (cpio.gz and ext2.gz). Does not help. Even does not with ext2.gz after YOCTO is done. In order to do it correctly, I MUST to add U-Boot header, and I do this with the following command: mkimage -n 'Ramdisk Image' -A arm -O linux -T ramdisk -C gzip -d initramfs.ext2.gz initramfs.uImage And the image I actually supply is: initramfs.uImage Then, the following happens: => run netloadfdt link up on port 0, speed 100, full duplex Using cpsw device TFTP from server 192.168.15.2; our IP address is 192.168.15.20 Filename 'am335x-boneblack.dtb'. Load address: 0x88000000 Loading: ### 697.3 KiB/s done Bytes transferred = 35016 (88c8 hex) => run netloadimage link up on port 0, speed 100, full duplex Using cpsw device TFTP from server 192.168.15.2; our IP address is 192.168.15.20 Filename 'zImage'. Load address: 0x82000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ######################## 772.5 KiB/s done Bytes transferred = 4161160 (3f7e88 hex) => tftp 0x88080000 initramfs.uImage link up on port 0, speed 100, full duplex Using cpsw device TFTP from server 192.168.15.2; our IP address is 192.168.15.20 Filename 'initramfs.uImage'. Load address: 0x88080000 Loading: ################################################################# ################################################################# [snap] ####################################################### 767.6 KiB/s done Bytes transferred = 46599246 (2c70c4e hex) => dhcp link up on port 0, speed 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.15.159 (21 ms) => run ramboot Booting from ramdisk ... ## Loading init Ramdisk from Legacy Image at 88080000 ... Image Name: Ramdisk Image Created: 2018-02-21 9:46:15 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 46599182 Bytes = 44.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8d38f000, end 8ffffc0e ... OK Loading Device Tree to 8d383000, end 8d38e8c7 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.13.8-jumpnow (oe-user@oe-host) (gcc version 7.2.0 (GCC)) #1 Tue Jan 9 15:37:12 CET 2018 [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: TI AM335x BeagleBone Black [ 0.000000] Memory policy: Data cache writeback [ 0.000000] cma: Reserved 16 MiB at 0x9f000000 [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] AM335X ES2.1 (sgx neon) [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Please, note the Kernal Command line in the log! [ 0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/ram0 rw rootfstype=ext2 <<======================== Kernel Command Line [SNAP] [ 1.770469] omap_voltage_late_init: Voltage driver support not added [ 1.777510] ThumbEE CPU extension supported. [ 1.791397] mmcblk0: mmc0:59b4 USD 1.87 GiB [ 1.801349] mmcblk0: p1 p2 [ 1.868955] mmc1: new high speed MMC card at address 0001 [ 1.876511] mmcblk1: mmc1:0001 MMC04G 3.60 GiB [ 1.882230] mmcblk1boot0: mmc1:0001 MMC04G partition 1 2.00 MiB [ 1.890172] mmcblk1boot1: mmc1:0001 MMC04G partition 2 2.00 MiB [ 1.896948] mmcblk1rpmb: mmc1:0001 MMC04G partition 3 128 KiB [ 1.906237] mmcblk1: p1 p2 [ 1.925804] tps65217 0-0024: TPS65217 ID 0xe version 1.2 [ 1.932470] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz [ 1.948789] omap_rtc 44e3e000.rtc: setting system clock to 2017-12-04 18:09:58 UTC (1512410998) [ 1.963613] List of all partitions: [ 1.967311] 0100 16384 ram0 [ 1.967322] (driver?) [ 1.973831] 0101 16384 ram1 [ 1.973840] (driver?) [ 1.980294] 0102 16384 ram2 [ 1.980303] (driver?) [ 1.986703] 0103 16384 ram3 [ 1.986711] (driver?) [ 1.993144] 0104 16384 ram4 [ 1.993153] (driver?) [ 1.999582] 0105 16384 ram5 [ 1.999590] (driver?) [ 2.005991] 0106 16384 ram6 [ 2.005999] (driver?) [ 2.012428] 0107 16384 ram7 [ 2.012437] (driver?) [ 2.018903] 0108 16384 ram8 [ 2.018911] (driver?) [ 2.025313] 0109 16384 ram9 [ 2.025321] (driver?) [ 2.031776] 010a 16384 ram10 [ 2.031785] (driver?) [ 2.038304] 010b 16384 ram11 [ 2.038312] (driver?) [ 2.044804] 010c 16384 ram12 [ 2.044812] (driver?) [ 2.051344] 010d 16384 ram13 [ 2.051352] (driver?) [ 2.057871] 010e 16384 ram14 [ 2.057879] (driver?) [ 2.064371] 010f 16384 ram15 [ 2.064379] (driver?) [ 2.070912] b300 1960960 mmcblk0 [ 2.070922] driver: mmcblk [ 2.078079] b301 131072 mmcblk0p1 46a788a5-01 [ 2.078088] [ 2.085214] b302 1828863 mmcblk0p2 46a788a5-02 [ 2.085222] [ 2.092652] b308 3776512 mmcblk1 [ 2.092663] driver: mmcblk [ 2.099840] b309 98304 mmcblk1p1 00000000-01 [ 2.099849] [ 2.106975] b30a 3677184 mmcblk1p2 00000000-02 [ 2.106984] [ 2.114160] b320 128 mmcblk1rpmb [ 2.114169] (driver?) [ 2.121235] b318 2048 mmcblk1boot1 [ 2.121244] (driver?) [ 2.128401] b310 2048 mmcblk1boot0 [ 2.128410] (driver?) [ 2.135533] No filesystem could mount root, tried: [ 2.135541] ext2 [ 2.140682] [ 2.144262] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) [ 2.153034] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) What could be the (list of) problem(s) here? Thank you, Zoran

2 6

[U-Boot] [PATCH] cmd: nvedit: add whitelist option for env import
by Quentin Schulz 02 Mar '18

02 Mar '18

While the `env export` can take as parameters variables to be exported, `env import` does not have such a mechanism of variable selection. Let's add a `-w` option that asks `env import` to look for the `whitelisted_vars` env variable for a space-separated list of variables that are whitelisted. Every env variable present in env at `addr` and in `whitelisted_vars` env variable will override the value of the variable in the current env. All the remaining variables are left untouched. One of its use case could be to load a secure environment from the signed U-Boot binary and load only a handful of variables from an other, unsecure, environment without completely losing control of U-Boot. Signed-off-by: Quentin Schulz <quentin.schulz(a)free-electrons.com> --- cmd/nvedit.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 64 insertions(+), 7 deletions(-) diff --git a/cmd/nvedit.c b/cmd/nvedit.c index 4e79d03856..9f983b41a1 100644 --- a/cmd/nvedit.c +++ b/cmd/nvedit.c @@ -971,7 +971,7 @@ sep_err: #ifdef CONFIG_CMD_IMPORTENV /* - * env import [-d] [-t [-r] | -b | -c] addr [size] + * env import [-d] [-t [-r] | -b | -c] [-w] addr [size] * -d: delete existing environment before importing; * otherwise overwrite / append to existing definitions * -t: assume text format; either "size" must be given or the @@ -982,6 +982,10 @@ sep_err: * for line endings. Only effective in addition to -t. * -b: assume binary format ('\0' separated, "\0\0" terminated) * -c: assume checksum protected environment format + * -w: specify that whitelisting of variables should be used when + * importing environment. The space-separated list of variables + * that should override the ones in current environment is stored + * in `whitelisted_vars`. * addr: memory address to read from * size: length of input data; if missing, proper '\0' * termination is mandatory @@ -991,11 +995,16 @@ static int do_env_import(cmd_tbl_t *cmdtp, int flag, { ulong addr; char *cmd, *ptr; + char **array = NULL; char sep = '\n'; int chk = 0; int fmt = 0; int del = 0; int crlf_is_lf = 0; + int wl = 0; + int wl_count = 0; + int ret; + unsigned int i; size_t size; cmd = *argv; @@ -1026,6 +1035,9 @@ static int do_env_import(cmd_tbl_t *cmdtp, int flag, case 'd': del = 1; break; + case 'w': + wl = 1; + break; default: return CMD_RET_USAGE; } @@ -1082,14 +1094,59 @@ static int do_env_import(cmd_tbl_t *cmdtp, int flag, ptr = (char *)ep->data; } - if (himport_r(&env_htab, ptr, size, sep, del ? 0 : H_NOCLEAR, - crlf_is_lf, 0, NULL) == 0) { + if(wl) { + char *str, *token, *tmp; + wl_count = 1; + + str = env_get("whitelisted_vars"); + if (!str) { + puts("## Error: whitelisted_vars is not set.\n"); + return CMD_RET_USAGE; + } + + tmp = malloc(sizeof(char) * (strlen(str) + 1)); + strcpy(tmp, str); + + token = strchr(tmp, ' '); + while (!token) { + wl_count++; + token = strchr(token + 1, ' '); + } + + strcpy(tmp, str); + + array = malloc(sizeof(char *) * wl_count); + wl_count = 0; + + token = strtok(tmp, " "); + while (token) { + array[wl_count] = malloc(sizeof(char) * + (strlen(token) + 1)); + strcpy(array[wl_count], token); + wl_count++; + token = strtok(NULL, " "); + } + + free(tmp); + } + + ret = himport_r(&env_htab, ptr, size, sep, del ? 0 : H_NOCLEAR, + crlf_is_lf, wl ? wl_count : 0, wl ? array : NULL); + if (!ret) { pr_err("Environment import failed: errno = %d\n", errno); - return 1; + ret = 1; + } else { + gd->flags |= GD_FLG_ENV_READY; + ret = 0; } - gd->flags |= GD_FLG_ENV_READY; - return 0; + if (wl) { + for (i = 0; i < wl_count; i++) + free(array[i]); + free(array); + } + + return ret; sep_err: printf("## %s: only one of \"-b\", \"-c\" or \"-t\" allowed\n", @@ -1212,7 +1269,7 @@ static char env_help_text[] = #endif #endif #if defined(CONFIG_CMD_IMPORTENV) - "env import [-d] [-t [-r] | -b | -c] addr [size] - import environment\n" + "env import [-d] [-t [-r] | -b | -c] [-w] addr [size] - import environment\n" #endif "env print [-a | name ...] - print environment\n" #if defined(CONFIG_CMD_RUN) -- 2.14.1

2 1

[U-Boot] [PATCH] usb: dwc2: Allow selection of data buffer size
by Alexey Brodkin 01 Mar '18

01 Mar '18

If we use hardware with very small RAM (let's consider just a couple of hundreds of kB but not megabytes) it is not super convenient to lose 64kB for statically allocated bufer which most probably won't be used as big as it is. Typically we'll have much shorter data packages to excahnge and in the worst case longer packets will be split on separate transactions. For those corner-cases user will be able to set his buffer size of choice via USB_DWC2_BUFFER_SIZE option in menuconfig. By default we'll use 64 kB as it was hard-coeded before so existing users shouldn't be affected at all. Signed-off-by: Alexey Brodkin <abrodkin(a)synopsys.com> Cc: Marek Vasut <marex(a)denx.de> --- drivers/usb/host/Kconfig | 12 ++++++++++++ drivers/usb/host/dwc2.c | 2 +- 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig index 90b2f78ec7d9..a7249b7511f4 100644 --- a/drivers/usb/host/Kconfig +++ b/drivers/usb/host/Kconfig @@ -245,3 +245,15 @@ config USB_DWC2 Hi-Speed (480 Mbps), Full-Speed (12 Mbps), and Low-Speed (1.5 Mbps) operation is compliant to the controller Supplement. If you want to enable this controller in host mode, say Y. + +if USB_DWC2 +config USB_DWC2_BUFFER_SIZE + int "Data buffer size in kB" + default 64 + ---help--- + By default 64 kB buffer is used but if amount of RAM avaialble on + the target is not enough to accommodate allocation of buffer of + that size it is possible to shrink it. Smaller sizes should be fine + because larger transactions could be split in smaller ones. + +endif # USB_DWC2 diff --git a/drivers/usb/host/dwc2.c b/drivers/usb/host/dwc2.c index 0efe645044c5..e436c711e720 100644 --- a/drivers/usb/host/dwc2.c +++ b/drivers/usb/host/dwc2.c @@ -25,7 +25,7 @@ DECLARE_GLOBAL_DATA_PTR; #define DWC2_HC_CHANNEL 0 #define DWC2_STATUS_BUF_SIZE 64 -#define DWC2_DATA_BUF_SIZE (64 * 1024) +#define DWC2_DATA_BUF_SIZE (CONFIG_USB_DWC2_BUFFER_SIZE * 1024) #define MAX_DEVICE 16 #define MAX_ENDPOINT 16 -- 2.14.3

2 1

[U-Boot] Regression: gpio: pca953x_gpio: Make live-tree compatible
by Martin Fuzzey 01 Mar '18

01 Mar '18

Hi, since this commit: commit f62ca2cd2ab8171f603960da9203ceb6ee8a1efd Author: Mario Six <mario.six(a)gdsys.cc> Date: Mon Jan 15 11:07:45 2018 +0100 gpio: pca953x_gpio: Make live-tree compatible I am getting the error message "__of_translate_address: Bad cell count for pcal6524@1" I don't think the patch - addr = fdtdec_get_int(gd->fdt_blob, dev_of_offset(dev), "reg", 0); + addr = dev_read_addr(dev); is correct since it replaces a simple lookup of the value "reg" property with an attempted translation to a CPU address (which fails for I2C) This does not cause the driver probe to fail since dev_read_addr() returns FDT_ADDR_T_NONE (== -1) and is followed by if (addr == 0) return -ENODEV; info->addr = addr; Although addr is stored in the driver data the only thing it is used for is to build the bank name snprintf(name, sizeof(name), "gpio@%x_", info->addr); I'm not even sure that using the value of the "reg" property as before is really a good idea - what happens if we have multiple chips with same address on seperate busses? Maybe it would be better to use the DT node name? But would that break existing configurations by renaming the device? Regards, Martin

2 5

[U-Boot] [UBOOT PATCH v2 0/2] mmc: Added Kconfig support to set minimum and maximum frequency of the mmc controller
by Vipul Kumar 01 Mar '18

01 Mar '18

This series of patch added Kconfig support for CONFIG_ZYNQ_SDHCI_MAX_FREQ and CONFIG_ZYNQ_SDHCI_MIN_FREQ and set the default values. -Changes in V2: -Set min. frequency for ep 100KHz -Branch: u-boot-microblaze/kconfig Vipul Kumar (2): mmc: Added Kconfig support for CONFIG_ZYNQ_SDHCI_MAX_FREQ mmc: Added Kconfig support for CONFIG_ZYNQ_SDHCI_MIN_FREQ arch/arm/cpu/armv8/zynqmp/Kconfig | 3 +++ arch/arm/mach-zynq/Kconfig | 3 +++ configs/xilinx_zynqmp_ep_defconfig | 2 ++ drivers/mmc/Kconfig | 13 +++++++++++++ drivers/mmc/zynq_sdhci.c | 4 ---- include/configs/xilinx_zynqmp.h | 3 --- include/configs/xilinx_zynqmp_ep.h | 2 -- include/configs/zynq-common.h | 5 ----- 8 files changed, 21 insertions(+), 14 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 3

[U-Boot] [UBOOT PATCH v2 0/2] microblaze: Moved U-boot headers to Kconfig
by Vipul Kumar 01 Mar '18

01 Mar '18

This seris of patch moved microblaze u-boot headers to the kconfig and enabled it in respective defconfig. These are the configs: -CONFIG_XILINX_GPIO -CONFIG_XILINX_TB_WATCHDOG - Changes in v2: - Removed "Enable" from description - Added select HW_WATCHDOG - Branch: u-boot-microblaze/kconfig Vipul Kumar (2): microblaze: Added Kconfig support for CONFIG_XILINX_GPIO microblaze: wdt: Added Kconfig support for CONFIG_XILINX_TB_WATCHDOG configs/microblaze-generic_defconfig | 2 ++ drivers/gpio/Kconfig | 5 +++++ drivers/watchdog/Kconfig | 7 +++++++ include/configs/microblaze-generic.h | 2 -- 4 files changed, 14 insertions(+), 2 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] [UBOOT PATCH 0/4] fpga: Moved fpga u-boot headers to the Kconfig
by Vipul Kumar 01 Mar '18

01 Mar '18

This series of patch moved fpga u-boot headers to the kconfig and enabled in respective defconfig. These are the configs: -CONFIG_FPGA_SPARTAN3 -CONFIG_FPGA_ZYNQPL Vipul Kumar (4): fpga: Added Kconfig support for FPGA_SPARTAN3 fpga: Added CONFIG_FPGA_SPARTAN3 in the the respective defconfig arm: zynq: fpga: Added Kconfig support for CONFIG_FPGA_ZYNQPL arm: zynq: fpga: Added CONFIG_FPGA_ZYNQPL in the respective defconfig configs/apf27_defconfig | 1 + configs/astro_mcf5373l_defconfig | 1 + configs/mt_ventoux_defconfig | 1 + configs/syzygy_hub_defconfig | 1 + configs/topic_miami_defconfig | 1 + configs/topic_miamilite_defconfig | 1 + configs/topic_miamiplus_defconfig | 1 + configs/x600_defconfig | 1 + configs/zynq_cc108_defconfig | 1 + configs/zynq_microzed_defconfig | 1 + configs/zynq_picozed_defconfig | 1 + configs/zynq_z_turn_defconfig | 1 + configs/zynq_zc702_defconfig | 1 + configs/zynq_zc706_defconfig | 1 + configs/zynq_zc770_xm010_defconfig | 1 + configs/zynq_zc770_xm011_defconfig | 1 + configs/zynq_zc770_xm011_x16_defconfig | 1 + configs/zynq_zc770_xm012_defconfig | 1 + configs/zynq_zc770_xm013_defconfig | 1 + configs/zynq_zed_defconfig | 1 + configs/zynq_zybo_defconfig | 1 + drivers/fpga/Kconfig | 12 ++++++++++++ include/configs/apf27.h | 1 - include/configs/astro_mcf5373l.h | 1 - include/configs/mt_ventoux.h | 1 - include/configs/x600.h | 1 - include/configs/zynq-common.h | 2 -- 27 files changed, 33 insertions(+), 6 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.

3 10