Re: [PATCH v4 0/2] Fix Android A/B backup

Hi, On Tue, 12 Mar 2024 07:57:27 -0500, Colin McAllister wrote: > - Addresses compiler error due to missing semicolon > - Removes use of preprocessor macros with ANDROID_AB_BACKUP_OFFSET > > Bug was found by noticing a semicolon was missing and not causing a > compiler error when

[PATCH v3 3/6] usb: xhci: Abort transfers with unallocated rings

From: Janne Grunau Discovered while trying to use the second interface in the USB keyboard driver necessary on Apple USB keyboards. Reviewed-by: Marek Vasut Reviewed-by: Neal Gompa Signed-off-by: Janne Grunau --- drivers/usb/host/xhci-ring.c | 5 + 1 file changed, 5 insertions(+) diff

Re: [PATCH v4] cmd: mtd: OTP access support

Hi Arseniy On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov wrote: > > Add access to OTP region. It supports info, dump, write and lock > operations. Usage example: > > 'mtd otpread nand0 u 0 1024' - dump 1024 bytes of user area starting > from offset 0 of device 'nand0'. > > 'mtd otpwrite nand0

Re: [PATCH v3 2/6] usb: xhci: Set up endpoints for the first 2 interfaces

On 3/22/24 08:47, Janne Grunau via B4 Relay wrote: From: Janne Grunau The xhci driver currently only does the necessary initialization for endpoints found in the first interface descriptor. Apple USB keyboards (released 2021) use the second interface descriptor for the HID keyboard boot

[PATCH v3 0/6] USB keyboard improvements for asahi / desktop systems

Apple USB Keyboards from 2021 need quirks to be useable. The boot HID keyboard protocol is unfortunately not described in the first interface descriptor but the second. This needs several changes. The USB keyboard driver has to look at all (2) interface descriptors during probing. Since I didn't

[PATCH v3 4/6] usb: Add environment based device ignorelist

From: Janne Grunau Add the environment variable "usb_ignorelist" to prevent USB devices listed in it from being bound to drivers. This allows to ignore devices which are undesirable or trigger bugs in u-boot's USB stack. Devices emulating keyboards are one example of undesirable devices as

[PATCH v3 6/6] usb: kbd: Add probe quirk for Apple and Keychron keyboards

From: Janne Grunau Those keyboards do not return the current device state. Polling will timeout unless there are key presses. This is not a problem during operation but the initial device state query during probing will fail. Skip this step in usb_kbd_probe_dev() to make these devices useable.

[PATCH v3 2/6] usb: xhci: Set up endpoints for the first 2 interfaces

From: Janne Grunau The xhci driver currently only does the necessary initialization for endpoints found in the first interface descriptor. Apple USB keyboards (released 2021) use the second interface descriptor for the HID keyboard boot protocol. To allow USB drivers to use endpoints from other

[PATCH v3 5/6] usb: kbd: support Apple Magic Keyboards (2021)

From: Janne Grunau Apple USB keyboards (Magic Keyboard from 2021 (product id 0x029c)) carry the HID keyboard boot protocol on the second interface descriptor. Probe via vendor and product IDs since the class/subclass/protocol match uses the first interface descriptor. Probe the two first

[PATCH v3 1/6] usb: xhci: refactor xhci_set_configuration

From: Janne Grunau In the next step endpoints for multiple interfaces are set up. Move most of the per endpoint initialization to separate function to avoid another identation level. Reviewed-by: Marek Vasut Reviewed-by: Neal Gompa Signed-off-by: Janne Grunau --- drivers/usb/host/xhci.c |

Re: [PATCH 2/5] mmc: zynq-sdhci: refactor tapdelay settings

Hi Venkatesh, we're not using the firmware when running in el3, so that should still work. The sdhci driver needs to know which controller it's operating on and uses the power-domain node for that. I can't add the power domain node without a firmware node (i think?), but the firmware node without

Re: [PATCH v4] cmd: mtd: OTP access support

Hi Arseniy On Fri, Mar 22, 2024 at 9:14 AM Arseniy Krasnov wrote: > > Hi, > > On 22.03.2024 11:12, Michael Nazzareno Trimarchi wrote: > > Hi Arseniy > > > > On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov > > wrote: > >> > >> Add access to OTP region. It supports info, dump, write and lock > >>

Re: [PATCH] scripts/Makefile.spl: Use 'sort' in SHRUNK_ARCH_DTB rule

út 19. 3. 2024 v 17:51 odesílatel Tom Rini napsal: > With configs such as "am64x_evm_a53" or "imx8mp_venice" which list > multiple device trees to build we get a warning such as: > scripts/Makefile.spl:578: target 'spl/dts/freescale/' given more than once > in the same rule > > If we sort this

