Re: [PATCH RFC v2 03/11] ti: etype: sysfw: Add entry type for sysfw

Hi Roger, On 31/05/22 14:14, Roger Quadros wrote: On 06/05/2022 07:37, Neha Malcom Francis wrote: For K3 devices that require a sysfw image, add entry for SYSFW. It can 'can' or 'should'? For binman, 'sysfw' and 'dm' (added in patch 4) are just binary blobs. correct? Why can't you just

Re: [PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3

Hi Roger, On 31/05/22 13:51, Roger Quadros wrote: Hi, On 06/05/2022 07:37, Neha Malcom Francis wrote: Devices that belong to the K3 architecture require SYSFW which is a FIT image consisting of a signed system firmware image and board config binaries. Board config binaries are needed to

Re: [PATCH 1/3] EFI: Populate descriptor_count value only when image_info_size is not zero

On 5/31/22 09:15, Sughosh Ganu wrote: The GetImageInfo function of the Firmware Mangement Protocol(FMP) gets called initially to query the size of the image descriptor array that would have to be allocated. During this call, the rest of the function arguments, specifically pointers might be

efi_firmware_raw_get_image_info and efi_firmware_fit_get_image_info

Hello Sughosh, I can't see any difference between efi_firmware_raw_get_image_info() and efi_firmware_fit_get_image_info(). Shouldn't we replace them by a single function to avoid maintaining duplicate code? Best regards Heinrich

Re: [PATCH] riscv: cpu: set gp before board_init_f_init_reserve

On Fri, May 20, 2022 at 02:41:17PM +0300, Nikita Shubin wrote: > From: Nikita Shubin > > Restore global pointer before board_init_f_init_reserve call, > as "a0" can be set in harts_early_init call and we end up with > invalid global pointer. > > Signed-off-by: Nikita Shubin > --- >

[PATCH 1/1] riscv: ae350: Fix XIP config boot failure

The booting flow is SPL -> OpenSBI -> U-Boot. The boot hart may change after OpenSBI and may not always be hart0, so wrap the related branch instruction with M-MODE. Current DTB setup for XIP is not valid. There is no chance for CONFIG_SYS_FDT_BASE, the DTB address used in XIP mode, to be

Re: [PATCH] efi_loader: disk: allow blk devices even without UCLASS_PARTITION

Hi Simon, On Thu, May 19, 2022 at 02:11:02PM +0900, AKASHI Takahiro wrote: > Hi Simon, > > On Mon, May 09, 2022 at 02:33:10PM +0900, AKASHI Takahiro wrote: > > Simon, > > > > On Thu, Apr 28, 2022 at 12:43:03PM +0200, Heinrich Schuchardt wrote: > > > On 4/28/22 06:49, AKASHI Takahiro wrote: > >

Re: [PATCH v5 07/12] efi_loader: disk: a helper function to create efi_disk objects from udevice

Hi Neil, On Thu, May 19, 2022 at 02:04:53PM +0900, AKASHI Takahiro wrote: > On Wed, May 18, 2022 at 11:23:32AM +0200, Neil Armstrong wrote: > > On 19/04/2022 03:05, AKASHI Takahiro wrote: > > > Add efi_disk_probe() function. > > > This function creates an efi_disk object for a raw disk device >

Re: [PATCH 2/2] efi: test/py: authenticate fit capsules

On Tue, May 31, 2022 at 09:55:34AM +0200, Vincent Stehl?? wrote: > Add support for the authentication of UEFI capsules containing FIT images. Thank you for adding this enhancement. Sughosh could and should have done it from the beginning. > The authentication code is moved out of the function

Re: [PATCH v7 2/7] fpga: add fit_fpga_load function

Hi Michal, On Mon, May 16, 2022 at 5:25 PM Michal Simek wrote: > > > > On 5/9/22 15:34, Adrian Fiergolski wrote: > > Michal, > > > > On 09.05.2022 15:28, Oleksandr Suvorov wrote: > >> Hi Adrian, > >> > >> On Mon, May 9, 2022 at 2:35 PM Adrian Fiergolski > >> wrote: > >>> Hi Oleksandr, > >>> >

[PATCH v8 13/14] fpga: zynqmp: support loading authenticated images

Add supporting new compatible string "u-boot,zynqmp-fpga-ddrauth" to handle loading authenticated images (DDR). Based on solution by Jorge Ramirez-Ortiz Signed-off-by: Oleksandr Suvorov --- (no changes since v1) boot/Kconfig | 4 ++--

[PATCH v8 11/14] fpga: zynqmp: optimize zynqmppl_load() code

Optimize function code preparing to add secure bitstream types support. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) drivers/fpga/zynqmppl.c | 27 +-- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/drivers/fpga/zynqmppl.c

