Re: [PATCH 16/25] microblaze: Migrate DCACHE/ICACHE to Kconfig

On 3/31/22 00:07, Tom Rini wrote: Move these two options to the arch Kconfig file. Cc: Michal Simek Signed-off-by: Tom Rini --- arch/microblaze/Kconfig | 8 include/configs/microblaze-generic.h | 3 --- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git

Re: TFTP hangs with fragmented IP packets

On Tue, Mar 29, 2022 at 11:28 PM Laurent Pinchart wrote: > > Hello, > > I've banged my head a few days ago trying to debug an issue with a TFTP > transfer hanging in the middle. > > I'm testing U-Boot 2022-rc5 on a Toradex Verdin i.MX8MP module (using > the verdin-imx8mp defconfig). My local

[PATCH v2] mtd: rawnand: mxs_nand: Fix use_minimum_ecc for spl driver

Because mxs_nand_spl driver does not support DM, to use the minimum ECC layout, it needs to handle the CONFIG_NAND_MXS_USE_MINIMUM_ECC. Signed-off-by: Ye Li Reviewed-by: Han Xu --- Changes in v2: - Use IS_ENABLED to replace #ifdef drivers/mtd/nand/raw/mxs_nand.c | 3 +++ 1 file changed, 3

Re: [PATCH 00/52] mips: octeon: Add ethernet support

Hi Daniel, On 3/31/22 01:56, Daniel Schwierzeck wrote: Am Mittwoch, dem 30.03.2022 um 12:06 +0200 schrieb Stefan Roese: This patchset adds the networking files and drivers including device helper headers and C files. Please excuse the massive amount of files in this patch series. Also the

Re: [EXT] [PATCH] ARM: imx: romapi: Repair FlexSPI NOR boot offset

On Thu, 2022-03-31 at 00:27 +0200, Marek Vasut wrote: > Caution: EXT Email > > On 3/29/22 11:56, Ye Li wrote: > > Hi, > > > > > > > > > > > > > > But once you want to upgrade the > > > > flash.bin, flexspi configurations will also be erased due to > > > > the > > > > block > > > > size. Then

Re: [PATCH 08/25] corvus: Migrate CONFIG_*_LED out of CONFIG namespace

Hello Tom, On 31.03.22 00:07, Tom Rini wrote: > This code is only used on the corvus platform, so migrate the LED on/off > code to this platform and remove it from the CONFIG namespace. In > theory, this should likely be moved to the modern GPIO LED driver as a > further cleanup. > > Cc: Heiko

[PATCH 2/3] imx: power-domain: Inline arch-imx8m/power-domain.h

The arch/arm/include/asm/arch-imx8m/power-domain.h is not included anywhere except in drivers/power/domain/imx8m-power-domain.c, just inline the content and drop the header. No functional change. Signed-off-by: Marek Vasut Cc: Fabio Estevam Cc: Peng Fan Cc: Stefano Babic ---

[PATCH 3/3] imx: power-domain: Get rid of SMCCC dependency

This driver is the only SMCCC dependency in iMX8M U-Boot port. Rework the driver based on Linux GPCv2 driver to directly control the GPCv2 block instead of using SMCCC calls. This way, U-Boot can operate the i.MX8M power domains without depending on anything else. This is losely based on Linux

[PATCH 1/3] imx: power-domain: Descend into pgc subnode if present

In case the power domain node structure is gpc@303a/pgc/power-domain@N, do not bind power domain driver to the 'pgc' node, but rather descend into it and only bind power domain drivers to power-domain@N subnodes. This way we do not waste one useless driver instance associated with 'pgc' node.

[PATCH] ARM: imx: Get rid of only i.MX8M SMCCC arch call

This is the only place where i.MX8M code does SMCCC call, remove it. The output has little value as it prints some part of commit ID, and worse, if there is no SMC handler installed, the code outright hangs or crashes the system. By removing this one instance of SMCCC call, U-Boot no longer

[PATCH] power-domain: Return 0 if ops unimplemented and remove empty functions

In case the ops is not implemented, return 0 in the core right away. This is better than having multiple copies of functions which just return 0 in each power domain driver. Drop all those empty functions. Signed-off-by: Marek Vasut Cc: Patrick Delaunay Cc: Simon Glass ---

Re: [PATCH v3 9/9] doc: uefi: Update the capsule update related documentation

Hi Sughosh, 2022年3月30日(水) 23:52 Sughosh Ganu : > > Update the capsule update functionality related documentation to > refect the fact that a unique image GUID is to be used per image > that forms part of the capsule file. Thank you for updating! Now the relationship of dfu_alt_info and GUIDs is

Re: [PATCH v3 1/9] capsule: Add Image GUIDs and image index for platforms using capsule updates