[PATCH 1/2] doc: man-page for itest

Provide a man-page for the itest command. Signed-off-by: Heinrich Schuchardt --- doc/usage/cmd/itest.rst | 113 doc/usage/index.rst | 1 + 2 files changed, 114 insertions(+) create mode 100644 doc/usage/cmd/itest.rst diff --git

[PATCH 2/2] doc: add reference to itest in if man-page

Add a cross reference to the itest command. Fix a typo: %s/Example/Examples/. Signed-off-by: Heinrich Schuchardt --- doc/usage/cmd/if.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/usage/cmd/if.rst b/doc/usage/cmd/if.rst index 6b3dbe7b0a0..813f903a8d8 100644

Re: [PATCH v4] cmd: mtd: OTP access support

Hi, On 22.03.2024 11:12, Michael Nazzareno Trimarchi wrote: > Hi Arseniy > > On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov > wrote: >> >> Add access to OTP region. It supports info, dump, write and lock >> operations. Usage example: >> >> 'mtd otpread nand0 u 0 1024' - dump 1024 bytes of user

Re: [PATCH v4] cmd: mtd: OTP access support

On 22.03.2024 11:17, Michael Nazzareno Trimarchi wrote: > Hi Arseniy > > On Fri, Mar 22, 2024 at 9:14 AM Arseniy Krasnov > wrote: >> >> Hi, >> >> On 22.03.2024 11:12, Michael Nazzareno Trimarchi wrote: >>> Hi Arseniy >>> >>> On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov >>> wrote:

Re: [PATCH] usb: gadget: UMS: fix 64-bit division on ARM32

Hi Caleb, On jeu., mars 21, 2024 at 17:01, Caleb Connolly wrote: > On 21/03/2024 16:48, Mattijs Korpershoek wrote: >> Hi Caleb, >> >> Thank you for the patch. >> >> On jeu., mars 21, 2024 at 15:28, Caleb Connolly >> wrote: >> >>> The patch introducing support for dynamic sector sizes

Re: [PATCH 0/4] arm: meson: Switch to using upstream DT for GXL, GXM, AXG, G12A, G12B & SM1 SoCs

Hi Viacheslav, On 19/03/2024 15:42, Neil Armstrong wrote: Enable OF_UPSTREAM to use upstream DT and add amlogic/ prefix to the DEFAULT_DEVICE_TREE. And thereby directly build DTB from dts/upstream/src/ including *-u-boot.dtsi files from arch/$(ARCH)/dts/ directory and drop redundant files from

Re: [PATCH 1/2] usb: udc: dwc3: Fold board dm_usb_gadget_handle_interrupts() into DWC3 gadget

On jeu., mars 21, 2024 at 20:38, Marek Vasut wrote: > On 3/21/24 11:01 AM, Mattijs Korpershoek wrote: >> Hi Marek, >> >> Thank you for the patch. >> >> On dim., mars 17, 2024 at 05:42, Marek Vasut >> wrote: >> >>> The dm_usb_gadget_handle_interrupts() has no place in board code. Move >>>

Re: [PATCH] rockchip: ringneck-px30: put STM32_RST line in input mode instead of output

Hi Kever, On 2/19/24 10:50, Quentin Schulz wrote: Hi Kever, On 2/18/24 02:14, Kever Yang wrote: Hi Quentin, On 2024/2/9 21:18, Quentin Schulz wrote: From: Quentin Schulz The STM32_RST line is routed to the ATtiny microcontroller PA0/RESET/UPDI pin. By driving the PX30 SoC pin as GPIO

RE: [PATCH v2 6/6] cmd: nand: Add new optional sub-command 'onfi'

Hi Michael, --- I think this command can be really useful. Let try to have more testing on more boards - I managed to test the command on sama7g54-curiosity board. I also forced timing

Re: [PATCH 05/14] initcall: Adjust the failure message and return value

Hi Simon, út 22. 8. 2023 v 5:18 odesílatel Simon Glass napsal: > Move the failure message outside the loop, so it is easier to follow the > code. Avoid swallowing the error code - just pass it along. > > Drop the initcall-list address from the output. This is confusing since > we show two

[PATCH v3 00/20] FWU: Add support for FWU metadata version 2

The following patch series adds support for version 2 of the FWU metadata. The version 2 metadata structure is defined in the latest revision of the FWU specification [1]. The earlier versions of these patches were migrating to a version 2 only support in U-Boot, similar to TF-A. However,

[PATCH v3 01/20] configs: fwu: remove FWU configs for metadata V2 support

