November 2023 - U-Boot

[GIT PULL] Please pull u-boot-dfu-next-20231124
by Mattijs Korpershoek 25 Nov '23

25 Nov '23

Hi Tom, Here are some developments for next including: - Make dfu entity name size configurable in KConfig - Implement start-stop for UMS (graceful shutdown via eject) - Improve help messages for cmd/bind - Improve help message for udc bind failures The CI job is at https://source.denx.de/u-boot/custodians/u-boot-dfu/-/pipelines/18704 Thanks, Mattijs The following changes since commit dca7a8958f8d0dbd53072caa4353353e062d80ca: Merge tag 'v2024.01-rc3' into next (2023-11-20 09:19:50 -0500) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-dfu.git tags/u-boot-dfu-next-20231124 for you to fetch changes up to 8a0d07807abb5370fe879321c7f1d22fdda3255f: usb: udc: Try to clarify an error message (2023-11-21 15:48:38 +0100) ---------------------------------------------------------------- u-boot-dfu-next-20231124 - Make dfu entity name size configurable in KConfig - Implement start-stop for UMS (graceful shutdown via eject) - Improve help messages for cmd/bind - Improve help message for udc bind failures ---------------------------------------------------------------- Jaehoon Chung (1): dfu: add CONFIG_DFU_NAME_MAX_SIZE configuration Marek Vasut (1): usb: gadget: f_mass_storage: Stop ums on START-STOP UNIT SCSI command Miquel Raynal (3): cmd: Change the dependencies between CMD_BIND and USB_GADGET cmd: bind: Try to improve the (un)bind help usb: udc: Try to clarify an error message cmd/Kconfig | 2 +- cmd/bind.c | 4 ++++ drivers/dfu/Kconfig | 9 +++++++++ drivers/usb/gadget/Kconfig | 1 + drivers/usb/gadget/f_mass_storage.c | 7 +++++++ drivers/usb/gadget/udc/udc-core.c | 13 ++++++++++++- include/dfu.h | 5 +++++ 7 files changed, 39 insertions(+), 2 deletions(-)

2 1

[PATCH v2 0/4] fix/add npcm845 serial and board error
by Jim Liu 25 Nov '23

25 Nov '23

1. Fix serial error and add bypass serial setting. 2. Fix/Add dts node node. 3. Add full function defconfig Jim Liu (4): arm: dts: npcm845-evb: fix/add node and aliases configs: arbel: Enable full functions serial: npcm: support skip uart clock setting board: nuvoton: update console environment variable arch/arm/dts/nuvoton-common-npcm8xx.dtsi | 11 ++- arch/arm/dts/nuvoton-npcm845-evb.dts | 29 ++++++-- arch/arm/dts/nuvoton-npcm8xx-u-boot.dtsi | 2 +- board/nuvoton/arbel_evb/Kconfig | 1 + board/nuvoton/arbel_evb/arbel_evb.c | 7 ++ board/nuvoton/common/Kconfig | 9 +++ board/nuvoton/common/Makefile | 1 + board/nuvoton/common/uart.c | 71 +++++++++++++++++++ board/nuvoton/common/uart.h | 11 +++ board/nuvoton/poleg_evb/Kconfig | 1 + board/nuvoton/poleg_evb/poleg_evb.c | 8 +++ configs/arbel_evb_defconfig | 16 ++++- drivers/serial/serial_npcm.c | 39 ++++++---- include/dt-bindings/phy/nuvoton,npcm-usbphy.h | 14 ++++ 14 files changed, 194 insertions(+), 26 deletions(-) create mode 100644 board/nuvoton/common/Kconfig create mode 100644 board/nuvoton/common/Makefile create mode 100644 board/nuvoton/common/uart.c create mode 100644 board/nuvoton/common/uart.h create mode 100644 include/dt-bindings/phy/nuvoton,npcm-usbphy.h -- 2.25.1

2 7

[PATCH] net: Make NET imply NETDEVICES
by Tom Rini 25 Nov '23

25 Nov '23

