[PATCH v2] clk: versal: Fix clock driver dependency

2025-06-04 Thread Michal Simek
Driver fully depends on firmware driver to be present that's why change imply to depends on to cover it. Signed-off-by: Michal Simek --- Changes in v2: - Also enable firmware node for versal platforms configs/xilinx_versal_net_virt_defconfig | 1 + configs/xilinx_versal_virt_defconfig | 1

Re: [PATCH v6 4/9] clk: at91: clk-main: drop parent_name check when registering main_rc oscillator

2025-06-04 Thread Eugen Hristev
On 6/3/25 08:05, Manikandan Muralidharan wrote: > The clk_register function logs an error if parent_name is missing from the > Device Tree.On the SAM9X7, the main_rc node is omitted to stay aligned with > the Linux Device Tree.Remove the parent_name check in at91_clk_main_rc() > to allow it to p

Re: [PATCH 6/6] arm: mach-k3: Print version of DM firmware during boot process

2025-06-04 Thread Moteen Shah
Hey Bryan, On 03/06/25 19:03, Bryan Brattlof wrote: On May 28, 2025 thus sayeth Moteen Shah: Print DM firmware's version in the boot up process of K3 devices. Signed-off-by: Moteen Shah --- arch/arm/mach-k3/am62ax/am62a7_init.c | 4 arch/arm/mach-k3/am62px/am62p5_init.c | 4 arc

Re: [PATCH 2/6] ti_sci_* : Add capability to access DM firmware's metadata

2025-06-04 Thread Neha Malcom Francis
On 05/06/25 11:43, Moteen Shah wrote: > Hey Neha, > > On 03/06/25 11:43, Neha Malcom Francis wrote: >> On 28/05/25 13:35, Moteen Shah wrote: >>> Introduce response and request structs to receive and request >>> information regarding DM version, etc from TI SCI. >>> >>> Signed-off-by: Moteen Shah

Re: [PATCH 2/6] ti_sci_* : Add capability to access DM firmware's metadata

2025-06-04 Thread Moteen Shah
Hey Dhruva, Thanks for the review. On 03/06/25 14:03, Dhruva Gole wrote: On May 28, 2025 at 13:35:15 +0530, Moteen Shah wrote: Introduce response and request structs to receive and request information regarding DM version, etc from TI SCI. Nit: Remove the ", etc" The patch is literally just a

Re: [PATCH 2/6] ti_sci_* : Add capability to access DM firmware's metadata

2025-06-04 Thread Moteen Shah
Hey Neha, On 03/06/25 11:43, Neha Malcom Francis wrote: On 28/05/25 13:35, Moteen Shah wrote: Introduce response and request structs to receive and request information regarding DM version, etc from TI SCI. Signed-off-by: Moteen Shah --- drivers/firmware/ti_sci.h | 29 +

Re: [PATCH 6/6] arm: mach-k3: Print version of DM firmware during boot process

2025-06-04 Thread Moteen Shah
Hey Neha, On 03/06/25 11:34, Neha Malcom Francis wrote: On 28/05/25 13:35, Moteen Shah wrote: Print DM firmware's version in the boot up process of K3 devices. Signed-off-by: Moteen Shah This patch does not apply cleanly on the latest master, you may have to rebase. I will do a rebase and

Re: [PATCH 09/12] efi: drop volatile qualifier from "save gd" variables

2025-06-04 Thread Heinrich Schuchardt
Am 4. Juni 2025 21:56:09 MESZ schrieb Rasmus Villemoes : >The global gd pointer is no longer volatile-qualified, so drop that >qualifier from these bookkeeping variables. > >Signed-off-by: Rasmus Villemoes Reviewed-by: Heinrich Schuchardt >--- > lib/efi_loader/efi_boottime.c | 2 +- > 1 file ch

Re: [PATCH v1] ti: k3: abstract common fdt api for reserved mem fixups

2025-06-04 Thread Anshul Dalal
On Wed Jun 4, 2025 at 11:27 PM IST, Tom Rini wrote: > On Thu, May 22, 2025 at 08:39:40PM +0530, Anshul Dalal wrote: > >> The usage of fdt_fixup_reserved is repeated for ATF and OP-TEE for >> multiple platforms, this patch creates a single fdt API for fixing up >> the reserved-memory node with added

Re: [PATCH v3 2/2] renesas: Renesas R-Car Gen4 watchdog driver

2025-06-04 Thread Shmuel Melamud
On Wed, Jun 4, 2025 at 12:02 PM Mattijs Korpershoek wrote: > > Hi Shmuel, > > Thank you for the patch. > > On Tue, Jun 03, 2025 at 06:06, Shmuel Leib Melamud via B4 Relay > wrote: > > > From: Shmuel Leib Melamud > > > > Add support of Renesas R-Car Gen4 watchdog timer. Timeouts up to > > 8184.0

Re: [PATCH] board: ti: am62ax: env: Use default MMC related args