Support is to be added in the following commits for the FWU metadata version 2. Disable the FWU feature on platforms that enable it for the V2 addition work. Signed-off-by: Sughosh Ganu --- Changes since V2: None configs/corstone1000_defconfig | 2 -- configs/sandbox64_defconfig

[PATCH v3 02/20] tools: mkfwumdata: fix the size parameter to the fwrite call

The fwrite call returns the number of bytes transferred as part of the write only when the size parameter is 1. Pass the size parameter to the library call as 1 so that the correct number of bytes transferred are returned. Fixes: fdd56bfd3ad ("tools: Add mkfwumdata tool for FWU metadata image")

[PATCH v3 07/20] fwu: metadata: add functions for handling version specific metadata fields

Support is being added in U-Boot for version 2 of the FWU metadata. Support for this version is to co-exist with version 1 support. To achieve this, a common, version agnostic structure has been added to keep information provided by the FWU metadata structure. Add API's to handle the version

[PATCH v3 08/20] fwu: make changes to access version agnostic structure fields

With addition of support for version 2 of the FWU metadata structure, the metadata information is collected into a version agnostic structure. Make changes to the FWU functions so that the information that was earlier obtained by reading the metadata structure is now obtained through this version

[PATCH v3 03/20] drivers: fwu: add the size parameter to the metadata access API's

In version 2 of the metadata structure, the size of the structure cannot be determined statically at build time. The structure is now broken into the top level structure which contains a field indicating the total size of the structure. Add a size parameter to the metadata access API functions to

[PATCH v3 06/20] fwu: metadata: add a version agnostic structure

The FWU specification now has two versions of the FWU metadata structure, and both are to be supported. Introduce a version agnostic structure for storing information about the FWU updatable images. This allows for a split of common version agnostic FWU code and version specific code. The version

[PATCH v3 04/20] drivers: fwu: mtd: allocate buffer for image info dynamically

The FWU metadata access driver for MTD partitioned devices currently uses a statically allocated array for storing the updatable image information. This array depends on the number of banks and images per bank. With migration of the FWU metadata to version 2, these parameters are now obtained at

[PATCH v3 05/20] fwu: metadata: add support for version 2 of the structure

Add support for version 2 of the FWU metadata structure. The top level structure is kept separate through a config symbol. Most of the fields, primarily used for providing information on updatable images are common across the two versions. Also change a few existing structure members used for

[PATCH] board: phytec: phycore_imx8mp.env fix netboot issues

fs +nfsroot=/srv/nfs sd_dev=1 --- base-commit: 86b79cf131b64eadae023a127921893d30503093 change-id: 20240322-phycore_mx8mp_netboot_fixes-337ceb4ba0cc Best regards, -- Yannic Moog

Re: [PATCH] arm64: zynqmp: Also support JTAG as alternative boot mode

On 3/21/24 17:20, Sean Anderson wrote: On 3/20/24 07:18, Michal Simek wrote: if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot mode which is 0. When 0 was used origin(HW) boot mode was used instead. That's why directly fill reg variable with requested boot mode and

[PATCH v2 2/2] arm64: zynqmp: Add MTD partition handling for dfu_alt_info generation

Generate dfu_alt_info generation based on information from MTD partitions. mtd_found_part() is trying to identify MTD partition which code is running from. If partitions are not defined and location is not found it is going to previous behavior. Signed-off-by: Michal Simek --- Changes in v2: -

[PATCH v2 1/2] arm64: zynqmp: Generate desc when SPL_FS_LOAD_PAYLOAD_NAME is valid

Generate description only when CONFIG_SPL_FS_LOAD_PAYLOAD_NAME is not empty. When name is empty there is no reason to generate description for it because it is not aligned with dfu rules. Signed-off-by: Michal Simek --- Changes in v2: - New patch is series coming from discussion at

Re: [PATCH v4 00/11] imx8mp: Enable PCIe/NVMe support

Hi Sumit, On Thu, Mar 21, 2024 at 11:55 AM Sumit Garg wrote: > Changes in v4: > - Incorporated misc comments from Marek and added his review tag. > - Dropped patch #4 (imx8mp: power-domain: Don't power off pd_bus) > since power domain off path is never excercised for DT based devices. > -

[PATCH] spl: riscv: opensbi: fix check of PAYLOAD_ARGS_ADDR

When Falcon Mode is enabled on RISC-V, use CONFIG_VAL to check PAYLOAD_ARGS_ADDR, not CONFIG_IS_ENABLED. Signed-off-by: Randolph --- common/spl/spl_opensbi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/spl/spl_opensbi.c b/common/spl/spl_opensbi.c index

Re: [PATCH v2 6/6] cmd: nand: Add new optional sub-command 'onfi'

