[PATCH v3 6/6] doc: describe Milk-V Mars board

Add instructions to build U-Boot for the Milk-V Mars board Signed-off-by: Heinrich Schuchardt --- v3: no change v2: describe how to preset fdtfile --- doc/board/starfive/index.rst | 1 + doc/board/starfive/milk-v_mars.rst | 111 + 2 files

[PATCH v3 5/6] riscv: starfive: avoid including common.h

The usage of common.h is deprecated. Remove it from board files. Signed-off-by: Heinrich Schuchardt Reviewed-by: Leo Yu-Chi Liang --- v3: no change v2: no change --- board/starfive/visionfive2/spl.c| 1 - board/starfive/visionfive2/starfive_visionfive2.c |

[PATCH v3 4/6] board: starfive: support Milk-V Mars board

The differences between the Milk-V Mars board and the VisionFive 2 board are small enough that we can support both using the same U-Boot build. * The model and compatible property are taken from proposed Linux patches. * The EEPROM is atmel,24c02 according to the vendor U-Boot. * The second

[PATCH v3 3/6] riscv: set fdtfile on Milk-V Mars

Set environment variable fdtfile to the correct value for the Milk-V Mars board. Signed-off-by: Heinrich Schuchardt Reviewed-by: Leo Yu-Chi Liang --- v3: no change v2: rebase patch --- .../visionfive2/starfive_visionfive2.c| 43 +-- 1 file changed, 30

[PATCH v3 2/6] eeprom: starfive: function get_product_id_from_eeprom()

Export a function get_product_id_from_eeprom() to read the product ID. This value can be used for fixing up the device-tree on JH7110 based products. Signed-off-by: Heinrich Schuchardt Reviewed-by: Leo Yu-Chi Liang --- v3: no change v2: no change ---

[PATCH v3 1/6] riscv: do not set default fdt for VisionFive 2

Currently in set_fdtfile() we set the value of environment variable fdtfile unconditionally. The implies that a value in the environment will be ignored. With the patch environment variable fdtfile will only be set if it does not yet exist. This requires that CONFIG_DEFAULT_FDT_FILE is not set.

[PATCH v3 0/6] riscv: add support for Milk-V Mars board

The Milk-V Mars board is technically very close to the StarFive VisionFive 2 board. With this patch series the VisionFive 2 U-Boot SPL will detect that it is running on a Milk-V board and patch the device-tree accordingly. This is the same approach that has been taken to handle the differences

[PATCH 1/1] net: dw_eth_qos: Add missing \n in error messages.

Missing line-feeds in error messages lead to output like: phy_startup() failed: -110FAILED: -110=> Output like the following is much easier to read: phy_startup() failed: -110 FAILED: -110 => Signed-off-by: Heinrich Schuchardt --- drivers/net/dwc_eth_qos.c | 108

Re: [PATCH v5 13/16] dts: sdm845-db845c: add u-boot fixups

On 28/03/2024 18:59, Caleb Connolly wrote: The USB VBUS supply for the type-A port is enabled via a GPIO regulator. This is incorrectly modelled in Linux where only the PCIe dependency is expressed. The correct way to handle this will be through a usb-connector node, but for now we'll just mark

Re: [PATCH v5 12/16] mach-snapdragon: call regulators_enable_boot_on()

On 28/03/2024 18:59, Caleb Connolly wrote: Make sure we power on any boot-on or always-on regulators. These are used for peripherals like USB on some platforms. Signed-off-by: Caleb Connolly --- arch/arm/mach-snapdragon/board.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [PATCH v5 11/16] mach-snapdragon: fixup power-domains

On 28/03/2024 18:59, Caleb Connolly wrote: We don't support the RPM(h)PD power domains in U-Boot, and we don't need to - the necessary resources are on, and we aren't going to enter any low power modes. We could try using a no-op device, but this requires adding a compatible for every platform,

Re: [PATCH v5 10/16] mach-snapdragon: fixup USB nodes

On 28/03/2024 18:59, Caleb Connolly wrote: We don't support USB super-speed in U-Boot yet, we lack the SS PHY drivers, however from my testing even with a PHY driver there seem to be other issues when talking to super-speed peripherals. In pursuit of maintaining upstream DT compatibility, and

Re: [PATCH] net: phy: broadcom: Configure LEDs on BCM54210E

On Thu Mar 28, 2024 at 4:09 PM CET, Tom Rini wrote: > On Mon, Jan 01, 2024 at 10:07:47PM +0100, Marek Vasut wrote: > > > Configure LEDs on BCM54210E so they would blink on activity > > and indicate link speed. Without this the LEDs are always on > > if cable is plugged in. > > > > Signed-off-by:

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

Hi, On Fri, 29 Mar 2024 18:51:47 +0100, 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

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

Hi, On Tue, 19 Mar 2024 15:42:59 +0100, 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

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

Hi Caleb, Thank you for the patch. On jeu., mars 28, 2024 at 17:59, Caleb Connolly wrote: > The patch introducing support for dynamic sector sizes changed the types > used in some divisions, resulting in the compiler attempting to use > libgcc helpers (__aeabi_ldivmod). Replace these

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

Hi Neil, Thank you for the series. On ven., mars 29, 2024 at 18:51, "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

<    1   2