2025-06-04 Thread Tom Rini
On Thu, 22 May 2025 11:40:13 -0500, Andrew Davis wrote: > There are common MMC args for TI plats in include/environment/ti/mmc.env. > Since we already include this, there is no need to redefine these > MMC vars. Use the defaults. > > This seems like something that could have been done while refac

Re: [PATCH v1] mach-k3: am62ax: enable caches for the SPL stage

2025-06-04 Thread Tom Rini
On Thu, 22 May 2025 18:03:04 +0530, Anshul Dalal wrote: > board_init_f for the am62a is missing the call to spl_enable_cache which > exists for all other am62 platforms (check am625_init.c & > am62p5_init.c). > > This allows the usage of caches while loading and parsing the u-boot.img > FIT resul

Re: [PATCH v2] mmc: am654_sdhci: Clear UHS_MODE_SELECT when <= MMC_HS_52

2025-06-04 Thread Tom Rini
On Thu, 22 May 2025 10:05:50 -0500, Judith Mendez wrote: > This clears UHS_MODE_SELECT for timing modes <= MMC_HS_52. > > When initializing to HS400 mode, the host controller downgrades to non-uhs > modes so clear UHS_MODE_SELECT at modes <= MMC_HS_52. > > This fixes eMMC writes on j7200 EVM. >

Re: [PATCH] mkimage: do a rough estimate for the size needed for hashes/signatures

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 10:19:41PM +0200, Rasmus Villemoes wrote: > On Wed, Jun 04 2025, Tom Rini wrote: > > > On Fri, May 16, 2025 at 02:54:30PM +0200, Rasmus Villemoes wrote: > > > >> > >> While not perfect, we can give a reasonable estimate of an upper bound > >> on the necessary extra size b

Re: [PATCH 00/12] drop volatile from global data

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 02:07:02PM -0600, Tom Rini wrote: > On Wed, Jun 04, 2025 at 09:56:00PM +0200, Rasmus Villemoes wrote: > > There's really no reason for the gd pointer to have the volatile > > qualifier. > > > > In fact, I claim that it's completely unnecessary and just pessimizes > > code g

Re: [PATCH 00/12] drop volatile from global data

2025-06-04 Thread Rasmus Villemoes
On Wed, Jun 04 2025, Tom Rini wrote: > On Wed, Jun 04, 2025 at 09:56:00PM +0200, Rasmus Villemoes wrote: >> There's really no reason for the gd pointer to have the volatile >> qualifier. >> >> In fact, I claim that it's completely unnecessary and just pessimizes >> code generation and forces ugl

Re: [PATCH] mkimage: do a rough estimate for the size needed for hashes/signatures

2025-06-04 Thread Rasmus Villemoes
On Wed, Jun 04 2025, Tom Rini wrote: > On Fri, May 16, 2025 at 02:54:30PM +0200, Rasmus Villemoes wrote: > >> >> While not perfect, we can give a reasonable estimate of an upper bound >> on the necessary extra size by simply counting the number of hash and >> signature nodes in the FIT image. >>

Re: [PATCH 00/12] drop volatile from global data

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 09:56:00PM +0200, Rasmus Villemoes wrote: > There's really no reason for the gd pointer to have the volatile > qualifier. > > In fact, I claim that it's completely unnecessary and just pessimizes > code generation and forces ugly casts in lots of places. For example, > see

[PATCH 03/12] mips: drop volatile qualifier from gd pointer

2025-06-04 Thread Rasmus Villemoes
Signed-off-by: Rasmus Villemoes --- arch/mips/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/mips/include/asm/global_data.h b/arch/mips/include/asm/global_data.h index 147a95ecea8..265dd2a3ec4 100644 --- a/arch/mips/include/asm/global_data.h ++

[PATCH 10/12] lib/trace: drop volatile qualifier from "save gd" variables

2025-06-04 Thread Rasmus Villemoes
The global gd pointer is no longer volatile-qualified, so drop that qualifier from these bookkeeping variables. Signed-off-by: Rasmus Villemoes --- lib/trace.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/trace.c b/lib/trace.c index 1d5f7dec979..3d54dfaddc0 100644

[PATCH 12/12] riscv: remove volatile from set_gd prototype

2025-06-04 Thread Rasmus Villemoes
It's slightly ironic that riscv at very first had the gd pointer volatile qualified [6020faf62c3 ("riscv: nx25: include: Add header files to support RISC-V")], removed that back in 2018 [40717eb849c ("riscv: checkpatch: Fix use of volatile")], and then in 2020 this helper was added [6b9966e1aa3 ("r

[PATCH 11/12] arm: remove volatile from set_gd prototype

2025-06-04 Thread Rasmus Villemoes
The global gd pointer is no longer volatile-qualified. Callers of this helper function have been updated to no longer use volatile-qualifed temporary variables, so update the prototype accordingly. Signed-off-by: Rasmus Villemoes --- arch/arm/include/asm/global_data.h | 2 +- 1 file changed, 1 i

[PATCH 09/12] efi: drop volatile qualifier from "save gd" variables

2025-06-04 Thread Rasmus Villemoes
The global gd pointer is no longer volatile-qualified, so drop that qualifier from these bookkeeping variables. Signed-off-by: Rasmus Villemoes --- lib/efi_loader/efi_boottime.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/efi_loader/efi_boottime.c b/lib/efi_loader/efi