HI On Fri, Mar 22, 2024 at 12:46 PM Alexander Dahl wrote: > > Hello Mihai, > > Am Fri, Mar 22, 2024 at 10:02:29AM + schrieb mihai.s...@microchip.com: > > Hi Michael, > > > > --- > > > > I think this command can be really useful. > > Let try

[PATCH v3 16/20] tools: mkfwumdata: add logic to append vendor data to the FWU metadata

The version 2 of the FWU metadata allows for appending opaque vendor specific data to the metadata structure. Add support for appending this data to the metadata. The vendor specific data needs to be provided through a file, passed through a command-line parameter. Make corresponding changes to

[PATCH v3 17/20] test: fwu: make changes to the FWU metadata access test

Make changes to the FWU metadata access tests corresponding to the changes in the FWU metadata access code. Signed-off-by: Sughosh Ganu --- Changes since V2: * Make changes to have the test work with v1 metadata. * Make changes to have the test work with updated logic in fwu code.

[PATCH v3 18/20] doc: fwu: make changes to reflect support for FWU metadata v2

The FWU Update Agent in U-Boot supports both versions of the FWU metadata. Make changes in the documentation to reflect this. Signed-off-by: Sughosh Ganu --- Changes since V2: * Changes to indicate support for both v1 and v2 instead of only v2. doc/board/socionext/developerbox.rst | 7 +--

[PATCH v3 20/20] configs: fwu: re-enable FWU configs

Now that support for FWU metadata version 2 has been added, the feature can be enabled on platforms which had enabled it. A new config symbol for selecting the metadata version for the platform is also being added. Signed-off-by: Sughosh Ganu --- Changes since V2: * Add config symbol for

Re: [PATCH v2 6/6] cmd: nand: Add new optional sub-command 'onfi'

Hello Mihai, Am Fri, Mar 22, 2024 at 10:02:29AM + schrieb mihai.s...@microchip.com: > Hi Michael, > > --- > > I think this command can be really useful. > Let try to have more testing on more boards > >

Re: [PATCH v2 16/24] xlnx: drop dt-binding headers

On 3/21/24 22:03, Caleb Connolly wrote: Drop in favour of dts/upstream Signed-off-by: Caleb Connolly --- include/dt-bindings/clock/xlnx-versal-clk.h| 123 --- include/dt-bindings/clock/xlnx-zynqmp-clk.h| 126

Re: [PATCH v2 24/24] dts: support building all dtb files for a specific vendor

On 3/21/24 22:04, Caleb Connolly wrote: This adjusts OF_UPSTREAM to behave more like the kernel by allowing for all the devicetree files for a given vendor to be compiled. This is useful for Qualcomm in particular as most boards are supported by a single U-Boot build just provided with a

[PATCH v3 12/20] fwu: mtd: get MTD partition specific info from driver

Information about FWU images on MTD partitions is now stored with the corresponding driver instead of a global variable. Get this information from the driver. Signed-off-by: Sughosh Ganu --- Changes since V2: * New patch lib/fwu_updates/fwu_mtd.c | 17 +++-- 1 file changed, 11

[PATCH 00/12] arm: xea: Provide support for different XEA board HW versions

This patch set provides support for different XEA board revisions. Due to very limited SPL size, the board's switch DTB decision is performed very early in u-boot proper; before driver model is set. Adjustments for DTS between revisions are for the u-boot adjustment code (i.e. tweaks due to

Re: [PATCH v2 6/6] cmd: nand: Add new optional sub-command 'onfi'

Hello Michael, Am Fri, Mar 22, 2024 at 12:54:27PM +0100 schrieb Michael Nazzareno Trimarchi: > HI > > On Fri, Mar 22, 2024 at 12:46 PM Alexander Dahl wrote: > > > > Hello Mihai, > > > > Am Fri, Mar 22, 2024 at 10:02:29AM + schrieb mihai.s...@microchip.com: > > > Hi Michael, > > > > > >

Re: [PATCH v2 6/6] cmd: nand: Add new optional sub-command 'onfi'

HI On Fri, Mar 22, 2024 at 1:02 PM Alexander Dahl wrote: > > Hello Michael, > > Am Fri, Mar 22, 2024 at 12:54:27PM +0100 schrieb Michael Nazzareno Trimarchi: > > HI > > > > On Fri, Mar 22, 2024 at 12:46 PM Alexander Dahl wrote: > > > > > > Hello Mihai, > > > > > > Am Fri, Mar 22, 2024 at

[PATCH 0/4] Cleanup K3 binman templating

This series does primarily three things: 1. Split out the common J721E defconfig for both EVM and SK 2. Cleanup k3-j721e-binman.dtsi to be SoC specific binman nodes and -u-boot.dtsi files of the respective boards can pick and edit according to their board.