Hi Sughosh, The DeveloperBox part looks good to me. Reviewed-by: Masami Hiramatsu Thank you, 2022年3月30日(水) 23:51 Sughosh Ganu : > > Currently, all platforms that enable capsule updates do so using > either EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID or > EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID. This

Re: [PATCH v3 2/9] capsule: FMP: Populate the image descriptor array from platform data

Hi Sughosh, This looks good to me. Reviewed-by: Masami Hiramatsu Thank you, 2022年3月30日(水) 23:51 Sughosh Ganu : > > Currently, the image descriptor array that has been passed to the > GetImageInfo function of the Firmware Management Protocol(FMP) gets > populated through the data stored with

Re: [PATCH v3 3/9] capsule: Put a check for image index before the update

Hi Sughosh, This looks good to me. Reviewed-by: Masami Hiramatsu Thank you! 2022年3月30日(水) 23:51 Sughosh Ganu : > > The current capsule update code compares the image GUID value in the > capsule header with the image GUID value obtained from the > GetImageInfo function of the Firmware

Re: [PATCH v3 5/9] capsule: kconfig: Select SET_DFU_ALT_INFO config symbol for capsule update

Hi, Even with this patch, if the platform configuration doesn't select EFI_CAPSULE_FIRMWARE_* (or user will disable it when use it), the platform will lose raw DFU availability. Thank you, 2022年3月30日(水) 23:51 Sughosh Ganu : > > The capsule update code uses the dfu_alt_info variable for the

Re: [PATCH v3 4/9] board: Define set_dfu_alt_info() for boards with UEFI capsule update enabled

Hi Sughosh, If you remove the DEFAULT_DFU_ALT_INFO definition but introduce set_dfu_alt_info(), this also must the CONFIG_SET_DFU_ALT_INFO for each platform configuration too. Unless that, some platform will not lose the dfu_alt_info until next patch ([5/9]) is applied. Thank you, 2022年3月30日(水)

[PATCH v2] ARM: dts: imx: Add support for Data Modul i.MX8M Mini eDM SBC

Add support for Data Modul i.MX8M Mini eDM SBC board. This is an evaluation board for various custom display units. Currently supported are serial console, ethernet, eMMC, SD, SPI NOR, USB host and USB OTG. Reviewed-by: Fabio Estevam Signed-off-by: Marek Vasut Cc: Fabio Estevam Cc: Peng Fan

Re: [PATCH v4 06/11] efi_loader: bootmgr: add booting from removable media

Hi Ilias, On Thu, 31 Mar 2022 at 04:13, Ilias Apalodimas wrote: > > Hello Akashi-san, > > On Thu, Mar 24, 2022 at 10:54:38PM +0900, Masahisa Kojima wrote: > > From: AKASHI Takahiro > > > > Under the current implementation, booting from removable media using > > a architecture-specific default

Re: Please pull clk-2022.04-next

On Wed, Mar 30, 2022 at 03:27:47PM -0400, Sean Anderson wrote: > The following changes since commit d2e5250be49fce4653689c41a5dc7e2d7e7ecf33: > > Merge tag 'next-20220328' of > https://source.denx.de/u-boot/custodians/u-boot-video into next (2022-03-28 > 17:04:45 -0400) > > are available in

Re: [PATCH 00/52] mips: octeon: Add ethernet support

Am Mittwoch, dem 30.03.2022 um 12:06 +0200 schrieb Stefan Roese: > This patchset adds the networking files and drivers including device > helper headers and C files. Please excuse the massive amount of files > in this patch series. Also the sometimes huge files (mostly headers > with register

Re: [RFC PATCH] mips: dts: add initial support for ls1c300 SoC

Am Mittwoch, dem 30.03.2022 um 03:30 +0800 schrieb Du Huanpeng: > Loongson 1C is a cost-effective SOC chip for industrial control and > the Internet of Things. The Loongson 1C includes a floating-point > processing unit, supports multiple types of memory, and supports > high-capacity MLC NAND

Re: [EXT] [PATCH] ARM: imx: romapi: Repair FlexSPI NOR boot offset

Hi Marek, On Wed, Mar 30, 2022 at 7:27 PM Marek Vasut wrote: > I still believe it is better (=less confusing for users) to have one > unified flash.bin for all boot media. I agree with your approach. Thanks

Re: [EXT] [PATCH] ARM: imx: romapi: Repair FlexSPI NOR boot offset

On 3/29/22 11:56, Ye Li wrote: Hi, But once you want to upgrade the flash.bin, flexspi configurations will also be erased due to the block size. Then you have to reprogram the configurations with flash.bin. So most of our customers add the flexspi configurations to flash.bin head. They don't

[PATCH 20/25] galileo: Remove CONFIG_DESIGNWARE_ETH reference

This platform has CONFIG_ETH_DESIGNWARE set already, which is the correct value for the driver in question. Remove this incorrect line. Signed-off-by: Tom Rini --- include/configs/galileo.h | 1 - 1 file changed, 1 deletion(-) diff --git a/include/configs/galileo.h b/include/configs/galileo.h

[PATCH 19/25] powerpc: mpc83xx: Migrate DEFAULT_IMMR to Kconfig

As no platforms override this value, set it for all mpc83xx platforms. Cc: Mario Six Cc: Wolfgang Denk Signed-off-by: Tom Rini --- arch/powerpc/cpu/mpc83xx/Kconfig | 4 include/mpc83xx.h| 4 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH 04/25] Convert CONFIG_CMDLINE_PS_SUPPORT to Kconfig