Normally, when NET is enabled, CMD_NET will then be enabled and in turn NETDEVICES will (likely) be enabled via imply. However, if we disable CMDLINE in a defconfig we now no longer get CMD_NET enabling NETDEVICES for us. This suggestion (as an imply is) really isn't about the network commands but network itself and is a legacy of how intertwined NET/CMD_NET were historically. Move this over to the NET entry instead where it is a more logical fit. Reported-by: Simon Glass <sjg(a)chromium.org> Signed-off-by: Tom Rini <trini(a)konsulko.com> --- This could also be dropping the imply from cmd/Kconfig and instead making drivers/net/Kconfig::NETDEVICES be default y, which is what it practically is today. This would require a more lengthy check however to be sure there's no functional change and I'm not sure it's any better or worse than this approach. --- cmd/Kconfig | 1 - net/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/Kconfig b/cmd/Kconfig index 629a90afb7b5..1b4aad5c930b 100644 --- a/cmd/Kconfig +++ b/cmd/Kconfig @@ -1682,7 +1682,6 @@ if NET menuconfig CMD_NET bool "Network commands" default y - imply NETDEVICES if CMD_NET diff --git a/net/Kconfig b/net/Kconfig index 4215889127c9..8c80b3a6c671 100644 --- a/net/Kconfig +++ b/net/Kconfig @@ -5,6 +5,7 @@ menuconfig NET bool "Networking support" default y + imply NETDEVICES if NET -- 2.34.1

2 2

[PATCH 0/6] siemens,am335x: clean up the draco board family
by Enrico Leto 25 Nov '23

25 Nov '23

The boards were not maintained upstream since the development phase. Restore SPL and remove unused settings. We need i2c to read the DDR settings from EEPROM, get u-boot from NAND, the console output and the watchdog. Restore u-boot up to the user prompt. The complete functionality will be restored in future patches. Signed-off-by: Enrico Leto <enrico.leto(a)siemens.com> --- Enrico Leto (6): siemens,am335x: clean-up draco targets configs: draco: remove spi flash support configs: thuban, rastaban: remove emmc configs: draco: remove unused resources from spl configs: draco: disable misc init configs: draco: restore clock driver arch/arm/mach-omap2/am33xx/Kconfig | 9 -- board/siemens/draco/Kconfig | 22 +-- board/siemens/draco/MAINTAINERS | 15 +-- ...tamin_defconfig => draco-etamin_defconfig} | 13 +- ...ban_defconfig => draco-rastaban_defconfig} | 19 +-- ...huban_defconfig => draco-thuban_defconfig} | 19 +-- configs/draco_defconfig | 127 ------------------ include/configs/{etamin.h => draco-etamin.h} | 0 .../configs/{rastaban.h => draco-rastaban.h} | 0 include/configs/{thuban.h => draco-thuban.h} | 0 include/configs/draco.h | 41 ------ 11 files changed, 20 insertions(+), 245 deletions(-) rename configs/{etamin_defconfig => draco-etamin_defconfig} (92%) rename configs/{rastaban_defconfig => draco-rastaban_defconfig} (90%) rename configs/{thuban_defconfig => draco-thuban_defconfig} (89%) delete mode 100644 configs/draco_defconfig rename include/configs/{etamin.h => draco-etamin.h} (100%) rename include/configs/{rastaban.h => draco-rastaban.h} (100%) rename include/configs/{thuban.h => draco-thuban.h} (100%) delete mode 100644 include/configs/draco.h -- 2.30.2

3 9

Re: orangepi zero3
by Andre Przywara 25 Nov '23

25 Nov '23

