January 2022 - U-Boot

[PATCH 1/3] dfu: use pointer to pass length to dfu_write()
by Frieder Schrempf 28 Jan '22

28 Jan '22

From: Frieder Schrempf <frieder.schrempf(a)kontron.de> This doesn't include any functional changes, but allows us to use the size parameter to report the actual written bytes back to the caller. This is useful in cases of unaligned writes to serial flash where the first write covers only a part of the buffer (until the next sector boundary) and the remaining bytes need to be written in a further call to dfu_write(). While at it, we also adjust the data type of the 'write' and 'left' variable in dfu_write_from_mem_addr() to match the values passed. Signed-off-by: Frieder Schrempf <frieder.schrempf(a)kontron.de> --- drivers/dfu/dfu.c | 23 ++++++++++++----------- include/dfu.h | 2 +- 2 files changed, 13 insertions(+), 12 deletions(-) diff --git a/drivers/dfu/dfu.c b/drivers/dfu/dfu.c index ff1859d946..5b2659ee7d 100644 --- a/drivers/dfu/dfu.c +++ b/drivers/dfu/dfu.c @@ -334,12 +334,12 @@ int dfu_flush(struct dfu_entity *dfu, void *buf, int size, int blk_seq_num) return ret; } -int dfu_write(struct dfu_entity *dfu, void *buf, int size, int blk_seq_num) +int dfu_write(struct dfu_entity *dfu, void *buf, int *size, int blk_seq_num) { int ret; debug("%s: name: %s buf: 0x%p size: 0x%x p_num: 0x%x offset: 0x%llx bufoffset: 0x%lx\n", - __func__, dfu->name, buf, size, blk_seq_num, dfu->offset, + __func__, dfu->name, buf, *size, blk_seq_num, dfu->offset, (unsigned long)(dfu->i_buf - dfu->i_buf_start)); ret = dfu_transaction_initiate(dfu, false); @@ -371,7 +371,7 @@ int dfu_write(struct dfu_entity *dfu, void *buf, int size, int blk_seq_num) dfu->i_blk_seq_num = (dfu->i_blk_seq_num + 1) & 0xffff; /* flush buffer if overflow */ - if ((dfu->i_buf + size) > dfu->i_buf_end) { + if ((dfu->i_buf + *size) > dfu->i_buf_end) { ret = dfu_write_buffer_drain(dfu); if (ret) { dfu_transaction_cleanup(dfu); @@ -381,19 +381,19 @@ int dfu_write(struct dfu_entity *dfu, void *buf, int size, int blk_seq_num) } /* we should be in buffer now (if not then size too large) */ - if ((dfu->i_buf + size) > dfu->i_buf_end) { + if ((dfu->i_buf + *size) > dfu->i_buf_end) { pr_err("Buffer overflow! (0x%p + 0x%x > 0x%p)\n", dfu->i_buf, - size, dfu->i_buf_end); + *size, dfu->i_buf_end); dfu_transaction_cleanup(dfu); dfu_error_callback(dfu, "Buffer overflow"); return -1; } - memcpy(dfu->i_buf, buf, size); - dfu->i_buf += size; + memcpy(dfu->i_buf, buf, *size); + dfu->i_buf += *size; /* if end or if buffer full flush */ - if (size == 0 || (dfu->i_buf + size) > dfu->i_buf_end) { + if (*size == 0 || (dfu->i_buf + *size) > dfu->i_buf_end) { ret = dfu_write_buffer_drain(dfu); if (ret) { dfu_transaction_cleanup(dfu); @@ -704,7 +704,8 @@ int dfu_get_alt(char *name) int dfu_write_from_mem_addr(struct dfu_entity *dfu, void *buf, int size) { - unsigned long dfu_buf_size, write, left = size; + unsigned int write, left = size; + unsigned long dfu_buf_size; int i, ret = 0; void *dp = buf; @@ -720,9 +721,9 @@ int dfu_write_from_mem_addr(struct dfu_entity *dfu, void *buf, int size) for (i = 0; left > 0; i++) { write = min(dfu_buf_size, left); - debug("%s: dp: 0x%p left: %lu write: %lu\n", __func__, + debug("%s: dp: 0x%p left: %lu write: %u\n", __func__, dp, left, write); - ret = dfu_write(dfu, dp, write, i); + ret = dfu_write(dfu, dp, &write, i); if (ret) { pr_err("DFU write failed\n"); return ret; diff --git a/include/dfu.h b/include/dfu.h index f6868982df..2df55e507e 100644 --- a/include/dfu.h +++ b/include/dfu.h @@ -335,7 +335,7 @@ int dfu_read(struct dfu_entity *de, void *buf, int size, int blk_seq_num); * @blk_seq_num: block sequence number * Return: 0 for success, -1 for error */ -int dfu_write(struct dfu_entity *de, void *buf, int size, int blk_seq_num); +int dfu_write(struct dfu_entity *de, void *buf, int *size, int blk_seq_num); /** * dfu_flush() - flush to dfu entity -- 2.33.0