This converts the following to Kconfig: CONFIG_CMDLINE_PS_SUPPORT Signed-off-by: Tom Rini --- README| 8 cmd/Kconfig | 7 +++ configs/socfpga_vining_fpga_defconfig | 1 + include/configs/socfpga_vining_fpga.h | 3 --- 4

[PATCH 22/25] Convert CONFIG_FSL_QIXIS et al to Kconfig

This converts the following to Kconfig: CONFIG_FSL_QIXIS CONFIG_QIXIS_I2C_ACCESS Signed-off-by: Tom Rini --- board/freescale/common/Kconfig | 8 configs/T2080QDS_NAND_defconfig | 2 ++ configs/T2080QDS_SDCARD_defconfig

[PATCH 25/25] arm: fsl-layerscape: Migrate more DP-DDR options to Kconfig

Based on current usage, migrate a number of DP-DDR related options to Kconfig. Cc: Priyanka Jain Cc: Rajesh Bhagat Signed-off-by: Tom Rini --- README| 3 --- arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 25 +++

[PATCH 24/25] siemens-am33x-common: Drop CONFIG_DMA_COHERENT*

These values are not used in the code, remove them. Signed-off-by: Tom Rini --- include/configs/siemens-am33x-common.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/include/configs/siemens-am33x-common.h b/include/configs/siemens-am33x-common.h index bfadf4a6b861..08c4d52d658f 100644

[PATCH 23/25] m53menlo: Drop CONFIG_DISCOVER_PHY

This is not used in code, drop. Signed-off-by: Tom Rini --- include/configs/m53menlo.h | 1 - 1 file changed, 1 deletion(-) diff --git a/include/configs/m53menlo.h b/include/configs/m53menlo.h index dd803e7053cb..5bd6cbefc67d 100644 --- a/include/configs/m53menlo.h +++

[PATCH 21/25] Convert CONFIG_DIMM_SLOTS_PER_CTLR to Kconfig

This converts the following to Kconfig: CONFIG_DIMM_SLOTS_PER_CTLR Signed-off-by: Tom Rini --- configs/T2080QDS_NAND_defconfig| 1 + configs/T2080QDS_SDCARD_defconfig | 1 + configs/T2080QDS_SECURE_BOOT_defconfig | 1 + configs/T2080QDS_SPIFLASH_defconfig

[PATCH 18/25] nds32: Migrate CONFIG_DEBUG_LED to Kconfig

Move this value to the board Kconfig file. Signed-off-by: Tom Rini --- arch/nds32/include/asm/arch-ag101/ag101.h | 3 --- arch/nds32/include/asm/arch-ag102/ag102.h | 2 -- board/AndesTech/adp-ag101p/Kconfig| 4 3 files changed, 4 insertions(+), 5 deletions(-) diff --git

[PATCH 17/25] ls1021atwr: Use DEBUG and not CONFIG_DEBUG

We use 'DEBUG' and not 'CONFIG_DEBUG' tree-wide for debug code that is left in, and not wrapped by some other regular debugging type print macro. Cc: Alison Wang Signed-off-by: Tom Rini --- board/freescale/ls1021atwr/ls1021atwr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 16/25] microblaze: Migrate DCACHE/ICACHE to Kconfig

Move these two options to the arch Kconfig file. Cc: Michal Simek Signed-off-by: Tom Rini --- arch/microblaze/Kconfig | 8 include/configs/microblaze-generic.h | 3 --- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/arch/microblaze/Kconfig

[PATCH 13/25] spi: cadence_qspi: Migrate CONFIG_CQSPI_REF_CLK to Kconfig

This is a little tricky since SoCFPGA has code to determine this as runtime. Introduce a guard variable for platforms to select if they have a static value to use. Then for ARCH_SOCFPGA, call cm_get_qspi_controller_clk_hz() and otherwise continue the previous behavior. Cc: Jagan Teki

[PATCH 15/25] tegra: Drop CONFIG_CHROMEOS_EXTRA_ENV_SETTINGS