On Thu, 23 Nov 2023 11:12:25 -0800 Stephen Graf <stephen.graf(a)gmail.com> wrote: Hi Stephen, > Thank you for your reply. Thanks for coming back. Please keep the list(s) on CC:, as this is also interesting for others, and more eyes help to find issues faster. CC:ing Piotr and Mikhail, who were debugging the LPDDR4 DRAM setup before. > I built u-boot with the proposed changes and it seems to work. It does > however report "DRAM: 2048 MiB" although I have a board with only 1G. Ah, that's a good report! I actually saw the same issue (reporting 8GB instead of 4GB), and my hunch is that it's related to some missing barriers or delays, as seen on other boards. Can you try to add a "dsb();" to the beginning of arch/arm/mach-sunxi/dram_helpers.c:mctl_mem_matches(), before the first writel()? I am still not convinced this is the right place to put the barrier, but it would confirm that this is the issue. Also I didn't see this effect consistently, so did this happen for you every time? Another thing you could try is to increase the voltage to 1150mV, this is what Piotr needed for reliable operation. > > When I built u-boot with the config that I used it reported 1G > correctly. The Zunlong distros do have different images for various RAM > configurations. Yeah, I saw this, and I hope we can avoid this. I am not sure if you are the first one with a 1GB board, so your testing is definitely helpful. > I do not know enough about the details to determine which differences in > the two configs result in the change. > > I am more than willing to test and report if someone can direct me a bit. > > sysadmin@ubuntu:~/defconfgs$ diff sg.txt andre.txt (please use "diff -u", that's easier to read and people are more used to its output style) > 9d8 > < CONFIG_DRAM_SUN50I_H616_TPR0=0x0 > 11,13c10,12 > < CONFIG_DRAM_SUN50I_H616_TPR10=0x402f0663 > < CONFIG_DRAM_SUN50I_H616_TPR11=0x24242323 > < CONFIG_DRAM_SUN50I_H616_TPR12=0x0e0e0e0e > --- > > CONFIG_DRAM_SUN50I_H616_TPR10=0x402f6663 > > CONFIG_DRAM_SUN50I_H616_TPR11=0x24242624 > > CONFIG_DRAM_SUN50I_H616_TPR12=0x0f0f100f I don't think those minor timing differences matter much, but you can try to experiment with both set of values. > 16d14 > < CONFIG_DRAM_CLK=792 Not specifying DRAM_CLK means it uses the default 720 MHz. In the past lowering the DRAM frequency was an easy way to stabilise the DRAM setup, even though this might somewhat paper over other issues. > 25c23 > < CONFIG_SPI_FLASH_MACRONIX=y > --- > > CONFIG_SPI_FLASH_ZBIT=y Please double check, but I think all new OrangePi boards now use a zBIT flash chip? Should have a small "Z" like logo on that 8 pin chip with the large pins on top. > 27a26 > > CONFIG_AXP313_POWER=y > 32,34c31 > < CONFIG_AXP313_POWER=y > < CONFIG_AXP_DCDC3_VOLT=1100 1100mV is the default, so putting exactly this value in doesn't change anything. > < CONFIG_CMD_BOOTZ=y Why do you need bootz? I don't think this doing anything useful in mainline U-Boot. Don't know if OrangePi was just confused and had an actual use case for this. > --- > > > > A second issue that I discovered with both builds is that the Ethernet > does not come up on a 1Gb switch, but works on a 100Mb switch. There is a pending patch for mainline Linux, can you try to apply those DT changes to U-Boot's DT copy and see if that helps? https://lore.kernel.org/linux-sunxi/2303336.ElGaqSPkdT@jernej-laptop/T/#m77… Cheers, Andre > > Output from the patch defconfig (1Gb LAN): > > U-Boot SPL 2024.01-rc3-00009-g9e53e45292-dirty (Nov 23 2023 - 18:08:24 > +0000) > DRAM: 2048 MiB > Trying to boot from MMC1 > NOTICE: BL31: v2.10.0 (debug):v2.10.0 > NOTICE: BL31: Built : 18:07:18, Nov 23 2023 > NOTICE: BL31: Detected Allwinner H616 SoC (1823) > NOTICE: BL31: Found U-Boot DTB at 0x4a0b2750, model: OrangePi Zero3 > INFO: ARM GICv2 driver initialized > INFO: Configuring SPC Controller > INFO: PMIC: Probing AXP305 on RSB > ERROR: RSB: set run-time address: 0x10003 > INFO: Could not init RSB: -65539 > INFO: BL31: Platform setup done > INFO: BL31: Initializing runtime services > INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied > INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied > INFO: PSCI: Suspend is unavailable > INFO: BL31: Preparing for EL3 exit to normal world > INFO: Entry point address = 0x4a000000 > INFO: SPSR = 0x3c9 > INFO: Changed devicetree. > > > U-Boot 2024.01-rc3-00009-g9e53e45292-dirty (Nov 23 2023 - 18:08:24 > +0000) Allwinner Technology > > CPU: Allwinner H616 (SUN50I) > Model: OrangePi Zero3 > DRAM: 2 GiB > Core: 57 devices, 25 uclasses, devicetree: separate > WDT: Not starting watchdog@30090a0 > MMC: mmc@4020000: 0 > Loading Environment from FAT... Unable to use mmc 0:1... > In: serial@5000000 > Out: serial@5000000 > Err: serial@5000000 > Allwinner mUSB OTG (Peripheral) > Net: eth0: ethernet@5020000using musb-hdrc, OUT ep1out IN ep1in STATUS > ep2in > MAC de:ad:be:ef:00:01 > HOST MAC de:ad:be:ef:00:00 > RNDIS ready > , eth1: usb_ether > starting USB... > Bus usb@5200000: USB EHCI 1.00 > Bus usb@5200400: USB OHCI 1.0 > scanning bus usb@5200000 for devices... 1 USB Device(s) found > scanning bus usb@5200400 for devices... 1 USB Device(s) found > scanning usb for storage devices... 0 Storage Device(s) found > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > > Device 0: unknown device > BOOTP broadcast 1 > BOOTP broadcast 2 > BOOTP broadcast 3 > BOOTP broadcast 4 > BOOTP broadcast 5 > BOOTP broadcast 6 > BOOTP broadcast 7 > BOOTP broadcast 8 > BOOTP broadcast 9 > BOOTP broadcast 10 > BOOTP broadcast 11 > BOOTP broadcast 12 > > Retry time exceeded; starting again > missing environment variable: pxeuuid > Retrieving file: pxelinux.cfg/01-02-00-d5-13-4f-ba > *** ERROR: `serverip' not set > > > Output from the defconfig that I had used (100Mb LAN): > > U-Boot SPL 2024.01-rc3-00009-g9e53e45292-dirty (Nov 23 2023 - 18:56:18 > +0000) > DRAM: 1024 MiB > Trying to boot from MMC1 > NOTICE: BL31: v2.10.0 (debug):v2.10.0 > NOTICE: BL31: Built : 18:07:18, Nov 23 2023 > NOTICE: BL31: Detected Allwinner H616 SoC (1823) > NOTICE: BL31: Found U-Boot DTB at 0x4a0b3b68, model: OrangePi Zero3 > INFO: ARM GICv2 driver initialized > INFO: Configuring SPC Controller > INFO: PMIC: Probing AXP305 on RSB > ERROR: RSB: set run-time address: 0x10003 > INFO: Could not init RSB: -65539 > INFO: BL31: Platform setup done > INFO: BL31: Initializing runtime services > INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied > INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied > INFO: PSCI: Suspend is unavailable > INFO: BL31: Preparing for EL3 exit to normal world > INFO: Entry point address = 0x4a000000 > INFO: SPSR = 0x3c9 > INFO: Changed devicetree. > > > U-Boot 2024.01-rc3-00009-g9e53e45292-dirty (Nov 23 2023 - 18:56:18 > +0000) Allwinner Technology > > CPU: Allwinner H616 (SUN50I) > Model: OrangePi Zero3 > DRAM: 1 GiB > Core: 57 devices, 25 uclasses, devicetree: separate > WDT: Not starting watchdog@30090a0 > MMC: mmc@4020000: 0 > Loading Environment from FAT... Unable to use mmc 0:1... > In: serial@5000000 > Out: serial@5000000 > Err: serial@5000000 > Allwinner mUSB OTG (Peripheral) > Net: eth0: ethernet@5020000using musb-hdrc, OUT ep1out IN ep1in STATUS > ep2in > MAC de:ad:be:ef:00:01 > HOST MAC de:ad:be:ef:00:00 > RNDIS ready > , eth1: usb_ether > starting USB... > Bus usb@5200000: USB EHCI 1.00 > Bus usb@5200400: USB OHCI 1.0 > scanning bus usb@5200000 for devices... 1 USB Device(s) found > scanning bus usb@5200400 for devices... 1 USB Device(s) found > scanning usb for storage devices... 0 Storage Device(s) found > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > > Device 0: unknown device > BOOTP broadcast 1 > DHCP client bound to address 192.168.1.63 (5 ms) > *** Warning: no boot file name; using 'C0A8013F.img' > Using ethernet@5020000 device > TFTP from server 192.168.1.253; our IP address is 192.168.1.63 > Filename 'C0A8013F.img'. > Load address: 0x42000000 > Loading: T T T > > defconfig used: > > CONFIG_ARM=y > CONFIG_ARCH_SUNXI=y > CONFIG_DEFAULT_DEVICE_TREE="sun50i-h618-orangepi-zero3" > CONFIG_SPL=y > CONFIG_DRAM_SUN50I_H616_DX_ODT=0x07070707 > CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e > CONFIG_DRAM_SUN50I_H616_CA_DRI=0x0e0e > CONFIG_DRAM_SUN50I_H616_ODT_EN=0xaaaaeeee > CONFIG_DRAM_SUN50I_H616_TPR0=0x0 > CONFIG_DRAM_SUN50I_H616_TPR6=0x44000000 > CONFIG_DRAM_SUN50I_H616_TPR10=0x402f0663 > CONFIG_DRAM_SUN50I_H616_TPR11=0x24242323 > CONFIG_DRAM_SUN50I_H616_TPR12=0x0e0e0e0e > CONFIG_MACH_SUN50I_H616=y > CONFIG_SUNXI_DRAM_H616_LPDDR4=y > CONFIG_DRAM_CLK=792 > CONFIG_R_I2C_ENABLE=y > CONFIG_SPL_SPI_SUNXI=y > # CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set > CONFIG_SPL_I2C=y > CONFIG_SPL_SYS_I2C_LEGACY=y > CONFIG_SYS_I2C_MVTWSI=y > CONFIG_SYS_I2C_SLAVE=0x7f > CONFIG_SYS_I2C_SPEED=400000 > CONFIG_SPI_FLASH_MACRONIX=y > CONFIG_PHY_MOTORCOMM=y > CONFIG_SUN8I_EMAC=y > CONFIG_SPI=y > CONFIG_USB_EHCI_HCD=y > CONFIG_USB_OHCI_HCD=y > CONFIG_USB_MUSB_GADGET=y > CONFIG_AXP313_POWER=y > CONFIG_AXP_DCDC3_VOLT=1100 > CONFIG_CMD_BOOTZ=y > > > On 2023-11-23 6:15 a.m., Andre Przywara wrote: > > On Tue, 21 Nov 2023 21:52:12 -0800 > > Stephen Graf <s_graf(a)telus.net> wrote: > > > > Hi Stephen, > > > >> I have been able to build a working (on my orangepi zero3 1G) u-boot for > >> the orangepi zero3 with the following defconfig. Would it be possible to > > thanks for your interest in contributing and for reaching out! > > As Peter already mentioned, you would need to send a patch, as generated > > by "git format-patch". "git send-email" would help you with sending this > > out. > > > > But actually I sent a small series already last week: > > https://lore.kernel.org/u-boot/20231114013106.31336-1-andre.przywara@arm.co… > > > > If you could apply these patches and test it on your board, I'd be > > grateful. If it works for you and you are happy, please reply to patch 3/3 > > and add a "Tested-by: Your Name <your(a)email.com>" line. > > For instructions how to reply, check "Reply instructions" at the end of > > that mailing list archive web page above. > > > > I was just waiting for confirmations by other people before merging it. > > > > Cheers, > > Andre > > > > > >> add this config to the working boards. I would test it again with an > >> official build. The dtb/dts is in linux and in u-boot. > >> > >> The H618 processor is software compatible with the H616 and the zero3 > >> board is very similar to the zero2 with the exception of DDR3 replaced > >> with LPDDR4 and the Realtek phy with Motorcomm. > >> > >> CONFIG_ARM=y > >> CONFIG_ARCH_SUNXI=y > >> CONFIG_DEFAULT_DEVICE_TREE="sun50i-h618-orangepi-zero3" > >> CONFIG_SPL=y > >> CONFIG_DRAM_SUN50I_H616_DX_ODT=0x07070707 > >> CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e > >> CONFIG_DRAM_SUN50I_H616_CA_DRI=0x0e0e > >> CONFIG_DRAM_SUN50I_H616_ODT_EN=0xaaaaeeee > >> CONFIG_DRAM_SUN50I_H616_TPR0=0x0 > >> CONFIG_DRAM_SUN50I_H616_TPR6=0x44000000 > >> CONFIG_DRAM_SUN50I_H616_TPR10=0x402f0663 > >> CONFIG_DRAM_SUN50I_H616_TPR11=0x24242323 > >> CONFIG_DRAM_SUN50I_H616_TPR12=0x0e0e0e0e > >> CONFIG_MACH_SUN50I_H616=y > >> CONFIG_SUNXI_DRAM_H616_LPDDR4=y > >> CONFIG_DRAM_CLK=792 > >> CONFIG_R_I2C_ENABLE=y > >> CONFIG_SPL_SPI_SUNXI=y > >> # CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set > >> CONFIG_SPL_I2C=y > >> CONFIG_SPL_SYS_I2C_LEGACY=y > >> CONFIG_SYS_I2C_MVTWSI=y > >> CONFIG_SYS_I2C_SLAVE=0x7f > >> CONFIG_SYS_I2C_SPEED=400000 > >> CONFIG_SPI_FLASH_MACRONIX=y > >> CONFIG_PHY_MOTORCOMM=y > >> CONFIG_SUN8I_EMAC=y > >> CONFIG_SPI=y > >> CONFIG_USB_EHCI_HCD=y > >> CONFIG_USB_OHCI_HCD=y > >> CONFIG_USB_MUSB_GADGET=y > >> CONFIG_AXP313_POWER=y > >> CONFIG_AXP_DCDC3_VOLT=1100 > >> CONFIG_CMD_BOOTZ=y > >>