[PATCH v8 14/14] fpga: zynqmp: support loading encrypted bitfiles

From: Adrian Fiergolski Add supporting new compatible string "u-boot,zynqmp-fpga-enc" to handle loading encrypted bitfiles. This feature requires encrypted FSBL,as according to UG1085: "The CSU automatically locks out the AES key, stored in either BBRAM or eFUSEs, as a key source to the AES

[PATCH v8 12/14] fpga: zynqmp: add bitstream compatible checking

Check whether the FPGA ZynqMP driver supports the given bitstream image type. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) drivers/fpga/zynqmppl.c | 27 +++ 1 file changed, 27 insertions(+) diff --git a/drivers/fpga/zynqmppl.c b/drivers/fpga/zynqmppl.c

[PATCH v8 09/14] spl: fit: pass real compatible flags to fpga_load()

Convert taken FPGA image "compatible" string to a binary compatible flag and pass it to an FPGA driver. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) common/spl/spl_fit.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/common/spl/spl_fit.c

[PATCH v8 10/14] fpga: xilinx: pass compatible flags to load() callback

These flags may be used to check whether an FPGA driver is able to load a particular FPGA bitstream image. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) drivers/fpga/spartan2.c | 2 +- drivers/fpga/spartan3.c | 2 +- drivers/fpga/versalpl.c | 2 +- drivers/fpga/virtex2.c | 2 +-

[PATCH v8 08/14] fpga: pass compatible flags to fpga_load()

These flags may be used to check whether an FPGA driver is able to load a particular FPGA bitstream image. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) boot/image-board.c| 4 ++-- cmd/fpga.c| 8 common/spl/spl_fit.c | 6 -- drivers/fpga/fpga.c | 5

[PATCH v8 07/14] fpga: xilinx: pass compatible flags to xilinx_load()

This flag is used to check whether a Xilinx FPGA driver is able to load a particular FPGA bitstream image. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) drivers/fpga/fpga.c | 2 +- drivers/fpga/xilinx.c | 2 +- include/xilinx.h | 2 +- 3 files changed, 3 insertions(+), 3

[PATCH v8 06/14] fpga: add fpga_compatible2flag

Add a "compatible" string to binary flag converter, which uses a callback str2flag() of given FPGA driver if available. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) drivers/fpga/fpga.c | 26 ++ include/fpga.h | 1 + 2 files changed, 27 insertions(+)

[PATCH v8 05/14] fpga: zynqmp: add str2flags call

Add a call to convert FPGA "compatible" string to a binary flag. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) drivers/fpga/zynqmppl.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/fpga/zynqmppl.c b/drivers/fpga/zynqmppl.c index 8ff12bf50a0..0ffcff0c148

[PATCH v8 04/14] fpga: xilinx: add bitstream flags to driver desc

Store a set of supported bitstream types in xilinx_desc structure. It will be used to determine whether an FPGA image is able to be loaded with a given driver. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) include/versalpl.h | 2 +- include/xilinx.h | 5 +

[PATCH v8 03/14] fpga: xilinx: add missed identifier names

Function definition arguments should also have identifier names. Add missed ones to struct xilinx_fpga_op callbacks, unifying code. Signed-off-by: Oleksandr Suvorov --- (no changes since v1) include/xilinx.h | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git

[PATCH v8 01/14] Prepare v2022.07-rc3

From: Tom Rini Signed-off-by: Tom Rini Signed-off-by: Oleksandr Suvorov --- (no changes since v1) Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 107685e82a0..61927f8918b 100644 --- a/Makefile +++ b/Makefile @@ -3,7 +3,7 @@ VERSION =

[PATCH v8 02/14] fpga: add option for loading FPGA secure bitstreams