2 3

[PATCH 1/1] doc: describe MSEL settings for booting from SD card
by Heinrich Schuchardt 28 Jan '22

28 Jan '22

unmatched.rst describes booting from SD card or from SPI. But only for booting from SPI the boot selection settings are described. Add the missing information. Fix a typo 'uSD'. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt(a)canonical.com> --- doc/board/sifive/unmatched.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/doc/board/sifive/unmatched.rst b/doc/board/sifive/unmatched.rst index b52a1f690c..24a889991c 100644 --- a/doc/board/sifive/unmatched.rst +++ b/doc/board/sifive/unmatched.rst @@ -20,8 +20,11 @@ The support for following drivers are already enabled: 4. SiFive SPI Driver. 5. MMC SPI Driver for MMC/SD support. -Booting from uSD using U-Boot SPL ---------------------------------- +Booting from micro SD card using U-Boot SPL +------------------------------------------- + +Booting from an SD card requires that the boot mode selection DIP switches +MSEL[3:0] are set to 1011. Building -------- -- 2.33.1

2 1

[RFC v2 00/20] efi_loader: more tightly integrate UEFI disks to driver model
by AKASHI Takahiro 28 Jan '22

28 Jan '22

# This is a kind of snapshot of my current work. # I submit this to show my progress on this effort, and then # I haven't addressed all the issues in this version. # See the change history below. The purpose of this RPC is to reignite the discussion about how UEFI subystem would best be integrated into U-Boot driver model. In the past, I poposed a couple of patch series, the latest one[1], while Heinrich revealed his idea[2], and the approach taken here is something between them, with a focus on block device handlings. # The code is a PoC and not well tested yet. Disks in UEFI world: ==================== In general in UEFI world, accessing to any device is performed through a 'protocol' interface which are installed to (or associated with) the device's UEFI handle (or an opaque pointer to UEFI object data). Protocols are implemented by either the UEFI system itself or UEFI drivers. For block IO's, it is a device which has EFI_BLOCK_IO_PROTOCOL (efi_disk hereafter). Currently, every efi_disk may have one of two origins: a.U-Boot's block devices or related partitions (lib/efi_loader/efi_disk.c) b.UEFI objects which are implemented as a block device by UEFI drivers. (lib/efi_driver/efi_block_device.c) All the efi_diskss as (a) will be enumelated and created only once at UEFI subsystem initialization (efi_disk_register()), which is triggered by first executing one of UEFI-related U-Boot commands, like "bootefi", "setenv -e" or "efidebug". EFI_BLOCK_IO_PROTOCOL is implemented by UEFI system using blk_desc(->ops) in the corresponding udevice(UCLASS_BLK). On the other hand, efi_disk as (b) will be created each time UEFI boot services' connect_controller() is executed in UEFI app which, as a (device) controller, gives the method to access the device's data, ie. EFI_BLOCK_IO_PROTOCOL. >>> more details >>> Internally, connect_controller() search for UEFI driver that can support this controller/protocol, 'efi_block' driver(UCLASS_EFI) in this case, then calls the driver's 'bind' interface, which eventually installs the controller's EFI_BLOCK_IO_PROTOCOL to efi_disk object. 'efi_block' driver also create a corresponding udevice(UCLASS_BLK) for * creating additional partitions efi_disk's, and * supporting a file system (EFI_SIMPLE_FILE_SYSTEM_PROTOCOL) on it. <<< <<< Issues: ======= 1. While an efi_disk represents a device equally for either a whole disk or a partition in UEFI world, the driver model treats only a whole disk as a real block device or udevice(UCLASS_BLK). 2. efi_disk holds and makes use of "blk_desc" data even though blk_desc in plat_data is supposed to be private and not to be accessed outside the driver model. # This issue, though, exists for all the implmenetation of U-Boot # file systems as well. For efi_disk(a), 3. A block device can be enumelated dynamically by 'scanning' a device bus in U-Boot, but UEFI subsystem is not able to update efi_disks accordingly. For examples, => scsi rescan; efidebug devices => usb start; efidebug devices ... (A) (A) doesn't show any usb devices detected. => scsi rescan; efidebug boot add -b 0 TEST scsi 0:1 ... => scsi rescan ... (B) => bootefi bootmgr ... (C) (C) may de-reference a bogus blk_desc pointer which has been freed by (B). (Please note that "scsi rescan" removes all udevices/blk_desc and then re-create them even if nothing is changed on a bus.) For efi_disk(b), 4. A "controller (handle)", combined with efi_block driver, has no corresponding udevice as a parent of efi_disks in DM tree, unlike, say, a scsi controller, even though it provides methods for block io operations. 5. There is no way supported to remove efi_disk's even after disconnect_controller() is called. My approach in this RFC: ======================== Due to functional differences in semantics, it would be difficult to identify "udevice" structure as a handle in UEFI world. Instead, we will have to somehow maintain a relationship between a udevice and a handle. 1-1. add a dedicated uclass, UCLASS_PARTITION, for partitions Currently, the uclass for paritions is not a UCLASS_BLK. It can be possible to define partitions as UCLASS_BLK (with IF_TYPE_PARTION?), but I'm afraid that it may introduce some chaos since udevice(UCLASS_BLK) is tightly coupled with 'struct blk_desc' data which is still used as a "structure to a whole disk" in a lot of interfaces. (I hope that you understand what it means.) In DM tree, a UCLASS_PARTITON instance has a UCLASS_BLK parent: For instance, UCLASS_SCSI --- UCLASS_BLK --- UCLASS_PARTITION (IF_TYPE_SCSI) | +- struct blk_desc +- struct disk_part +- scsi_blk_ops +- blk_part_ops 1-2. create partition udevices in the context of device_probe() part_init() is already called in blk_post_probe(). See the commit d0851c893706 ("blk: Call part_init() in the post_probe() method"). Why not enumelate partitions as well in there. 2. add new block access interfaces, which takes a *udevice* as a target device, in U-Boot and use those functions to implement efi_disk operations (i.e. EFI_BLOCK_IO_PROTOCOL). 3-1. maintain a bi-directional link between a udevice and an efi_disk by adding - a UEFI handle pointer as a tag for a udevice - a udevice pointer in UEFI handle (in fact, in "struct efi_disk_obj") 3-2. synchronize the lifetime of efi_disk objects in UEFI world with the driver model using - event notification associated with device's probe/remove. 4. I have no answer to issue(4) and (5) yet. Patchs: ======= For easy understandings, patches may be categorized into seperate groups of changes. Patch#1-#10: DM: add device_probe() for later use of events Patch#11-#12: DM: add new features (tag and event notification) Patch#13-#16: UEFI: dynamically create/remove efi_disk's for a raw disk and its partitions For removal case, we may need more consideration since removing handles unconditionally may end up breaking integrity of handles (as some may still be held and referenced to by a UEFI app). Patch#17-#18: UEFI: use udevice read/write interfaces Patch#19-#20: UEFI: fix-up efi_driver, aligning with changes in DM integration [1] https://lists.denx.de/pipermail/u-boot/2019-February/357923.html [2] https://lists.denx.de/pipermail/u-boot/2021-June/452297.html Change history: =============== RFCv2 (Dec 10, 2021) * rebased on 2022-rc3 * re-order and merge some related commits into ones * call device_probe() in MMC (not bind, but) probe hook (patch#5) * fix a wrong name of variable (patch#7) * add patch#9 * invoke device_probe() for virtio devices (patch#10) * add DM event notitication (from Simon) (patch#11) * add DM tag support (patch#12) * move UCLASS_PARTITION driver under disk/ (patch#13) * create partition's dp using its parent's. This change is necessary in particular for 'efi_blk' efi_disk (patch#13) * modify the code so that we will use new features like tags and event notification (patch#13,15,16,20) * rename new functions from blk_read/write() to dev_read/write() (patch#17,18) * isolate changes in efi_driver from the rest (in efi_loader) (patch#19) * drop the previous patch#22 ("efi_selftest: block device: adjust dp for a test") due to the fix in patch#13 RFC (Nov 16, 2021) * initial RFC AKASHI Takahiro (19): part: call part_init() in blk_get_device_by_str() only for MMC blk: add a helper function, blk_probe_or_unbind() scsi: call device_probe() after scanning usb: storage: call device_probe() after scanning mmc: call device_probe() after scanning nvme: call device_probe() after scanning sata: call device_probe() after scanning block: ide: call device_probe() after scanning dm: fix an 'undefined' error in some macros virtio: call device_probe() in scanning dm: add tag support dm: disk: add UCLASS_PARTITION dm: blk: add a device-probe hook for scanning disk partitions efi_loader: disk: a helper function to create efi_disk objects from udevice efi_loader: disk: a helper function to delete efi_disk objects dm: disk: add read/write interfaces with udevice efi_loader: disk: use udevice instead of blk_desc efi_loader: disk: not create BLK device for BLK(IF_TYPE_EFI) devices efi_driver: align with efi_disk-dm integration Simon Glass (1): dm: add event notification cmd/virtio.c | 21 +- common/Kconfig | 11 + common/Makefile | 2 + common/board_f.c | 2 + common/event.c | 103 ++++++++++ common/log.c | 1 + common/usb_storage.c | 4 + disk/Makefile | 3 + disk/disk-uclass.c | 249 ++++++++++++++++++++++ disk/part.c | 3 +- drivers/ata/dwc_ahsata.c | 5 + drivers/ata/fsl_sata.c | 11 + drivers/ata/sata_mv.c | 5 + drivers/ata/sata_sil.c | 12 ++ drivers/block/blk-uclass.c | 17 ++ drivers/block/ide.c | 4 + drivers/core/Makefile | 2 +- drivers/core/device-remove.c | 9 + drivers/core/device.c | 9 + drivers/core/tag.c | 162 +++++++++++++++ drivers/mmc/mmc-uclass.c | 13 ++ drivers/nvme/nvme.c | 4 + drivers/scsi/scsi.c | 5 + include/asm-generic/global_data.h | 3 + include/blk.h | 12 ++ include/dm/device-internal.h | 10 + include/dm/device.h | 8 +- include/dm/tag.h | 76 +++++++ include/dm/uclass-id.h | 1 + include/efi_loader.h | 4 +- include/event.h | 105 ++++++++++ include/event_internal.h | 34 +++ include/log.h | 2 + include/part.h | 18 ++ lib/efi_driver/efi_block_device.c | 34 +-- lib/efi_loader/Kconfig | 2 + lib/efi_loader/efi_disk.c | 329 ++++++++++++++++++++++-------- lib/efi_loader/efi_setup.c | 11 +- test/common/Makefile | 1 + test/common/event.c | 87 ++++++++ test/test-main.c | 5 + 41 files changed, 1274 insertions(+), 125 deletions(-) create mode 100644 common/event.c create mode 100644 disk/disk-uclass.c create mode 100644 drivers/core/tag.c create mode 100644 include/dm/tag.h create mode 100644 include/event.h create mode 100644 include/event_internal.h create mode 100644 test/common/event.c -- 2.33.0