3 3

U-Booters at LPC
by Sean Anderson 24 Nov '23

24 Nov '23

Hi All, I'm at LPC this week, and I'd love to chat with anyone else who's there in person. --Sean

2 4

[PATCH] pci: Enable dm_pci_map_bar() for 64-bit BARs
by Moritz Fischer 24 Nov '23

24 Nov '23

Allow dm_pci_map_bar() usage on systems with CONFIG_PCI_SYS_64BIT. Signed-off-by: Moritz Fischer <moritzf(a)google.com> --- drivers/pci/pci-uclass.c | 11 +++++++++++ include/pci.h | 4 ++-- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/drivers/pci/pci-uclass.c b/drivers/pci/pci-uclass.c index e0d01f6a85..82308c7477 100644 --- a/drivers/pci/pci-uclass.c +++ b/drivers/pci/pci-uclass.c @@ -1611,6 +1611,17 @@ void *dm_pci_map_bar(struct udevice *dev, int bar, size_t offset, size_t len, dm_pci_read_config32(udev, bar, &bar_response); pci_bus_addr = (pci_addr_t)(bar_response & ~0xf); + /* + * This assumes that dm_pciauto_setup_device() will allocate + * a 64-bit address if CONFIG_SYS_PCI_64BIT is enabled and + * the device advertises that it supports it. + */ + if (IS_ENABLED(CONFIG_SYS_PCI_64BIT) && + (bar_response & PCI_BASE_ADDRESS_MEM_TYPE_64)) { + dm_pci_read_config32(udev, bar + 4, &bar_response); + pci_bus_addr |= (pci_addr_t)bar_response << 32; + } + if (~((pci_addr_t)0) - pci_bus_addr < offset) return NULL; diff --git a/include/pci.h b/include/pci.h index 2f5eb30b83..0d1ac7b015 100644 --- a/include/pci.h +++ b/include/pci.h @@ -1350,8 +1350,8 @@ pci_addr_t dm_pci_phys_to_bus(struct udevice *dev, phys_addr_t addr, size_t len, * * Looks up a base address register and finds the physical memory address * that corresponds to it. - * Can be used for 32b BARs 0-5 on type 0 functions and for 32b BARs 0-1 on - * type 1 functions. + * Can be used for 32b/64b BARs 0-5 on type 0 functions and for 32b BARs 0-1 + * on type 1 functions. * Can also be used on type 0 functions that support Enhanced Allocation for * 32b/64b BARs. Note that duplicate BEI entries are not supported. * -- 2.43.0.rc1.413.gea7ed67945-goog

2 1

[PATCH] remoteproc: k3-dsp: Avoid reloading of firmware
by Udit Kumar 24 Nov '23

24 Nov '23

DSP core is going into abnormal state when load callback is called after starting of DSP core. Reload of firmware needs core to be stopped first, followed by load. So avoid loading of firmware, when core is started. Signed-off-by: Udit Kumar <u-kumar1(a)ti.com> --- drivers/remoteproc/ti_k3_dsp_rproc.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/drivers/remoteproc/ti_k3_dsp_rproc.c b/drivers/remoteproc/ti_k3_dsp_rproc.c index 576de4bb26..daf6eae90a 100644 --- a/drivers/remoteproc/ti_k3_dsp_rproc.c +++ b/drivers/remoteproc/ti_k3_dsp_rproc.c @@ -63,6 +63,7 @@ struct k3_dsp_privdata { struct k3_dsp_boot_data *data; struct k3_dsp_mem *mem; int num_mems; + bool in_use; }; /* @@ -128,6 +129,13 @@ static int k3_dsp_load(struct udevice *dev, ulong addr, ulong size) u32 boot_vector; int ret; + if (dsp->in_use) { + dev_err(dev, + "Invalid op: Trying to load/start on already running core %d\n", + dsp->tsp.proc_id); + return -EINVAL; + } + dev_dbg(dev, "%s addr = 0x%lx, size = 0x%lx\n", __func__, addr, size); ret = ti_sci_proc_request(&dsp->tsp); if (ret) @@ -195,6 +203,7 @@ static int k3_dsp_start(struct udevice *dev) ti_sci_proc_power_domain_off(&dsp->tsp); } + dsp->in_use = true; proc_release: ti_sci_proc_release(&dsp->tsp); @@ -207,6 +216,7 @@ static int k3_dsp_stop(struct udevice *dev) dev_dbg(dev, "%s\n", __func__); + dsp->in_use = false; ti_sci_proc_request(&dsp->tsp); reset_assert(&dsp->dsp_rst); ti_sci_proc_power_domain_off(&dsp->tsp); -- 2.34.1

1 0

[PATCH] arm: afs: Set the filesize env. var. on load
by robert.catherall＠foss.arm.com 23 Nov '23

23 Nov '23

From: Robert Catherall <robert.catherall(a)arm.com> The `afs load` command copies data to RAM. Set the filesize environment variable to record how much data was 'loaded' Signed-off-by: Robert Catherall <robert.catherall(a)arm.com> --- cmd/armflash.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/cmd/armflash.c b/cmd/armflash.c index d1466f73aa..fdaea5ad81 100644 --- a/cmd/armflash.c +++ b/cmd/armflash.c @@ -180,6 +180,7 @@ static int load_image(const char * const name, const ulong address) { struct afs_image *afi = NULL; int i; + loff_t len_read = 0; parse_flash(); for (i = 0; i < num_afs_images; i++) { @@ -197,6 +198,7 @@ static int load_image(const char * const name, const ulong address) for (i = 0; i < afi->region_count; i++) { ulong from, to; + u32 size; from = afi->flash_mem_start + afi->regions[i].offset; if (address) { @@ -208,14 +210,20 @@ static int load_image(const char * const name, const ulong address) return CMD_RET_FAILURE; } - memcpy((void *)to, (void *)from, afi->regions[i].size); + size = afi->regions[i].size; + memcpy((void *)to, (void *)from, size); printf("loaded region %d from %08lX to %08lX, %08X bytes\n", i, from, to, - afi->regions[i].size); + size); + + len_read += size; } + + env_set_hex("filesize", len_read); + return CMD_RET_SUCCESS; } -- 2.17.1

2 1

[PATCH RFC 0/2] Unify K3 initial memory map
by Andrew Davis 23 Nov '23

23 Nov '23

Hello all, This is just an RFC as it probably breaks remoteproc loading. I wanted to post anyway as the complexity of having a dedicated memory map for each SoC came up in a different series. Or maybe we can take this now and that will expose the issue in remoteproc loading better and force someone to go fix it. :) This series depends on this[0]. Thanks, Andrew [0] https://patchwork.ozlabs.org/project/uboot/patch/20231106165205.22066-1-afd… Andrew Davis (2): arm: mach-k3: Remove non-cached memory map areas arm: mach-k3: Merge initial memory maps arch/arm/mach-k3/arm64-mmu.c | 253 +---------------------------------- 1 file changed, 2 insertions(+), 251 deletions(-) -- 2.39.2

2 3