[PATCH 1/4] configs: j721e_sk: Move to separate defconfig for J721E SK board

Add defconfig for J721E SK R5 and A72 configuration. This includes and modifies the J721E EVM defconfigs: j721e_evm_r5_defconfig -> j721e_sk_r5_defconfig j721e_evm_a72_defconfig -> j721e_sk_a72_defconfig Signed-off-by: Neha Malcom Francis --- board/ti/j721e/MAINTAINERS | 2 ++

[PATCH 2/4] tools: binman: control.py: Delete template nodes after parsing

Dynamically going through the subnode array and deleting leads to templates being skipped from deletion when templates are consecutive in the subnode list. Prevent this from happening by first parsing the DT and then deleting the nodes. Signed-off-by: Neha Malcom Francis ---

[PATCH 3/4] arm: dts: k3-*-binman.dtsi: Clean up and templatize boot binaries

Clean up templatized boot binaries for all K3 boards. This includes modifying the k3-binman.dtsi to use SPL_BOARD_DTB, BOARD_DESCRIPTION and UBOOT_BOARD_DESCRIPTION from the files that include it to further reuse code. All k3--binman.dtsi will contain only templates. Only required boot binaries

[PATCH v3 10/20] fwu: add config symbols for enabling FWU metadata versions

Support has been added for version 2 of the FWU metadata structure. Add config symbols to enable either of the two versions. Signed-off-by: Sughosh Ganu --- Changes since V2: * New patch lib/fwu_updates/Kconfig | 14 ++ lib/fwu_updates/Makefile | 2 ++ 2 files changed, 16

[PATCH v3 15/20] tools: mkfwumdata: add support for metadata version 2

Add support for generating the FWU metadata version 2. The tool now requires the version to be provided as a command-line option. Make corresponding changes to the tool's manpage. Signed-off-by: Sughosh Ganu --- Changes since V2: * Support both metadata versions instead of only v2.

[PATCH 12/12] arm: env: Add support for booting different HW revisions of XEA boards

In the scenario of recovery, the FitImage is used to boot the system. This patch provides support for deciding which dtb configuration shall be used. Signed-off-by: Lukasz Majewski --- board/liebherr/xea/xea.env | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 10/12] config: xea: Enable late board initialization to set revision variable

The 'board_som_rev' environment variable will be used to point correct configuration from the Linux FIT file. Signed-off-by: Lukasz Majewski --- board/liebherr/xea/xea.c | 12 configs/imx28_xea_defconfig| 1 + configs/imx28_xea_sb_defconfig | 1 + 3 files changed, 14

[PATCH 11/12] arm: xea: Print information about XEA's SoM HW revision

As now XEA has its second HW revision - this information is printed when u-boot proper starts. Signed-off-by: Lukasz Majewski --- board/liebherr/xea/xea.c | 9 + 1 file changed, 9 insertions(+) diff --git a/board/liebherr/xea/xea.c b/board/liebherr/xea/xea.c index

[PATCH 07/12] dts: xea: Add device tree description for XEA HW rev. 2

For SPL and u-boot proper, the difference between revsions boils down only to the GPIO pin for PHY reset. Signed-off-by: Lukasz Majewski --- arch/arm/dts/Makefile| 3 ++- arch/arm/dts/imx28-xea-2-u-boot.dtsi | 11 +++ arch/arm/dts/imx28-xea-2.dts | 8

[PATCH 08/12] arm: spl: Add definition for PHY reset GPIO for XEA HW rev. 2