This is not currently set by any boards, so drop. Signed-off-by: Tom Rini --- include/configs/tegra-common-post.h | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/include/configs/tegra-common-post.h b/include/configs/tegra-common-post.h index d9d89b6d7581..755a41fef7e2

[PATCH 07/25] MPC837XERDB: Stop using CONFIG_RAMDISKFILE

We don't really configure this, just set it directly in the environment section. Signed-off-by: Tom Rini --- include/configs/MPC837XERDB.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/include/configs/MPC837XERDB.h b/include/configs/MPC837XERDB.h index

[PATCH 12/25] Convert CONFIG_SH_SCIF_CLK_FREQ to Kconfig

This converts the following to Kconfig: CONFIG_SH_SCIF_CLK_FREQ Signed-off-by: Tom Rini --- configs/stout_defconfig| 1 + drivers/serial/Kconfig | 5 + include/configs/alt.h | 3 --- include/configs/armadillo-800eva.h | 3 --- include/configs/gose.h

[PATCH 09/25] stm32f429-discovery: Migrate CONFIG_*_LED out of CONFIG namespace

These values are only used in one file, reference them more directly. Cc: Kamil Lulko Cc: Patrick Delaunay Cc: Patrice Chotard Cc: uboot-st...@st-md-mailman.stormreply.com Signed-off-by: Tom Rini --- board/st/stm32f429-discovery/led.c| 19 +++

[PATCH 14/25] controlcenterdc: Migrate CUSTOMER_BOARD_SUPPORT to Kconfig

This symbol is only possibly useful on some mvebu platforms, so move the symbol there and select it for the only current user. Cc: Mario Six Cc: Stefan Roese Signed-off-by: Tom Rini --- arch/arm/mach-mvebu/Kconfig | 4 include/configs/controlcenterdc.h | 5 - 2 files changed, 4

[PATCH 01/25] Convert CONFIG_BOARD_SIZE_LIMIT to Kconfig

This converts the following to Kconfig: CONFIG_BOARD_SIZE_LIMIT To do this, introduce CONFIG_HAS_BOARD_SIZE_LIMIT. Signed-off-by: Tom Rini --- Kconfig| 17 + README | 5 -

[PATCH 11/25] Convert CONFIG_CONS_SCIF0 et al to Kconfig

This converts the following to Kconfig: CONFIG_CONS_SCIF0 CONFIG_CONS_SCIF1 CONFIG_CONS_SCIF2 CONFIG_CONS_SCIF4 CONFIG_CONS_SCIFA0 Signed-off-by: Tom Rini --- drivers/serial/Kconfig | 21 + include/configs/alt.h | 1 -

[PATCH 10/25] at91: Remove unused LED code

These LED files (and CONFIG values) are unused today, remove the code in question. Signed-off-by: Tom Rini --- arch/arm/mach-at91/arm926ejs/Makefile | 1 - arch/arm/mach-at91/arm926ejs/led.c| 47 --- board/atmel/at91sam9260ek/Makefile| 1 -

[PATCH 08/25] corvus: Migrate CONFIG_*_LED out of CONFIG namespace

This code is only used on the corvus platform, so migrate the LED on/off code to this platform and remove it from the CONFIG namespace. In theory, this should likely be moved to the modern GPIO LED driver as a further cleanup. Cc: Heiko Schocher Signed-off-by: Tom Rini ---

[PATCH 06/25] s5p_goni, smdkc100: Move some environment settings out of CONFIG

A number of CONFIG options are used on these platforms as part of the default environment. Set some of these more directly and in other cases, just reference them directly. Cc: Jaehoon Chung Cc: Minkyu Kang Signed-off-by: Tom Rini --- include/configs/s5p_goni.h | 23 ++-

[PATCH 02/25] mvebu: Move BOOTROM_ERR_REG out of CONFIG namespace

This register is referenced in one location and does not seem configurable, so remove it from CONFIG namespace. Cc: Stefan Roese Signed-off-by: Tom Rini --- arch/arm/mach-mvebu/cpu.c | 2 +- arch/arm/mach-mvebu/include/mach/soc.h | 2 +- 2 files changed, 2 insertions(+), 2

[PATCH 03/25] tegra: Migrate CI_UDC_HAS_HOSTPC to Kconfig

This option is only enabled for CI_UDC and !TEGRA20, so implement it as such in Kconfig directly. Signed-off-by: Tom Rini --- arch/arm/mach-tegra/Kconfig | 4 include/configs/apalis-tk1.h | 1 - include/configs/apalis_t30.h | 1 -

[PATCH 05/25] arm: integrator: Migrate platform-specific options and cleanup armcoremodule.h