5 50

[PATCH 1/2] clk: imx: select [SPL_]CLK_COMPOSITE_CCF for imx8mm
by Heiko Thiery 28 Jan '22

28 Jan '22

The clock composite is required when using the clock framework. So select it automatically. Signed-off-by: Heiko Thiery <heiko.thiery(a)gmail.com> --- drivers/clk/imx/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/clk/imx/Kconfig b/drivers/clk/imx/Kconfig index 96721bcbf3..1800b1860b 100644 --- a/drivers/clk/imx/Kconfig +++ b/drivers/clk/imx/Kconfig @@ -26,6 +26,7 @@ config SPL_CLK_IMX8MM depends on ARCH_IMX8M && SPL select SPL_CLK select SPL_CLK_CCF + select SPL_CLK_COMPOSITE_CCF help This enables SPL DM/DTS support for clock driver in i.MX8MM @@ -34,6 +35,7 @@ config CLK_IMX8MM depends on ARCH_IMX8M select CLK select CLK_CCF + select CLK_COMPOSITE_CCF help This enables support clock driver for i.MX8MM platforms. -- 2.30.2

2 3

How to modify defconfig file - make savedefconfig?
by Grant Edwards 28 Jan '22

28 Jan '22

What is the "right" way to modify a defconfig file? Most sources I've found just say things like "edit the defconfig file". That seems error-prone -- especially when dealing with settings that have side effects. I did stumble across one mention of "make savedefconfig", and this seems to be the right way to modify a defconfig file: make myboard_defconfig make menuconfig make savedefconfig cp defconfig configs/myboard_defconfig Do people manually edit their defconfig file when they want to make a change, or do they use "make savedefconfig" like I show above? One reason I'm asking is that the original defconfig file provided by the silicon vendor (Renesas) appears to be a manually stripped-down ..config file, because when I do make vendors_defconfig make savedefconfig The defconfig file generated by 'make savedefconfig' looks _nothing_ like the starting vendors_defconfig. The new defconfig generates the same .config file as the vendors_defconfig file. But the vendors_defconfig file is arranged completely differently with different/extra comments, extra blank lines, etc. -- Grant