It allows using this feature without enabling the "fpga loads" command. Signed-off-by: Oleksandr Suvorov Tested-by: Ricardo Salveti Co-developed-by: Adrian Fiergolski Signed-off-by: Adrian Fiergolski --- (no changes since v1) cmd/Kconfig | 3 ++- drivers/fpga/Kconfig| 14

[PATCH v8 00/14] fpga: zynqmp: Adding support of loading authenticated images

This patchset introduces support for the authenticated and encrypted FPGA images on ZynqMP boards, besides that introducing common way to pass the compatible property to any fpga driver. It bases on the initial work by Jorge Ramirez-Ortiz

Re: Pull request for efi-2022-07-rc4-3

On Tue, May 31, 2022 at 06:57:18PM +0200, Heinrich Schuchardt wrote: > Dear Tom, > > this replaces pull request for efi-2022-07-rc4-2. > > The following changes since commit 4fe629d2e8bbda5f265e870d771b92be26e885f6: > > Merge https://source.denx.de/u-boot/custodians/u-boot-riscv >

Re: [PATCH v6 0/2] sf: Check protection before writing/erasing flash

On Sat, May 28, 2022 at 02:07:17PM +0200, Jan Kiszka wrote: > On 02.03.22 15:01, Jan Kiszka wrote: > > Changes in v6: > > - fixed embarrassingly inverted logic in unlock check > >(and properly tested it this time) > > > > Changes in v5: > > - adjust unused is_locked callback to our

[PATCH v2 14/14] cpu: add CPU driver for microblaze

Add a basic CPU driver that retrieves information about the microblaze CPU core. cpu_ops handlers are implemented so that the "cpu" command can work properly: U-Boot-mONStR> cpu list 0: cpu@0 MicroBlaze @ 50MHz, Rev: 11.0, FPGA family: zynq7000 U-Boot-mONStR> cpu detail 0: cpu@0

[PATCH v2 12/14] microblaze: Kconfig: introduce XILINX_MICROBLAZE0_FPGA_FAMILY option

Provide a static Kconfig value for the target FPGA archtitecture, as it is done in Linux. The cpu-uclass driver will cross-check it with the value read from PVR10 register. Signed-off-by: Ovidiu Panait --- Changes in v2: - New patch. board/xilinx/microblaze-generic/Kconfig | 8 1

[PATCH v2 13/14] microblaze: add support for handling PVR data

Add helper code for PVR (Processor Version Register) data handling. It will be used by the UCLASS_CPU driver to populate cpuinfo fields at runtime. Signed-off-by: Ovidiu Panait --- Changes in v2: - New patch. arch/microblaze/cpu/Makefile| 1 + arch/microblaze/cpu/pvr.c

[PATCH v2 10/14] microblaze: cache: introduce cpuinfo structure

Introduce a minimal cpuinfo structure to hold cache related info. The instruction/data cache size and cache line size are initialized early in the boot to default Kconfig values. They will be overwritten with data from PVR/dtb if the microblaze UCLASS_CPU driver is enabled. The cpuinfo struct was

[PATCH v2 09/14] microblaze: cache: introduce flush_cache_all()

All flush_cache() calls in microblaze code are supposed to flush the entire instruction and data caches, so introduce flush_cache_all() helper to handle this. Also, provide implementations for flush_dcache_all() and invalidate_icache_all() so that icache and dcache u-boot commands can work.

[PATCH v2 08/14] microblaze: cache: introduce Kconfig options for icache/dcache sizes

Replace XILINX_DCACHE_BYTE_SIZE macro with two Kconfig symbols for instruction and data caches sizes, respectively: CONFIG_XILINX_MICROBLAZE0_ICACHE_SIZE CONFIG_XILINX_MICROBLAZE0_DCACHE_SIZE Also, get rid of the hardcoded value in icache_disable(). Signed-off-by: Ovidiu Panait --- Changes in

[PATCH v2 11/14] microblaze: cache: introduce flush_dcache_range()

Align microblaze with the other architectures and provide an implementation for flush_dcache_range(). Also, remove the microblaze exception in drivers/core/device.c. Signed-off-by: Ovidiu Panait --- Changes in v2: - Added debug message for invalid range. arch/microblaze/cpu/cache.c | 11

[PATCH v2 07/14] microblaze: cache: split flush_cache() function