This converts the following to Kconfig: CONFIG_CM_INIT CONFIG_CM_REMAP CONFIG_CM_SPD_DETECT CONFIG_CM_MULTIPLE_SSRAM CONFIG_CM_TCRAM We make the first three of these options be always enabled, as that matches usage. We select the last two based on how they were defined in

Re: [PATCH v2] board: gateworks: venice: determine dram size at runtime

On Wed, Mar 30, 2022 at 1:58 PM Fabio Estevam wrote: > > Hi Tim, > > On Wed, Mar 30, 2022 at 5:39 PM Tim Harvey wrote: > > > > The SPL does not update the memory node with the dram size from EEPROM > > but instead we can use get_ram_size which does a simple memory test > > to determine the

Re: [PATCH v2] board: gateworks: venice: determine dram size at runtime

Hi Tim, On Wed, Mar 30, 2022 at 5:39 PM Tim Harvey wrote: > > The SPL does not update the memory node with the dram size from EEPROM > but instead we can use get_ram_size which does a simple memory test > to determine the available RAM. Update PHYS_SDRAM_SIZE to 4GiB as that > is the max used on

Re: [RFC PATCH] mips: dts: add initial support for ls1c300 SoC

On 3/29/22 3:30 PM, Du Huanpeng wrote: Loongson 1C is a cost-effective SOC chip for industrial control and the Internet of Things. The Loongson 1C includes a floating-point processing unit, supports multiple types of memory, and supports high-capacity MLC NAND Flash. Loongson 1C provides

[PATCH] [PATCH] sunxi-nand: Undo removal of DMA that breaks NAND SPL

From: Chris Morgan For the sun5i based NAND, removal of the DMA specific code from the SPL driver caused it to no longer function. These patches revert the changes made here, specifically patches 13/20 and 14/20: https://lore.kernel.org/u-boot/20210624120540.7oyhdmerjndsylbq@gilmour/ These

[PATCH] imx8m{m,n}-venice-gw7902: add support for GPY111 phy

The TI DP83867 phy has been replaced with the MaxLinear GPY111 phy due to part availability. Add support for it: - increase post-reset time to 300ms per datasheet - add tx-delay/rx-delay config Signed-off-by: Tim Harvey --- arch/arm/dts/imx8mm-venice-gw7902-u-boot.dtsi | 2 +-

[PATCH v2] board: gateworks: venice: determine dram size at runtime

The SPL does not update the memory node with the dram size from EEPROM but instead we can use get_ram_size which does a simple memory test to determine the available RAM. Update PHYS_SDRAM_SIZE to 4GiB as that is the max used on the Venice boards. Signed-off-by: Tim Harvey Reviewed-by: Fabio

Re: [PATCH] efi_loader (v2): Expose relocated address for gdb debugging purposes

On 3/24/22 20:00, Alexander von Gluck IV wrote: * If users want to debug EFI applications via qemu + GDB, they need to know the relocated address of the application to align their symbols to in GDB via add-symbol-file. * This exposes where EFI applications are relocated to enable

[PATCH] Makefile: add endian link flag to u-boot-elf.o

From: Du Huanpeng fix compile error when using a little-endian to build with configs: sfr_nb4-ser_ram_defconfig comtrend_wap5813n_ram_defconfig comtrend_ar5387un_ram_defconfig comtrend_ct5361_ram_defconfig comtrend_vr3032u_ram_defconfig

Re: [PATCH 3/3] doc: usage: Convert README.plan9 to reST

