Hi Heinrich,
On 6/8/24 6:12 AM, Heinrich Schuchardt wrote:
%s/prbing/probing/
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Quentin Schulz
Thanks!
Quentin
On Sat, Apr 20, 2024 at 12:03 AM Marek Vasut wrote:
>
> Make sure the OS would not get any spurious IWDG pretimeout IRQ
> right after the system wakes up. This may happen in case the SoC
> got woken up by another source than the IWDG pretimeout and the
> pretimeout IRQ arrived immediately afterwar
On Sat, Jun 8, 2024 at 6:13 AM Heinrich Schuchardt
wrote:
>
> %s/prbing/probing/
>
> Signed-off-by: Heinrich Schuchardt
> ---
> drivers/core/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/core/Kconfig b/drivers/core/Kconfig
> index 1081d61fcf0..754649f09
On Sat, 8 Jun 2024 at 01:39, Jonathan Humphreys wrote:
>
> Define the firmware components updatable via EFI capsule update, including
> defining capsule GUIDs for the various firmware components for the
> SK-TDA4VM.
>
> Signed-off-by: Jonathan Humphreys
> ---
> board/ti/j721e/evm.c| 40 +
On Sat, 8 Jun 2024 at 01:39, Jonathan Humphreys wrote:
>
> Define the firmware components updatable via EFI capsule update, including
> defining capsule GUIDs for the various firmware components for the
> BeaglePlay.
>
> Note this involved creating BeaglePlay's own beagleplay.h board header file
>
On Thu, Jun 6, 2024 at 2:24 PM Mattijs Korpershoek
wrote:
>
> When calling android_image_get_dtb_by_index() using boot image v3+,
> we should also pass the vendor_boot ramdisk address.
>
> Use get_avendor_bootimg_addr() to do so.
>
> Note: on boot image v2, this is harmless since get_avendor_booti
On Sat, 8 Jun 2024 at 01:39, Jonathan Humphreys wrote:
>
> Define the firmware components updatable via EFI capsule update, including
> defining capsule GUIDs for the various firmware components for the AM69
> SK.
>
> TODO: possibly make the struct's sk specific.
> TODO: add doc commit (and make s
On Sat, 8 Jun 2024 at 01:39, Jonathan Humphreys wrote:
>
> Define the firmware components updatable via EFI capsule update, including
> defining capsule GUIDs for the various firmware components for the AM62x
> SK.
>
> Signed-off-by: Jonathan Humphreys
> ---
> board/ti/am62x/evm.c| 34 ++
On Sat, 8 Jun 2024 at 01:39, Jonathan Humphreys wrote:
>
> Define the firmware components updatable via EFI capsule update, including
> defining capsule GUIDs for the various firmware components for the AM62px
> SK.
>
> Signed-off-by: Jonathan Humphreys
> ---
> board/ti/am62px/evm.c| 34
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/', '
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 the
Allow appending a device-path to a device-path that contains an end node
as separator. We need this feature for creating boot options specifying
kernel, initrd, and dtb.
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Ilias Apalodimas
---
v3:
no change
v2:
update efi_dp_concat()
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 the
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
Reviewed-by: Ilias Apalodimas
---
v3:
Use calloc() instead of malloc().
Add missing '@' in load_fdt_from
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
Reviewed-by: Ilias Apalodimas
---
v3:
No change
v2:
rebase patch
---
boot/bootmeth_efi.c | 60 ++---
include/efi_
For finding distro supplied device-trees we need to know from which device
we are booting. This can be identified via the device-path of the binary.
Up to now efi_dp_from_lo() only could return the initrd or fdt device-path.
Allow returning the binary device-path, too.
Signed-off-by: Heinrich Sch
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
Reviewed-by: Ilias Apalodimas
---
v3:
no change
v2:
no change
---
include/efi_loa
We can reuse this function to load the device-tree.
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Ilias Apalodimas
---
v3:
No change
v2:
Move unrelated changes to different patch.
---
include/efi_loader.h | 4
lib/efi_loader/efi_boottime.c | 1 -
2 files changed,
As we now also store device-tree device-paths in load options rename
struct efi_initrd_dp to efi_lo_dp_prefix.
Signed-off-by: Heinrich Schuchardt
---
v3:
new patch
---
cmd/eficonfig.c | 4 ++--
cmd/efidebug.c | 4 ++--
include/efi_load_initrd.h
Hi Mattijs,
On Thu, Jun 6, 2024 at 2:24 PM Mattijs Korpershoek
wrote:
>
> When reading a boot image header, we may need to retrieve the header
> version.
>
> Add a helper function for it.
>
> Signed-off-by: Mattijs Korpershoek
> ---
> boot/image-android.c | 7 ++-
> include/image.h | 7
Hi Mattijs,
On Thu, Jun 6, 2024 at 2:24 PM Mattijs Korpershoek
wrote:
>
> Some bootflows might be able to only boot from MMC devices.
>
> Add a helper function these bootflows can use.
>
> Signed-off-by: Mattijs Korpershoek
> ---
> boot/bootflow.c| 12
> include/bootflow.h | 9
On Mon, 10 Jun 2024 at 12:11, Heinrich Schuchardt
wrote:
>
> As we now also store device-tree device-paths in load options rename
> struct efi_initrd_dp to efi_lo_dp_prefix.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v3:
> new patch
> ---
> cmd/eficonfig.c | 4 ++--
On Fri, 7 Jun 2024 at 21:53, Sughosh Ganu wrote:
>
> The lmb_is_reserved() API is not used. There is another API,
> lmb_is_reserved_flags() which can be used to check if a particular
> memory region is reserved. Remove the unused API.
>
> Signed-off-by: Sughosh Ganu
> ---
> include/lmb.h | 11 --
On Fri, 7 Jun 2024 at 21:53, Sughosh Ganu wrote:
>
> The __lmb_alloc_base() function is only called from within the lmb
> module. Moreover, the lmb_alloc() and lmb_alloc_base() API's are good
> enough for the allocation API calls. Make the __lmb_alloc_base()
> function static.
>
> Signed-off-by: S
On Mon 10 Jun 2024 at 11:43, Mattijs Korpershoek
wrote:
> When decompressing, it's possible that the algorithm only performs
> a partial decompression.
> This usually happens when CONFIG_SYS_BOOTM_LEN is too small for
> the uncompressed image.
>
> When that happens, image_decomp() returns an
On Mon 10 Jun 2024 at 11:45, Mattijs Korpershoek
wrote:
> commit dfeb4f0d7935 ("cmd: bcb: extend BCB C API to allow read/write the
> fields")
> introduced the bcb_get() function.
>
> When CONFIG_CMD_BCB=n, that function is stubbed.
> The stubbed function has a wrong prototype: value_size arg
On Mon 10 Jun 2024 at 11:46, Mattijs Korpershoek
wrote:
> Fix some trivial typos found by browsing the code.
> Done with flyspell.
>
> Reviewed-by: Quentin Schulz
> Signed-off-by: Mattijs Korpershoek
> ---
> include/bootmeth.h | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletio
Hello Marek!
On Sun, 2024-06-09 at 23:32 +0200, Marek Vasut wrote:
> Use the .match_ep() callback instead of workaround in core code.
> Replace descriptor parsing with ch9 macros with the same effect.
> Drop the SPL specific behavior, it is unclear why SPL should even
> be special.
>
> Signed-off
Hi Sughosh
[...]
> #define LMB_ALLOC_ANYWHERE 0
>
> +#if !IS_ENABLED(CONFIG_LMB_USE_MAX_REGIONS)
> +struct lmb_property memory_regions[CONFIG_LMB_MEMORY_REGIONS];
> +struct lmb_property reserved_regions[CONFIG_LMB_RESERVED_REGIONS];
> +#endif
> +
> +struct lmb lmb = {
> +#if IS_ENABLED(CONF
On Sat, Jun 08, 2024 at 12:22:16AM +0530, Sughosh Ganu wrote:
> With the move to make the LMB allocations persistent and the common
> memory regions being reserved during board init, the
> lmb_init_and_reserve_range() API can be replaced with a simple
> lmb_add() call.
>
> Signed-off-by: Sughosh G
On 1/1/70 01:00, Ilias Apalodimas wrote:
Hi Sughosh
[...]
#define LMB_ALLOC_ANYWHERE0
+#if !IS_ENABLED(CONFIG_LMB_USE_MAX_REGIONS)
+struct lmb_property memory_regions[CONFIG_LMB_MEMORY_REGIONS];
+struct lmb_property reserved_regions[CONFIG_LMB_RESERVED_REGIONS];
+#endif
+
+struct lmb lm
On Sat, 8 Jun 2024 at 06:59, Heinrich Schuchardt wrote:
>
>
>
> Am 7. Juni 2024 20:52:37 MESZ schrieb Sughosh Ganu :
> >The LMB memory map is now persistent and global. There is therefore no
> >need to add memory to the LMB memory map as part of the bdinfo
> >command. Only dump the current availab
On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
>
> Add a Kconfig symbol to enable getting updates on any memory map
> changes that might be done by some other module. This notification
> mechanism can then be used to have a synchronous view of allocated and
> free memory.
Is there any chance we
On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
>
> The changes in the EFI memory map are now notified to the LMB
> module. There is therefore no need to explicitly get the efi memory
> map and set aside the EFI allocated memory.
>
> Signed-off-by: Sughosh Ganu
> ---
> lib/lmb.c | 35 --
hi Ilias,
On Mon, 10 Jun 2024 at 17:15, Ilias Apalodimas
wrote:
>
> On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> >
> > Add a Kconfig symbol to enable getting updates on any memory map
> > changes that might be done by some other module. This notification
> > mechanism can then be used to h
Hi Sughosh
On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
>
> Allow for resizing of LMB regions if the region attributes match. The
> current code returns a failure status on detecting an overlapping
> address. This worked up until now since the LMB calls were not
> persistent and global -- th
On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
>
> There are events that would be used to notify other interested modules
> of any changes in available and occupied memory. This would happen
> when a module allocates or reserves memory, or frees up memory. These
> changes in memory map should be
hi Ilias,
On Mon, 10 Jun 2024 at 17:34, Ilias Apalodimas
wrote:
>
> Hi Sughosh
>
>
> On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> >
> > Allow for resizing of LMB regions if the region attributes match. The
> > current code returns a failure status on detecting an overlapping
> > address. T
On 19.05.24 17:35, Roman Stratiienko wrote:
Use GPT_PRIMARY_PARTITION_TABLE_LBA as the only source for a primary GPT
location instead of hardcoding it every time.
Sometimes, we need to shift the primary GPT location.
Having the location in the single place simplifies such shifting.
In gdisk th
On Mon, 10 Jun 2024 at 17:40, Ilias Apalodimas
wrote:
>
> On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> >
> > There are events that would be used to notify other interested modules
> > of any changes in available and occupied memory. This would happen
> > when a module allocates or reserves
On 03.06.24 5:57 PM, Alexey Romanov wrote:
> UBI block is virtual block device, which is an abstraction
> over MTD layer. Therefore it is logical to use it in
> combination with MTD drivers.
>
> Signed-off-by: Alexey Romanov
I think I already sent a review tag for v2, but anyway:
Reviewed-by: F
On Mon, 10 Jun 2024 at 15:20, Sughosh Ganu wrote:
>
> hi Ilias,
>
> On Mon, 10 Jun 2024 at 17:34, Ilias Apalodimas
> wrote:
> >
> > Hi Sughosh
> >
> >
> > On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> > >
> > > Allow for resizing of LMB regions if the region attributes match. The
> > > curr
On 10.06.24 14:20, Sughosh Ganu wrote:
hi Ilias,
On Mon, 10 Jun 2024 at 17:34, Ilias Apalodimas
wrote:
Hi Sughosh
On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
Allow for resizing of LMB regions if the region attributes match. The
current code returns a failure status on detecting an o
On Mon, 10 Jun 2024 at 18:17, Ilias Apalodimas
wrote:
>
> On Mon, 10 Jun 2024 at 15:20, Sughosh Ganu wrote:
> >
> > hi Ilias,
> >
> > On Mon, 10 Jun 2024 at 17:34, Ilias Apalodimas
> > wrote:
> > >
> > > Hi Sughosh
> > >
> > >
> > > On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> > > >
> > >
On Mon, 10 Jun 2024 at 18:29, Heinrich Schuchardt wrote:
>
> On 10.06.24 14:20, Sughosh Ganu wrote:
> > hi Ilias,
> >
> > On Mon, 10 Jun 2024 at 17:34, Ilias Apalodimas
> > wrote:
> >>
> >> Hi Sughosh
> >>
> >>
> >> On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> >>>
> >>> Allow for resizing
This has a dependency on
https://lore.kernel.org/u-boot/20240528170406.353616-1-liujianfeng1...@gmail.com/
Changes in v3:
- rebased on top of next,
- changed patch series dependency from DRAM ATAGS (merged) to RK3588
upstream DTS cherry-picks from 6.10-rc1 (USB nodes),
- cherry-picked kernel DT
From: Heiko Stuebner
Enable the mali gpu node and add the som-specific supply-regulator.
Signed-off-by: Heiko Stuebner
Reviewed-by: Quentin Schulz
Link: https://lore.kernel.org/r/20240327112120.1181570-2-he...@sntech.de
Signed-off-by: Heiko Stuebner
[ upstream commit: f5256f8ed4b729c3ab9d9cd
From: Heiko Stuebner
The association of uart2 to the q7-uart pins is part of the module
itself and not the baseboard used. Therefore move the pinctrl over
to the tiger dtsi.
Signed-off-by: Heiko Stuebner
Reviewed-by: Quentin Schulz
Link: https://lore.kernel.org/r/20240422143356.2596414-1-he...
From: Jing Luo
gpio_pwrctrl2 gets duplicated by both rk806_dvs1_null and rk806_dvs2_null
gpio_pwrctrl1 is unset. This typo appears in multiple files. Let's fix them.
Note: I haven't had the chance to test them all because I don't own all
of these boards (obviously). Please test if it's needed.
From: Heiko Stuebner
The clock-generator of course only produces a 100MHz clock rate,
not 1GHz.
Signed-off-by: Heiko Stuebner
Reviewed-by: Quentin Schulz
Link: https://lore.kernel.org/r/20240423114635.2637310-1-he...@sntech.de
Signed-off-by: Heiko Stuebner
[ upstream commit: 0eb2a93518fb4728
From: Heiko Stuebner
The comment for the host2_xhci points to the wrong port on the board.
The upper usb3 port is the correct one, so fix the comment to prevent
confusion.
Signed-off-by: Heiko Stuebner
Reviewed-by: Quentin Schulz
Link: https://lore.kernel.org/r/20240422163951.2604273-2-he...@s
From: Heiko Stuebner
The Q7 standard specifies a usb-id pin on the connector to distiuish
between host and device mode. Model this via the usb-id extcon binding.
While the pin is part of the Q7 standard, so part of the module, the
extcon stays disabled in the som dtsi and will only be enabled in
From: Heiko Stuebner
Apart from the host-only usb3 controller (host2) the rk3588 also provides
two dual-role controllers. On the Tiger-Haikou combination these are
connected to the lower usb3-host port in host-only mode and the micro-usb3
port for dual-role operation.
Add the necessary controlle
From: Quentin Schulz
The RK3588-Q7 SoM is a Qseven-compatible (70mm x 70mm, MXM-230
connector) system-on-module from Theobroma Systems, featuring the
Rockchip RK3588.
It provides the following feature set:
* up to 16GB LPDDR4x
* on-module eMMC
* SD card (on a baseboard) via edge connector
*
This patch set is for u-boot/next.
It includes various fixes and improvements for phyCORE-AM62x and
phyCORE-AM64x SoMs. Notable is the last patch which prepares for use
with future ECC memory fixups.
Nathan Morrisson (2):
arch: arm: dts: k3-am625-phyboard-lyra: Add fixed partitions
arch: arm:
From: Nathan Morrisson
Add a fixed partitions node to the AM62x device tree so that it can
be used to fixup the Linux device tree.
Signed-off-by: Nathan Morrisson
Signed-off-by: Wadim Egorov
---
.../k3-am625-phyboard-lyra-rdk-u-boot.dtsi| 26 +++
1 file changed, 26 inserti
From: Nathan Morrisson
Add a fixed partitions node to the AM64x device tree so that it can
be used to fixup the Linux device tree.
Signed-off-by: Nathan Morrisson
Signed-off-by: Wadim Egorov
---
.../k3-am642-phyboard-electra-rdk-u-boot.dtsi | 26 +++
1 file changed, 26 inserti
Update environment location to align with OSPI fixed-partition
definitions and provide a redundant environment at a 2nd location.
Signed-off-by: Wadim Egorov
---
configs/phycore_am64x_a53_defconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configs/phycore_am64x_a53_d
Update environment location to align with OSPI fixed-partition
definitions and provide a redundant environment at a 2nd location.
Signed-off-by: Wadim Egorov
---
configs/phycore_am62x_a53_defconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configs/phycore_am62x_a53_d
Copy fixed-partitions nodes from U-Boot device tree to OS device tree.
Signed-off-by: Wadim Egorov
---
board/phytec/common/k3/board.c | 10 ++
configs/phycore_am62x_a53_defconfig | 1 +
2 files changed, 11 insertions(+)
diff --git a/board/phytec/common/k3/board.c b/board/phytec/co
Make sure spl_board_init() gets compiled by enabling missing
CONFIG_SPL_BOARD_INIT and including hardware.h.
Fixes: 085cd6459dae ("board: phytec: am62x: Add PHYTEC phyCORE-AM62x SoM")
Signed-off-by: Wadim Egorov
---
board/phytec/phycore_am62x/phycore-am62x.c | 1 +
configs/phycore_am62x_a53_def
Enable usb0 in all boot phases for use with DFU.
Signed-off-by: Wadim Egorov
---
arch/arm/dts/k3-am625-phyboard-lyra-rdk-u-boot.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/dts/k3-am625-phyboard-lyra-rdk-u-boot.dtsi
b/arch/arm/dts/k3-am625-phyboard-lyra-rdk-u-boot.
Enable configs required for booting via DFU.
Configs taken from the am62x_a53_usbdfu.config config fragment.
Signed-off-by: Wadim Egorov
---
configs/phycore_am62x_a53_defconfig | 28
1 file changed, 28 insertions(+)
diff --git a/configs/phycore_am62x_a53_defconfig
Pull in ti/k3_dfu.env for dfu_alt_info_ram in SPL stage.
Signed-off-by: Wadim Egorov
---
board/phytec/phycore_am62x/phycore_am62x.env | 2 ++
1 file changed, 2 insertions(+)
diff --git a/board/phytec/phycore_am62x/phycore_am62x.env
b/board/phytec/phycore_am62x/phycore_am62x.env
index ada3a9233
Enable mtd command and remove SPI NOR flashes we do not
populate on our SoMs.
Signed-off-by: Wadim Egorov
---
configs/phycore_am62x_a53_defconfig | 4 ++--
configs/phycore_am62x_r5_defconfig | 1 -
configs/phycore_am64x_a53_defconfig | 4 ++--
configs/phycore_am64x_r5_defconfig | 1 -
4 files
Provide boot switch config for USB DFU boot.
Signed-off-by: Wadim Egorov
---
doc/board/phytec/phycore-am62x.rst | 4
1 file changed, 4 insertions(+)
diff --git a/doc/board/phytec/phycore-am62x.rst
b/doc/board/phytec/phycore-am62x.rst
index bc6d5246694..f8870657be0 100644
--- a/doc/board/p
Update Flash to SPI NOR chapter for use with mtd commands.
This is more convenient as we do not have to remember any
offsets in the SPI.
Signed-off-by: Wadim Egorov
---
doc/board/phytec/phycore-am62x.rst | 8
doc/board/phytec/phycore-am64x.rst | 8
2 files changed, 8 insertions
There is no need to reread the EEPROM multiple times in different stages
to detect the RAM size. We can do this once at an early stage and let
higher stages decode memory nodes using fdtdec.
Make sure to pass fixup memory nodes before passing to u-boot stage.
Signed-off-by: Wadim Egorov
---
boar
Hi Heinrich,
On Mon, 10 Jun 2024 at 03:11, Heinrich Schuchardt
wrote:
>
> 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 man
Hi Sughosh,
On Thu, 6 Jun 2024 at 13:18, Sughosh Ganu wrote:
>
> hi Simon,
>
> On Wed, 29 May 2024 at 22:00, Simon Glass wrote:
> >
> > +Sughosh Ganu for reference
> >
> >
> > On Sun, 31 Dec 2023 at 09:16, Tom Rini wrote:
> > >
> > > On Sun, Dec 31, 2023 at 04:40:06PM +0100, Heinrich Schuchardt
On 10.06.24 15:53, Simon Glass wrote:
Hi Heinrich,
On Mon, 10 Jun 2024 at 03:11, Heinrich Schuchardt
wrote:
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.
W
Hi,
On 10/11/23 12:06 PM, AKASHI Takahiro wrote:
SCMI specification allows any protocol to have its own channel for
the transport. While the current SCMI driver may assign its channel
from a device tree, the core function, devm_scmi_process_msg(), doesn't
use a protocol's channel, but always use
Hi Sughosh
On Mon, 10 Jun 2024 at 15:25, Sughosh Ganu wrote:
>
> On Mon, 10 Jun 2024 at 17:40, Ilias Apalodimas
> wrote:
> >
> > On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> > >
> > > There are events that would be used to notify other interested modules
> > > of any changes in available
Hi Sughosh
On Mon, 10 Jun 2024 at 15:57, Sughosh Ganu wrote:
>
> On Mon, 10 Jun 2024 at 18:17, Ilias Apalodimas
> wrote:
> >
> > On Mon, 10 Jun 2024 at 15:20, Sughosh Ganu wrote:
> > >
> > > hi Ilias,
> > >
> > > On Mon, 10 Jun 2024 at 17:34, Ilias Apalodimas
> > > wrote:
> > > >
> > > > Hi Su
On 6/10/2024 9:11 AM, Sam Protsenko wrote:
Replace fifoth_val property with its fifo-depth counterpart in all DW
MMC drivers. fifo-depth is a common property used in upstream Linux
kernel. The FIFOTH register value will be calculated using fifo-depth
value in DW MMC core (dw_mmc.c). This change r
On Thu, Jun 6, 2024 at 2:24 PM Mattijs Korpershoek
wrote:
>
> The only way to configure the load addresses for both bootimg and
> vendor_bootimg is by using the "abootimg" command.
> If we want to use the C API, there is no equivalent.
>
> Add set_abootimg_addr() and set_avendor_bootimg_addr() so
hi Ilias,
On Mon, 10 Jun 2024 at 19:52, Ilias Apalodimas
wrote:
>
> Hi Sughosh
>
> On Mon, 10 Jun 2024 at 15:57, Sughosh Ganu wrote:
> >
> > On Mon, 10 Jun 2024 at 18:17, Ilias Apalodimas
> > wrote:
> > >
> > > On Mon, 10 Jun 2024 at 15:20, Sughosh Ganu
> > > wrote:
> > > >
> > > > hi Ilias,
hi Simon,
On Mon, 10 Jun 2024 at 19:25, Simon Glass wrote:
>
> Hi Sughosh,
>
> On Thu, 6 Jun 2024 at 13:18, Sughosh Ganu wrote:
> >
> > hi Simon,
> >
> > On Wed, 29 May 2024 at 22:00, Simon Glass wrote:
> > >
> > > +Sughosh Ganu for reference
> > >
> > >
> > > On Sun, 31 Dec 2023 at 09:16, Tom
hi Ilias,
On Mon, 10 Jun 2024 at 19:48, Ilias Apalodimas
wrote:
>
> Hi Sughosh
>
> On Mon, 10 Jun 2024 at 15:25, Sughosh Ganu wrote:
> >
> > On Mon, 10 Jun 2024 at 17:40, Ilias Apalodimas
> > wrote:
> > >
> > > On Fri, 7 Jun 2024 at 21:54, Sughosh Ganu wrote:
> > > >
> > > > There are events t
On Mon, 10 Jun 2024 at 20:22, Sughosh Ganu wrote:
>
> hi Ilias,
>
> On Mon, 10 Jun 2024 at 19:48, Ilias Apalodimas
> wrote:
> >
> > Hi Sughosh
> >
> > On Mon, 10 Jun 2024 at 15:25, Sughosh Ganu wrote:
> > >
> > > On Mon, 10 Jun 2024 at 17:40, Ilias Apalodimas
> > > wrote:
> > > >
> > > > On Fri
This cannot be enabled early in boot since some other init is needed.
At this point it is unclear exactly what init is needed, so disable
the debug UART to avoid a hang.
Signed-off-by: Simon Glass
---
(no changes since v1)
configs/nyan-big_defconfig | 1 -
1 file changed, 1 deletion(-)
diff -
It does not make sense to enable all SHA algorithms unless they are
needed. It bloats the code and in this case, causes chromebook_link to
fail to build. That board does use the TPM, but not with measured boot,
nor EFI.
Since EFI_TCG2_PROTOCOL already selects these options, we just need to
add the
Add better logging for power init so that CONFIG_LOG_ERROR_RETURN can
be enabled.
Signed-off-by: Simon Glass
---
Changes in v2:
- Remove the superfluous if() and drop the debug() as well
board/google/veyron/veyron.c | 30 --
1 file changed, 12 insertions(+), 18 dele
With a recent change, regulators_enable_boot_on() returns an error if a
regulator is already set. Check for and handle this situation.
Fixes: d99fb64a98a power: regulator: Only run autoset once for each regulator
Reviewed-by: Jonas Karlman
Reviewed-by: Quentin Schulz
Signed-off-by: Simon Glass
The dcache may not be enabled in SPL. Add a check to avoid trying to
use an undefined function.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
---
(no changes since v1)
common/spl/spl_atf.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/common/spl/spl_atf.c b/common/s
On some boards, the bloblist is created in SPL once SDRAM is ready. It
cannot be accessed until that point, so is not available early in SPL.
Add a condition to avoid a hang in this case.
This fixes a hang in chromebook_coral
Fixes: 70fe2385943 ("fdt: Allow the devicetree to come from a bloblist
At present gd->ram_size is 0 in SPL, meaning that it is not possible to
enable the cache. Correct this by always populating the RAM size
correctly.
Part of the confusion here comes from the large blocks of code which
are #ifdefed out. Add a function phase_sdram_init() which returns
whether SDRAM i
This causes a hang, so disable it. Unfortunately the RAM-size fix does
not resolve the problem and I am unsure what is wrong. As soon as the
cache is enabled the board appears to hang.
Fixes: 6d8cdfd1536 ("rockchip: spl: Enable caches to speed up checksum
validation")
Signed-off-by: Simon Glass
Now that am335x_evm boots OK on the Beaglebone black, drop the latter
and update the docs to cover the change.
Also add a few updates about 'make fit' and drop the note about the
security review, as U-Boot's verified boot has had quite extensive
review now.
Signed-off-by: Simon Glass
---
Change
Hi Sughosh,
On Mon, 10 Jun 2024 at 08:40, Sughosh Ganu wrote:
>
> hi Simon,
>
> On Mon, 10 Jun 2024 at 19:25, Simon Glass wrote:
> >
> > Hi Sughosh,
> >
> > On Thu, 6 Jun 2024 at 13:18, Sughosh Ganu wrote:
> > >
> > > hi Simon,
> > >
> > > On Wed, 29 May 2024 at 22:00, Simon Glass wrote:
> > >
On Fri, 26 Apr 2024 at 07:38, Michal Simek wrote:
>
> 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
On Fri, 26 Apr 2024 at 07:38, Michal Simek wrote:
>
> 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
> differentiat
Hi Michal,
On Fri, 7 Jun 2024 at 01:53, Michal Simek wrote:
>
>
>
> On 5/24/24 12:07, Ilias Apalodimas wrote:
> > Hi Michal
> >
> >
> > On Fri, 24 May 2024 at 12:45, Michal Simek wrote:
> >>
> >> Hi Ilias,
> >>
> >> On 4/26/24 15:38, Michal Simek wrote:
> >>> Hi,
> >>>
> >>> currently only DT wa
On 07.06.24 20:52, Sughosh Ganu wrote:
There are events that would be used to notify other interested modules
of any changes in available and occupied memory. This would happen
when a module allocates or reserves memory, or frees up memory. These
I am worried about the "frees up memory" case.
Hi Mattijs,
On Thu, Jun 6, 2024 at 2:24 PM Mattijs Korpershoek
wrote:
>
> Android boot flow is a bit different than a regular Linux distro.
> Android relies on multiple partitions in order to boot.
>
> A typical boot flow would be:
> 1. Parse the Bootloader Control Block (BCB, misc partition)
> 2
hi Simon,
On Mon, 10 Jun 2024 at 20:33, Simon Glass wrote:
>
> Hi Sughosh,
>
> On Mon, 10 Jun 2024 at 08:40, Sughosh Ganu wrote:
> >
> > hi Simon,
> >
> > On Mon, 10 Jun 2024 at 19:25, Simon Glass wrote:
> > >
> > > Hi Sughosh,
> > >
> > > On Thu, 6 Jun 2024 at 13:18, Sughosh Ganu wrote:
> > >
Hi Jonas,
On Thu, 6 Jun 2024 at 09:04, Simon Glass wrote:
>
> Hi Jonas,
>
> On Wed, 5 Jun 2024 at 05:07, Jonas Karlman wrote:
> >
> > Hi Simon,
> >
> > On 2024-06-05 05:25, Simon Glass wrote:
> > > This causes a hang, so disable it.
> >
> > When I initially tested this on multiple boards there w
On Mon, 10 Jun 2024 at 20:47, Heinrich Schuchardt wrote:
>
> On 07.06.24 20:52, Sughosh Ganu wrote:
> > There are events that would be used to notify other interested modules
> > of any changes in available and occupied memory. This would happen
> > when a module allocates or reserves memory, or f
Hi Heinrich,
On Mon, 10 Jun 2024 at 08:00, Heinrich Schuchardt
wrote:
>
> On 10.06.24 15:53, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Mon, 10 Jun 2024 at 03:11, Heinrich Schuchardt
> > wrote:
> >>
> >> In U-Boot EFI boot options can already specify both an EFI binary and
> >> an initrd. Wi
Hi Ilias,
On Tue, 4 Jun 2024 at 23:33, Ilias Apalodimas
wrote:
>
> Hi Simon,
>
> On Wed, 5 Jun 2024 at 06:26, Simon Glass wrote:
> >
> > On some boards, the bloblist is created in SPL once SDRAM is ready. It
> > cannot be accessed until that point, so is not available early in SPL.
> >
> > Add a
1 - 100 of 147 matches
Mail list logo