2 1

[PATCH 00/25] SIERRA: Add support for MultiLink
by Aswath Govindraju 28 Jan '22

28 Jan '22

The following series of patches, - add support for MultiLink on Sierra SerDes - Also adds the required to configs, dt node changes to enable this on J721e common processor board. Notes: - Patches 1, 2, 3, 4, 5, 6, 7, 8, 13, 14, 15, 16, 17, 18, 19, 20, 21 and 22 are ported from upstream kernel v5.17-rc1 - Patch 24, syncs with linux kernel dt, with the following patch https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=608996 Aswath Govindraju (8): phy: cadence: Sierra: Add a UCLASS_PHY device for links phy: cadence: Sierra: Model PLL_CMNLC and PLL_CMNLC1 as a clock phy: ti: phy-j721e-wiz.c: Fix the condition for setting P_ENABLE_FORCE board: ti: j721e: evm.c: Add support for probing SerDes0 arm: dts: k3-j721e: Add support for PLL_CMNLC clocks in SerDes0 phy: cadence: Sierra: Add support for skipping configuration arm: dts: k3-j721e: Add support for multilink PCIe + QSGMII include: configs: j721e_evm: Add support to boot ethfw core in j721e Kishon Vijay Abraham I (6): phy: cadence: Sierra: Fix PHY power_on sequence phy: cadence: Sierra: Create PHY only for "phy" or "link" sub-nodes phy: cadence: Sierra: Move all clk_get_*() to a separate function phy: cadence: Sierra: Move all reset_control_get*() to a separate function phy: cadence: Sierra: Add array of input clocks in "struct cdns_sierra_phy" phy: cadence: Sierra: Add missing clk_disable_unprepare() in .remove callback Sanket Parmar (1): phy: cadence: sierra: Fix for USB3 U1/U2 state Swapnil Jakhade (10): phy: cadence: Sierra: Prepare driver to add support for multilink configurations dt-bindings: phy: cadence-sierra: Add binding to specify SSC mode phy: cadence: Sierra: Add support to get SSC type from device tree. phy: cadence: Sierra: Rename some regmap variables to be in sync with Sierra documentation phy: cadence: Sierra: Add PHY PCS common register configurations phy: cadence: Sierra: Check cmn_ready assertion during PHY power on phy: cadence: Sierra: Check PIPE mode PHY status to be ready for operation phy: cadence: Sierra: Update single link PCIe register configuration phy: cadence: Sierra: Add support for PHY multilink configurations phy: cadence: Sierra: Add PCIe + QSGMII PHY multilink configuration .../k3-j721e-common-proc-board-u-boot.dtsi | 15 + arch/arm/dts/k3-j721e-common-proc-board.dts | 14 +- .../arm/dts/k3-j721e-r5-common-proc-board.dts | 32 + board/ti/j721e/evm.c | 37 + configs/j721e_evm_a72_defconfig | 2 +- drivers/phy/cadence/phy-cadence-sierra.c | 1536 +++++++++++++++-- drivers/phy/ti/phy-j721e-wiz.c | 2 +- include/configs/j721e_evm.h | 19 +- include/dt-bindings/phy/phy-cadence.h | 4 + 9 files changed, 1493 insertions(+), 168 deletions(-) -- 2.17.1

