Hi Sughosh,
OK I understand that if the platform uses the FIT capsule, the
fw_images[] must have 1 entry and it is completely non relationship
with dfu_alt_info... We may need a document for this case too.
Thanks,
2022年3月25日(金) 10:09 Masami Hiramatsu :
>
> Hi Sughosh,
>
> 2022年3月24日(木) 23:40
Sughosh,
On Thu, Mar 24, 2022 at 06:08:55PM +0530, Sughosh Ganu wrote:
>
> This series is cleaning up the usage of the image GUIDs that are used
> in capsule update and the EFI System Resource Table(ESRT).
>
> Currently, there are two instances of the Firmware Management
> Protocol(FMP), one
On 3/24/22 18:13, Andre Przywara wrote:
On Wed, 23 Mar 2022 19:03:48 -0700
William Zhang wrote:
Hi,
This is the initial support for Broadcom's ARM-based 47622 SOC.
In this change, our first SOC is an armv7 platform called 47622. The
initial support includes a bare-bone implementation and
Dear Tom,
On Fri, 25 Mar 2022 at 09:22, Jaehoon Chung wrote:
>
> On 3/25/22 06:17, Tom Rini wrote:
> > This value isn't used anywhere, drop it.
> >
> > Signed-off-by: Tom Rini
>
> Reviewed-by : Jaehoon Chung
>
>
>
Reviewed-by: Minkyu Kang
--
Thanks,
Minkyu Kang.
Dear Tom,
On Thu, 24 Mar 2022 at 06:23, Tom Rini wrote:
> We only set one of these values ever at this point, so remove dead code.
>
> Cc: Minkyu Kang
> Cc: Jaehoon Chung
> Signed-off-by: Tom Rini
> ---
> arch/arm/mach-exynos/exynos4_setup.h | 20
>
On Sun, Mar 20, 2022 at 7:42 PM Andrew Scull wrote:
>
> The calls to `virtio_pci_map_capability()` return NULL on error. If this
> happens, later accesses to the pointers would be unsafe. Avoid this by
> failing if the configs were not successfully mapped.
>
> Signed-off-by: Andrew Scull
> ---
>
On Sun, Mar 20, 2022 at 7:42 PM Andrew Scull wrote:
>
> Read the virtio PCI capability out of the device configuration space to
> a struct rather than accessing fields directly from the configuration
> space as they are needed. This both makes access to the fields easier
> and avoids re-reading
On Fri, Mar 25, 2022 at 12:24 AM Andrew Scull wrote:
>
> On Thu, 24 Mar 2022 at 14:19, Bin Meng wrote:
> >
> > On Sun, Mar 20, 2022 at 7:41 PM Andrew Scull wrote:
> > >
> > > Make sure virtio notifications are written within their allocated
> > > buffer.
> > >
> > > Signed-off-by: Andrew Scull
On Wed, 23 Mar 2022 19:03:48 -0700
William Zhang wrote:
Hi,
> This is the initial support for Broadcom's ARM-based 47622 SOC.
>
> In this change, our first SOC is an armv7 platform called 47622. The
> initial support includes a bare-bone implementation and dts with ARM
> PL011 uart.
As Tom
On Fri, Mar 25, 2022 at 12:27 AM Andrew Scull wrote:
>
> On Thu, 24 Mar 2022 at 15:24, Bin Meng wrote:
> >
> > On Sun, Mar 20, 2022 at 7:41 PM Andrew Scull wrote:
> > >
> > > Ensure the virtio PCI capabilities are contained within the bounds of
> > > the device's configuration space. The
Kojima-san,
On Thu, Mar 24, 2022 at 10:54:32PM +0900, Masahisa Kojima wrote:
> This patch series adds the menu-driven boot device selection,
> by extending the existing "bootmenu" to include UEFI and distro_boot
> related entries, and supports menu-driven UEFI boot variable
> maintenance.
>
>
Hi Sughosh,
2022年3月24日(木) 23:40 Sughosh Ganu :
>
> hi Masami,
>
> On Thu, 24 Mar 2022 at 19:14, Masami Hiramatsu
> wrote:
> >
> > Hi Sughosh,
> >
> > 2022年3月24日(木) 21:39 Sughosh Ganu :
> > >
> > > Currently, all platforms that enable capsule updates do so using
> > > either
On 3/25/22 06:17, Tom Rini wrote:
> This value isn't used anywhere, drop it.
>
> Signed-off-by: Tom Rini
Reviewed-by : Jaehoon Chung
Best Regards,
Jaehoon Chung
> ---
> include/configs/exynos5420-common.h | 3 ---
> include/configs/exynos7420-common.h | 3 ---
>
Hi Anatloij,
On Fri, 25 Mar 2022 at 11:16, Anatolij Gustschin wrote:
>
> Hi Simon,
>
> On Thu, 24 Mar 2022 13:54:22 -0600
> Simon Glass s...@chromium.org wrote:
> ...
> >
> > Is there any word on this series, please?
>
> last week I've rebased and applied this series to next (PATCH 02/14
>
Hi Simon,
On Thu, 24 Mar 2022 13:54:22 -0600
Simon Glass s...@chromium.org wrote:
...
>
> Is there any word on this series, please?
last week I've rebased and applied this series to next (PATCH 02/14
dropped) and will submit a pull request when Tom merges last -rc
into his next branch.
Hi Hajo,
I've added Stefan.
When you send patches for Kirkwood or other Marvell boards, please
also send it directly to Stefan (Stefan is the maintainer of Marvell
u-boots).
Tony
On Thu, Mar 24, 2022 at 3:11 AM Pali Rohár wrote:
>
> Hello!
>
> On Thursday 24 March 2022 10:55:38 Hajo
On Thu, Mar 24, 2022 at 6:39 PM Han Xu wrote:
>
> Previous u-boot code changed the default bch setting behavior and caused
> backward compatible issue. This fix choose the legacy bch geometry back
> again as the default option. If the minimum ecc strength that NAND chips
> required need to be
Previous u-boot code changed the default bch setting behavior and caused
backward compatible issue. This fix choose the legacy bch geometry back
again as the default option. If the minimum ecc strength that NAND chips
required need to be chosen, it can be enabled by either adding DT flag
On Thu, Mar 24, 2022 at 05:42:27PM +0100, Stefan Roese wrote:
> Hi Tom,
>
> please pull this Espressobin fix from Pali:
>
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
This converts the following to Kconfig:
CONFIG_SYS_MONITOR_BASE
Note that for how this is re-used on some PowePC platforms, we introduce
CONFIG_SPL_SYS_MONITOR_BASE and CONFIG_TPL_SYS_MONITOR_BASE and use the
CONFIG_VAL macro to get the correct value at build time, in the code.
Signed-off-by:
All options have now been migrated to Kconfig correctly so remove this
support.
Signed-off-by: Tom Rini
---
boot/Kconfig | 13
doc/README.kconfig | 7
doc/develop/moveconfig.rst | 3 +-
scripts/Makefile.autoconf | 4 ---
scripts/build-whitelist.sh | 23
The values CONFIG_SYS_USE_NANDFLASH and CONFIG_SYS_USE_MMC serve the
same purpose as CONFIG_SD_BOOT / CONFIG_NAND_BOOT so migrate to using
these switches instead as they're already in Kconfig.
Cc: Stelian Pop
Cc: Heiko Schocher
Cc: Daniel Gorsulowski
Cc: Eugen Hristev
Signed-off-by: Tom Rini
This converts the following to Kconfig:
CONFIG_NORFLASH_PS32BIT
Note that we also attempt to correct the behavior of the code here,
which had been testing for "NORFLASH_PS32BIT" which would never be set,
instead check for the now set "CONFIG_NORFLASH_PS32BIT", which results
in some behavior
This converts the following to Kconfig:
CONFIG_E300
CONFIG_E5500
Signed-off-by: Tom Rini
---
arch/powerpc/cpu/mpc83xx/Kconfig | 3 +++
arch/powerpc/cpu/mpc85xx/Kconfig | 6 ++
arch/powerpc/include/asm/config_mpc85xx.h | 2 --
include/configs/MPC837XERDB.h
This converts the following to Kconfig:
CONFIG_SRIO_PCIE_BOOT_SLAVE
Signed-off-by: Tom Rini
---
board/freescale/t208xqds/Kconfig | 3 +++
configs/T2080QDS_SRIO_PCIE_BOOT_defconfig | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/board/freescale/t208xqds/Kconfig
Signed-off-by: Tom Rini
---
board/freescale/mx53loco/Kconfig | 3 +++
include/configs/mx53loco.h | 1 -
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/board/freescale/mx53loco/Kconfig b/board/freescale/mx53loco/Kconfig
index a690a601ac0e..5dcdcd9f725e 100644
---
This converts the following to Kconfig:
CONFIG_DEEP_SLEEP
Signed-off-by: Tom Rini
---
README | 4
board/freescale/common/Kconfig | 7 +++
configs/ls1021aiot_qspi_defconfig | 1 +
configs/ls1021aiot_sdcard_defconfig | 1 +
This value isn't used anywhere, drop it.
Signed-off-by: Tom Rini
---
include/configs/exynos5420-common.h | 3 ---
include/configs/exynos7420-common.h | 3 ---
include/configs/exynos78x0-common.h | 3 ---
3 files changed, 9 deletions(-)
diff --git a/include/configs/exynos5420-common.h
In the case of M5373EVB we always had NANDFLASH_SIZE=16, so just use it
directly. In the case of M5329EVB we had not removed the rest of NAND
support when saying we didn't have NAND, so instead use that to key off
of rather than NANDFLASH_SIZE.
Cc: TsiChung Liew
Signed-off-by: Tom Rini
---
The value CONFIG_DB_784MP_GP is only used in the DDR code to refer to
CONFIG_TARGET_DB_MV784MP_GP so just use that second value directly.
Cc: Stefan Roese
Signed-off-by: Tom Rini
---
arch/arm/mach-mvebu/serdes/axp/high_speed_env_lib.c | 2 +-
drivers/ddr/marvell/axp/ddr3_axp.h
On Thu, Mar 24, 2022 at 02:04:57PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Thu, 24 Mar 2022 at 13:27, Tom Rini wrote:
> >
> > On Thu, Mar 24, 2022 at 12:33:38PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Thu, 24 Mar 2022 at 08:46, Tom Rini wrote:
> > > >
> > > > On Wed, Mar 23,
On 3/24/22 11:58, Tom Rini wrote:
On Thu, Mar 24, 2022 at 11:53:19AM -0700, William Zhang wrote:
Hi Tom,
On 3/23/22 20:08, Tom Rini wrote:
On Wed, Mar 23, 2022 at 07:03:48PM -0700, William Zhang wrote:
This is the initial support for Broadcom's ARM-based 47622 SOC.
In this change, our
On 24/03/22, Michal Simek wrote:
>
>
> On 3/23/22 15:04, Jorge Ramirez-Ortiz wrote:
> > From 528b3117a36b7b4eea1839afbea7191d60638b0c Mon Sep 17 00:00:00 2001
> > From: Jorge Ramirez-Ortiz
> > Date: Wed, 23 Mar 2022 14:41:15 +0100
> > Subject: [PATCH] arm64: zynqmp: enable the PMUFW watchdog
>
On Thu, Mar 24, 2022 at 12:01:19PM -0400, Tom Rini wrote:
> On Thu, Mar 24, 2022 at 01:08:48PM +0200, Eugen Hristev wrote:
>
> > With the commit that moves the BOOTCOMMAND to Kconfig:
> >
> > 970bf8603b ("Convert CONFIG_USE_BOOTCOMMAND et al to Kconfig")
> >
> > some stray ifdefs have been left
Hi Pali,
On Thu, 24 Mar 2022 at 13:56, Pali Rohár wrote:
>
> On Thursday 24 March 2022 13:54:22 Simon Glass wrote:
> > Hi Anatolij,
> >
> > On Sun, 23 Jan 2022 at 07:04, Simon Glass wrote:
> > >
> > > There is still quite a bit of cruft in the video subsystem. Mainly this is
> > > users of the
On Thursday 24 March 2022 13:54:22 Simon Glass wrote:
> Hi Anatolij,
>
> On Sun, 23 Jan 2022 at 07:04, Simon Glass wrote:
> >
> > There is still quite a bit of cruft in the video subsystem. Mainly this is
> > users of the now-removed CONFIG_VIDEO, cfb_console and CONFIG_LCD.
> >
> > This series
Hi Anatolij,
On Sun, 23 Jan 2022 at 07:04, Simon Glass wrote:
>
> There is still quite a bit of cruft in the video subsystem. Mainly this is
> users of the now-removed CONFIG_VIDEO, cfb_console and CONFIG_LCD.
>
> This series removes most of the first two. The exception is videomodes.c
> and its
Hi Tom,
On Thu, 24 Mar 2022 at 13:27, Tom Rini wrote:
>
> On Thu, Mar 24, 2022 at 12:33:38PM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Thu, 24 Mar 2022 at 08:46, Tom Rini wrote:
> > >
> > > On Wed, Mar 23, 2022 at 08:13:42PM -0600, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On
On Thu, Mar 24, 2022 at 12:33:38PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Thu, 24 Mar 2022 at 08:46, Tom Rini wrote:
> >
> > On Wed, Mar 23, 2022 at 08:13:42PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Wed, 23 Mar 2022 at 14:09, Tom Rini wrote:
> > > >
> > > > On Wed, Mar 23,
March 24, 2022 1:25 PM, "Alexander von Gluck IV" wrote:
> March 24, 2022 12:06 PM, "Heinrich Schuchardt" wrote:
>
>> On 3/24/22 17:22, Alexander von Gluck IV wrote:
>> Do we really always need this output for every invokation of LoadImage()?
>>
>> Writing test messages during the runtime of a
* If users want to debug EFI applications via qemu + GDB, they
need to know the relocated address of the application to
align their symbols to in GDB via add-symbol-file.
* This exposes where EFI applications are relocated to enable
debugging EFI applications via qemu + gdb
* Usage is
On Thu, Mar 24, 2022 at 11:53:19AM -0700, William Zhang wrote:
> Hi Tom,
>
> On 3/23/22 20:08, Tom Rini wrote:
> > On Wed, Mar 23, 2022 at 07:03:48PM -0700, William Zhang wrote:
> > > This is the initial support for Broadcom's ARM-based 47622 SOC.
> > >
> > > In this change, our first SOC is an
Hi Tom,
On 3/23/22 20:08, Tom Rini wrote:
On Wed, Mar 23, 2022 at 07:03:48PM -0700, William Zhang wrote:
This is the initial support for Broadcom's ARM-based 47622 SOC.
In this change, our first SOC is an armv7 platform called 47622. The
initial support includes a bare-bone implementation and
Hi Tom,
On Thu, 24 Mar 2022 at 08:46, Tom Rini wrote:
>
> On Wed, Mar 23, 2022 at 08:13:42PM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Wed, 23 Mar 2022 at 14:09, Tom Rini wrote:
> > >
> > > On Wed, Mar 23, 2022 at 12:45:50PM -0600, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On
March 24, 2022 12:06 PM, "Heinrich Schuchardt" wrote:
> On 3/24/22 17:22, Alexander von Gluck IV wrote:
> Do we really always need this output for every invokation of LoadImage()?
>
> Writing test messages during the runtime of a menu driven program like
> the UEFI SCT can be very disturbing.
>
Fman microcode is executable code (AFAICT) loaded into a
coprocessor. As such, if verified boot is enabled, it must be verified
like other executable code. However, this is not currently done.
This commit adds verified boot functionality by encapsulating the
microcode in a FIT, which can then be
This adds a new method to load Fman firmware from a filesystem. This
allows users to use regular files instead of hard-coded offsets for the
firmware.
Signed-off-by: Sean Anderson
---
drivers/net/fm/fm.c | 25 -
drivers/qe/Kconfig | 4
2 files changed, 28
In order to read the firmware from the filesystem, we need a file name.
Read the firmware name from the device tree, using the firmware-name
property. This property is commonly used in Linux to determine the
correct name to use (and can be seen in several device trees in U-Boot).
Signed-off-by:
The fs_loader device is used to pull in settings via the chosen node.
However, there was no library function for this, so arria10 was doing it
explicitly. This function subsumes that, and uses ofnode_get_chosen_node
instead of navigating the device tree directly. Because fs_loader pulls
its config
Several different firmware users have repetitive code to extract the
firmware data from a FIT. Add some helper functions to reduce the amount
of repetition. fit_conf_get_prop_node (eventually) calls
fdt_check_node_offset_, so we can avoid an explicit if. In general, this
version avoids printing on
Surprisingly, Fman microcode does not seem to be verified. This series
aims to rectify this by introducing an optional FIT wrapper. This
wrapper is made mandatory if FIT_SIGNATURE is enabled. NXP boards do not
use this config, so the microcode will remain unverified for them. This
is OK, since we
The config to use for FIT images can be better specified by enabling
CONFIG_MULTI_DTB_FIT and implementing board_fit_config_name_match.
Signed-off-by: Sean Anderson
---
arch/arm/cpu/armv8/sec_firmware.c | 17 -
1 file changed, 4 insertions(+), 13 deletions(-)
diff --git
Am 2022-03-23 22:19, schrieb Tom Rini:
This converts the following to Kconfig:
CONFIG_LSCHLV2
CONFIG_LSXHL
Cc: Michael Walle
Signed-off-by: Tom Rini
Reviewed-by: Michael Walle
thanks,
-michael
---
board/buffalo/lsxl/Kconfig | 11 +++
configs/lschlv2_defconfig | 2 +-
On 3/24/22 17:44, Sughosh Ganu wrote:
On Sun, 13 Mar 2022 at 20:18, Sughosh Ganu wrote:
The Qemu platform has a function defined to get the random number
generator(RNG) device. However, the RNG device can be obtained simply
by searching for a device belonging to the RNG uclass. Remove the
On 3/24/22 17:22, Alexander von Gluck IV wrote:
* If users want to debug EFI applications via qemu + GDB, they
need to know the relocated address of the application to
align their symbols to in GDB via add-symbol-file.
* This exposes where EFI applications are relocated to enable
hi Heinrich,
On Sun, 13 Mar 2022 at 20:18, Sughosh Ganu wrote:
>
> The Qemu platform has a function defined to get the random number
> generator(RNG) device. However, the RNG device can be obtained simply
> by searching for a device belonging to the RNG uclass. Remove the
> superfluous platform
Hi Tom,
please pull this Espressobin fix from Pali:
- a37xx: espressobin: Fix non-working SPI (Pali)
Here the Azure build, without any issues:
On 3/23/22 14:18, Pali Rohár wrote:
Commit 0934dddc6436 ("arm: a37xx: Update DTS files to version from
upstream Linux kernel") ported Linux's device-tree files for Armada 3720
SOCs. This broke SPI support on some Espressobin boards and results in
following U-Boot error:
Loading Environment
See "[PATCH] efi_loader: Expose relocated address for gdb debugging purposes"
This actually solves the problem by exposing (previously hidden) relocated
address.
Now it's a *LOT* easier to debug u-boot loaded EFI binaries using the exposed
address:
This is helpful on pretty much every
On Thu, 24 Mar 2022 at 15:24, Bin Meng wrote:
>
> On Sun, Mar 20, 2022 at 7:41 PM Andrew Scull wrote:
> >
> > Ensure the virtio PCI capabilities are contained within the bounds of
> > the device's configuration space. The expected size of the capability is
> > passed when searching for the
* If users want to debug EFI applications via qemu + GDB, they
need to know the relocated address of the application to
align their symbols to in GDB via add-symbol-file.
* This exposes where EFI applications are relocated to enable
debugging EFI applications via qemu + gdb
* Usage is
hi Heinrich,
On Fri, 4 Mar 2022 at 19:05, Sughosh Ganu wrote:
>
> The 'rng' command dumps a number of random bytes on the console. Add a
> set of tests for the 'rng' command. The test function performs basic
> sanity testing of the command.
>
> Since a unit test is being added for the command,
hi Heinrich,
On Sun, 13 Mar 2022 at 20:19, Sughosh Ganu wrote:
>
> The 'rng' command dumps a number of random bytes on the console. Add a
> set of tests for the 'rng' command. The test function performs basic
> sanity testing of the command.
>
> Since a unit test is being added for the command,
hi Heinrich,
On Sun, 13 Mar 2022 at 20:19, Sughosh Ganu wrote:
>
> Add a usage document for the 'rng' u-boot command.
>
> Signed-off-by: Sughosh Ganu
> Reviewed-by: Ilias Apalodimas
> Reviewed-by: Simon Glass
> ---
>
> Changes since V4:
>
> * Reflect the fact that a maximum of 64 bytes can be
hi Heinrich,
On Sun, 13 Mar 2022 at 20:19, Sughosh Ganu wrote:
>
> Use a statically allocated buffer on stack instead of using malloc for
> reading the random bytes. Using a local array is faster than
> allocating heap memory on every initiation of the command.
>
> Signed-off-by: Sughosh Ganu
>
hi Heinrich,
On Mon, 14 Mar 2022 at 03:53, Simon Glass wrote:
>
> Hi Sughosh,
>
> On Sun, 13 Mar 2022 at 08:49, Sughosh Ganu wrote:
> >
> > The 'rng' u-boot command is used for printing a select number of
> > random bytes on the console. Currently, the RNG device from which the
> > random bytes
On Thu, Mar 24, 2022 at 8:59 AM Fabio Estevam wrote:
>
> Hi Tim,
>
> On Thu, Mar 24, 2022 at 12:32 PM Tim Harvey wrote:
> >
> > commit 7c84319af9c7 ("dm: gpio: Correct use of -ENODEV in drivers")
> > changed the return code for an I2C NAK from -ENODEV to -EREMOTEIO.
>
> I think we should be
On Thu, Mar 24, 2022 at 01:08:48PM +0200, Eugen Hristev wrote:
> With the commit that moves the BOOTCOMMAND to Kconfig:
>
> 970bf8603b ("Convert CONFIG_USE_BOOTCOMMAND et al to Kconfig")
>
> some stray ifdefs have been left in the header files which
> are now useless.
> Clean up the include
On Thu, Mar 24, 2022 at 12:11 PM Christoph Fritz
wrote:
>
> Add support for reading GPIO pin value when function is output.
> With this patch applied, gpio toggle command is working.
>
> Signed-off-by: Christoph Fritz
> Cc: Fabio Estevam
> Reviewed-by: Peng Fan
Reviewed-by: Fabio Estevam
Hi Tim,
On Thu, Mar 24, 2022 at 12:32 PM Tim Harvey wrote:
>
> commit 7c84319af9c7 ("dm: gpio: Correct use of -ENODEV in drivers")
> changed the return code for an I2C NAK from -ENODEV to -EREMOTEIO.
I think we should be consistent with Linux and return -ENXIO for the NACK case:
On Thu, 24 Mar 2022 at 20:40, Michal Simek wrote:
>
>
>
> On 3/24/22 15:51, Sughosh Ganu wrote:
> > On Thu, 24 Mar 2022 at 19:55, Michal Simek wrote:
> >>
> >>
> >>
> >> On 3/24/22 13:39, Sughosh Ganu wrote:
> >>> While building a capsule, the GUID value of that specific image is to
> >>> be
commit 7c84319af9c7 ("dm: gpio: Correct use of -ENODEV in drivers")
changed the return code for an I2C NAK from -ENODEV to -EREMOTEIO.
Update the gsc_i2c_read and gsc_i2c_write functions for this change
to properly retry the transaction on a NAK meaning the GSC is busy.
Fixes: 7c84319af9c7 ("dm:
+Heinrich Schuchardt
On Thu, Mar 24, 2022 at 10:51 PM Alex wrote:
>
> Good morning!
>
> So, some time ago I wrote a short guide on how to debug EFI bootloaders
> started
> by u-boot in qemu.
>
> https://www.haiku-os.org/blog/kallisti5/2021-01-17_debugging_riscv-64_bootloader_in_qemu/
>
> At the
Hardware-accelerated hash functions require that the input and output
buffers be aligned to the minimum DMA alignment. memalign.h helpfully
provides a macro just for this purpose. It doesn't exist on the host,
but we don't need to be aligned there either.
Fixes: 5dfb521386 ("[new uImage] New
On Thu, Mar 24, 2022 at 11:22 PM Heinrich Schuchardt
wrote:
>
> We use Sphinx style comments to describe functions.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> include/dm/ofnode.h | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
Reviewed-by: Bin Meng
On Sun, Mar 20, 2022 at 7:41 PM Andrew Scull wrote:
>
> Ensure the virtio PCI capabilities are contained within the bounds of
> the device's configuration space. The expected size of the capability is
> passed when searching for the capability to enforce this check.
>
> Signed-off-by: Andrew
We use Sphinx style comments to describe functions.
Signed-off-by: Heinrich Schuchardt
---
include/dm/ofnode.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/dm/ofnode.h b/include/dm/ofnode.h
index 744dffe0a2..6a996d9521 100644
--- a/include/dm/ofnode.h
+++
Add support for reading GPIO pin value when function is output.
With this patch applied, gpio toggle command is working.
Signed-off-by: Christoph Fritz
Cc: Fabio Estevam
Reviewed-by: Peng Fan
---
drivers/gpio/imx_rgpio2p.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
On 3/24/22 15:51, Sughosh Ganu wrote:
On Thu, 24 Mar 2022 at 19:55, Michal Simek wrote:
On 3/24/22 13:39, Sughosh Ganu wrote:
While building a capsule, the GUID value of that specific image is to
be passed through the --guid command option to the mkeficapsule
tool. This renders the
On Thu, 24 Mar 2022 at 20:21, Michal Simek wrote:
>
>
>
> On 3/24/22 15:44, Sughosh Ganu wrote:
> > On Thu, 24 Mar 2022 at 19:55, Michal Simek wrote:
> >>
> >>
> >>
> >> On 3/24/22 13:38, Sughosh Ganu wrote:
> >>> Currently, all platforms that enable capsule updates do so using
> >>> either
Good morning!
So, some time ago I wrote a short guide on how to debug EFI bootloaders started
by u-boot in qemu.
https://www.haiku-os.org/blog/kallisti5/2021-01-17_debugging_riscv-64_bootloader_in_qemu/
At the time it worked, however figuring the elf load addresses from u-boot was
extremely
On 3/24/22 15:44, Sughosh Ganu wrote:
On Thu, 24 Mar 2022 at 19:55, Michal Simek wrote:
On 3/24/22 13:38, Sughosh Ganu wrote:
Currently, all platforms that enable capsule updates do so using
either EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID or
EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID. This is
On Thu, 24 Mar 2022 at 19:55, Michal Simek wrote:
>
>
>
> On 3/24/22 13:39, Sughosh Ganu wrote:
> > While building a capsule, the GUID value of that specific image is to
> > be passed through the --guid command option to the mkeficapsule
> > tool. This renders the
On Wed, Mar 23, 2022 at 08:13:42PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 23 Mar 2022 at 14:09, Tom Rini wrote:
> >
> > On Wed, Mar 23, 2022 at 12:45:50PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Wed, 23 Mar 2022 at 08:05, Tom Rini wrote:
> > > >
> > > > On Sun, Mar 06,
On Thu, 24 Mar 2022 at 19:55, Michal Simek wrote:
>
>
>
> On 3/24/22 13:38, Sughosh Ganu wrote:
> > Currently, all platforms that enable capsule updates do so using
> > either EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID or
> > EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID. This is based on the Firmware
> >
hi Masami,
On Thu, 24 Mar 2022 at 19:14, Masami Hiramatsu
wrote:
>
> Hi Sughosh,
>
> 2022年3月24日(木) 21:39 Sughosh Ganu :
> >
> > Currently, all platforms that enable capsule updates do so using
> > either EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID or
> > EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID. This
On 3/23/22 15:04, Jorge Ramirez-Ortiz wrote:
From 528b3117a36b7b4eea1839afbea7191d60638b0c Mon Sep 17 00:00:00 2001
From: Jorge Ramirez-Ortiz
Date: Wed, 23 Mar 2022 14:41:15 +0100
Subject: [PATCH] arm64: zynqmp: enable the PMUFW watchdog
If the PMUFW was built with support for the CSU
On 3/24/22 13:38, Sughosh Ganu wrote:
Currently, all platforms that enable capsule updates do so using
either EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID or
EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID. This is based on the Firmware
Management Protocol(FMP) instance used on the platform. However, this
On 3/24/22 13:39, Sughosh Ganu wrote:
While building a capsule, the GUID value of that specific image is to
be passed through the --guid command option to the mkeficapsule
tool. This renders the EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID and
EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID values
On Sun, Mar 20, 2022 at 7:41 PM Andrew Scull wrote:
>
> Check that the common config is at least as large as the struct it is
> expected to contain. Only then is it safe to cast the pointer and be
> safe from out-of-bounds accesses.
>
> Signed-off-by: Andrew Scull
> ---
>
On Sun, Mar 20, 2022 at 7:41 PM Andrew Scull wrote:
>
> Make sure virtio notifications are written within their allocated
> buffer.
>
> Signed-off-by: Andrew Scull
> ---
> drivers/virtio/virtio_pci_modern.c | 12 ++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git
Add pwm1/backlight support nodes for imx8mm_evk board
Signed-off-by: Tommaso Merciai
---
arch/arm/dts/imx8mm-evk.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/dts/imx8mm-evk.dtsi b/arch/arm/dts/imx8mm-evk.dtsi
index 60179e006d..e7a2bd8a64 100644
---
Enable support for backlight/pwm-imx driver
Signed-off-by: Tommaso Merciai
---
configs/imx8mm_evk_defconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/configs/imx8mm_evk_defconfig b/configs/imx8mm_evk_defconfig
index 01395fc7eb..cfba6cc673 100644
--- a/configs/imx8mm_evk_defconfig
Move pwm_imx_get_parms, pwm_id_to_reg functions into pwm-imx.c
and drop off pwm-imx-util.c
Signed-off-by: Tommaso Merciai
---
drivers/pwm/Makefile | 2 +-
drivers/pwm/pwm-imx-util.c | 80 --
drivers/pwm/pwm-imx-util.h | 15 ---
Introduce pwm_dm_imx_get_parms, dm version of pwm_imx_get_parms.
This function get clock rate using clk dm api
Signed-off-by: Tommaso Merciai
---
drivers/pwm/pwm-imx.c | 32 +++-
1 file changed, 31 insertions(+), 1 deletion(-)
diff --git a/drivers/pwm/pwm-imx.c
Separe dm implementation from non dm implementation of pwm-imx
driver using CONFIG_DM_PWM
Signed-off-by: Tommaso Merciai
---
drivers/pwm/pwm-imx.c | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/drivers/pwm/pwm-imx.c b/drivers/pwm/pwm-imx.c
index
Get and enable ipg/per pwms clocks using dm api into imx_pwm_of_to_plat
and imx_pwm_probe driver function
Signed-off-by: Tommaso Merciai
---
drivers/pwm/pwm-imx.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/pwm/pwm-imx.c b/drivers/pwm/pwm-imx.c
Add clocks support for the PWM controllers. This is ported from
Linux v5.17-rc8.
Signed-off-by: Tommaso Merciai
---
drivers/clk/imx/clk-imx8mm.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/clk/imx/clk-imx8mm.c b/drivers/clk/imx/clk-imx8mm.c
index
Add pwm_regs struct for i.MX8MM SOC
Signed-off-by: Tommaso Merciai
---
arch/arm/include/asm/arch-imx8m/imx-regs.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/include/asm/arch-imx8m/imx-regs.h
b/arch/arm/include/asm/arch-imx8m/imx-regs.h
index 57a95de1b8..f31f54ad0c
Add pwm control registers fields defines into imx-regs.h:
- prescaler
- dozeen
- waiten
- dbgen
- clksrc_ipg_high
- clksrc_ipg, en field
References:
- iMX8MMRM.pdf p 3884
Signed-off-by: Tommaso Merciai
---
arch/arm/include/asm/arch-imx8m/imx-regs.h | 8
1 file changed, 8
1 - 100 of 166 matches
Mail list logo
