This is required for compiling.
Signed-off-by: John Watts
---
drivers/spi/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 025c81adc9..f1c6a838ae 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -417,6 +417,7 @@ config
This code uses dev_err which is defined in dm/device_compat.h
Signed-off-by: John Watts
---
drivers/spi/ca_sflash.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/ca_sflash.c b/drivers/spi/ca_sflash.c
index 38bddd3861..78e442cac9 100644
--- a/drivers/spi/ca_sflash.c
+++
This created a conflict when linking.
Signed-off-by: John Watts
---
drivers/spi/mtk_spim.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/spi/mtk_spim.c b/drivers/spi/mtk_spim.c
index 90f4c3cecb..2979487fff 100644
--- a/drivers/spi/mtk_spim.c
+++ b/drivers/spi/mtk_spim.c
@@ -18,7
These dependencies are required for building the drivers and create
compile errors if not enabled.
Signed-off-by: John Watts
---
drivers/spi/Kconfig | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 612434633b..025c81adc9
I'm doing some SPI work so I tried to compile all the drivers on my
sunxi board to try and avoid some regressions. This failed, so here are
some fixes for this.
Signed-off-by: John Watts
---
John Watts (4):
spi: Kconfig: Add some required arch depends for drivers
spi: mtk_spim:
Hi Marek,
On Fri, Apr 26, 2024 at 5:49 PM Marek Vasut wrote:
>
> [...]
>
> > diff --git a/include/mmc.h b/include/mmc.h
> > index 4b8327f1f93b..7243bd761202 100644
> > --- a/include/mmc.h
> > +++ b/include/mmc.h
> > @@ -381,6 +381,21 @@ enum mmc_voltage {
> > #define MMC_TIMING_MMC_HS200
[...]
diff --git a/include/mmc.h b/include/mmc.h
index 4b8327f1f93b..7243bd761202 100644
--- a/include/mmc.h
+++ b/include/mmc.h
@@ -381,6 +381,21 @@ enum mmc_voltage {
#define MMC_TIMING_MMC_HS200 9
#define MMC_TIMING_MMC_HS400 10
+/* emmc hardware partition values */
+enum
eMMC devices have hardware partitions such as user, boot0, and boot1.
Add an enumerated type defining the hardware partition values and an
array of names describing them by name that can be used throughout
U-Boot.
Allow these names to be displayed when reading and used when setting
the mmc
On Fri, Apr 26, 2024 at 12:26 PM Dragan Simic wrote:
>
> Hello Tim,
>
> Please see my comments below.
>
> On 2024-04-26 18:55, Tim Harvey wrote:
> > To aid in understanding what emmc hardware partition is being
> > used to boot on power-up, display the hardware partition name in the
> > SPL.
> >
On Fri, 26 Apr 2024 at 17:13, Heinrich Schuchardt
wrote:
>
> We should not pass GUIDs by value as this requires copying.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> include/efi_loader.h | 2 +-
> lib/efi_loader/efi_helper.c | 4 ++--
> lib/efi_loader/efi_load_initrd.c | 2 +-
On 4/26/24 19:34, Tim Harvey wrote:
On Fri, Apr 26, 2024 at 7:45 AM Heinrich Schuchardt wrote:
On 26.04.24 06:03, Marek Vasut wrote:
On 4/26/24 2:16 AM, Tim Harvey wrote:
diff --git a/drivers/crypto/fsl/Makefile b/drivers/crypto/fsl/Makefile
index 7a2543e16cc..4fbce519a0b 100644
---
Hello Tim,
Please see my comments below.
On 2024-04-26 18:55, Tim Harvey wrote:
To aid in understanding what emmc hardware partition is being
used to boot on power-up, display the hardware partition name in the
SPL.
Signed-off-by: Tim Harvey
---
board/gateworks/venice/spl.c | 16
On 4/26/24 7:36 PM, Tim Harvey wrote:
On Fri, Apr 26, 2024 at 10:25 AM Marek Vasut wrote:
On 4/26/24 7:12 PM, Tim Harvey wrote:
eMMC devices have hardware partitions such as user, boot0, and boot1.
Allow these names to be displayed when reading the mmc PARTITION_CONFIG
field via 'mmc
On Fri, Apr 26, 2024 at 10:25 AM Marek Vasut wrote:
>
> On 4/26/24 7:12 PM, Tim Harvey wrote:
> > eMMC devices have hardware partitions such as user, boot0, and boot1.
> > Allow these names to be displayed when reading the mmc PARTITION_CONFIG
> > field via 'mmc partconf'. Additionally allow a
On Fri, Apr 26, 2024 at 7:45 AM Heinrich Schuchardt wrote:
>
> On 26.04.24 06:03, Marek Vasut wrote:
> > On 4/26/24 2:16 AM, Tim Harvey wrote:
> >
> >>> diff --git a/drivers/crypto/fsl/Makefile b/drivers/crypto/fsl/Makefile
> >>> index 7a2543e16cc..4fbce519a0b 100644
> >>> ---
On 4/26/24 4:39 PM, Heinrich Schuchardt wrote:
On 26.04.24 06:03, Marek Vasut wrote:
On 4/26/24 2:16 AM, Tim Harvey wrote:
diff --git a/drivers/crypto/fsl/Makefile b/drivers/crypto/fsl/Makefile
index 7a2543e16cc..4fbce519a0b 100644
--- a/drivers/crypto/fsl/Makefile
+++
On 4/26/24 7:12 PM, Tim Harvey wrote:
eMMC devices have hardware partitions such as user, boot0, and boot1.
Allow these names to be displayed when reading the mmc PARTITION_CONFIG
field via 'mmc partconf'. Additionally allow a name to be specified when
setting the PARTITION_CONFIG.
Before:
eMMC devices have hardware partitions such as user, boot0, and boot1.
Allow these names to be displayed when reading the mmc PARTITION_CONFIG
field via 'mmc partconf'. Additionally allow a name to be specified when
setting the PARTITION_CONFIG.
Before:
u-boot=> mmc partconf 2 1 1 0 && mmc
On 4/26/24 6:00 PM, Tom Rini wrote:
On Fri, Apr 26, 2024 at 08:56:29AM -0700, Tim Harvey wrote:
On Fri, Apr 26, 2024 at 8:51 AM Tom Rini wrote:
On Fri, Apr 26, 2024 at 08:30:23AM -0700, Tim Harvey wrote:
On Thu, Apr 25, 2024 at 4:07 PM Marek Vasut wrote:
Update documentation and use
To aid in understanding what emmc hardware partition is being
used to boot on power-up, display the hardware partition name in the
SPL.
Signed-off-by: Tim Harvey
---
board/gateworks/venice/spl.c | 16
1 file changed, 16 insertions(+)
diff --git a/board/gateworks/venice/spl.c
On Fri, Apr 26, 2024 at 08:56:29AM -0700, Tim Harvey wrote:
> On Fri, Apr 26, 2024 at 8:51 AM Tom Rini wrote:
> >
> > On Fri, Apr 26, 2024 at 08:30:23AM -0700, Tim Harvey wrote:
> > > On Thu, Apr 25, 2024 at 4:07 PM Marek Vasut wrote:
> > > >
> > > > Update documentation and use nxp_imx8mcst
On 4/26/24 5:14 PM, Tim Harvey wrote:
On Thu, Apr 25, 2024 at 9:07 PM Marek Vasut wrote:
On 4/26/24 2:14 AM, Tim Harvey wrote:
eMMC devices have hardware partitions such as user, boot0, and boot1.
Allow these names to be displayed when reading the mmc PARTITION_CONFIG
field via 'mmc
On Fri, Apr 26, 2024 at 8:51 AM Tom Rini wrote:
>
> On Fri, Apr 26, 2024 at 08:30:23AM -0700, Tim Harvey wrote:
> > On Thu, Apr 25, 2024 at 4:07 PM Marek Vasut wrote:
> > >
> > > Update documentation and use nxp_imx8mcst binman etype for signing
> > > of flash.bin instead of previous horrible
Hi Dario
On Fri, Apr 26, 2024 at 5:52 PM Tom Rini wrote:
>
> On Fri, Apr 26, 2024 at 07:18:18AM +0200, Heiko Schocher wrote:
> > Hello Tom,
> >
> > On 11.04.24 08:09, Michael Nazzareno Trimarchi wrote:
> > > Hi
> > >
> > > On Thu, Apr 11, 2024 at 7:06 AM John Watts wrote:
> > > >
> > > > UBI
On Fri, Apr 26, 2024 at 07:18:18AM +0200, Heiko Schocher wrote:
> Hello Tom,
>
> On 11.04.24 08:09, Michael Nazzareno Trimarchi wrote:
> > Hi
> >
> > On Thu, Apr 11, 2024 at 7:06 AM John Watts wrote:
> > >
> > > UBI required MTD to build correctly, add it as a Kconfig dependency.
> > >
> > >
On Fri, Apr 26, 2024 at 07:38:30PM +0900, Jaehoon Chung wrote:
> Dear Tom,
>
> Please pull u-boot-mmc master into u-boot master branch.
> If there is any problem, let me know, plz
>
> Best Regards,
> Jaehoon Chung
>
> CI: https://source.denx.de/u-boot/custodians/u-boot-mmc/-/pipelines/20547
>
denx.de/u-boot/custodians/u-boot-fsl-qoriq (2024-04-23
> 17:53:06 -0600)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-rockchip.git
> tags/u-boot-rockchip-20240426
>
> for you to fetch changes up to f6114fb871108eb2bad7
On Fri, Apr 26, 2024 at 10:06:53AM +0300, Ilias Apalodimas wrote:
> Hi Tom
>
> The following changes since commit d097f9e1299a3bdb7de468f0d9bbc63932f461cd:
>
> Merge tag 'fsl-qoriq-2024-4-24' of
> https://source.denx.de/u-boot/custodians/u-boot-fsl-qoriq (2024-04-23
> 17:53:06 -0600)
>
>
On Fri, Apr 26, 2024 at 08:30:23AM -0700, Tim Harvey wrote:
> On Thu, Apr 25, 2024 at 4:07 PM Marek Vasut wrote:
> >
> > Update documentation and use nxp_imx8mcst binman etype for signing
> > of flash.bin instead of previous horrible shell scripting.
>
> Hi Marek,
>
> To be completely fair we
Hi Heinrich
On Fri, 26 Apr 2024 at 17:53, Heinrich Schuchardt
wrote:
>
> On 26.04.24 16:30, Ilias Apalodimas wrote:
> > Hi Heinrich,
> >
> > On Fri, 26 Apr 2024 at 17:13, Heinrich Schuchardt
> > wrote:
> >>
> >> Provide a function to append a device_path to a list of device paths
> >> that is
s/ENTENDED/EXTENDED
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/am62a7_init.c | 2 +-
arch/arm/mach-k3/include/mach/am62a_hardware.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-k3/am62a7_init.c b/arch/arm/mach-k3/am62a7_init.c
index
From: Chris Morgan
For root partitions, the UUID should still be random but the partition
type uuid should either be b921b045-1df0-41c3-af44-4c6f280d3fae for
aarch64 or 69dad710-2ce4-4e3c-b16c-21a1d49abed3 for aarch32. Correct
the attribute so it is the partition type that is hard coded and not
On 26.04.2024 17:32, Heinrich Schuchardt wrote:
On 26.04.24 11:11, Maxim Moskalets wrote:
Loading and running the ELF image is the responsibility of the
library and should not be associated with the command line interface.
It is also required to run ELF images from FIT with the bootm command
On Thu, Apr 25, 2024 at 4:07 PM Marek Vasut wrote:
>
> Update documentation and use nxp_imx8mcst binman etype for signing
> of flash.bin instead of previous horrible shell scripting.
Hi Marek,
To be completely fair we are just replacing a shell script and
template file with a python script
On 26.04.24 16:52, Caleb Connolly wrote:
Hi Heinrich,
On 26/04/2024 16:13, Heinrich Schuchardt wrote:
Move distro_efi_get_fdt_name() to a separate C module
and rename it to efi_get_distro_fdt_name().
Signed-off-by: Heinrich Schuchardt
---
boot/bootmeth_efi.c | 60
On Thu, Apr 25, 2024 at 9:07 PM Marek Vasut wrote:
>
> On 4/26/24 2:14 AM, Tim Harvey wrote:
> > eMMC devices have hardware partitions such as user, boot0, and boot1.
> > Allow these names to be displayed when reading the mmc PARTITION_CONFIG
> > field via 'mmc partconf'. Additionally allow a
On Thu, Apr 25, 2024 at 6:37 PM Fabio Estevam wrote:
>
> On Thu, Apr 25, 2024 at 10:35 PM Fabio Estevam wrote:
>
> > This is a nice improvement:
> >
> > Reviewed-by: Fabio Estevam
>
> There is a typo in the Subject: "partition"
Hi Fabio,
Thanks - I will fix this in v2.
Best Regards,
Tim
On 26.04.24 16:30, Ilias Apalodimas wrote:
Hi Heinrich,
On Fri, 26 Apr 2024 at 17:13, Heinrich Schuchardt
wrote:
Provide a function to append a device_path to a list of device paths
that is separated by final end nodes.
Signed-off-by: Heinrich Schuchardt
---
include/efi_loader.h
Hi Heinrich,
On 26/04/2024 16:13, Heinrich Schuchardt wrote:
Move distro_efi_get_fdt_name() to a separate C module
and rename it to efi_get_distro_fdt_name().
Signed-off-by: Heinrich Schuchardt
---
boot/bootmeth_efi.c | 60 ++---
include/efi_loader.h |
On 26.04.24 06:03, Marek Vasut wrote:
On 4/26/24 2:16 AM, Tim Harvey wrote:
diff --git a/drivers/crypto/fsl/Makefile b/drivers/crypto/fsl/Makefile
index 7a2543e16cc..4fbce519a0b 100644
--- a/drivers/crypto/fsl/Makefile
+++ b/drivers/crypto/fsl/Makefile
@@ -6,6 +6,6 @@ obj-y += sec.o
On 26.04.24 11:11, Maxim Moskalets wrote:
Loading and running the ELF image is the responsibility of the
library and should not be associated with the command line interface.
It is also required to run ELF images from FIT with the bootm command
so as not to depend on the command line interface.
Hi Heinrich,
On Fri, 26 Apr 2024 at 17:13, Heinrich Schuchardt
wrote:
>
> Provide a function to append a device_path to a list of device paths
> that is separated by final end nodes.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> include/efi_loader.h | 3 +++
>
Hi everyone,
The latest version of u-boot seems to have some serious issues with USB
drives. More than half of my disks do not work. I have traced the issue
down to the following:
1. During a transfer, the XHCI TRB ring buffer reports back an error of
type 4. (USB Transaction Error)
2. The
Migrate sandbox over to generating it's capsule update image GUIDs
dynamically rather than using a set of hardcoded ones.
Signed-off-by: Caleb Connolly
---
arch/Kconfig| 1 +
board/sandbox/sandbox.c | 28 +++-
2 files changed, 16 insertions(+), 13
Document how platforms can generate GUIDs at runtime rather than
maintaining a list of GUIDs per-board.
Signed-off-by: Caleb Connolly
---
doc/develop/uefi/uefi.rst | 35 +++
1 file changed, 35 insertions(+)
diff --git a/doc/develop/uefi/uefi.rst
Introduce a new helper efi_capsule_update_info_gen_ids() which takes
several strings to identify the currently running board as well as a
platform specific salt UUID and uses this data to populate the capsule
update fw images image_type_id field. This allows for determinstic UUIDs
to be used that
Add support for generate version 5 UUIDs, these are determistic and work
by hashing a "namespace" UUID together with some unique data. One intended
usecase is to allow for dynamically generate payload UUIDs for UEFI
capsule updates, so that supported boards can have their own UUIDs
without needing
As more boards adopt support for the EFI CapsuleUpdate mechanism, there
is a growing issue of being able to target updates to them properly. The
current mechanism of hardcoding UUIDs for each board at compile time is
unsustainable, and maintaining lists of GUIDs is similarly cumbersome.
In this
If no device-tree is specified, try to load a device-tree from the boot
device use the $fdtfile concatenated to either of the paths '/dtb/', '/',
'/dtb/current/'.
Signed-off-by: Heinrich Schuchardt
---
include/efi_loader.h | 1 +
lib/efi_loader/efi_bootmgr.c | 13 +--
Up to now efi_dp_from_lo() only could return the initrd or fdt device-path.
Allow returning the binary device-path to.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_device_path.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git
Move distro_efi_get_fdt_name() to a separate C module
and rename it to efi_get_distro_fdt_name().
Signed-off-by: Heinrich Schuchardt
---
boot/bootmeth_efi.c | 60 ++---
include/efi_loader.h | 2 ++
lib/efi_loader/Makefile | 1 +
lib/efi_loader/efi_fdt.c |
We allow to specify the triple of binary, initrd, and device-tree in boot
options.
Add the code to actually load the specified device-tree.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_bootmgr.c | 57 +++-
1 file changed, 56 insertions(+), 1
The image is not unloaded if a security violation occurs.
If efi_set_load_options() fails, we do not free the memory allocated for
the optional data. We do not unload the image.
* Unload the image if a security violation occurs.
* Free load_options if efi_set_load_options() fails.
* Unload the
We can reuse this function to load the device-tree.
Signed-off-by: Heinrich Schuchardt
---
include/efi_loader.h | 4
lib/efi_loader/efi_bootmgr.c | 17 +
lib/efi_loader/efi_boottime.c | 1 -
3 files changed, 17 insertions(+), 5 deletions(-)
diff --git
If the UEFI boot manager fails there is no point in installing the
device-tree as a configuration table.
Unload image if device-tree cannot be installed.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_bootmgr.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
EFI_CALL() invokes __efi_entry_check() which executes set_gd(efi_gd).
There is no need to execute set_gd(efi_gd) again via efi_restore_gd().
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Ilias Apalodimas
---
cmd/bootefi.c | 1 -
cmd/efidebug.c | 2 --
We already support creating a load option where the device-path
field contains the concatenation of the binary device-path and
optionally the device path of the initrd which we expose via the
EFI_LOAD_FILE2_PROTOCOL.
Allow to append another device-path pointing to the device-tree
identified by
If efi_bootmgr_load() fails, there is no point in trying to start an image
that has not been loaded.
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Ilias Apalodimas
---
cmd/efidebug.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/cmd/efidebug.c b/cmd/efidebug.c
index
We already support creating a load option where the device-path
field contains the concatenation of the binary device-path and
optionally the device path of the initrd which we expose via the
EFI_LOAD_FILE2_PROTOCOL.
Allow to append another device-path pointing to the device-tree
identified by
Provide a function to append a device_path to a list of device paths
that is separated by final end nodes.
Signed-off-by: Heinrich Schuchardt
---
include/efi_loader.h | 3 +++
lib/efi_loader/efi_device_path.c | 31 +++
2 files changed, 34 insertions(+)
As we now have efi_dp_merge() we can use this function to replace
efi_dp_concat(,,true) and remove the last parameter from efi_dp_concat()
otherwise.
Signed-off-by: Heinrich Schuchardt
---
cmd/eficonfig.c| 22 +-
cmd/efidebug.c
We should not pass GUIDs by value as this requires copying.
Signed-off-by: Heinrich Schuchardt
---
include/efi_loader.h | 2 +-
lib/efi_loader/efi_helper.c | 4 ++--
lib/efi_loader/efi_load_initrd.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git
In U-Boot EFI boot options can already specify both an EFI binary and
an initrd. With this series we can additionally define the matching
device-tree to be loaded in the boot option.
With the last patch the boot manager will fall back the device-tree
specified by $fdtfile in directories '/dtb/',
Code is pretty much supports only DT properties and completely ignore
information coming from sysinfo driver.
Code is calling smbios_add_prop() which calls with
smbios_add_prop_si(SYSINFO_ID_NONE). But SYSINFO_ID_NONE can't
differentiate different entries from sysinfo driver.
That's why introduce
It is good to be aware what information is shared via smbios interface
that's why enable it by default.
Signed-off-by: Michal Simek
---
configs/xilinx_versal_net_virt_defconfig | 1 +
configs/xilinx_versal_virt_defconfig | 1 +
configs/xilinx_zynqmp_kria_defconfig | 1 +
Currently code looks like that it sysinfo drivers are supported but
actually none checking that system is detected. That's why call
sysinfo_detect() to make sure that priv->detected in sysinfo uclass is
setup hence information from driver can be passed to smbios.
Signed-off-by: Michal Simek
---
Hi,
currently only DT way is supported and it is added directly to lib/smbios.c
but I think DT and env is only one way how information can be found that's
why this series is improving handling with using sysinfo driver which can
be platform specific.
At the end of day DT should be taken from
On 4/26/24 8:27 AM, Jaehoon Chung wrote:
Dear Marek,
-Original Message-
From: Marek Vasut
Sent: Wednesday, April 24, 2024 8:18 AM
To: u-boot@lists.denx.de; Jaehoon Chung
Cc: Peng Fan ; Simon Glass
Subject: Re: [PATCH v4] mmc: Poll CD in case cyclic framework is enabled
On 3/16/24
On 4/26/24 9:49 AM, Patrice CHOTARD wrote:
On 4/22/24 01:16, Marek Vasut wrote:
Add another mux option for ADC pins, this is used on
DH electronics STM32MP13xx DHCOR DHSBC board.
Signed-off-by: Marek Vasut
---
Cc: Patrice Chotard
Cc: Patrick Delaunay
Cc: u-b...@dh-electronics.com
Cc:
On 26.04.2024 11:55, neil.armstr...@linaro.org wrote:
> On 26/04/2024 10:40, Arseniy Krasnov wrote:
>> Hi,
>>
>> On 26.04.2024 11:21, Neil Armstrong wrote:
>>> Hi,
>>>
>>> On 25/04/2024 19:50, Arseniy Krasnov wrote:
nfc: Synced from Linux commit 7ca2ef33179f ("Linux 6.6-rc1")
Dear Tom,
Please pull u-boot-mmc master into u-boot master branch.
If there is any problem, let me know, plz
Best Regards,
Jaehoon Chung
CI: https://source.denx.de/u-boot/custodians/u-boot-mmc/-/pipelines/20547
The following changes since commit d097f9e1299a3bdb7de468f0d9bbc63932f461cd:
On Fri, 26 Apr 2024 at 13:09, Heinrich Schuchardt
wrote:
>
> Use Sphinx style for return value.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> lib/efi_loader/efi_device_path.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/efi_loader/efi_device_path.c
>
Use Sphinx style for return value.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_device_path.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_loader/efi_device_path.c b/lib/efi_loader/efi_device_path.c
index 46aa59b9e40..aec224d8466 100644
---
Hi Kever,
On 4/26/24 09:41, Kever Yang wrote:
Hi Quentin,
On 2024/4/25 18:46, Quentin Schulz wrote:
From: Quentin Schulz
Allow RK3568 and RK3588 based boards to get the RAM bank configuration
from the ROCKCHIP_TPL stage instead of the current logic. This fixes
both an issue where 256MB of
/custodians/u-boot-rockchip.git
tags/u-boot-rockchip-20240426
for you to fetch changes up to f6114fb871108eb2bad7393191c9983f0b125dc1:
rockchip: rk356x: use DRAM banks from ATAGS (2024-04-26 15:47:06 +0800)
Christopher Obbard (4
Loading and running the ELF image is the responsibility of the
library and should not be associated with the command line interface.
It is also required to run ELF images from FIT with the bootm command
so as not to depend on the command line interface.
Signed-off-by: Maxim Moskalets
---
On 26/04/2024 10:40, Arseniy Krasnov wrote:
Hi,
On 26.04.2024 11:21, Neil Armstrong wrote:
Hi,
On 25/04/2024 19:50, Arseniy Krasnov wrote:
nfc: Synced from Linux commit 7ca2ef33179f ("Linux 6.6-rc1")
nand_all_pins: Synced from Linux commit be18d53c32b2 ("Linux 6.7-rc3")
No need to sync DT
Hi,
On 26.04.2024 11:21, Neil Armstrong wrote:
> Hi,
>
> On 25/04/2024 19:50, Arseniy Krasnov wrote:
>> nfc: Synced from Linux commit 7ca2ef33179f ("Linux 6.6-rc1")
>> nand_all_pins: Synced from Linux commit be18d53c32b2 ("Linux 6.7-rc3")
>
> No need to sync DT anymore, this is handled by
Hi,
On 25/04/2024 19:50, Arseniy Krasnov wrote:
nfc: Synced from Linux commit 7ca2ef33179f ("Linux 6.6-rc1")
nand_all_pins: Synced from Linux commit be18d53c32b2 ("Linux 6.7-rc3")
No need to sync DT anymore, this is handled by OF_UPSTREAM and for next release
it's already aligned with v6.9
On 4/22/24 01:17, Marek Vasut wrote:
> This stm32mp135f-dhcor-dhsbc board is a stack of DHCOR SoM based on
> STM32MP135F SoC (900MHz / crypto capabilities) populated on DHSBC
> carrier board.
>
> The SoM contains the following peripherals:
> - STPMIC (power delivery)
> - 512MB DDR3L memory
> -
On Fri, Apr 26, 2024 at 10:02:24AM +0200, Matthias Schiffer wrote:
> With netconsole, any log message can result in an eth_init(), possibly
> causing an reentrant call into eth_init() if a driver's ops print
> anything:
>
> eth_init() -> driver.start() -> printf() -> netconsole -> eth_init()
On 4/22/24 01:17, Marek Vasut wrote:
> Add another mux option for UART7 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:17, Marek Vasut wrote:
> Add another mux option for UART4 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:17, Marek Vasut wrote:
> Add another mux option for USART2 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:17, Marek Vasut wrote:
> Add another mux option for USART1 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:17, Marek Vasut wrote:
> Add another mux option for SPI3 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for SPI2 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
Buffers must not have an unclean cache before being used for DMA - a
pending write-back may corrupt the next dev-to-mem transfer otherwise.
This was consistently noticeable during long TFTP transfers, when an ARP
request is answered by U-Boot in the middle of the transfer:
As U-Boot's
net.h is needed for PKTBUFSRX. Without this definition, the driver will
always use 4 RX buffers, causing am65-cpsw-nuss initialization to fail
when a higher number of buffers is requested.
Signed-off-by: Matthias Schiffer
---
drivers/dma/ti/k3-udma.c | 1 +
1 file changed, 1 insertion(+)
diff
The RX DMA channel has been requested at this point already, so it must
be freed.
Signed-off-by: Matthias Schiffer
---
drivers/net/ti/am65-cpsw-nuss.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ti/am65-cpsw-nuss.c b/drivers/net/ti/am65-cpsw-nuss.c
index
The eth-uclass state machine doesn't prevent imbalanced start()/stop()
calls - to the contrary, it even provides eth_init_state_only() and
eth_halt_state_only() functions that change the state without any calls
into the driver. This means that the driver must be robust against
duplicate start()
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for SDMMC2 D4..D7 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
With netconsole, any log message can result in an eth_init(), possibly
causing an reentrant call into eth_init() if a driver's ops print
anything:
eth_init() -> driver.start() -> printf() -> netconsole -> eth_init()
eth_halt() -> driver.stop() -> printf() -> netconsole -> eth_init()
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for SAI1 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for QSPI pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for PWM13 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for PWM5 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for MCAN2 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for MCAN1 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
On 4/22/24 01:16, Marek Vasut wrote:
> Add another mux option for I2C5 pins, this is used on
> DH electronics STM32MP13xx DHCOR DHSBC board.
>
> Signed-off-by: Marek Vasut
> ---
> Cc: Patrice Chotard
> Cc: Patrick Delaunay
> Cc: u-b...@dh-electronics.com
> Cc:
1 - 100 of 124 matches
Mail list logo