On 3/29/22 19:11, Heinrich Schuchardt wrote: On 3/28/22 04:43, Bin Meng wrote: This converts the existing README.plan9 to reST, and puts it under the doc/usage/os directory. Signed-off-by: Bin Meng ---   doc/usage/index.rst  |  1 +   doc/{README.plan9 =>

Please pull clk-2022.04-next

The following changes since commit d2e5250be49fce4653689c41a5dc7e2d7e7ecf33: Merge tag 'next-20220328' of https://source.denx.de/u-boot/custodians/u-boot-video into next (2022-03-28 17:04:45 -0400) are available in the Git repository at:

Re: [PATCH 0/7] clk: Make clk_free return void

On Sat, 15 Jan 2022 17:24:57 -0500, Sean Anderson wrote: > clk_free cleans up resources allocated by clk_request et. al. It returns an > error code, but it really shouldn't. Much like regular free(), there is > typically no way to handle an error, and errors from clk_free shouldn't > prevent >

Re: [PATCH] clk: Consolidate some clock functions

On Sun, 27 Feb 2022 14:01:13 -0500, Sean Anderson wrote: > These functions are exactly the same as their "nodev" varients, except they > accept a device and not an ofnode. Rewrite them to just call the other > function. > > Applied, thanks! [1/1] clk: Consolidate some clock functions

Re: [PATCH 1/2] clk: ccf: Add some helper functions for clock ops

On Sun, 20 Mar 2022 16:34:45 -0400, Sean Anderson wrote: > Most CCF drivers follow a common pattern where their clock ops defer the > actual operation to the backing CCF clock. Add some generic implementations > of these functions to reduce duplication of code. > > Applied, thanks! [1/2] clk:

Re: [PATCH 2/2] clk: Use generic CCF ops where possible

On 3/20/22 4:34 PM, Sean Anderson wrote: This converts most CCF drivers to use generic ops. imx6q is the only outlier, where we retain the existing functionality by moving the check to request(). Signed-off-by: Sean Anderson --- drivers/clk/at91/pmc.c | 56 ++--

Re: [PATCH v1 1/1] efi_loader: initrddump: Actually use the custom CFLAGS

On 3/30/22 11:14, Andy Shevchenko wrote: It seems a copy'n'paste typo when tool had been introduced. It has never had the 'exit' suffix in the file name. Hence, the custom CFLAGS never been applied and, for example, BFD linker complains: LD lib/efi_loader/initrddump_efi.so ld.bfd:

Re: [PATCH v4 06/11] efi_loader: bootmgr: add booting from removable media

Hello Akashi-san, On Thu, Mar 24, 2022 at 10:54:38PM +0900, Masahisa Kojima wrote: > From: AKASHI Takahiro > > Under the current implementation, booting from removable media using > a architecture-specific default image name, say BOOTAA64.EFI, is > supported only in distro_bootcmd script. See

Re: [PATCH v3 0/3] malloc: Enable profiling dlmalloc with valgrind

Hi all, On 3/23/22 2:04 PM, Sean Anderson wrote: This series adds support for running valgrind against U-Boot's internal malloc. This allows for much more useful reports to be generated. Some example output of valgrind run against u-boot/master with this branch applied may be found at [1].

Re: [PATCH] IOMUX: Fix access past end of console_devices

On 3/30/22 1:13 PM, Andy Shevchenko wrote: On Wed, Mar 30, 2022 at 7:49 PM Sean Anderson wrote: Also I don't like to have workarounds for the broken tools. But if you still want to have something, what about rather this #define for_each_console_dev(i, file, dev) \ - for

Re: [PATCH] IOMUX: Fix access past end of console_devices

On Wed, Mar 30, 2022 at 7:49 PM Sean Anderson wrote: Also I don't like to have workarounds for the broken tools. But if you still want to have something, what about rather this > #define for_each_console_dev(i, file, dev) \ > - for (i = 0, dev = console_devices[file][i];

Re: [PATCH] IOMUX: Fix access past end of console_devices

On 3/30/22 1:07 PM, Andy Shevchenko wrote: On Wed, Mar 30, 2022 at 8:01 PM Andy Shevchenko wrote: On Wed, Mar 30, 2022 at 7:49 PM Sean Anderson wrote: ... #define for_each_console_dev(i, file, dev) \ - for (i = 0, dev = console_devices[file][i]; \ When we enter

Re: [PATCH] IOMUX: Fix access past end of console_devices

On Wed, Mar 30, 2022 at 8:05 PM Sean Anderson wrote: > On 3/30/22 1:01 PM, Andy Shevchenko wrote: > > On Wed, Mar 30, 2022 at 7:49 PM Sean Anderson wrote: ... > >> #define for_each_console_dev(i, file, dev) \ > >> - for (i = 0, dev = console_devices[file][i]; \ > > > >

Re: [PATCH] IOMUX: Fix access past end of console_devices

On Wed, Mar 30, 2022 at 8:01 PM Andy Shevchenko wrote: > On Wed, Mar 30, 2022 at 7:49 PM Sean Anderson wrote: ... > > #define for_each_console_dev(i, file, dev) \ > > - for (i = 0, dev = console_devices[file][i]; \ > > When we enter the loop, the dev is assigned and

Re: [PATCH] IOMUX: Fix access past end of console_devices

On 3/30/22 1:01 PM, Andy Shevchenko wrote: On Wed, Mar 30, 2022 at 7:49 PM Sean Anderson wrote: We should only access console_devices[file][i] once we have checked that i < cd_count[file]. Otherwise, we will access uninitialized memory at the end of the loop. console_devices[file][i] should

Re: [PATCH] IOMUX: Fix access past end of console_devices

On Wed, Mar 30, 2022 at 7:49 PM Sean Anderson wrote: > > We should only access console_devices[file][i] once we have checked that > i < cd_count[file]. Otherwise, we will access uninitialized memory at the end > of > the loop. console_devices[file][i] should not be NULL, but putting the >

[PATCH 0/4] mmc: sandbox: Some small fixes

Various small fixes which were found with valgrind. Sean Anderson (4): mmc: sandbox: Initialize the status register mmc: sandbox: Initialize backing buffer mmc: Import some defines for R1 responses mmc: sandbox: Set the response drivers/mmc/sandbox_mmc.c | 13 +++--- include/mmc.h

[PATCH 3/4] mmc: Import some defines for R1 responses

This imports defines for R1 responses from include/linux/mmc/mmc.h from Linux 5.10. Signed-off-by: Sean Anderson --- Yes, this is an old version, but it's what I had checked out, and I don't think there are any new fields we need to handle :) include/mmc.h | 52