[PATCH 08/12] arm: imx: remove unnecessary volatile qualifiers from "save gd" variables

2025-06-04 Thread Rasmus Villemoes
Now that the global gd pointer is no longer volatile-qualified, there's no reason for the temporary variables used for saving/restoring it to have that qualifier. Signed-off-by: Rasmus Villemoes --- arch/arm/mach-imx/hab.c | 2 +- arch/arm/mach-imx/imx9/scmi/soc.c | 4 ++-- arch/arm/ma

[PATCH 07/12] arc: drop volatile qualifier from gd pointer

2025-06-04 Thread Rasmus Villemoes
Signed-off-by: Rasmus Villemoes --- arch/arc/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arc/include/asm/global_data.h b/arch/arc/include/asm/global_data.h index fd9b7fb5f8d..4c3a25996fc 100644 --- a/arch/arc/include/asm/global_data.h +++ b/

[PATCH 01/12] arm: drop volatile qualifier from gd pointer

2025-06-04 Thread Rasmus Villemoes
There's a bunch of other places where this qualifier should be dropped, e.g. in the set_gd() prototype and for various variables used for stashing the value in the mach-imx/ directory and elsewhere. But that will be done in follow-up patches. Signed-off-by: Rasmus Villemoes --- arch/arm/include/

[PATCH 06/12] m68k: drop pointless #if 0 block

2025-06-04 Thread Rasmus Villemoes
The way DECLARE_GLOBAL_DATA_PTR is used, the stuff under #if 0 can never compile as you cannot have a non-constant initializer at global scope (and one would get linker errors as well because the 'gd' symbol would be defined in multiple TUs). Signed-off-by: Rasmus Villemoes --- arch/m68k/include

[PATCH 05/12] m68k: drop volatile qualifier from gd pointer

2025-06-04 Thread Rasmus Villemoes
Signed-off-by: Rasmus Villemoes --- arch/m68k/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/m68k/include/asm/global_data.h b/arch/m68k/include/asm/global_data.h index 4ac886933c6..29b46645676 100644 --- a/arch/m68k/include/asm/global_data.h ++

[PATCH 04/12] microblaze: drop volatile qualifier from gd pointer

2025-06-04 Thread Rasmus Villemoes
Signed-off-by: Rasmus Villemoes --- arch/microblaze/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/microblaze/include/asm/global_data.h b/arch/microblaze/include/asm/global_data.h index bb4112f22a3..f7922fac41c 100644 --- a/arch/microblaze/incl

[PATCH 00/12] drop volatile from global data

2025-06-04 Thread Rasmus Villemoes
There's really no reason for the gd pointer to have the volatile qualifier. In fact, I claim that it's completely unnecessary and just pessimizes code generation and forces ugly casts in lots of places. For example, see the casts in drivers/core/tag.c where elements are added to gd->dm_taglist, or

[PATCH 02/12] powerpc: drop volatile qualifier from gd pointer

2025-06-04 Thread Rasmus Villemoes
Signed-off-by: Rasmus Villemoes --- arch/powerpc/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/include/asm/global_data.h b/arch/powerpc/include/asm/global_data.h index cc2ce617350..26cbc7854d9 100644 --- a/arch/powerpc/include/asm/glob

Re: [PATCH] drivers: scsi: fix: memory leak in do_scsi_scan_one()

2025-06-04 Thread Heinrich Schuchardt
Am 4. Juni 2025 20:24:01 MESZ schrieb Tom Rini : >On Fri, May 16, 2025 at 08:40:20PM +0300, ant.v.morya...@gmail.com wrote: > >> From: Anton Moryakov >> >> Free allocated name buffer when blk_create_devicef() fails to prevent >> memory leak. After successful device creation, the name ownership is

Re: [PATCH] x86: Correct condition for init_cache_f_r()

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 12:20:17PM -0600, Simon Glass wrote: > Hi Tom, > > On Wed, 4 Jun 2025 at 11:23, Tom Rini wrote: > > > > On Wed, Jun 04, 2025 at 10:17:32AM -0600, Simon Glass wrote: > > > Hi Jerome, > > > > > > On Wed, 4 Jun 2025 at 07:15, Jerome Forissier > > > wrote: > > > > > > > > On

Re: [PATCH v1] mach-k3: am62ax: enable caches for the SPL stage

2025-06-04 Thread Tom Rini
On Thu, May 22, 2025 at 06:03:04PM +0530, Anshul Dalal wrote: > board_init_f for the am62a is missing the call to spl_enable_cache which > exists for all other am62 platforms (check am625_init.c & > am62p5_init.c). > > This allows the usage of caches while loading and parsing the u-boot.img > FIT

Re: [PATCH] drivers: scsi: fix: memory leak in do_scsi_scan_one()

2025-06-04 Thread Tom Rini
On Fri, May 16, 2025 at 08:40:20PM +0300, ant.v.morya...@gmail.com wrote: > From: Anton Moryakov > > Free allocated name buffer when blk_create_devicef() fails to prevent > memory leak. After successful device creation, the name ownership is > transferred to the device structure and should not b