Factor out icache/dcache components from flush_cache() function. Call the newly added __flush_icache()/__flush_dcache() functions inside icache_disable() and dcache_disable(), respectively. There is no need to flush both caches when disabling a particular cache type. Signed-off-by: Ovidiu Panait

[PATCH v2 06/14] microblaze: cache: improve icache Kconfig options

Replace CONFIG_ICACHE with a Kconfig option more limited in scope - XILINX_MICROBLAZE0_USE_WIC. It should be enabled if the processor supports the "wic" (Write to Instruction Cache) instruction. It will be used to guard "wic" invocations in microblaze cache code. Signed-off-by: Ovidiu Panait ---

[PATCH v2 05/14] microblaze: cache: improve dcache Kconfig options

Replace CONFIG_DCACHE with a Kconfig option more limited in scope - XILINX_MICROBLAZE0_USE_WDC. It should be enabled if the processor supports the "wdc" (Write to Data Cache) instruction. It will be used to guard "wdc" invocations in microblaze cache code. Also, drop all ifdefs around

[PATCH v2 03/14] microblaze: start.S: remove unused code

in16/out16 routines seem to not be used anywhere in microblaze code, so remove them. Signed-off-by: Ovidiu Panait --- (no changes since v1) arch/microblaze/cpu/start.S | 33 - 1 file changed, 33 deletions(-) diff --git a/arch/microblaze/cpu/start.S

[PATCH v2 04/14] microblaze: cache: replace XILINX_USE_DCACHE -> CONFIG_DCACHE

XILINX_USE_DCACHE macro was removed in 7556fa09e0e ("microblaze: Simplify cache handling"), but it was still used in a couple of places. Replace those occurences with CONFIG_DCACHE. Signed-off-by: Ovidiu Panait --- (no changes since v1) arch/microblaze/cpu/cache.c | 2 +-

[PATCH v2 01/14] cmd: cpu: migrate cpu command to U_BOOT_CMD_WITH_SUBCMDS()

Migrate cpu command to use U_BOOT_CMD_WITH_SUBCMDS() helper macro, to reduce duplicated code. This also fixes the cpu command on boards that enable CONFIG_NEEDS_MANUAL_RELOC. Signed-off-by: Ovidiu Panait --- NOTE: this series depends on the following "events" patch:

[PATCH v2 02/14] cpu-uclass: relocate ops pointers for CONFIG_NEEDS_MANUAL_RELOC

Relocate cpu_ops pointers when CONFIG_NEEDS_MANUAL_RELOC is enabled. The (gd->flags & GD_FLG_RELOC) check was added to make sure the reloc_done logic works for drivers that use DM_FLAG_PRE_RELOC. Signed-off-by: Ovidiu Panait --- Changes in v2: - New patch. drivers/cpu/cpu-uclass.c | 30

Re: Pull request for efi-2022-07-rc4-3

On Tuesday 31 May 2022 18:57:18 Heinrich Schuchardt wrote: > Dear Tom, > > this replaces pull request for efi-2022-07-rc4-2. > > The following changes since commit 4fe629d2e8bbda5f265e870d771b92be26e885f6: > > Merge https://source.denx.de/u-boot/custodians/u-boot-riscv > (2022-05-27 08:50:42

Pull request for efi-2022-07-rc4-3

Dear Tom, this replaces pull request for efi-2022-07-rc4-2. The following changes since commit 4fe629d2e8bbda5f265e870d771b92be26e885f6: Merge https://source.denx.de/u-boot/custodians/u-boot-riscv (2022-05-27 08:50:42 -0400) are available in the Git repository at:

[PATCH] net: enetc: unregister mdiobus

If the device fails to probe - for example, when there is no ethaddr set - then the private data is automatically freed but the mdiobus remains registered. Fixes: 1e354cb39314 ("drivers: net: fsl_enetc: register internal MDIO bus") Signed-off-by: Michael Walle --- This actually causes the

Re: Pull request for efi-2022-07-rc4-2

On Mon, May 30, 2022 at 10:56:13AM +0200, Pali Rohár wrote: > On Monday 30 May 2022 09:32:53 Masahisa Kojima wrote: > > Hi Heinrich, > > > > On Mon, 30 May 2022 at 01:16, Heinrich Schuchardt > > wrote: > > > > > > Dear Tom, > > > > > > this replaces pull request for efi-2022-07-rc4. > > > > > >