[PATCH 1/4] mmc: sandbox: Initialize the status register

The send status command expects the status register to be returned as a response. Without writing data back, whatever is on the stack will be interpreted as the status register. There are a lot of fields in this register, but fortunately all zeros is interpreted as "we don't support anything."

[PATCH 4/4] mmc: sandbox: Set the response

The mmc subsystem checks the response, but we (almost) never set it. Add a bare-bones implementation. Technically, we are supposed to return our current state in our responses, but I don't think the subsystem checks it. Signed-off-by: Sean Anderson --- drivers/mmc/sandbox_mmc.c | 10 --

[PATCH 2/4] mmc: sandbox: Initialize backing buffer

Private data is initialized to all zeros by DM. Malloc does not do this. Initialize it. This fixes partition detection logic from trying to detect partitions in uninitialized memory. Fixes: 0bf61aced2 ("sandbox: mmc: Support a backing file") Signed-off-by: Sean Anderson ---

[PATCH] IOMUX: Fix access past end of console_devices

We should only access console_devices[file][i] once we have checked that i < cd_count[file]. Otherwise, we will access uninitialized memory at the end of the loop. console_devices[file][i] should not be NULL, but putting the assignment in the loop condition allows us to ensure that i is checked

[PATCH] dm: core: Use device_foreach_child where possible

We have some nice macros for iterating over devices in device.h, but they are not used by the driver core. Convert all the users I could find. Signed-off-by: Sean Anderson --- drivers/core/device-remove.c | 4 ++-- drivers/core/device.c| 21 ++--- drivers/core/devres.c

Re: [PATCH 0/6] Add MV88E61xx DSA driver and use on gwventana

On Tue, Mar 29, 2022 at 3:52 PM Tim Harvey wrote: > > This series adds a DSA driver for the MV88E61xx based on > drivers/net/phy/mv88e61xx and uses in on the gwventana_gw5904_defconfig. > > The hope is that the other three boards that use the MV88E61xx driver > can move to this as well eventually

Re: [PATCH v1 1/2] hexdump: Introduce debug APIs

On 3/30/22 11:30, Andy Shevchenko wrote: On Sat, Nov 13, 2021 at 11:14:28AM -0700, Simon Glass wrote: On Tue, 9 Nov 2021 at 05:03, Andy Shevchenko wrote: debug_hex_dump() and debug_hex_dump_bytes() conditionally print the dump based on DEBUG definition. Signed-off-by: Andy Shevchenko ---

Re: [PATCH v7 4/4] configs: sama5d2: enable option CONFIG_ATMEL_TCB_TIMER

Le Tue, 22 Mar 2022 13:35:08 +0100, Clément Léger a écrit : > Le Tue, 22 Mar 2022 11:18:39 +, > a écrit : > [...] > > > > Could not initialize timer (err -22) > > > > ... > > > > > > > > Could you investigate this please ? > > Hi Eugen, > > Ok, I'll try to debug that ! Hi

[PATCH v1 1/1] Revert "x86: Move FACP table into separate functions"

Before the culprit patch (see BugLink for the details): => acpi list Name Base Size Detail - -- RSDP 000e4500 24 v02 U-BOOT RSDT 000e4530 38 v01 U-BOOT U-BOOTBL 20220401 INTL 0 XSDT 000e45e0 4c v01 U-BOOT U-BOOTBL 20220401 INTL 0

Re: [ANN] U-Boot v2022.04-rc1 released

On Sat, Feb 12, 2022 at 05:02:00PM +0200, Andy Shevchenko wrote: > On Fri, Feb 11, 2022 at 9:15 PM Andy Shevchenko > wrote: > > On Fri, Feb 11, 2022 at 8:46 PM Andy Shevchenko > > wrote: > > > On Fri, Feb 11, 2022 at 8:31 PM Andy Shevchenko > > > wrote: > > > > On Mon, Jan 31, 2022 at

Re: [PATCH 5/6] net: add MV88E61xx DSA driver

On Tue, Mar 29, 2022 at 4:22 PM Marek Behún wrote: > > On Tue, 29 Mar 2022 15:52:39 -0700 > Tim Harvey wrote: > > > Add a DSA driver for the MV88E61xx compatible GbE Ethernet switches. > > > > Signed-off-by: Tim Harvey > Marek, Thanks for looking at this. > Is this final version that should