Re: [PATCH] x86: Correct condition for init_cache_f_r()

2025-06-04 Thread Simon Glass
Hi Tom, On Wed, 4 Jun 2025 at 11:23, Tom Rini wrote: > > On Wed, Jun 04, 2025 at 10:17:32AM -0600, Simon Glass wrote: > > Hi Jerome, > > > > On Wed, 4 Jun 2025 at 07:15, Jerome Forissier > > wrote: > > > > > > On 6/4/25 15:09, Simon Glass wrote: > > > > The condition here is reversed, which make

Re: [PATCH v1] ti: k3: abstract common fdt api for reserved mem fixups

2025-06-04 Thread Tom Rini
On Thu, May 22, 2025 at 08:39:40PM +0530, Anshul Dalal wrote: > The usage of fdt_fixup_reserved is repeated for ATF and OP-TEE for > multiple platforms, this patch creates a single fdt API for fixing up > the reserved-memory node with added error handling. > > All k3 platforms already share a com

Re: [PATCH] x86: Correct condition for init_cache_f_r()

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 10:17:32AM -0600, Simon Glass wrote: > Hi Jerome, > > On Wed, 4 Jun 2025 at 07:15, Jerome Forissier > wrote: > > > > On 6/4/25 15:09, Simon Glass wrote: > > > The condition here is reversed, which makes link and coral very slow, > > > leading to lab failures. > > > > > > S

Re: [PATCH v7] arm: imx: Add support for Mettler-Toledo snowflake board

2025-06-04 Thread Fabio Estevam
Hi Wojciech, On Wed, Jun 4, 2025 at 11:09 AM Tom Rini wrote: > > On Wed, Jun 04, 2025 at 01:25:05PM +0200, Wojciech Dubowik wrote: > > > From: Manuel Traut > > > > The board is similar to "Kontron SL i.MX 8M Mini" SoM. I think you meant that the snowflake board is a carrier board that uses the

[PATCH v2 2/2] mtd: spinand: winbond: add Winbond W25N04KV flash support

2025-06-04 Thread Christian Marangi
Add Winbond W25N04KV flash support that use a different value to detect ECC bitflip. Signed-off-by: Christian Marangi --- drivers/mtd/nand/spi/winbond.c | 13 + 1 file changed, 13 insertions(+) diff --git a/drivers/mtd/nand/spi/winbond.c b/drivers/mtd/nand/spi/winbond.c index dd4ed2

[PATCH v2 1/2] linux/bitfield.h: sync from Linux 6.15

2025-06-04 Thread Christian Marangi
Sync bitfield.h header with Linux 6.15 version. Mainly is to permit the introduction of FIELD_PREP_CONST. The bug.h header changed to build_bug.h doesn't cause any regression as we also ship split header similar to how it's done with in Linux. Signed-off-by: Christian Marangi --- Changes v2: - Co

Re: [PATCH] x86: Correct condition for init_cache_f_r()

