Hi Patrice, Marek,
On lun., févr. 10, 2025 at 14:42, Marek Vasut wrote:
> On 2/10/25 11:28 AM, Patrice CHOTARD wrote:
>>
>> Hi Marek
>
> Hi,
>
>> Any chance to get this series merged in next U-Boot tag 2025.04-rc2 ?
> Gadget stuff is on Mattijs desk, please ping me in a few days if he
> doesn'
On lun., févr. 10, 2025 at 14:42, Marek Vasut wrote:
> On 2/10/25 11:28 AM, Patrice CHOTARD wrote:
>> Hi Marek
>
> Hi,
>
>> Any chance to get this patch merged in next U-Boot tag 2025.04-rc2 ?
> Gadget stuff is on Mattijs desk, please ping me in a few days if he
> doesn't pick it up, I'll do so
On 10.02.25 23:01, Tom Rini wrote:
Hey all,
It's release day and so here's v2025.04-rc2. As this is the -rc2
release, I've now also opened up the -next branch and will be stricter
about what I apply myself, and what I see coming in for pull requests as
well moving forward.
Continuing on with wh
Hi!
10/02/2025 20.50, Evgeny Bachinin wrote:
The Amlogic Meson SoC secure monitor (TF-A) handles a call (0x8244)
to retrieve a chip_id from eFuse OTP data [1].
Previously, this sm call (0x8244) was used to retrieve just unique
SoC number [2] (a.k.a. SoC "serial" [3]), identifying partic
Superseed by
https://lore.kernel.org/u-boot/20250210-meson_chip_id_all_vers-v1-0-b98f8b688...@salutedevices.com/
17/01/2025 13.41, Viacheslav Bocharov wrote:
From: Nikita Maslo
The Amlogic Meson SoC Secure Monitor implements a call to retrieve an
unique SoC ID starting from the GX Family and
There are some device-tree overlays with missing entries for the
keyfile. Add them to sign all images in the U-Boot FIT image.
Signed-off-by: Daniel Schultz
---
Changes:
v2: Removed keyfile definitions which are already defined in k3-binman.dtsi
arch/arm/dts/k3-am642-phycore-som-binman.dtsi |
There are some device-tree overlays with missing entries for the
keyfile. Add them to sign all images in the U-Boot FIT image.
Signed-off-by: Daniel Schultz
---
Changes:
v2: Removed keyfile definitions which are already defined in k3-binman.dtsi
arch/arm/dts/k3-am625-phycore-som-binman.dtsi |
Boot the Radxa ROCK 3B from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ rkflashtool l < mkimage-in-simple-bin.mkimage-rockchip-tpl
$ rkflashtool L < mkimage-in-simple-bin.mkimage-u-boot-spl
1b. Download the TPL and SPL usin
Boot the Radxa ROCK Pi S from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ openssl rc4 -provider legacy -K 7c4e0304550509072d2c7b38170d1711 \
< mkimage-in-simple-bin.mkimage-rockchip-tpl | rkflashtool l
$ openssl rc4
Boot the Radxa ROCK Pi E v1/v3 from the USB OTG port using
rkflashtool[1] or rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ openssl rc4 -provider legacy -K 7c4e0304550509072d2c7b38170d1711 \
< mkimage-in-simple-bin.mkimage-u-boot-tpl | rkflashtool l
$ openssl
Boot the Radxa ZERO 3E/3W from the USB OTG port using rkflashtool[1]
or rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ rkflashtool l < mkimage-in-simple-bin.mkimage-rockchip-tpl
$ rkflashtool L < mkimage-in-simple-bin.mkimage-u-boot-spl
1b. Download the TPL and SPL u
Boot the Radxa ROCK 5B from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ rkflashtool l < mkimage-in-simple-bin.mkimage-rockchip-tpl
$ rkflashtool L < mkimage-in-simple-bin.mkimage-u-boot-spl
1b. Download the TPL and SPL usin
Boot the Radxa ROCK 3A from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ rkflashtool l < mkimage-in-simple-bin.mkimage-rockchip-tpl
$ rkflashtool L < mkimage-in-simple-bin.mkimage-u-boot-spl
1b. Download the TPL and SPL usin
This patch series adds the ability to boot from the USB OTG port
(dr_mode = "otg") to the Radxa boards.
Use rkflashtool[1] or rkusbboot[2] to download TPL and SPL from
MASKROM mode, and dfu-util to download U-Boot from DFU mode.
This patch series depends on patches[3] that add DFU to SPL.
[1] ht
Hello Tom,
On 10.02.25 23:26, Tom Rini wrote:
Here's the latest report.
-- Forwarded message -
From:
Date: Mon, Feb 10, 2025 at 4:12 PM
Subject: New Defects reported by Coverity Scan for Das U-Boot
To:
Hi,
Please find the latest report on new defect(s) introduced to Das U-B
Hi Quentin,
On 2/5/25 21:59, Quentin Schulz wrote:
Hi Naoki,
On 1/29/25 2:25 PM, FUKAUMI Naoki wrote:
After adding the below configs, binman produces an error.
CONFIG_SPL_DFU
CONFIG_SPL_ENV_SUPPORT
CONFIG_SPL_USB_DWC3_GENERIC
CONFIG_SPL_USB_GADGET
binman: Section '/binman/simple-bin-
Boot the RK3568 from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ rkflashtool l < mkimage-in-simple-bin.mkimage-rockchip-tpl
$ rkflashtool L < mkimage-in-simple-bin.mkimage-u-boot-spl
1b. Download the TPL and SPL using rkusb
This patch series adds the ability to boot from the USB OTG port to
the RK3588, RK3568, RK3566, RK3399, RK3328, and RK3308.
Use rkflashtool[1] or rkusbboot[2] to download TPL and SPL from
MASKROM mode, and dfu-util to download U-Boot from DFU mode.
This patch series depends on patches[3] that fix
Boot the RK3328 from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ openssl rc4 -provider legacy -K 7c4e0304550509072d2c7b38170d1711 \
< mkimage-in-simple-bin.mkimage-rockchip-tpl | rkflashtool l
$ openssl rc4 -provider
Boot the RK3399 from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ openssl rc4 -provider legacy -K 7c4e0304550509072d2c7b38170d1711 \
< mkimage-in-simple-bin.mkimage-rockchip-tpl | rkflashtool l
$ openssl rc4 -provider
Boot the RK3308 from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ openssl rc4 -provider legacy -K 7c4e0304550509072d2c7b38170d1711 \
< mkimage-in-simple-bin.mkimage-rockchip-tpl | rkflashtool l
$ openssl rc4 -provider
Allows SPL to use DFU when SPL is booted from USB.
Signed-off-by: FUKAUMI Naoki
---
arch/arm/mach-rockchip/spl-boot-order.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-rockchip/spl-boot-order.c
b/arch/arm/mach-rockchip/spl-boot-order.c
index 3dce9b30898..2943c8bb494 10
Place U-Boot at 8MiB in order to place FIT at 2MiB.
Signed-off-by: Jonas Karlman
Signed-off-by: FUKAUMI Naoki
---
arch/arm/mach-rockchip/Kconfig| 6 +++---
arch/arm/mach-rockchip/rk3308/Kconfig | 3 ---
arch/arm/mach-rockchip/rk3568/Kconfig | 3 ---
arch/arm/mach-rockchip/rk3588/Kconfig
Boot the RK3588 from the USB OTG port using rkflashtool[1] or
rkusbboot[2] and dfu-util.
1a. Download the TPL and SPL using rkflashtool
$ rkflashtool l < mkimage-in-simple-bin.mkimage-rockchip-tpl
$ rkflashtool L < mkimage-in-simple-bin.mkimage-u-boot-spl
1b. Download the TPL and SPL using rkusb
Hi Daniel,
Am 10.02.25 um 14:36 schrieb Daniel Schultz:
There are some device-tree overlays and firmwares with missing entries
for the keyfile. Add them to sign all images in the U-Boot FIT image.
Signed-off-by: Daniel Schultz
---
arch/arm/dts/k3-am625-phycore-som-binman.dtsi | 49 ++
If CONFIG_EFI_CAPSULE_FIRMWARE_RAW, CONFIG_SPL_ENV_SUPPORT, and
CONFIG_SPL_DFU are enabled, linking u-boot-spl will fail.
LD spl/u-boot-spl
ld.bfd: drivers/dfu/dfu.o: in function `dfu_init_env_entities':
/home/radxa/u-boot/drivers/dfu/dfu.c:173:(.text.dfu_init_env_entities+0x24):
undefined
Rockchip RK3399 targets build TPL. If CONFIG_SPL_USB_DWC3_GENERIC and
CONFIG_SPL_USB_GADGET are enabled, linking u-boot-tpl will fail.
LD tpl/u-boot-tpl
ld.bfd: drivers/usb/dwc3/dwc3-generic.o: in function `dwc3_glue_bind_common':
/home/radxa/u-boot/drivers/usb/dwc3/dwc3-generic.c:527:(.tex
Hi Tom,
On 2025/2/11 00:41, Tom Rini wrote:
On Fri, Feb 07, 2025 at 09:53:01AM -0800, Jonathan Bar Or wrote:
Thank you.
So, I'm attaching my findings in a md file - see attachment.
All of those could be avoided by using safe math, such as
__builtin_mul_overflow and __builtin_add_overflow, whi
Am 10.02.25 um 22:25 schrieb Daniel Schultz:
Increase the maximum Image size from 23 MB to 26 MB by moving the
initramfs start address up. This gives us a bigger ranger to
provide kernel images which are not stripped down too much.
Signed-off-by: Daniel Schultz
Reviewed-by: Wadim Egorov
---
Am 10.02.25 um 22:25 schrieb Daniel Schultz:
Increase the maximum Image size from 23 MB to 26 MB by moving the
initramfs start address up. This gives us a bigger ranger to
provide kernel images which are not stripped down too much.
Signed-off-by: Daniel Schultz
Reviewed-by: Wadim Egorov
---
Am 10.02.25 um 22:25 schrieb Daniel Schultz:
Enable ENV_IS_IN_SPI_FLASH to read the environment from the SPI
flash when booting from it. The oftree, kernel and ramdisk sizes
are located in this environment and therefore required to boot
an initramfs.
Signed-off-by: Daniel Schultz
Reviewed-by:
Am 10.02.25 um 22:25 schrieb Daniel Schultz:
Enable ENV_IS_IN_SPI_FLASH to read the environment from the SPI
flash when booting from it. The oftree, kernel and ramdisk sizes
are located in this environment and therefore required to boot
an initramfs.
Signed-off-by: Daniel Schultz
Reviewed-by:
Hi Dhruva,
Am 05.02.25 um 12:55 schrieb Dhruva Gole:
On Feb 05, 2025 at 05:30:12 +0100, Wadim Egorov wrote:
Detect RAM size via EEPROM and adjust DDR size and banks accordingly.
Include necessary fixups to handle ECC-enabled configurations.
Signed-off-by: Wadim Egorov
Tested-by: Daniel Schult
The PCS exists only in GMAC1 and relates to SGMII interface and
is used to control the SGMII PHY.
Signed-off-by: Jim Liu
---
arch/arm/include/asm/arch-npcm8xx/gmac.h | 18
drivers/net/designware.c | 27
2 files changed, 45 insertions(+)
On Wed, Feb 05, 2025 at 07:00:25PM +0300, Maks Mishin wrote:
> Dynamic memories, referenced by 'ptr' and 'res' is allocated
> by calling function 'hexport_r' and lost when the function success returns.
>
> Signed-off-by: Maks Mishin
This leads to run time failures such as:
https://source.denx.
On Thu, Feb 06, 2025 at 04:48:09PM +0300, Maks Mishin wrote:
> Changing the order of actions: the input argument is checked before
> memory is allocated.
>
> The input argument `n` is of type `size_t` and cannot take
> negative values, so the comparison has been fixed.
>
> Signed-off-by: Maks
On Mon, Feb 10, 2025 at 04:43:31PM -0600, Judith Mendez wrote:
> Hi Tom,
>
> On 2/10/25 2:29 PM, Judith Mendez wrote:
> > Some K3 devices like am62x and am64x have a M4 processor in the MCU
> > voltage domain. This patch series introduces remoteproc M4 driver which
> > will be used to load firmwar
On Mon, Feb 03, 2025 at 07:10:12PM +0300, Maks Mishin wrote:
> For a variable `info.name` memory is allocated when calling the
> `fit_image_setup_sig` function and is lost when the error code is returned.
>
> The situation is similar for the `region_prop` variable,
> the memory for which is all
Hi Tom,
On 2/10/25 2:29 PM, Judith Mendez wrote:
Some K3 devices like am62x and am64x have a M4 processor in the MCU
voltage domain. This patch series introduces remoteproc M4 driver which
will be used to load firmware into and start the M4 remote core.
This series also adds support for R5F cor
On Mon, Feb 10, 2025 at 09:03:58PM +, Ilias Apalodimas wrote:
> On Mon, 10 Feb 2025 at 20:38, Tom Rini wrote:
> >
> > On Sun, 01 Dec 2024 07:42:28 -0700, Simon Glass wrote:
> >
> > > This series collects together a set of reverts and fixes to get most of
> > > the boards in the sjg lab running
On Sun, 01 Dec 2024 07:42:28 -0700, Simon Glass wrote:
> This series collects together a set of reverts and fixes to get most of
> the boards in the sjg lab running again.
>
> Unfortunately three of them have developed a failure which requires more
> diagnosis, as it may just be a hardware failur
On Mon, 10 Feb 2025 at 20:38, Tom Rini wrote:
>
> On Sun, 01 Dec 2024 07:42:28 -0700, Simon Glass wrote:
>
> > This series collects together a set of reverts and fixes to get most of
> > the boards in the sjg lab running again.
> >
> > Unfortunately three of them have developed a failure which req
Here's the latest report.
-- Forwarded message -
From:
Date: Mon, Feb 10, 2025 at 4:12 PM
Subject: New Defects reported by Coverity Scan for Das U-Boot
To:
Hi,
Please find the latest report on new defect(s) introduced to Das U-Boot
found with Coverity Scan.
3 new defect(s) in
Hi Simon,
On 2025-02-09 22:14, Simon Glass wrote:
> At present simple-bin-spi relies on the u-boot.itb file created by the
> simple-bin image. Use the template to avoid this, since Binman may
> change to process images in parallel in the future.
>
> Drop the filename to prevent another image bein
Hey all,
It's release day and so here's v2025.04-rc2. As this is the -rc2
release, I've now also opened up the -next branch and will be stricter
about what I apply myself, and what I see coming in for pull requests as
well moving forward.
Continuing on with what I started after the -rc1 release,
On 2025-02-09 22:14, Simon Glass wrote:
> Fix the indentation on the template. This is done in a separate patch
> so that it is easier to review.
>
> Signed-off-by: Simon Glass
Reviewed-by: Jonas Karlman
Regards,
Jonas
> ---
>
> (no changes since v1)
>
> arch/arm/dts/rockchip-u-boot.dtsi |
Hi Simon,
On 2025-02-09 22:14, Simon Glass wrote:
> Move the FIT description into a template so that it can (later) be used
> in multiple places in the image.
>
> Signed-off-by: Simon Glass
> ---
>
> (no changes since v1)
>
> arch/arm/dts/rockchip-u-boot.dtsi | 57 ++--
Hi Simon,
On 2025-02-09 22:14, Simon Glass wrote:
> Add an fdtmap so it is possible to look at the image with 'binman ls'.
>
> Signed-off-by: Simon Glass
> ---
>
> (no changes since v1)
>
> arch/arm/dts/rockchip-u-boot.dtsi | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/ar
On Fri, 07 Feb 2025 13:12:50 -0600, Tom Rini wrote:
> Without setting the shell flag to exit immediately when a command exists
> with a non-zero status we can have the situation where the htmldocs
> target fails with an error but the job will succeed due to infodocs
> passing and being the last bu
On Thu, 30 Jan 2025 13:36:46 +, Andre Przywara wrote:
> The env_fat_get_dev_part() function mostly returns a fixed string, set
> via some Kconfig variable. However when the first character is a colon,
> that means that the boot device number is determined at runtime, and
> patched in. This req
On Wed, 29 Jan 2025 17:44:01 -0600, Judith Mendez wrote:
> This patch series enables ESM reset configuration in board_init_f
> for am62x and am62px devices.
>
> This is necessary in order for error events to reset the system.
>
> This patches are tested using watchdog to reset the system via ESM
On Wed, 29 Jan 2025 02:34:44 -0800, Daniel Schultz wrote:
> Add the optargs variable so that we can set optional arguments while
> booting.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Mon, 03 Feb 2025 10:18:57 +0100, Michal Simek wrote:
> emul_rtc_probe() is not called from anywhere else that's why make it
> static. Issue is reported by build with W=1.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Sat, 01 Feb 2025 14:47:58 +0530, Siddharth Vadapalli wrote:
> This series re-enables MUX_MMIO at U-Boot proper on J721E and J7200
> SoCs. The commits which introduced support for Hyperflash boot on both
> of these SoCs disabled MUX_MMIO functionality at U-Boot proper, thereby
> introducing a re
On Wed, 05 Feb 2025 09:24:37 +0800, Weijie Gao wrote:
> This patch enables switch auto-detction for mt7981 as some new mt7981
> boards will use AN8855 ethernet switch.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Wed, 05 Feb 2025 10:01:06 +0800, Michael Chang wrote:
> Support phy io micro voltage setting for NPCM8XX rgmii
> interface.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Wed, 05 Feb 2025 05:30:11 +0100, Wadim Egorov wrote:
> Add bootph-all properties to I2C0 nodes to ensure the bus and EEPROM
> are accessible across all stages. This enables reading the SoM
> configuration at any point during the boot process.
>
>
Applied to u-boot/master, thanks!
--
Tom
From: Hari Nagalla
Add remoteproc specific env support for am62x device. If the
remoteproc CMD is defined, include the K3 remoteproc environment.
Also define rproc_fw_binaries which holds a list of remoteproc FW
binaries for u-boot loading of remote cores.
Signed-off-by: Hari Nagalla
Signed-off
On Thu, 06 Feb 2025 08:41:28 +0800, Weijie Gao wrote:
> The change from pinctrl to pio was missing in mt7986-u-boot.dtsi and will
> cause build failure. Now fix it.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Wed, 05 Feb 2025 13:04:26 +, Andrew Goodbody wrote:
> USB tests on ext partitions can fail with the following output
>
> test/py/tests/test_usb.py:245: in test_usb_part
> 'fstype usb %d:%d' % i, part_id
> E TypeError: not enough arguments for format string
>
> So add brackets around
On Wed, 05 Feb 2025 15:34:28 +0100, Marek Vasut wrote:
> The -V version parameter is missing in the optional list of parameters
> in help text. Add it.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Thu, 06 Feb 2025 10:18:57 +0800, Weijie Gao wrote:
> The reg-names in mt7988.dtsi have no _base suffix. Remove the suffix
> will also make it match upstream linux format.
>
>
Applied to u-boot/master, thanks!
--
Tom
Enable CMD_REMOTEPROC by default if building for K3 ARCH so
that it does not have to be defined in each board defconfig
file.
Signed-off-by: Judith Mendez
---
Changes since v4:
- Add patch
---
cmd/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 4c4ad9d
Now that remoteproc configs are enabled by default in Kconfig
files, remove these configs which are no longer needed to be
defined here in configs/.
Signed-off-by: Judith Mendez
---
Changes since v4:
- Add patch
---
configs/am62ax_evm_a53_defconfig | 4
configs/am62ax_evm_r5_defco
Add remoteproc config options to enable remoteproc drivers by
default as per what remotproc subsystem is supported on each
SoC.
Signed-off-by: Judith Mendez
---
Changes since v4:
- Add patch
---
arch/arm/mach-k3/Kconfig | 24
1 file changed, 24 insertions(+)
diff --git
If building for v7R and K3 architecture, enable SPL
remoteproc so that it does not have to be defined in each
board defconfig file.
Signed-off-by: Judith Mendez
---
Changes since v4:
- Add patch
---
common/spl/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/spl/Kconfig b/commo
From: Hari Nagalla
Add remoteproc specific env support for am64x device. If the
remoteproc CMD is defined, include the K3 remoteproc environment.
Also define rproc_fw_binaries which holds a list of remoteproc FW
binaries for u-boot loading of remote cores.
Signed-off-by: Hari Nagalla
Signed-off
From: Hari Nagalla
AM64x SoCs have two R5F clusters in the main power domain.
Extend support for R5F remote proc driver on AM64x with compatible
strings.
Signed-off-by: Hari Nagalla
Signed-off-by: Judith Mendez
Reviewed-by: Daniel Schultz
---
Changes since v4:
- No change
---
drivers/remotep
If SYS_K3_SPL_ATF is enabled, for K3 ARCH enable the
remoteproc ARM64 driver by default so that it does not
have to be defined in each board defconfig file.
Signed-off-by: Judith Mendez
---
Changes since v4:
- Add patch
---
drivers/remoteproc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff -
From: Hari Nagalla
Add remoteproc specific env support for am62px device. If the
remoteproc CMD is defined, include the K3 remoteproc environment.
Also define rproc_fw_binaries which holds a list of remoteproc FW
binaries for u-boot loading of remote cores.
Signed-off-by: Hari Nagalla
Signed-of
From: Hari Nagalla
Some K3 devices like AM64, AM62 devices have a M4 processor in MCU
voltage domain.
Add a remote proc driver to support this subsystem to be able to load
and boot the M4 core.
Signed-off-by: Hari Nagalla
[Ryan: Fix implicitly include warning]
Signed-off-by: Ryan Eatmon
[Judi
Some K3 devices like am62x and am64x have a M4 processor in the MCU
voltage domain. This patch series introduces remoteproc M4 driver which
will be used to load firmware into and start the M4 remote core.
This series also adds support for R5F cores on am64x SoCs in patch 2 and
sets up environment
Use LwIP network stack and enable wget HTTP command. The tftpput command
is not currently supported by LwIP network stack so remove it.
Signed-off-by: E Shattow
---
configs/starfive_visionfive2_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/configs/starfive_visio
Hi Tom,
On Mon, 10 Feb 2025 at 07:35, Tom Rini wrote:
>
> On Sun, Feb 09, 2025 at 01:14:29PM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sun, 9 Feb 2025 at 09:49, Tom Rini wrote:
> > >
> > > On Sun, Feb 09, 2025 at 07:27:37AM -0700, Simon Glass wrote:
> > > > Hi Jonas,
> > > >
> > > > On Fr
Hi Arnaud,
On 2/10/25 4:30 PM, Arnaud Patard wrote:
[You don't often get email from arnaud.pat...@collabora.com. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
For SPL DFU booting, define u-boot,spl-boot-order and
configure usb nodes for enabling the gadget in S
Hi Arnaud,
On 2/10/25 4:30 PM, Arnaud Patard wrote:
[You don't often get email from arnaud.pat...@collabora.com. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
To use SPL DFU, some environment variables are needed so define
CFG_EXTRA_ENV_SETTINGS for XPL builds.
socinfo_ API uses u32 type, hence let's use it everywhere
for consistency.
Signed-off-by: Evgeny Bachinin
---
arch/arm/mach-meson/board-info.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-meson/board-info.c b/arch/arm/mach-meson/board-info.c
index
b
Patch introduces:
* chip_id API - useful for various things, but used now for
device_id (did) generation as mentioned in [1] on our private board
code. Our device_id is calculated by means of permutations of
chip_id value.
* new SoCs (a1, s4, etc) are usually coming with the support of chip_i
The Amlogic Meson SoC secure monitor (TF-A) handles a call (0x8244)
to retrieve a chip_id from eFuse OTP data [1].
Previously, this sm call (0x8244) was used to retrieve just unique
SoC number [2] (a.k.a. SoC "serial" [3]), identifying particular die.
This SoC serial, stored in the eFuse,
SM_CHIP_ID_SIZE is used nowhere. Moreover, it specifies wrong
chip_id size: Amlogic chip_id v1 and v2 is always 16 bytes long.
Signed-off-by: Evgeny Bachinin
---
arch/arm/mach-meson/sm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-meson/sm.c b/arch/arm/mach-meson/sm.c
index
Marek,
In the future if you're doing a large series like this please do a cover
letter outlining what the series is trying to achieve.
Peter
On Sun, 9 Feb 2025 at 12:04, Marek Vasut
wrote:
> The init function does nothing, the bb_miiphy_init() already checks
> whether the .init callback is ass
On Mon, 10 Feb 2025 at 16:48, Arnaud Patard
wrote:
> This patch series aims at allowing to boot u-boot proper over DFU on
> roc-pc-rk3399.
> While the changes are pretty generic, I wanted to enable the device I've
> tested. I may try later to test that on my pinebook pro.
>
> What I tried was to
On Sun, Feb 09, 2025 at 07:26:38AM -0700, Simon Glass wrote:
> Hi Jonas,
>
> On Wed, 5 Feb 2025 at 15:18, Jonas Karlman wrote:
> >
> > Hi Simon,
> >
> > On 2025-02-05 02:54, Simon Glass wrote:
> > > TPL runs before VPL. The earliest updatable phase with VBE is SPL. We
> > > want to be able to upd
On Mon, Jan 27, 2025 at 10:11:06AM +0800, ZHANG Yuntian wrote:
> Hi Tom,
>
> On 2025/1/26 23:59, Tom Rini wrote:
> > On Sun, Jan 26, 2025 at 03:13:46PM +0800, ZHANG Yuntian wrote:
> > > Hi Tom,
> > >
> > > On 2025/1/25 02:23, Tom Rini wrote:
> > > > On Fri, Jan 24, 2025 at 02:05:28PM +0800, ZHANG
Hi all,
For reference this is the same issue I was attempting to fix [1] back in
April 2024. Since [2] was merged the issue has manifested as a crash
whenever the usb system is initialized on nanopi-r4s boards.
[1] https://lists.denx.de/pipermail/u-boot/2024-April/551383.html
[2]
https://source.
For SPL DFU booting, define u-boot,spl-boot-order and
configure usb nodes for enabling the gadget in SPL.
Signed-off-by: Arnaud Patard
---
arch/arm/dts/rk3399-roc-pc-u-boot.dtsi | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/arm/dts/rk3399-roc-pc-u-boot.dtsi
b
From: Gabriel Nesteruk
U-Boot currently reserves only 0x3000 bytes when copying the FDT
in `copy_fdt()`, which may not be sufficient if additional nodes
(such as FMAN firmware) are added later.
This patch introduces a new `CONFIG_FDT_EXTRA_SPACE` Kconfig option
to allow users to define the amoun
Add needed configuration to enable SPL DFU.
Signed-off-by: Arnaud Patard
---
configs/roc-pc-rk3399_defconfig | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/configs/roc-pc-rk3399_defconfig b/configs/roc-pc-rk3399_defconfig
index 0ef86748778..a02deefbaf8 100644
To use SPL DFU, some environment variables are needed so define
CFG_EXTRA_ENV_SETTINGS for XPL builds.
Signed-off-by: Arnaud Patard
---
include/configs/rk3399_common.h | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/include/configs/rk3399_common.h b/includ
Define the device node used when booting over usb, allowing to
use 'same-as-spl' boot entry.
Signed-off-by: Arnaud Patard
---
arch/arm/mach-rockchip/rk3399/rk3399.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-rockchip/rk3399/rk3399.c
b/arch/arm/mach-rockchip/rk3399/rk3399.
Make it possible to boot over gadget.
Signed-off-by: Arnaud Patard
---
arch/arm/mach-rockchip/spl-boot-order.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-rockchip/spl-boot-order.c
b/arch/arm/mach-rockchip/spl-boot-order.c
index 3dce9b30898..7cc410d0ae7 100644
--- a/arc
When building TPL with DWC3 generic enabled, the following error is
occuring:
aarch64-linux-gnu-ld.bfd: drivers/usb/dwc3/dwc3-generic.o: in function
`dwc3_glue_bind_common':
.../drivers/usb/dwc3/dwc3-generic.c:527: undefined reference to
`usb_get_dr_mode'
.../drivers/usb/dwc3/dwc3-generic.c:527:(
This patch series aims at allowing to boot u-boot proper over DFU on
roc-pc-rk3399.
While the changes are pretty generic, I wanted to enable the device I've
tested. I may try later to test that on my pinebook pro.
What I tried was to boot u-boot TPL+SPL with the device in maskrom mode,
downloaded
On Fri, Feb 07, 2025 at 09:53:01AM -0800, Jonathan Bar Or wrote:
> Thank you.
>
> So, I'm attaching my findings in a md file - see attachment.
> All of those could be avoided by using safe math, such as
> __builtin_mul_overflow and __builtin_add_overflow, which are used in some
> modules in Das-U
forgot to add a link (b4 should pick it up though from headers)
https://lore.kernel.org/u-boot/20250210-b4-clk-stub-v4-0-f1e7d845f...@linaro.org
---
Caleb Connolly (2):
power: regulator: add additional supported LDOs for pm8150l
pinctrl: qcom: sm8250: fix pin count
drivers/pinctrl
Add the other LDOs that our rpmh driver can currently support. Some of
these are used on the RB5 to power the sdcard.
Signed-off-by: Caleb Connolly
---
drivers/power/regulator/qcom-rpmh-regulator.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/power/regulator/qcom-rpmh-regul
The pin count wasn't updated when the special pins were added, as a
result it was never possible to configure the special pins on SM8250
boards.
Fix the pin count and allow the special pins to be configured. This
fixes sdcard support on the RB5.
Fixes: 58fa52042471 ("pinctr: qcom: sm8250: add spe
Enable the missing regulators and fix pinctrl so that the sdcard works
on the RB5 board and presumably other devices.
This depends on the clk-stub patches since the MMC block itself
references the rpmh vote-clock which we intend to stub.
---
Caleb Connolly (2):
power: regulator: add additio
From: Julius Lehmann
Add support for sm8150 clock controller to clk stub driver.
Signed-off-by: Julius Lehmann
---
drivers/clk/clk-stub.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/clk-stub.c b/drivers/clk/clk-stub.c
index
ea817031fa6c0cc1ea21000273b5651be5d05e65..5fbbb07
Add a stub clock driver which can be used to bind clock controllers
which aren't required for the platform to boot, but which are needed for
U-Boot drivers to work.
In addition, add a NOP parent driver to allow for binding the parent
nodes of the clock.
Initially this driver supports a Qualcomm p
1 - 100 of 166 matches
Mail list logo