[PATCH v3 9/9] doc: uefi: Update the capsule update related documentation

Update the capsule update functionality related documentation to refect the fact that a unique image GUID is to be used per image that forms part of the capsule file. Signed-off-by: Sughosh Ganu --- Changes since V2: * Add a description for adding image index value and definition of

[PATCH v3 8/9] mkeficapsule: Remove raw and FIT GUID types

While building a capsule, the GUID value of that specific image is to be passed through the --guid command option to the mkeficapsule tool. This renders the EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID and EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID values superfluous. Remove the --raw and --fit command line

[PATCH v3 6/9] test: capsule: Modify the capsule tests to use GUID values for sandbox

The current UEFI capsule updation code uses two GUID values, one for FIT images, and one for raw images across platforms. This logic is being changed to have GUID values per image, per platform. Change the tests for the capsule update code to reflect this change. The GUID values now used are the

[PATCH v3 7/9] FMP: Remove GUIDs for FIT and raw images

The capsule update code has been modified for getting the image GUID values from the platform code. With this, each image now has a unique GUID value. With this change, there is no longer a need for defining GUIDs for FIT and raw images. Remove these GUID values. Signed-off-by: Sughosh Ganu ---

[PATCH v3 4/9] board: Define set_dfu_alt_info() for boards with UEFI capsule update enabled

Currently, there are a bunch of boards which enable the UEFI capsule update feature. The actual update of the firmware images is done through the dfu framework which uses the dfu_alt_info environment variable for getting information on the update, like device, partition number/address etc.

[PATCH v3 5/9] capsule: kconfig: Select SET_DFU_ALT_INFO config symbol for capsule update

The capsule update code uses the dfu_alt_info variable for the actual update of the firmware component. The dfu_alt_info variable gives information needed to perform the update, like the device on which the update is to be made, the partition, type of partition etc. Since the dfu_alt_info is a

[PATCH v3 3/9] capsule: Put a check for image index before the update

The current capsule update code compares the image GUID value in the capsule header with the image GUID value obtained from the GetImageInfo function of the Firmware Management Protocol(FMP). This comparison is done to ascertain if the FMP's SetImage function can be called for the update. Make

[PATCH v3 1/9] capsule: Add Image GUIDs and image index for platforms using capsule updates

Currently, all platforms that enable capsule updates do so using either EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID or EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID. This is based on the Firmware Management Protocol(FMP) instance used on the platform. However, this means that all platforms that enable a

[PATCH v3 2/9] capsule: FMP: Populate the image descriptor array from platform data

Currently, the image descriptor array that has been passed to the GetImageInfo function of the Firmware Management Protocol(FMP) gets populated through the data stored with the dfu framework. The dfu data is not restricted to contain information only of the images updatable through the capsule

[PATCH v3 0/9] efi: capsule: Capsule Update fixes and enhancements

This series is cleaning up the usage of the image GUIDs that are used in capsule update and the EFI System Resource Table(ESRT). There are some other enhancements being made to the capsule update code to make it more robust. Firstly, an overview of the fixes being made. Currently, there are

Re: [PATCH 1/2] net: phy: marvell: Support reg config via "marvell, reg-init" DT property

On Wed, 30 Mar 2022 15:33:34 +0200 Stefan Roese wrote: > So how to continue? Add this "reg-init" "feature" for now? And perhaps > drop it once this LED configuration is possible via the way you describe > above? Or drop it once it's also dropped in the Kernel? My personal > feeling is, that

Re: [PATCH] powerpc: Fix incorrect SYS_IMMR migration values

On Wednesday 30 March 2022 09:30:15 Tom Rini wrote: > When migrating SYS_IMMR, I didn't allow for boards to provide > non-default values here. This lead to an incorrect migration on the > platforms where CONFIG_SYS_IMMR is set to CONFIG_SYS_CCSRBAR and > CONFIG_SYS_CSSRBAR is NOT the same as

Re: [PATCH 1/2] net: phy: marvell: Support reg config via "marvell, reg-init" DT property

On 3/30/22 14:16, Marek Behún wrote: On Wed, 30 Mar 2022 10:38:25 +0200 Stefan Roese wrote: This patch adds support for the "marvell,reg-init" DT property, which is used to describe board specific Marvell PHY register configurations in the board dts file. This DT property is supported in the

[PATCH] powerpc: Fix incorrect SYS_IMMR migration values

When migrating SYS_IMMR, I didn't allow for boards to provide non-default values here. This lead to an incorrect migration on the platforms where CONFIG_SYS_IMMR is set to CONFIG_SYS_CCSRBAR and CONFIG_SYS_CSSRBAR is NOT the same as CONFIG_SYS_CCSRBAR_DEFAULT. Add text to the prompt so that

  1   2   >