[PATCH 1/3] spl: Move all VPL, TPL and PowerPC specific CONFIG options to separate files

- Move all PowerPC (and some shared with Layerscape) options to common/spl/Kconfig.nxp - Move all other TPL related options to common/spl/Kconfig.tpl - Move all VPL related options to common/spl/Kconfig.vpl This makes the whole of common/spl/Kconfig slightly more readable. Signed-off-by: Tom

[PATCH 3/3] spl: Rework and tighten some dependencies

- In a few places, add missing "depends on" that can be implied from the option name (i.e. SPL_DM_xxx depends on SPL_DM). - Make less use of "if SPL_xxx ... endif" clauses as most of the time this reads better as depends on. In the case of UBI however, move it all to a sub-menu. - Rework

[PATCH 2/3] spl: Rework Kconfig to be more menu driven

Make it so that all of SPL, TPL and VPL are proper menus hidden behind a gating question. Signed-off-by: Tom Rini --- common/spl/Kconfig | 54 +++--- 1 file changed, 22 insertions(+), 32 deletions(-) diff --git a/common/spl/Kconfig b/common/spl/Kconfig

[0/3] spl: Start cleaning up common/spl/Kconfig

Hey all, This series depends on: https://patchwork.ozlabs.org/project/uboot/list/?series=299963 https://patchwork.ozlabs.org/project/uboot/list/?series=300980 https://patchwork.ozlabs.org/project/uboot/list/?series=301665 https://patchwork.ozlabs.org/project/uboot/list/?series=302137

[PATCH v2 11/14] reset: scmi: support SCMI multi-channel

Update SCMI reset controller driver to get its assigned SCMI channel during initialization. This change allows SCMI reset domain protocol to use a dedicated channel when defined in the DT. The reference is saved in SCMI reset controller driver private data. Signed-off-by: Etienne Carriere ---

[PATCH v2 13/14] power: regulator: scmi: simplify scmi_voltd_set_enable()

Simplify scmi_voltd_set_enable() exit sequence. Cc: Jaehoon Chung Signed-off-by: Etienne Carriere --- No change since v1. --- drivers/power/regulator/scmi_regulator.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/power/regulator/scmi_regulator.c

[PATCH v2 12/14] power: regulator: scmi: support SCMI multi-channel

Update SCMI regulator controller driver to get its assigned SCMI channel during initialization. This change allows SCMI voltage domain protocol to use a dedicated channel when defined in the DT. The reference is saved in SCMI regulator controller driver private data. Cc: Jaehoon Chung

[PATCH v2 14/14] firmware: scmi: use multi channel in mailbox, optee and smccc agents

Updates .process_msg operators of the SCMI transport drivers that supports multi-channel to use it now that drivers do provide the reference through channel argument. These are the mailbox agent, the optee agent and the smccc agent. Signed-off-by: Etienne Carriere --- No change since v1. ---

[PATCH v2 10/14] clk: scmi: support SCMI multi-channel

Update SCMI clock driver to get its assigned SCMI channel during initialization. This change allows SCMI clock protocol to use a dedicated channel when defined in the DT. The reference is saved in SCMI clock driver private data. Cc: Lukasz Majewski Cc: Sean Anderson Signed-off-by: Etienne

[PATCH v2 06/14] firmware: scmi: add multi-channel support

Adds resources for SCMI protocols to possibly use a dedicated SCMI channel instead of the default channel allocated by the SCMI agent during initialization. As per DT binding documentation, some SCMI transports can define a specific SCMI communication channel for given SCMI protocols. It allows

[PATCH v2 09/14] firmware: scmi: optee transport: implement multi-channel

Implements multi SCMI channel support in OP-TEE SCMI transport. An SCMI protocol may use a dedicated channel, specified by the DT. Signed-off-by: Etienne Carriere --- No change since v1. --- drivers/firmware/scmi/optee_agent.c | 76 - 1 file changed, 63

[PATCH v2 07/14] firmware: scmi: mailbox transport: implement multi-channel

Updates SCMI mailbox transport driver to get SCMI channel reference at initialization and use when posting SCMI messages. Signed-off-by: Etienne Carriere --- No change since v1. --- drivers/firmware/scmi/mailbox_agent.c | 63 --- 1 file changed, 57 insertions(+), 6