2025-06-04 Thread Simon Glass
Hi Jerome, On Wed, 4 Jun 2025 at 07:15, Jerome Forissier wrote: > > On 6/4/25 15:09, Simon Glass wrote: > > The condition here is reversed, which makes link and coral very slow, > > leading to lab failures. > > > > Signed-off-by: Simon Glass > > Fixes 6c171f7a184 ("common: board: make initcalls

[PATCH v2] sandbox: solve undefined reference to pthread_kill symbol

2025-06-04 Thread Raymond Mao
This patch is to solve the sandbox building error: $ make O=build-sandbox -s sandbox_defconfig $ make O=build-sandbox -s -j2 /usr/bin/ld: /tmp/u-boot.27rzOu.ltrans58.ltrans.o: undefined reference to symbol 'pthread_kill@@GLIBC_2.2.5' /usr/bin/ld: /lib/x86_64-linux-gnu/libpthread.so.0: error adding

Re: [PATCH] sandbox: solve undefined reference to pthread_kill symbol

2025-06-04 Thread Raymond Mao
Hi Tom, On Wed, 4 Jun 2025 at 09:56, Tom Rini wrote: > > On Wed, Jun 04, 2025 at 03:33:31PM +0530, Anshul Dalal wrote: > > Hi Raymond, > > > > On Wed Jun 4, 2025 at 2:30 AM IST, Raymond Mao wrote: > > > Hi Tom, > > > > > > On Tue, 3 Jun 2025 at 15:23, Tom Rini wrote: > > >> > > >> On Tue, Jun 03

Re: [PATCH] sandbox: solve undefined reference to pthread_kill symbol

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 05:03:44PM +0200, Patrice CHOTARD wrote: > > > On 6/4/25 15:56, Tom Rini wrote: > > On Wed, Jun 04, 2025 at 03:33:31PM +0530, Anshul Dalal wrote: > >> Hi Raymond, > >> > >> On Wed Jun 4, 2025 at 2:30 AM IST, Raymond Mao wrote: > >>> Hi Tom, > >>> > >>> On Tue, 3 Jun 2025 a

Re: [PATCH] sandbox: solve undefined reference to pthread_kill symbol

2025-06-04 Thread Patrice CHOTARD
On 6/4/25 15:56, Tom Rini wrote: > On Wed, Jun 04, 2025 at 03:33:31PM +0530, Anshul Dalal wrote: >> Hi Raymond, >> >> On Wed Jun 4, 2025 at 2:30 AM IST, Raymond Mao wrote: >>> Hi Tom, >>> >>> On Tue, 3 Jun 2025 at 15:23, Tom Rini wrote: On Tue, Jun 03, 2025 at 02:00:23PM -0400, Raymon

Re: [PATCH] usb: gadget: atmel: reliably generate disconnect by disabling controller instead of toggling PULLD_DIS

2025-06-04 Thread Zixun LI
Hi all, The case has been reported with No.01589331. In brief line high-impedance is not observed when both PULLD_DIS & DETACH bits are 1: - In unenumerated state (no cable attached) DP is still pulled up - In enumerated state, disconnection is not detected by host [1] [2] only by [3]. The test

Re: [PATCH v3 1/2] bootstd: Add implementation for bootmeth rauc

2025-06-04 Thread Wadim Egorov
Am 04.06.25 um 15:15 schrieb Martin Schwan: Add a bootmeth driver which supports booting A/B system with RAUC as their update client. Signed-off-by: Martin Schwan Tested-by: Wadim Egorov phycore-am62x log: https://pastebin.ubuntu.com/p/Sh9rXqPbgX --- boot/Kconfig | 51 ++

Re: [PATCH v2] ARM: imx: mxs: Add support for imx287 based BTT devices

2025-06-04 Thread Lukasz Majewski
Hi Fabio, > Hi Lukasz, > > On Wed, Jun 4, 2025 at 8:55 AM Lukasz Majewski wrote: > > > +source "board/liebherr/btt/Kconfig" > > source "board/freescale/mx28evk/Kconfig" > > source "board/liebherr/xea/Kconfig" > > Please keep the entries sorted. Ok. > > > --- /dev/null > > +++ b/board/li

Re: [PATCH] x86: Correct condition for init_cache_f_r()

2025-06-04 Thread Tom Rini
On Wed, 04 Jun 2025 07:09:02 -0600, Simon Glass wrote: > The condition here is reversed, which makes link and coral very slow, > leading to lab failures. > > Fixes 6c171f7a184 ("common: board: make initcalls static") > > Applied to u-boot/master, thanks! [1/1] x86: Correct condition for init_

Re: [PATCH] mkimage: do a rough estimate for the size needed for hashes/signatures

2025-06-04 Thread Tom Rini
On Fri, May 16, 2025 at 02:54:30PM +0200, Rasmus Villemoes wrote: > Background: > > I have several customers that will be using a certain remote signing > service for signing their images, in order that the private keys are > never exposed outside that company's secure servers. This is done via >

Re: [PATCH v7] arm: imx: Add support for Mettler-Toledo snowflake board

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 01:25:05PM +0200, Wojciech Dubowik wrote: > From: Manuel Traut > > The board is similar to "Kontron SL i.MX 8M Mini" SoM. > There are two variants. Snowflake_v2 has an external SDCard Interface. > LEIG is the same but without display and with emmc card only. > Both varian

Re: [PATCH v2] ARM: imx: mxs: Add support for imx287 based BTT devices

2025-06-04 Thread Fabio Estevam
Hi Lukasz, On Wed, Jun 4, 2025 at 8:55 AM Lukasz Majewski wrote: > +source "board/liebherr/btt/Kconfig" > source "board/freescale/mx28evk/Kconfig" > source "board/liebherr/xea/Kconfig" Please keep the entries sorted. > --- /dev/null > +++ b/board/liebherr/btt/btt.c > @@ -0,0 +1,449 @@ > +//

Re: [PATCH] sandbox: solve undefined reference to pthread_kill symbol

2025-06-04 Thread Tom Rini
On Wed, Jun 04, 2025 at 03:33:31PM +0530, Anshul Dalal wrote: > Hi Raymond, > > On Wed Jun 4, 2025 at 2:30 AM IST, Raymond Mao wrote: > > Hi Tom, > > > > On Tue, 3 Jun 2025 at 15:23, Tom Rini wrote: > >> > >> On Tue, Jun 03, 2025 at 02:00:23PM -0400, Raymond Mao wrote: > >> > Hi Tom, > >> > > >>

Re: [PATCH v4 24/28] board: google: Add board_debug_uart_init() for Trogdor

2025-06-04 Thread Casey Connolly
On 5/28/25 13:25, Caleb Connolly via groups.io wrote: On 5/24/25 00:58, Stephen Boyd wrote: Implement board_debug_uart_init() for Trogdor boards so that the debug UART can be used. Initialize the clk to XO speed (19.2MHz) and change the pin configuration to mux out the uart hardware on the

Re: [PATCH v3 0/3] u-boot chain-loading LineageOS bootimg

2025-06-04 Thread Casey Connolly
On 5/18/25 13:16, George Chan via B4 Relay wrote: This is a series of patches to enable chainloading LineageOS on qcom SOC. Patch #1 introduce kconfig to ignore those default value and use loadaddr instead. That workaround some androidboot image have invalid kernel/ramdisk loadaddr. Patch #2

Re: Determining Simon Glass's future in the U-Boot project

2025-06-04 Thread Casey Connolly
On 6/4/25 15:15, Casey Connolly wrote: Hi Tom, On 5/28/25 19:59, Tom Rini wrote: Hey all, First, I am not happy to be writing this email. But at this point, I feel I have no other choice, for the good of the overall project and community. Back in January[0] of this year I made a post with

Re: Determining Simon Glass's future in the U-Boot project

2025-06-04 Thread Casey Connolly
Hi Tom, On 5/28/25 19:59, Tom Rini wrote: Hey all, First, I am not happy to be writing this email. But at this point, I feel I have no other choice, for the good of the overall project and community. Back in January[0] of this year I made a post with almost this same subject line. At that poin

Re: [PATCH] x86: Correct condition for init_cache_f_r()

2025-06-04 Thread Jerome Forissier
On 6/4/25 15:09, Simon Glass wrote: > The condition here is reversed, which makes link and coral very slow, > leading to lab failures. > > Signed-off-by: Simon Glass > Fixes 6c171f7a184 ("common: board: make initcalls static") > --- > > common/board_f.c | 2 +- > 1 file changed, 1 insertion(+),

Re: [PATCH v6 2/3] common: board: make initcalls static

2025-06-04 Thread Simon Glass
Hi Tom, On Tue, 3 Jun 2025 at 10:10, Tom Rini wrote: > > On Tue, Jun 03, 2025 at 09:22:01AM -0600, Simon Glass wrote: > > Hi Jerome, > > > > On Fri, 4 Apr 2025 at 07:50, Jerome Forissier > > wrote: > > > > > > Change board_init_f(), board_init_f_r() and board_init_r() to make > > > static calls

[PATCH] x86: Correct condition for init_cache_f_r()

2025-06-04 Thread Simon Glass
The condition here is reversed, which makes link and coral very slow, leading to lab failures. Signed-off-by: Simon Glass Fixes 6c171f7a184 ("common: board: make initcalls static") --- common/board_f.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/board_f.c b/common

[PATCH v7] arm: imx: Add support for Mettler-Toledo snowflake board

2025-06-04 Thread Wojciech Dubowik
From: Manuel Traut The board is similar to "Kontron SL i.MX 8M Mini" SoM. There are two variants. Snowflake_v2 has an external SDCard Interface. LEIG is the same but without display and with emmc card only. Both variants support 1GiB of main memory. [ bigeasy: porting and a bit of cleanup ] Sig

Re: [PATCH 1/3] usb: udc: ci: support USB gadget driver model

2025-06-04 Thread Wojciech Dubowik
On Sat, Apr 19, 2025 at 09:32:04AM +, Sam Day wrote: > Heya Stephan, > > On Wed Apr 16, 2025 at 8:51 PM CEST, Stephan Gerhold wrote: > > On Sat, Apr 12, 2025 at 07:39:57PM +, Sam Day wrote: > >> When CONFIG_DM_USB_GADGET is enabled, a UCLASS_USB_GADGET_GENERIC driver > >> will be defined t

Re: [PATCH v2 0/7] Qualcomm: teach the build system to emit signed ELF images

2025-06-04 Thread Stephan Gerhold
On Mon, Jun 02, 2025 at 06:10:51PM +0200, Casey Connolly wrote: > With several new Qualcomm platforms appearing on the mailing list, all > of which build U-Boot as an ELF, sign it, and then flash it to some > partition on the board, we're getting a lot of defconfigs which just > contain a debug UAR

Re: [PATCH RFC/RFT 0/2] gpio: qcom: rewritte SPMI gpio driver from Linux driver

2025-06-04 Thread Casey Connolly
On 6/3/25 18:43, Neil Armstrong wrote: On 01/04/2025 11:47, Neil Armstrong wrote: The current SPMI gpio driver is very old and doesn't support pin state tracking to fully support the whole pinconf calls. The simplest is to rewritte the driver using the v6.14 Linux driver and fully implement

Re: [PATCH] board: qualcomm: add a MAINTAINERS file

2025-06-04 Thread Neil Armstrong
On 04/06/2025 13:34, Casey Connolly wrote: Add a MAINTAINERS file for assigning maintainership of a particular Qualcomm platform or board (if board specific files exist). It is intended to supplement the treewide ARM SNAPDRAGON maintainers with folks who have a more specific interest. Add an ini

Re: [PATCH 0/2] arm: armv7: fix a bug that prevents CONFIG_BLOBLIST and CONFIG_POSITION_INDEPENDENT to be enabled together

2025-06-04 Thread Mikko Rapeli
Hi, On Mon, Jun 02, 2025 at 12:37:10PM +0200, Quentin Schulz wrote: > +Cc Mikko Rapeli who's attempting to patch this in OpenEmbedded-Core > > On 5/31/25 3:10 PM, Yang Xiwen via B4 Relay wrote: > > [You don't often get email from > > devnull+forbidden405.outlook@kernel.org. Learn why this is

[PATCH v3 2/2] doc: Add description for bootmeth rauc

2025-06-04 Thread Martin Schwan
Add documentation for the bootmeth "rauc", which boots an A/B system with RAUC from MMC. Signed-off-by: Martin Schwan --- doc/develop/bootstd/index.rst| 1 + doc/develop/bootstd/overview.rst | 1 + doc/develop/bootstd/rauc.rst | 56 3 files chan

[PATCH v3 1/2] bootstd: Add implementation for bootmeth rauc

2025-06-04 Thread Martin Schwan
Add a bootmeth driver which supports booting A/B system with RAUC as their update client. Signed-off-by: Martin Schwan --- boot/Kconfig | 51 ++ boot/Makefile| 1 + boot/bootmeth_rauc.c | 432 +++ 3 files changed, 484 inserti

[PATCH v3 0/2] bootstd: New bootmeth for RAUC A/B systems

2025-06-04 Thread Martin Schwan
This series implements a new bootmeth for RAUC A/B systems. RAUC (Robust Auto Update Controller) is a lightweight update client, providing "Safe and Secure OTA Updates for Embedded Linux". See the following links for more information about RAUC: https://rauc.io/ https://rauc.readthedocs.io/en/

[PATCH v2] ARM: imx: mxs: Add support for imx287 based BTT devices

2025-06-04 Thread Lukasz Majewski
The btt[c3] devices are based on imx287 SoC. U-Boot SPL 2025.04-01081-g07e086681d26 (Apr 16 2025 - 12:24:36 +0200) Trying to boot from MMC1 U-Boot 2025.04-01081-g07e086681d26 (Apr 16 2025 - 12:24:36 +0200) CPU: Freescale i.MX28 rev1.2 at 454 MHz BOOT: SSP SPI #3, master, 3V3 NOR Model: BTT3 B

[PATCH] board: qualcomm: add a MAINTAINERS file

2025-06-04 Thread Casey Connolly
Add a MAINTAINERS file for assigning maintainership of a particular Qualcomm platform or board (if board specific files exist). It is intended to supplement the treewide ARM SNAPDRAGON maintainers with folks who have a more specific interest. Add an initial entry for the QCS6490 platform which pow

Re: [PATCH v2 0/5] Introduce support for QCS615 SoC based Platform

2025-06-04 Thread Casey Connolly
On 6/3/25 21:22, Tom Rini wrote: On Tue, Jun 03, 2025 at 06:25:22PM +0200, Casey Connolly wrote: Hi Aswin, Varadaraja, Since we're expecting to do some more cleanup after adding all these dragonwing platforms, would you be up for adding MAINTAINERS entries for them? This way you'll actually

Re: [PATCH v2 0/7] Qualcomm: teach the build system to emit signed ELF images

2025-06-04 Thread Casey Connolly
On 6/4/25 11:07, Stephan Gerhold wrote: On Mon, Jun 02, 2025 at 06:10:51PM +0200, Casey Connolly wrote: With several new Qualcomm platforms appearing on the mailing list, all of which build U-Boot as an ELF, sign it, and then flash it to some partition on the board, we're getting a lot of def

Re: [PATCH v2 6/7] configs: qualcomm: use mkmbn and stop creating ELF files

2025-06-04 Thread Casey Connolly
On 6/4/25 11:21, Stephan Gerhold wrote: On Mon, Jun 02, 2025 at 06:10:57PM +0200, Casey Connolly wrote: Remove qcs9100_defconfig since it is now identical to qcom_defconfig. Additionally remove the load address and REMAKE_ELF from other Qualcomm defconfigs. For these platforms you should exp

Re: [PATCH v2 3/7] tools: add mkmbn tool for Qualcomm

2025-06-04 Thread Casey Connolly
Hi Stephan On 6/4/25 11:15, Stephan Gerhold wrote: On Mon, Jun 02, 2025 at 06:10:54PM +0200, Casey Connolly wrote: This is a fork of qtestsign[1] with modifications to integrate with the U-Boot build system. I think it would be good if the "library" part of qtestsign (cert.py, elf.py, hashseg

Re: [PATCH v2 6/7] configs: qualcomm: use mkmbn and stop creating ELF files

2025-06-04 Thread Stephan Gerhold
On Mon, Jun 02, 2025 at 06:10:57PM +0200, Casey Connolly wrote: > Remove qcs9100_defconfig since it is now identical to qcom_defconfig. > Additionally remove the load address and REMAKE_ELF from other Qualcomm > defconfigs. > > For these platforms you should explicitly build the u-boot.mbn target

Re: [PATCH] usb: gadget: atmel: reliably generate disconnect by disabling controller instead of toggling PULLD_DIS

2025-06-04 Thread Mattijs Korpershoek
Hi Zixun, Thank you for the patch. On Mon, Jun 02, 2025 at 17:45, Zixun LI wrote: I'm surprised that checkpatch.pl does not catch this, but the subject (title) is too long (it should be less than 70 chars): https://docs.u-boot.org/en/latest/develop/sending_patches.html#commit-message-convention

Re: [PATCH v3 2/6] lmb: replace the lmb_alloc() and lmb_alloc_base() API's

2025-06-04 Thread Sughosh Ganu
On Wed, 4 Jun 2025 at 12:53, Ilias Apalodimas wrote: > > [...] > > > > > > > > > > > > > > > > > > > This tends to blow up in random ways. See > > > > > > commit 67be24906fe. TL;DR 0 is a valid address in some systems. > > > > > > > > > > Yes, I see your point. I think the calling function will ha

Re: [PATCH] sandbox: solve undefined reference to pthread_kill symbol

2025-06-04 Thread Anshul Dalal
Hi Raymond, On Wed Jun 4, 2025 at 2:30 AM IST, Raymond Mao wrote: > Hi Tom, > > On Tue, 3 Jun 2025 at 15:23, Tom Rini wrote: >> >> On Tue, Jun 03, 2025 at 02:00:23PM -0400, Raymond Mao wrote: >> > Hi Tom, >> > >> > On Tue, 3 Jun 2025 at 11:47, Tom Rini wrote: >> > > >> > > On Tue, Jun 03, 2025 a

Re: [PATCH] usb: gadget: atmel: reliably generate disconnect by disabling controller instead of toggling PULLD_DIS

2025-06-04 Thread Eugen Hristev
On 6/4/25 11:20, Mattijs Korpershoek wrote: > Hi Zixun, > > Thank you for the patch. > > On Mon, Jun 02, 2025 at 17:45, Zixun LI wrote: > > I'm surprised that checkpatch.pl does not catch this, but the subject > (title) is too long (it should be less than 70 chars): > https://docs.u-boot.org

Re: [PATCH v2 3/7] tools: add mkmbn tool for Qualcomm

2025-06-04 Thread Stephan Gerhold
On Mon, Jun 02, 2025 at 06:10:54PM +0200, Casey Connolly wrote: > This is a fork of qtestsign[1] with modifications to integrate with the > U-Boot build system. I think it would be good if the "library" part of qtestsign (cert.py, elf.py, hashseg.py) would stay unmodified if possible, and you only

Re: [PATCH 1/2] linux/bitfield.h: import FIELD_PREP_CONST macro from Linux Kernel

2025-06-04 Thread Quentin Schulz
Hi Christian, On 6/3/25 10:37 PM, Christian Marangi wrote: On Tue, Jun 03, 2025 at 05:08:13PM +0200, Quentin Schulz wrote: Hi Christian, On 6/3/25 10:51 AM, Christian Marangi wrote: Import FIELD_PREP_CONST macro from Linux Kernel to permit usage of FIELD_PREP with scenario where a constant va

Re: [PATCH v3 2/2] renesas: Renesas R-Car Gen4 watchdog driver

2025-06-04 Thread Mattijs Korpershoek
Hi Shmuel, Thank you for the patch. On Tue, Jun 03, 2025 at 06:06, Shmuel Leib Melamud via B4 Relay wrote: > From: Shmuel Leib Melamud > > Add support of Renesas R-Car Gen4 watchdog timer. Timeouts up to > 8184.0s are supported (CKS1 register is not involved). The watchdog > uses the clock of

Re: [PATCH v2 04/13] clk: add CONFIG_CLK_AUTO_ID

2025-06-04 Thread Patrice CHOTARD
On 6/4/25 08:50, Michael Nazzareno Trimarchi wrote: > Hi > > On Wed, Jun 4, 2025 at 8:48 AM Michael Nazzareno Trimarchi > wrote: >> >> Hi Patrice >> >> On Wed, Jun 4, 2025 at 8:46 AM Patrice CHOTARD >> wrote: >>> >>> >>> >>> On 6/4/25 08:14, Michael Nazzareno Trimarchi wrote: Hi >>>

Re: [PATCH v3 1/2] renesas: Handle CLK_TYPE_GEN4_MDSEL in gen3_clk_get_rate64()

2025-06-04 Thread Mattijs Korpershoek
Hi Shmuel, Thank you for the patch. On Tue, Jun 03, 2025 at 06:06, Shmuel Leib Melamud via B4 Relay wrote: > From: Shmuel Leib Melamud > > Add support of CLK_TYPE_GEN4_MDSEL clock type to gen3_clk_get_rate64() > function. In particular, this type of clock is used by Renesas R-Car > Gen4 watch

Re: [PATCH v3 2/6] lmb: replace the lmb_alloc() and lmb_alloc_base() API's

2025-06-04 Thread Ilias Apalodimas
[...] > > > > > > > > > > > > > > > This tends to blow up in random ways. See > > > > > commit 67be24906fe. TL;DR 0 is a valid address in some systems. > > > > > > > > Yes, I see your point. I think the calling function will have to be > > > > re-written such that the env variables get stored only