The imx287 based XEA board's revision 2 uses GPIO_3_21 for PHY reset It is safe to keep the GPIO_2_13 as well, as in the SPL SPI1 is not used for transmission. This simplifies the code, as the proper configuration is performed either in falcon boot's read DTB or in u-boot proper (with correct FIT

[PATCH 09/12] arm: config: xea: Enable support for multiple DTBs for XEA board

After this change u-boot proper is able to support two HW revisions of the XEA board. Signed-off-by: Lukasz Majewski --- configs/imx28_xea_defconfig| 2 ++ configs/imx28_xea_sb_defconfig | 2 ++ 2 files changed, 4 insertions(+) diff --git a/configs/imx28_xea_defconfig

Re: [PATCH] arm64: zynqmp: Do not setup default SPL options without SPL

On 3/12/24 16:51, Michal Simek wrote: mach Kconfig file select some options independently of if SPL is actually enabled. It ends up in situation that SPL is disabled but symbols are still present in .config. That's why add SPL dependency for them but also group them with other SPL options in

Re: [PATCH 00/12] arm: xea: Provide support for different XEA board HW versions

Hi Lukasz, On Fri, Mar 22, 2024 at 8:43 AM Lukasz Majewski wrote: > arch/arm/dts/Makefile | 3 +- > arch/arm/dts/imx28-xea-1-u-boot.dtsi | 11 > arch/arm/dts/imx28-xea-1.dts | 8 +++ > arch/arm/dts/imx28-xea-2-u-boot.dtsi | 11

[PATCH 02/12] arm: xea: Add support for reading SoM (CPU) and base board HW revision

The XEA board now has several HW revisions for both SoM and base boards. This patch provides support for reading those revision ID values in SPL (u-boot.sb) and then pass this information to u-boot proper, as the maximal SPL size (~55KiB) is not allowing for having FIT support in it. It was

[PATCH 03/12] arm: xea: Rename imx28-xea.dts to imx28-xea-1.dts

The former imx28-xea.dts file has been renamed to imx28-xea.dtsi, which is included to new imx28-xea-1.dts file. This is a preparatory work to add support for multiple versions of XEA boards to u-boot. Signed-off-by: Lukasz Majewski --- arch/arm/dts/Makefile | 2 +-

[PATCH 01/12] arm: spl: xea: Remove I2S pins configuration from early initialization

XEA is not supporting and using I2S codec, so there is no need to configure pins for it. Signed-off-by: Lukasz Majewski --- board/liebherr/xea/spl_xea.c | 7 --- 1 file changed, 7 deletions(-) diff --git a/board/liebherr/xea/spl_xea.c b/board/liebherr/xea/spl_xea.c index

[PATCH] xilinx: Do not call private env_get_location() when !ENV_IS_NOWHERE

Private function for finding out location of environment is not working when ENV_IS_NOWHERE is disabled. The reason is that current fallback is ENVL_UNKNOWN when CONFIG_ENV_IS_NOWHERE is not enabled. The code could be updated like this - return ENVL_NOWHERE; + if

[PATCH 04/12] dts: xea: Move phy-reset-gpios property to version specific DTS file

The DTS description in XEA for mac0 node in u-boot differs considerably from what we do have available in Linux, as u-boot is not supporting L2 switch (i.e. 'fixed-link' property is used). To facilitate HW revision management - this particular property has been moved to version specific file.

[PATCH 05/12] dts: xea: Remove outdated comment

The comment in u-boot specific adjustment to XEA DTS is not valid anymore. Signed-off-by: Lukasz Majewski --- arch/arm/dts/imx28-xea-1-u-boot.dtsi | 4 1 file changed, 4 deletions(-) diff --git a/arch/arm/dts/imx28-xea-1-u-boot.dtsi b/arch/arm/dts/imx28-xea-1-u-boot.dtsi index

[PATCH 06/12] arm: xea: Add support for multiple dtbs in u-boot

As XEA board uses imx287, which has some constrains on SPL (u-boot.sb) size - it must be less than ~55 KiB, multiple boards versions are included in u-boot proper's FIT image. The decision of using proper configuration is based on information passed from SPL (u-boot.sb) in OCRAM dedicated

Re: [PATCH] arm64: zynqmp: Do not describe u-boot.itb if SPL is disabled

On 2/23/24 17:18, Michal Simek wrote: There is no reason to describe u-boot.itb on system without SPL. Pretty much this is cover all systems which are using only boot.bin which contains all images inside. Signed-off-by: Michal Simek --- board/xilinx/common/board.c | 2 +- 1 file

Re: [PATCH v3 4/6] usb: Add environment based device ignorelist

On 3/22/24 8:47 AM, Janne Grunau via B4 Relay wrote: [...] @@ -1099,6 +1142,20 @@ int usb_select_config(struct usb_device *dev) le16_to_cpus(>descriptor.idProduct); le16_to_cpus(>descriptor.bcdDevice); + /* ignore devices from usb_ignorelist */ + err =

[PATCH v3 11/20] fwu: mtd: remove unused argument from function call

The third argument passed to the function gen_image_alt_info() is not used and is superfluous. Remove this unused argument from the function call. Fixes: 4898679e190 (FWU: Add FWU metadata access driver for MTD storage regions) Signed-off-by: Sughosh Ganu --- Changes since V2: * New patch

[PATCH v3 13/20] fwu: mtd: obtain image information from version agnostic structure

Make changes to the functions used for generating the DFU's alt variable so that the FWU image information is obtained from the common version agnostic structure instead of reading the metadata. While here, also update the name of the field used for storing the image GUID in the FWU metadata.

[PATCH v3 14/20] cmd: fwu: make changes for supporting FWU metadata version 2

Add support for displaying data specific to FWU metadata version 2. Because the size of the v2 metadata structure is read from the structure itself, allocate memory for the metadata structure by first getting the size of the structure. Signed-off-by: Sughosh Ganu --- Changes since V2: * Earlier

[PATCH v3 09/20] capsule: fwu: transition the platform state on a successful update

Transition the platform to either Trial State or Regular State on a successful update. Do this by calling the fwu_state_machine_updates() API function. For version 1 of the FWU metadata, the transition to Trial State is done by starting the Trial State counter, while for version 2, in addition to

[PATCH v3 19/20] MAINTAINERS: add entry for FWU multi bank update feature

Add an entry for the FWU Multi Bank Update feature. Signed-off-by: Sughosh Ganu --- Changes since V2: * New patch MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index cd9b2d42e8..5409b1d78a 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1147,6

Re: [PATCH v3 01/20] configs: fwu: remove FWU configs for metadata V2 support

On Fri, 22 Mar 2024 at 12:58, Sughosh Ganu wrote: > > Support is to be added in the following commits for the FWU metadata > version 2. Disable the FWU feature on platforms that enable it for the > V2 addition work. > > Signed-off-by: Sughosh Ganu > --- > Changes since V2: None > >

Re: [PATCH v3 19/20] MAINTAINERS: add entry for FWU multi bank update feature

On Fri, 22 Mar 2024 at 12:59, Sughosh Ganu wrote: > > Add an entry for the FWU Multi Bank Update feature. > > Signed-off-by: Sughosh Ganu > --- > Changes since V2: > * New patch > > MAINTAINERS | 8 > 1 file changed, 8 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index

Re: [PATCH] arm64: zynqmp: Add MTD partition handling for dfu_alt_info generation

On 2/23/24 17:18, Michal Simek wrote: Generate dfu_alt_info generation based on information from MTD partitions. mtd_found_part() is trying to identify MTD partition which code is running from. If partitions are not defined and location is not found it is going to previous behavior.

Re: [PATCH v1 3/6] drivers: introduce UBI block abstraction

Hello Alexey, On 06.03.24 14:49, Alexey Romanov wrote: UBI block is an virtual device, that runs on top of the MTD layer. The blocks are UBI volumes. Intended to be used in combination with other MTD drivers. Despite the fact that it, like mtdblock abstraction, it used with UCLASS_MTD, they

Re: [PATCH v3 0/2] Add remoteproc driver support for J721S2 SoC

On Tue, 12 Mar 2024 15:14:34 +0530, Apurva Nandan wrote: > This series adds relevant ip data in remoteproc driver for j721s2 compatible. > > Logs: > https://gist.githubusercontent.com/apurvanandan1997/276098af439e11105ab9f809159fcc98/raw/ > > Changes in v3: > - Removed j721s2.env patch from

Re: [PATCH v7] remoteproc: uclass: Add methods to load firmware to rproc and boot rproc

On Thu, 21 Mar 2024 15:58:19 +0530, MD Danish Anwar wrote: > Add APIs to set a firmware_name to a rproc and boot the rproc with the > same firmware. > > Clients can call rproc_set_firmware() API to set firmware_name for a rproc > whereas rproc_boot() will load the firmware set by

Re: [PATCH v1 5/6] disk: support UBI partitions

Hello Alexey, On 06.03.24 14:49, Alexey Romanov wrote: UBI partition is abstraction over UBI volumes. Can be used by UBI block device. Signed-off-by: Alexey Romanov --- drivers/mtd/ubi/Makefile | 1 + drivers/mtd/ubi/part.c | 99 include/part.h

Re: [PATCH v1 4/6] disk: don't try search for partition type if already set

Hello Alexey, On 06.03.24 14:49, Alexey Romanov wrote: Block devices can already set partition type at initialization stage, so, in this case is no point in searching for partition type. Signed-off-by: Alexey Romanov --- disk/part.c | 7 +++ 1 file changed, 7 insertions(+)

Re: [PATCH v1 2/6] ubi: allow to write to volume with offset

Hello Alexey, On 06.03.24 14:49, Alexey Romanov wrote: Introduce ubi_volume_offset_write() helper, which allow to write to ubi volume with specified offset. Signed-off-by: Alexey Romanov --- cmd/ubi.c | 71 +++-- env/ubi.c | 10

Re: [PATCH v1 6/6] spinand: bind UBI block

Hello Alexey, On 06.03.24 14:49, 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 --- drivers/mtd/nand/spi/core.c | 9 - 1 file changed,

Re: [PATCH v1 1/6] ubi: allow to read from volume with offset

Hello Alexey, On 06.03.24 14:49, Alexey Romanov wrote: Now user can pass an additional parameter 'offset' to ubi_volume_read() function. Signed-off-by: Alexey Romanov --- cmd/ubi.c | 6 +++--- env/ubi.c | 6 +++--- include/ubi_uboot.h | 2 +- 3 files changed, 7

[PATCH v2 3/3] rockchip: spl: Add SPI NOR flash to boot_devices array

Add missing boot source id <-> device tree node path mapping for SPI NOR flash on PX30, RK3288, RK3308, RK3368 and RV1126. Signed-off-by: Jonas Karlman --- v2: - New patch --- arch/arm/mach-rockchip/px30/px30.c | 1 + arch/arm/mach-rockchip/rk3288/rk3288.c | 1 +

[PATCH v2 2/3] rockchip: spl: Cache boot source id for later use

Rockchip BROM writes a boot source id at CFG_IRAM_BASE + 0x10, this id indicates from what storage media TPL/SPL was loaded from. SPL uses this id to determine what device "same-as-spl" represent when determining from where FIT should be loaded. This works as long as the boot_devices array

[PATCH v2 1/3] rockchip: bootrom: Sync bootsource id enum from bootrom

From: Jason Zhu Add more bootsource id: 1. BROM_BOOTSOURCE_UNKNOWN 2. BROM_BOOTSOURCE_I2C 3. BROM_BOOTSOURCE_SPI Signed-off-by: Jason Zhu [jo...@kwiboo.se: Update commit message] Signed-off-by: Jonas Karlman --- v2: - New patch --- arch/arm/include/asm/arch-rockchip/bootrom.h | 3 +++ 1 file

[PATCH v2 0/3] rockchip: spl: Cache boot source id for later use

This series fixes an issue where /chosen/u-boot,spl-boot-device prop cannot be resolved to the SPI flash node path in spl_perform_fixups() if the affected device was booted from SPI flash. Changes in v2: - Add patch that sync boot source id enum with bootrom - Add patch that adds missing SPI

Re: [PATCH v2 2/2] rockchip: rock-pi-4-rk3399: enable booting from SPI flash

Hi Jonas, On Mon, 2024-03-18 at 11:37 +0100, Jonas Karlman wrote: > Hi Christopher, > > On 2024-03-15 13:01, Christopher Obbard wrote: > > Some variants of the ROCK Pi 4 series have an SPI flash chip populated > > which can be booted from. This patch enables support in U-Boot for > > building

Re: [PATCH] arm: dts: k3-am625-verdin-r5: Change CPU frequency to 800MHz

On Tue, 19 Mar 2024 11:04:27 -0300, Joao Paulo Goncalves wrote: > The lowest speed grade of Toradex AM62 SoMs is K speed, resulting in a > max value of 800MHz for the CPU operating frequency. A solution with > runtime selection of the CPU frequency is already planned to avoid these > kinds of

Re: [PATCH 1/1] .mailmap entry for Masahisa Kojima

On Mon, 18 Mar 2024 11:47:16 +0100, Heinrich Schuchardt wrote: > The Linaro mail address is not valid anymore. > > Applied to u-boot/master, thanks! -- Tom

Re: [PATCH v1] board: toradex: verdin-am62_r5: Increase SPL_STACK_R_MALLOC_SIMPLE_LEN

On Wed, 20 Mar 2024 13:48:45 -0300, Hiago De Franco wrote: > Increase the SPL_STACK_R_MALLOC_SIMPLE_LEN to 0x20 to accommodate the > size of tispl.bin fit image. With the recent upgrade of ti-linux-firmware > from version v9.1.0 to v9.2.5, the size of tispl.bin fit image has > increased to

Re: [PATCH 1/2] clk: clk-imx8qxp: Add LPUART IPG entries

On Fri, 08 Mar 2024 17:13:15 -0300, Fabio Estevam wrote: > Since commit cc7df0b9e8bc ("serial: lpuart: Enable IPG clock") > the colibri-imx8qxp board no longer boots. > > The reason is that the imx8qxp clock driver does not handle the > LPUART IPG clocks inside get_rate(), set_rate() and

Re: [PATCH] arm64: Fix map_range() not splitting mapped blocks

On Fri, Mar 22, 2024 at 4:31 PM Fabio Estevam wrote: > As Pierre's explanation addresses Marc's concern, > do you think this can go to 2024.01 to fix the boot regression on imx8qxp/8qm? I meant 2024.04, sorry.

Re: [PATCH] arm64: Fix map_range() not splitting mapped blocks

Hi Tom, On Tue, Mar 19, 2024 at 9:39 AM Pierre-Clément Tosi wrote: > For most AArch64 U-Boot ports (including the i.MX family), the answer is > trivial > because they use the arch code i.e. setup_all_pgtables(). However, as > fsl-layerscape re-implements mmu_setup(), it had to be looked at

  1   2   >