[PATCH v2 08/14] firmware: scmi: smccc transport: implement multi-channel

Updates SCMI SMCCC transport driver to get SCMI channel reference at initialization and use when posting SCMI messages. Signed-off-by: Etienne Carriere --- No change since v1. --- drivers/firmware/scmi/smccc_agent.c | 54 +++-- 1 file changed, 52 insertions(+), 2

[PATCH v2 04/14] firmware: scmi: prepare uclass to pass channel reference

Changes SCMI transport operator ::process_msg to pass the SCMI channel reference provided by caller SCMI protocol device. Signed-off-by: Etienne Carriere --- No change since v1. --- drivers/firmware/scmi/mailbox_agent.c | 4 +++- drivers/firmware/scmi/optee_agent.c| 4 +++-

[PATCH v2 05/14] firmware: scmi: factorize scmi transport look up

Defines local helper function find_scmi_transport_device() with the instructions to find the SCMI transport device from a SCMI protocol device. Cc: Patrick Delaunay Signed-off-by: Etienne Carriere --- No change since v1. --- drivers/firmware/scmi/scmi_agent-uclass.c | 26

[PATCH v2 03/14] firmware: scmi: prepare scmi uclass API to multi-channel

Changes SCMI driver API function devm_scmi_process_msg() to add an SCMI channel reference argument for when SCMI agent supports SCMI protocol specific channels. First argument of devm_scmi_process_msg() is also change to point to the caller SCMI protocol device rather than its parent device (the

[PATCH v2 02/14] firmware: scmi: optee: fix inline description of PTA_SCMI_CMD_GET_CHANNEL

Removes inaccurate inline description of OP-TEE SCMI PTA command PTA_SCMI_CMD_GET_CHANNEL. Signed-off-by: Etienne Carriere --- No change since v1. --- drivers/firmware/scmi/optee_agent.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/firmware/scmi/optee_agent.c

[PATCH v2 01/14] firmware: scmi: optee: use TEE shared memory for SCMI messages

Changes implementation when using TEE dynamically allocated shared memory to synchronize with the Linux implementation where the legacy SMT protocol cannot be used with such memory since it is expected from device mapped memory whereas OP-TEE shared memory is cached and hence should not be

[PATCH v2 00/14] SCMI multi-channel and optee shm

Dear all, This series implements 2 features in driver/firmware/scmi. First, a single change adds support for SCMI OP-TEE transport to use OP-TEE native shared memory. See the 1st patch in this series: "firmware: scmi: optee: use TEE shared memory for SCMI messages". Then come changes for

RE: [PATCH v1] board: apalis_t30/tk1/colibri_t20/t30: integrate mac address via dt

Thanks, Marcel. Been OOTO, I'll take a look and get a PR up this week. -Original Message- From: Marcel Ziswiler Sent: Wednesday, May 25, 2022 1:20 AM To: u-boot@lists.denx.de Cc: Tom Warren Subject: Re: [PATCH v1] board: apalis_t30/tk1/colibri_t20/t30: integrate mac address via dt

Re: [PATCH v3 01/13] serial: sandbox: Fix buffer underflow in puts

On 5/30/22 6:00 AM, Andrew Scull wrote: > Fix the buffer underflow that would occur if puts is called with length > of zero. > > Fixes: efa51f2bd64 ("serial: sandbox: Implement puts") > Cc: Sean Anderson > Cc: Simon Glass > --- > drivers/serial/sandbox.c | 2 +- > 1 file changed, 1

Re: [u-boot PATCH 3/3] k3-am642-evm-u-boot: Use binman to generate u-boot.img and tispl.bin

On 5/31/22 12:06 AM, Roger Quadros wrote: Hi, On 27/05/2022 20:50, Alper Nebi Yasak wrote: On 26/05/2022 17:15, Tom Rini wrote: On Thu, May 26, 2022 at 10:28:45AM +0300, Roger Quadros wrote: Any thoughts on how to get the new ti-secure etype work with atf-bl31 and tee-os etypes so that it

[PATCH] arm: dts: socfpga: stratix10: Add freeze controller node

From: Dinesh Maniyam The freeze controller is required for FPGA partial reconfig. This node is disable on default. Enable this node via u-boot fdt command when needed. Signed-off-by: Yau Wai Gan Signed-off-by: Dinesh Maniyam --- arch/arm/dts/socfpga_stratix10_socdk-u-boot.dtsi | 11

[PATCH] arm: dts: socfpga: agilex: Add freeze controller node

From: Dinesh Maniyam The freeze controller is required for FPGA partial reconfig. This node is disable on default. Enable this node via u-boot fdt command when needed. Signed-off-by: Yau Wai Gan Signed-off-by: Dinesh Maniyam --- arch/arm/dts/socfpga_agilex_socdk-u-boot.dtsi | 11 ++-

RE: [PATCH] fpga: intel_sdm_mb: Add checking for INTEL_SIP_SMC_STATUS_BUSY (1)

> -Original Message- > From: Chee, Tien Fong > Sent: Tuesday, 24 May 2022 6:29 pm > To: Maniyam, Dinesh ; u-boot@lists.denx.de > Cc: Michal Simek ; Hea, Kok Kiang > ; Gan, Yau Wai ; Kho, Sin > Hui ; Lokanathan, Raaj ; > Ley Foon Tan > Subject: RE: [PATCH] fpga: intel_sdm_mb: Add checking

[PATCH v3] fpga: intel_sdm_mb: Add checking for INTEL_SIP_SMC_STATUS_BUSY (1)

From: Dinesh Maniyam Status busy means transfer is accepted but SDM does not have more freed buffer. It is not an error. Continue process the data if receive OK or BUSY status. Signed-off-by: Dinesh Maniyam --- v2->v3 -Copyright year updated and alignment adjusted. ---

[PATCH v6] board: purism: add the Purism Librem5 phone

Initial commit of Librem5 u-boot and SPL All of the pre-requisite patches for this board are now upstream or in review. Changes since v5: Proper handling of the Display Port firmware for CI builds Update the DP section of the docs Changes since v4: Include imx8mq-u-boot.dtsi instead of adding

[PATCH v2] fpga: intel_sdm_mb: Add checking for INTEL_SIP_SMC_STATUS_BUSY (1)

From: Dinesh Maniyam Status busy means transfer is accepted but SDM does not have more freed buffer. It is not an error. Continue process the data if receive OK or BUSY status. Signed-off-by: Ley Foon Tan Signed-off-by: Dinesh Maniyam --- v1 -> v2 - change to "OK or Busy status in commit

Re: [PATCH RFC v2 11/11] ti: dtsi: j721e: Use binman to package tispl.bin

On 06/05/2022 07:37, Neha Malcom Francis wrote: > Explicit make commands were earlier used to generate tispl.bin image, > now it is replaced using binman. > > Binman picks up and packages entries according to the description of > entries given in the binman node in the device tree. The make

Re: [PATCH v2 2/2] arm: k3: j721e: add dynamic sf bus override support for j721e

Hi Vaishnav, On 11/05/22 11:33AM, Vaishnav Achath wrote: > implement overrides for spl_spi_boot_bus() and spl_spi_boot_cs() > lookup functions according to bootmode selection, so as to support > both QSPI and OSPI boot using the same build. > > Signed-off-by: Vaishnav Achath > --- >

Re: [PATCH RFC v2 09/11] ti: x509: Remove shell script used for signing

On 06/05/2022 07:37, Neha Malcom Francis wrote: > Earlier the k3_gen_x509_cert.sh was used for signing binaries with the > x509 certificate for Texas Instruments K3 architecture devices. Since > the signing process is handled by x509 etype now, there is no more > requirement for this script,

Re: [PATCH RFC v2 08/11] ti: tispl.bin: Removed script that packages tispl.bin

On 06/05/2022 07:37, Neha Malcom Francis wrote: > As tispl.bin is to be packaged (with ATF, OPTEE, DM and A72 SPL) using > binman, the shell script k3_fit_atf.sh is no longer needed. Removing This is not true until you have migrated all K3 platforms to use binman. So let's leave this script

Re: [PATCH RFC v2 07/11] ti: tiboot3.bin: Remove tiboot3.bin target from makefile

On 06/05/2022 07:37, Neha Malcom Francis wrote: > Intention of patch is to move the signing and packaging of tiboot3.bin > image to binman, thus removing target from makefile. > > Also deleting k3_gen_x509_cert.sh which was earlier used to sign a > binary associated with K3 devices with x509

[PATCH v1] spi: nuvoton: add NPCM PSPI controller driver

Add Nuvoton NPCM BMC Peripheral SPI controller driver. NPCM750 include two general-purpose SPI interface. Signed-off-by: Jim Liu --- drivers/spi/Kconfig | 5 + drivers/spi/Makefile| 1 + drivers/spi/npcm_pspi.c | 226 3 files changed, 232

Re: [PATCH RFC v2 05/11] ti: etype: x509: Add etype for x509 certificate for K3 devices

On 06/05/2022 07:37, Neha Malcom Francis wrote: > K3 devices x509 certificate added to certain binaries that allows ROM to what binaries? > validate the integrity of the image. Etype that generates an x509 > certificate depending on boot flow added. Could you please explain in more detail as

Re: [PATCH v2 1/2] common: spl: spl_spi: add support for dynamic override of sf bus

On 11/05/22 11:33AM, Vaishnav Achath wrote: > Currently the SPI flash to load from is defined through the compile > time config CONFIG_SF_DEFAULT_BUS and CONFIG_SF_DEFAULT_CS, this > prevents the loading of binaries from different SPI flash using the > same build.E.g. supporting QSPI flash boot

Re: [PATCH RFC v2 03/11] ti: etype: sysfw: Add entry type for sysfw

On 06/05/2022 07:37, Neha Malcom Francis wrote: > For K3 devices that require a sysfw image, add entry for SYSFW. It can 'can' or 'should'? For binman, 'sysfw' and 'dm' (added in patch 4) are just binary blobs. correct? Why can't you just use blob entry type? > contain system firmware image

[PATCH] distroboot: Fix ubifs

Fix multiple issues in ubifs distroboot code: U-Boot supports attaching only one MTD device as UBI at the time. So always call 'ubifsmount ubi0:${bootubivol}' for mounting UBI volume ${bootubivol}. Usage of 'ubi${devnum}' is incorrect as 'ubi part' command attach MTD device always as UBI device

Re: [PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3

Hi, On 06/05/2022 07:37, Neha Malcom Francis wrote: > Devices that belong to the K3 architecture require SYSFW which is a FIT > image consisting of a signed system firmware image and board config > binaries. > > Board config binaries are needed to bring up SYSFW during U-Boot SPL > startup. The

[PATCH 2/2] efi: test/py: authenticate fit capsules

Add support for the authentication of UEFI capsules containing FIT images. The authentication code is moved out of the function handling raw images into a new function efi_firmware_capsule_authenticate(). The special case for the FMP header coming from edk2 tools is preserved. There is no

[PATCH 1/2] test/py: efi_capsule: repair image authentication test

Repair the python tests for authenticated EFI capsules, which can be run with sandbox_defconfig plus CONFIG_EFI_CAPSULE_AUTHENTICATE=y. - Account for the reset changes done by commit 3e6f81000672 ("efi_loader: test/py: Reset system after capsule update on disk"). - Fix the capsule GUID typo

[PATCH 3/3] EFI: Update the documentation to reflect the correct value of OsIndications

The OsIndications is a 64 bit variable, and the current code expects the value of the variable to be 64 bit. Update the documentation to reflect this fact. Signed-off-by: Sughosh Ganu --- doc/develop/uefi/uefi.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/3] EFI: Do not read OsIndications variable if EFI_IGNORE_OSINDICATIONS is enabled

The EFI_IGNORE_OSINDICATIONS config symbol was introduced as a mechanism to have capsule updates work even on platforms where the SetVariable runtime service was not supported. The current logic requires the OsIndications variable to have been set to a 64 bit value even when the

[PATCH 1/3] EFI: Populate descriptor_count value only when image_info_size is not zero

The GetImageInfo function of the Firmware Mangement Protocol(FMP) gets called initially to query the size of the image descriptor array that would have to be allocated. During this call, the rest of the function arguments, specifically pointers might be passed as NULL. Do not populate the

[PATCH 0/3] EFI: Miscellaneous capsule update fixes

The following set of patches fix separate issues relating to the capsule update code. The first patch moves the setting of the descriptor_count parameter to the GetImageInfo function after assertion of a non zero image descriptor buffer. The second patch enables capsule update to proceed even