1 26

[PATCH] efi_loader: correctly handle mixed hashes and signatures in db
by Ilias Apalodimas 28 Jan '22

28 Jan '22

A mix of signatures and hashes in db doesn't always work as intended. Currently if the digest algorithm is not supported we stop walking the security database and reject the image. That's problematic in case we find and try to check a signature before inspecting the sha256 hash. If the image is unsigned we will reject it even if the digest matches Signed-off-by: Ilias Apalodimas <ilias.apalodimas(a)linaro.org> --- lib/efi_loader/efi_signature.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/efi_loader/efi_signature.c b/lib/efi_loader/efi_signature.c index 3243e2c60de0..8fa82f8cea4c 100644 --- a/lib/efi_loader/efi_signature.c +++ b/lib/efi_loader/efi_signature.c @@ -176,7 +176,7 @@ bool efi_signature_lookup_digest(struct efi_image_regions *regs, if (guidcmp(&siglist->sig_type, &efi_guid_sha256)) { EFI_PRINT("Digest algorithm is not supported: %pUs\n", &siglist->sig_type); - break; + continue; } if (!efi_hash_regions(regs->reg, regs->num, &hash, &size)) { -- 2.32.0

2 2

[PATCH 0/5] sunxi: remove lowlevel_init
by Andre Przywara 28 Jan '22

28 Jan '22

For a long time the Allwinner platform was using the lowlevel_init() routine in U-Boot's boot process, even though there did not seem to be a real need for that. The README file suggests it should only be used for "bare minimum" tasks to reach board_init_f(). The routines called in arch/arm/mach-sunxi/board.c:s_init() did nothing that really warranted the early and special execution. Since we always run with an SPL, the board_init_f() routine in there seems to be the right place for early peripherals initialisation. Having those routines in s_init() actually forced other parts of U-Boot to follow suit: for instance we added a lowlevel_init() function to the armv8 side, just for sunxi. The same game seems to repeat for the ARM9 support we need for the F1C100s chip, and possibly for the RISC-V part as well. To avoid this and to cleanup some code on the way, remove the need for lowlevel_init for sunxi completely, by: - moving the early peripheral init (clocks, timer, pinmux) to board_init_f(). This also avoids executing those bits a second time when we boot up U-Boot proper. (patch 1/5) - move the "SRAM setup" bits for just a few old SoCs into a separate file, and include this only if needed. (patch 3/5) - move the ACTLR.SMPEN bit setting from board.c into start.S, because we actually need to set this bit early. Other platforms should be able to scrap their own copies and piggy back on this change. (patch 2/5) This allows us to actually remove the lowlevel_init.S file from armv8 in patch 4/5, as sunxi was the only user. For good measure, we also clean up some bits in sunxi_common.h. (patch 5/5) I compile tested this for all sunxi boards, and boot tested (into Linux) on Pine64, PineH64, BananaPi M1, OrangePi Zero. But there is a high chance of something breaking, so please give it a good shake on whatever Allwinner hardware you have access to. Thanks, Andre Andre Przywara (5): sunxi: move non-essential code out of s_init() sunxi: move Cortex SMPEN setting into start.S sunxi: move early "SRAM setup" into separate file armv8: remove no longer needed lowlevel_init.S sunxi-common.h: remove pointless #ifdefs arch/arm/Kconfig | 3 -- arch/arm/cpu/armv7/Kconfig | 7 +++ arch/arm/cpu/armv7/start.S | 11 +++++ arch/arm/cpu/armv7/sunxi/Makefile | 3 ++ arch/arm/cpu/armv7/sunxi/sram.c | 45 +++++++++++++++++ arch/arm/cpu/armv8/Makefile | 1 - arch/arm/cpu/armv8/lowlevel_init.S | 43 ---------------- arch/arm/mach-sunxi/Kconfig | 2 - arch/arm/mach-sunxi/board.c | 78 ++++++++---------------------- include/configs/sunxi-common.h | 7 --- 10 files changed, 86 insertions(+), 114 deletions(-) create mode 100644 arch/arm/cpu/armv7/sunxi/sram.c delete mode 100644 arch/arm/cpu/armv8/lowlevel_init.S -- 2.17.6

4 19

[RFC PATCH 0/1] RISCV_EFI_BOOT_PROTOCOL support in U-boot
by Sunil V L 28 Jan '22

28 Jan '22

This patch adds the support in u-boot for new RISCV_EFI_BOOT_PROTOCOL for RISC-V UEFI platforms. This protocol is required to communicate the boot hart ID to the bootloader/kernel which need to follow the EFI calling conventions. The latest draft spec of this new protocol is available at https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0-rc2/RISCV… This u-boot patch can be found in: riscv_boot_protocol_rfc_v1 branch at https://github.com/vlsunil/u-boot.git This patch is tested in qemu. To fully test the feature, we need Linux changes which consume this protocol. The linux patch can be found in: riscv_boot_protocol_rfc_v1 branch at https://github.com/vlsunil/linux.git Sunil V L (1): efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support include/efi_api.h | 4 +++ include/efi_loader.h | 2 ++ include/efi_riscv.h | 16 +++++++++ lib/efi_loader/Kconfig | 7 ++++ lib/efi_loader/Makefile | 1 + lib/efi_loader/efi_riscv.c | 69 ++++++++++++++++++++++++++++++++++++++ lib/efi_loader/efi_setup.c | 6 ++++ 7 files changed, 105 insertions(+) create mode 100644 include/efi_riscv.h create mode 100644 lib/efi_loader/efi_riscv.c -- 2.25.1

3 5

Please pull u-boot-dm
by Simon Glass 28 Jan '22

28 Jan '22

Hi Tom, https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/10771 The following changes since commit 6146cd62aedc4849fec66f10ab0aa57f1dc64b8e: Merge branch '2022-01-24-assorted-updates' (2022-01-25 08:01:43 -0500) are available in the Git repository at: git://git.denx.de/u-boot-dm.git tags/dm-pull-26jan22 for you to fetch changes up to 2d2384bbaff0ab84c868b553c74048a5f6acc9e3: tools: mkimage: Show where signatures/keys are written (2022-01-26 08:50:44 -0700) ---------------------------------------------------------------- acpi refactoring to allow non-x86 use binman support for bintools (binary tools) minor tools improvements in preparation for FDT signing various minor fixes and improvements ---------------------------------------------------------------- Heiko Thiery (1): binman: doc: fix typo for u-boot-tpl Heinrich Schuchardt (2): sandbox: sandbox_serial_pending depends on DM_VIDEO sandbox: eth-raw: fix building with musl library Patrice Chotard (1): dm: Fix OF_BAD_ADDR definition Rasmus Villemoes (1): introduce CONFIG_DEVICE_TREE_INCLUDES Sean Anderson (1): usb: Use the first available device for ehci_gadget Simon Glass (83): x86: Allow any arch to generate ACPI tables x86: Move the acpi table to generic global_data arm: Allow supporting ACPI-table generation x86: Tidy up use of CONFIG_ACPIGEN sandbox: Allow building with GENERATE_ACPI_TABLE efi: Correct call to write_acpi_tables() efi: Correct address handling with ACPI tables acpi: Use finer-grained control of ACPI-table generation acpi: Allow include files within the board directory acpi: Move acpi_fill_header() to the generic header acpi: Add a table start acpi: Add a linker list for ACPI tables x86: acpi: Split out context creation from base tables x86: Use the ACPI table writer x86: Move base tables to a writer function x86: Move FACS table to a writer function x86: Move DSDT table to a writer function x86: Move GNVS table to a writer function x86: Move FADT table to a writer function x86: Move FACP table into separate functions x86: Move SSDT table to a writer function x86: Move TPM2 table to a writer function x86: Move MADT table to a writer function x86: Move TCPA table to a writer function x86: Move CSRT table to a writer function x86: acpi: Update acpi_fill_csrt() to use acpi_ctx x86: Move device-specific ACPI tables to a writer function x86: Move acpi_get_rsdp_addr() ACPI tables to the writer acpi: Collect tables in the acpi_item list acpi: Tidy up the item list acpi: Tidy up the table list doc: Add usage information for the acpi command acpi: Add some tables needed by ARM devices acpi: Add myself as maintainer Makefile: Fake external blobs by default with binman binman: Tweak elf tests for a toolchain change mkimage: Show the external-offset error binman: Expand the external FIT test a little patman: Allow running a tool and returning the full result buildman: Move the download function to tools patman: Tidy up the download function a little patman: Add a function to find a tool on the path binman: Drop the image name from the fake-blob message binman: Allow faked blobs in blob-ext-list binman: Correct path for fip_util binman: Add installation instructions binman: Add support for bintools binman: Plumb in support for bintools binman: Add tests for bintool binman: Add a bintool implementation for cbfstool binman: Add a bintool implementation for fiptool binman: Add a bintool implementation for futility binman: Add a bintool implementation for ifwitool binman: Add a bintool implementation for mkimage binman: Enable bintool tests including cmdline processing binman: Convert to using the CBFS bintool binman: Convert to using the FIP bintool binman: Convert to using the futility bintool binman: Convert to using the ifwitool bintool binman: Convert to using the mkimage bintool binman: Move compression into binman binman: Tidy up pylint warnings in comp_util binman: Add a bintool implementation for lz4 binman: Convert to using the lz4 bintool binman: Add a bintool implementation for lzma_alone binman: Convert to using the lzma_alone bintool binman: Plumb in support for missing bintools binman: Complete test coverage of comp_util binman: Add a command to generate bintool docs binman: Add documentation for bintools binman: Document the __bss_size symbol error rsa: Add debugging for failure cases fit_check_sign: Update help to mention the key is in a dtb tools: Move copyfile() into a common file tools: Avoid leaving extra data at the end of copied files tools: Improve comments in signing functions tools: Drop unused name in image-host tools: Avoid confusion between keys and signatures tools: Tidy up argument order in fit_config_check_sig() tools: Pass the key blob around image: Return destination node for add_verify_data() method tools: Pass public-key node through to caller tools: mkimage: Show where signatures/keys are written MAINTAINERS | 6 + Makefile | 2 +- arch/Kconfig | 6 +- arch/sandbox/cpu/eth-raw-os.c | 2 + arch/sandbox/include/asm/acpi_table.h | 2 + arch/sandbox/include/asm/global_data.h | 1 - arch/sandbox/include/asm/tables.h | 0 arch/x86/Kconfig | 9 - arch/x86/cpu/apollolake/acpi.c | 17 +- arch/x86/cpu/baytrail/acpi.c | 27 +- arch/x86/cpu/quark/acpi.c | 27 +- arch/x86/cpu/tangier/acpi.c | 34 ++- arch/x86/include/asm/acpi_table.h | 4 - arch/x86/include/asm/global_data.h | 1 - arch/x86/lib/Makefile | 2 +- arch/x86/lib/acpi_table.c | 374 +++++++------------------- boot/image-fit-sig.c | 151 ++++++++--- boot/image-fit.c | 12 +- cmd/acpi.c | 13 +- common/spl/spl_fit.c | 3 +- configs/cherryhill_defconfig | 1 + configs/chromebook_link64_defconfig | 1 + configs/chromebook_link_defconfig | 1 + configs/chromebook_samus_tpl_defconfig | 1 + configs/coreboot64_defconfig | 1 + configs/coreboot_defconfig | 1 + configs/crownbay_defconfig | 1 + configs/efi-x86_payload32_defconfig | 1 + configs/efi-x86_payload64_defconfig | 1 + configs/slimbootloader_defconfig | 1 + configs/tools-only_defconfig | 1 + doc/develop/devicetree/control.rst | 18 ++ doc/develop/package/bintools.rst | 1 + doc/usage/acpi.rst | 235 +++++++++++++++++ doc/usage/index.rst | 1 + drivers/core/acpi.c | 70 +++-- drivers/misc/qfw.c | 3 +- drivers/serial/sandbox.c | 2 +- drivers/usb/host/usb-uclass.c | 4 +- dts/Kconfig | 9 + include/acpi/acpi_table.h | 235 ++++++++++++++++- include/asm-generic/global_data.h | 8 + include/dm/acpi.h | 110 ++++++++ include/fdtdec.h | 5 +- include/image.h | 51 +++- include/u-boot/ecdsa.h | 5 +- include/u-boot/rsa.h | 5 +- lib/Kconfig | 18 ++ lib/Makefile | 2 +- lib/acpi/Makefile | 23 +- lib/acpi/acpi_table.c | 82 ------ lib/acpi/acpi_writer.c | 131 +++++++++ lib/acpi/base.c | 94 +++++++ lib/acpi/csrt.c | 49 ++++ lib/acpi/dsdt.c | 55 ++++ lib/acpi/facs.c | 35 +++ lib/acpi/ssdt.c | 49 ++++ lib/ecdsa/ecdsa-libcrypto.c | 4 +- lib/efi_loader/efi_acpi.c | 5 +- lib/rsa/rsa-sign.c | 5 +- lib/rsa/rsa-verify.c | 13 +- scripts/Makefile.lib | 6 +- test/dm/acpi.c | 79 ++++-- test/dm/ofnode.c | 2 +- test/dm/pci.c | 4 +- test/dm/test-fdt.c | 2 +- tools/binman/binman.rst | 129 ++++++++- tools/binman/bintool.py | 466 +++++++++++++++++++++++++++++++++ tools/binman/bintool_test.py | 353 +++++++++++++++++++++++++ tools/binman/bintools.rst | 115 ++++++++ tools/binman/btool/_testing.py | 36 +++ tools/binman/btool/cbfstool.py | 219 ++++++++++++++++ tools/binman/btool/fiptool.py | 123 +++++++++ tools/binman/btool/futility.py | 178 +++++++++++++ tools/binman/btool/ifwitool.py | 166 ++++++++++++ tools/binman/btool/lz4.py | 140 ++++++++++ tools/binman/btool/lzma_alone.py | 126 +++++++++ tools/binman/btool/mkimage.py | 80 ++++++ tools/binman/cbfs_util.py | 33 +-- tools/binman/cbfs_util_test.py | 59 ++--- tools/binman/cmdline.py | 12 + tools/binman/comp_util.py | 76 ++++++ tools/binman/control.py | 50 +++- tools/binman/elf_test.py | 8 +- tools/binman/entry.py | 47 +++- tools/binman/etype/blob_ext_list.py | 1 + tools/binman/etype/fit.py | 20 +- tools/binman/etype/gbb.py | 37 +-- tools/binman/etype/intel_ifwi.py | 25 +- tools/binman/etype/mkimage.py | 13 +- tools/binman/etype/section.py | 19 +- tools/binman/etype/vblock.py | 32 ++- tools/binman/fip_util.py | 26 -- tools/binman/fip_util_test.py | 25 +- tools/binman/ftest.py | 163 +++++++++++- tools/binman/image.py | 14 + tools/binman/main.py | 11 +- tools/binman/test/162_fit_external.dts | 2 +- tools/binman/test/218_blob_ext_list_fake.dts | 14 + tools/buildman/toolchain.py | 46 +--- tools/fdt_host.h | 8 + tools/fit_check_sign.c | 4 +- tools/fit_common.c | 69 +++++ tools/fit_common.h | 23 ++ tools/fit_image.c | 64 +---- tools/image-host.c | 155 ++++++++--- tools/imagetool.h | 3 + tools/mkimage.c | 4 + tools/patman/tools.py | 238 +++++++++-------- 109 files changed, 4567 insertions(+), 989 deletions(-) create mode 100644 arch/sandbox/include/asm/tables.h create mode 120000 doc/develop/package/bintools.rst create mode 100644 doc/usage/acpi.rst create mode 100644 lib/acpi/acpi_writer.c create mode 100644 lib/acpi/base.c create mode 100644 lib/acpi/csrt.c create mode 100644 lib/acpi/dsdt.c create mode 100644 lib/acpi/facs.c create mode 100644 lib/acpi/ssdt.c create mode 100644 tools/binman/bintool.py create mode 100644 tools/binman/bintool_test.py create mode 100644 tools/binman/bintools.rst create mode 100644 tools/binman/btool/_testing.py create mode 100644 tools/binman/btool/cbfstool.py create mode 100644 tools/binman/btool/fiptool.py create mode 100644 tools/binman/btool/futility.py create mode 100644 tools/binman/btool/ifwitool.py create mode 100644 tools/binman/btool/lz4.py create mode 100644 tools/binman/btool/lzma_alone.py create mode 100644 tools/binman/btool/mkimage.py create mode 100644 tools/binman/comp_util.py create mode 100644 tools/binman/test/218_blob_ext_list_fake.dts Regards, Simon

2 3