January 2025 - U-Boot

[PATCH] mach-snapdragon: fix board_fdt_blob_setup()
by Caleb Connolly 23 Jan '25

23 Jan '25

In fc37a73e6679 (fdt: Swap the signature for board_fdt_blob_setup()) there was a subtle change to the Snapdragon implementation, removing the assignment to gd->fdt_blob partway through the function. This breaks qcom_parse_memory() which was also called during board_fdt_blob_setup(). Since this was a strange (and seemingly unnecessary choice), take the chance to move this to the more typical dram_init() phase so that we don't depend on gd->fdt_blob being correct until after board_fdt_blob_setup() has finished. Fixes: fc37a73e6679 (fdt: Swap the signature for board_fdt_blob_setup()) Signed-off-by: Caleb Connolly <caleb.connolly(a)linaro.org> --- arch/arm/mach-snapdragon/board.c | 67 +++++++++++++++----------------- 1 file changed, 31 insertions(+), 36 deletions(-) diff --git a/arch/arm/mach-snapdragon/board.c b/arch/arm/mach-snapdragon/board.c index f1319df43147..fbb3d6e588e3 100644 --- a/arch/arm/mach-snapdragon/board.c +++ b/arch/arm/mach-snapdragon/board.c @@ -45,17 +45,8 @@ static struct { phys_addr_t start; phys_size_t size; } prevbl_ddr_banks[CONFIG_NR_DRAM_BANKS] __section(".data") = { 0 }; -int dram_init(void) -{ - /* - * gd->ram_base / ram_size have been setup already - * in qcom_parse_memory(). - */ - return 0; -} - static int ddr_bank_cmp(const void *v1, const void *v2) { const struct { phys_addr_t start; @@ -69,42 +60,22 @@ static int ddr_bank_cmp(const void *v1, const void *v2) return (res1->start >> 24) - (res2->start >> 24); } -/* This has to be done post-relocation since gd->bd isn't preserved */ -static void qcom_configure_bi_dram(void) -{ - int i; - - for (i = 0; i < CONFIG_NR_DRAM_BANKS; i++) { - gd->bd->bi_dram[i].start = prevbl_ddr_banks[i].start; - gd->bd->bi_dram[i].size = prevbl_ddr_banks[i].size; - } -} - -int dram_init_banksize(void) -{ - qcom_configure_bi_dram(); - - return 0; -} - static void qcom_parse_memory(void) { ofnode node; - const fdt64_t *memory; + const fdt64_t *memory = NULL; int memsize; phys_addr_t ram_end = 0; int i, j, banks; node = ofnode_path("/memory"); - if (!ofnode_valid(node)) { - log_err("No memory node found in device tree!\n"); - return; - } - memory = ofnode_read_prop(node, "reg", &memsize); - if (!memory) { - log_err("No memory configuration was provided by the previous bootloader!\n"); + if (ofnode_valid(node)) + memory = ofnode_read_prop(node, "reg", &memsize); + + if (!memory || !ofnode_valid(node)) { + panic("No memory configuration was provided by the previous bootloader!\n"); return; } banks = min(memsize / (2 * sizeof(u64)), (ulong)CONFIG_NR_DRAM_BANKS); @@ -134,8 +105,32 @@ static void qcom_parse_memory(void) debug("ram_base = %#011lx, ram_size = %#011llx, ram_end = %#011llx\n", gd->ram_base, gd->ram_size, ram_end); } +int dram_init(void) +{ + qcom_parse_memory(); + return 0; +} + +/* This has to be done post-relocation since gd->bd isn't preserved */ +static void qcom_configure_bi_dram(void) +{ + int i; + + for (i = 0; i < CONFIG_NR_DRAM_BANKS; i++) { + gd->bd->bi_dram[i].start = prevbl_ddr_banks[i].start; + gd->bd->bi_dram[i].size = prevbl_ddr_banks[i].size; + } +} + +int dram_init_banksize(void) +{ + qcom_configure_bi_dram(); + + return 0; +} + static void show_psci_version(void) { struct arm_smccc_res res; @@ -173,9 +168,9 @@ int board_fdt_blob_setup(void **fdtp) ret = -EEXIST; } else { debug("Using external FDT\n"); /* So we can use it before returning */ - *fdtp = fdt; + gd->fdt_blob = *fdtp = fdt; } /* * Parse the /memory node while we're here, -- 2.48.0

2 2

[PATCH v6 1/3] bloblist: add api to get blob with size
by Raymond Mao 23 Jan '25

23 Jan '25

bloblist_find function only returns the pointer of blob data, which is fine for those self-describing data like FDT. But as a common scenario, an interface is needed to retrieve both the pointer and the size of the blob data. Add a few ut test cases for the new api. Signed-off-by: Raymond Mao <raymond.mao(a)linaro.org> Reviewed-by: Simon Glass <sjg(a)chromium.org> Reviewed-by: Ilias Apalodimas <ilias.apalodimas(a)linaro.org> --- Changes in v2 - Rename function argument. - Add ut tests. Changes in v3 - None. Changes in v4 - None. Changes in v5 - None. Changes in v6 - None. common/bloblist.c | 17 +++++++++++++++-- include/bloblist.h | 18 ++++++++++++++++++ test/common/bloblist.c | 4 ++++ 3 files changed, 37 insertions(+), 2 deletions(-) diff --git a/common/bloblist.c b/common/bloblist.c index 110bb9dc44..ab48a3cdb9 100644 --- a/common/bloblist.c +++ b/common/bloblist.c @@ -222,14 +222,27 @@ static int bloblist_ensurerec(uint tag, struct bloblist_rec **recp, int size, } void *bloblist_find(uint tag, int size) +{ + void *blob = NULL; + int blob_size; + + blob = bloblist_get_blob(tag, &blob_size); + + if (size && size != blob_size) + return NULL; + + return blob; +} + +void *bloblist_get_blob(uint tag, int *sizep) { struct bloblist_rec *rec; rec = bloblist_findrec(tag); if (!rec) return NULL; - if (size && size != rec->size) - return NULL; + + *sizep = rec->size; return (void *)rec + rec_hdr_size(rec); } diff --git a/include/bloblist.h b/include/bloblist.h index f999391f74..52ba0ddcf8 100644 --- a/include/bloblist.h +++ b/include/bloblist.h @@ -250,6 +250,24 @@ static inline void *bloblist_check_magic(ulong addr) return ptr; } +#if CONFIG_IS_ENABLED(BLOBLIST) +/** + * bloblist_get_blob() - Find a blob and get the size of it + * + * Searches the bloblist and returns the blob with the matching tag + * + * @tag: Tag to search for (enum bloblist_tag_t) + * @sizep: Size of the blob found + * Return: pointer to bloblist if found, or NULL if not found + */ +void *bloblist_get_blob(uint tag, int *sizep); +#else +static inline void *bloblist_get_blob(uint tag, int *sizep) +{ + return NULL; +} +#endif + /** * bloblist_find() - Find a blob * diff --git a/test/common/bloblist.c b/test/common/bloblist.c index 4bca62110a..324127596f 100644 --- a/test/common/bloblist.c +++ b/test/common/bloblist.c @@ -98,10 +98,12 @@ static int bloblist_test_blob(struct unit_test_state *uts) struct bloblist_hdr *hdr; struct bloblist_rec *rec, *rec2; char *data; + int size = 0; /* At the start there should be no records */ hdr = clear_bloblist(); ut_assertnull(bloblist_find(TEST_TAG, TEST_BLOBLIST_SIZE)); + ut_assertnull(bloblist_get_blob(TEST_TAG, &size)); ut_assertok(bloblist_new(TEST_ADDR, TEST_BLOBLIST_SIZE, 0, 0)); ut_asserteq(sizeof(struct bloblist_hdr), bloblist_get_size()); ut_asserteq(TEST_BLOBLIST_SIZE, bloblist_get_total_size()); @@ -114,6 +116,8 @@ static int bloblist_test_blob(struct unit_test_state *uts) ut_asserteq_addr(rec + 1, data); data = bloblist_find(TEST_TAG, TEST_SIZE); ut_asserteq_addr(rec + 1, data); + ut_asserteq_addr(bloblist_get_blob(TEST_TAG, &size), data); + ut_asserteq(size, TEST_SIZE); /* Check the data is zeroed */ ut_assertok(check_zero(data, TEST_SIZE)); -- 2.25.1

3 6

[PATCH v2 0/2] mach-snapdragon: Fix and improve /memory parsing
by Sam Day 23 Jan '25

23 Jan '25

The first commit in this series is a fix for qcom_parse_memory, which is currently broken on master (since fc37a73e6679). It's an alternative to the patch Caleb proposed a couple of days ago (20250117102734.3725009-2-caleb.connolly(a)linaro.org). This approach results in a smaller diff, and also makes it possible to do the thing introduced in the second commit. The second commit introduces the ability to boot with an internal DT that lacks a fully specified /memory node, instead obtaining that information from the FDT supplied by the previous bootloader. The first commit should ideally land even if the second one needs more rounds before it's ready. I opted to submit both commits together as one series because, as noted earlier, the way the fix is done introduces functionality that the second commit relies on (specifically: passing the pointer of the specific FDT to parse for its /memory node). I've tested both these commits together on an msm8916 device and an sdm845 device. The msm8916 device booted with an internal DT that relies on /memory in the external FDT to properly function. The sdm845 device booted with an entirely external FDT. So I reckon I hit all the various code paths in both qcom_parse_memory and board_fdt_blob_setup. Signed-off-by: Sam Day <me(a)samcday.com> --- Changes in v2: - Update qcom_parse_memory to return -ENODATA if provided FDT lacks valid /memory node - Reworked board_fdt_blob_setup logic to always try qcom_parse_memory on internal FDT, falling back to external if needed - Link to v1: https://lore.kernel.org/r/20250120-qcom-parse-memory-updates-v1-0-54a7f0550… --- Sam Day (2): mach-snapdragon: pass fdt to qcom_parse_memory mach-snapdragon: support parsing memory info from external FDT arch/arm/mach-snapdragon/board.c | 100 ++++++++++++++++++++++++++------------- 1 file changed, 67 insertions(+), 33 deletions(-) --- base-commit: 639cd409987acf173eaffebe7876968b42fd7c32 change-id: 20250120-qcom-parse-memory-updates-96ffe248cdf1 Best regards, -- Sam Day <me(a)samcday.com>

3 8

[PATCH v4 0/9] Restore USB and add UMS support for STiH407-B2260
by Patrice Chotard 23 Jan '25

23 Jan '25

This series is : _ restoring USB on STiH410-B2260 which hasn't been tested since a while. _ migrating STi DWC3 glue from proprietary driver to dwc3-generic driver. _ adding UMS support for STiH410-B2260. Changes in v4: - Update Kconfig description Changes in v3: - Update comment by adding "Remove useless include files" - Replace debug() by dev_err() - check return value of syscon_regmap_lookup_by_phandle() Changes in v2: - remove useless include files - add dwc3-sti.c DWC3 wrapper as done for dwc3-am62.c Patrice Chotard (9): ARM: dts: sti: Add fixed clock for ehci and ohci nodes in stih410-b2260.dtsi configs: stih410-b2260: Enable DM_REGULATOR flag usb: dwc3-generic: Reorder include usb: dwc3-generic: Add STih407 support configs: stih410-b2260: Enable USB_DWC3_GENERIC and USB_DWC3_STI flags usb: dwc3: Remove dwc3 glue driver support for STi configs: stih410-b2260: Enable DM_USB_GADGET flag board: stih410-b2260: Remove board_usb_init/cleanup() configs: stih410-b2260: Enable CMD_USB_MASS_STORAGE flag MAINTAINERS | 3 +- arch/arm/dts/stih410-b2260-u-boot.dtsi | 10 + board/st/stih410-b2260/board.c | 30 --- configs/stih410-b2260_defconfig | 5 + drivers/usb/dwc3/Kconfig | 8 + drivers/usb/dwc3/Makefile | 1 + drivers/usb/dwc3/dwc3-generic-sti.c | 132 +++++++++++++ drivers/usb/dwc3/dwc3-generic.c | 20 +- drivers/usb/host/Kconfig | 9 - drivers/usb/host/Makefile | 1 - drivers/usb/host/dwc3-sti-glue.c | 253 ------------------------- include/dwc3-sti-glue.h | 41 ---- 12 files changed, 161 insertions(+), 352 deletions(-) create mode 100644 drivers/usb/dwc3/dwc3-generic-sti.c delete mode 100644 drivers/usb/host/dwc3-sti-glue.c delete mode 100644 include/dwc3-sti-glue.h -- 2.25.1

1 9

[PATCH 00/28] test: Complete the suite migration
by Simon Glass 23 Jan '25

23 Jan '25

This series completes the removal of test commands for suites. With this it is possible to declare a suite (including init and uninit functions) without needing to write a command. It also adds timing for test suites, so we can keep track of how long things take. Simon Glass (28): test: Fix a stray asterisk in ut_run_list() test: Add up the number of tests manually test: Keep track of suite duration test: Show the average time per test test: Leave out the prefix when printing test names test: Support an init/uninit functions for test suites test: Tweak FDT-overlay tests test: Move env-test rule into test/ test: Move optee-test rule into test/ test: Move fdt-overlay-test rule into test/ test: Make all tests depend on UNIT_TEST test: Move fdt_overlay init into a function test: Update fdt_overlay test to use fdtdec functions test: Update fdt_overlay to do init from tests test: Drop the function for running fdt_overlay tests test: Update bootstd to do init from tests test: Drop the function for running bootstd tests test: Update optee to do init and uninit from tests test: Split optee tests into three functions test: Drop the function for running optee tests test: Rename optee test-file test: Drop support for test commands test: Make cmd_ut_category() static test: Drop suites.h test: Allow running a selection of suites test: Move code out of cmd_ut_category() test: Do flag-processing in the correct place test: Update documentation Makefile | 3 - doc/develop/tests_writing.rst | 52 ++-- doc/usage/cmd/ut.rst | 145 ++++++++--- drivers/timer/sandbox_timer.c | 5 + include/test/fdt_overlay.h | 19 ++ include/test/optee.h | 4 +- include/test/overlay.h | 15 -- include/test/suites.h | 43 ---- include/test/test.h | 28 ++ include/time.h | 15 +- test/Kconfig | 23 +- test/Makefile | 3 + test/boot/bootdev.c | 1 - test/boot/bootflow.c | 1 - test/boot/bootm.c | 1 - test/boot/bootmeth.c | 1 - test/boot/bootstd_common.c | 29 +-- test/boot/bootstd_common.h | 10 +- test/boot/expo.c | 1 - test/boot/image.c | 1 - test/boot/measurement.c | 1 - test/boot/upl.c | 1 - test/boot/vbe_simple.c | 4 - test/cmd/addrmap.c | 1 - test/cmd/bdinfo.c | 1 - test/cmd/exit.c | 1 - test/cmd/fdt.c | 1 - test/cmd/font.c | 1 - test/cmd/loadm.c | 1 - test/cmd/mbr.c | 1 - test/cmd/pci_mps.c | 1 - test/cmd/seama.c | 1 - test/cmd/setexpr.c | 1 - test/cmd_ut.c | 243 ++++++++++-------- test/common/bloblist.c | 1 - test/dm/Kconfig | 2 +- test/env/Kconfig | 1 - test/env/cmd_ut_env.c | 1 - test/{overlay => fdt_overlay}/Kconfig | 4 +- test/{overlay => fdt_overlay}/Makefile | 2 +- .../cmd_ut_fdt_overlay.c} | 221 +++++++--------- .../test-fdt-base.dts | 0 .../test-fdt-overlay-stacked.dtso | 0 .../test-fdt-overlay.dtso | 0 test/log/cont_test.c | 1 - test/log/nolog_test.c | 1 - test/log/pr_cont_test.c | 1 - test/log/syslog_test.c | 1 - test/log/syslog_test_ndebug.c | 1 - test/optee/Kconfig | 2 +- test/optee/Makefile | 2 +- test/optee/{cmd_ut_optee.c => optee.c} | 105 +++++--- test/py/tests/test_suite.py | 34 ++- test/test-main.c | 41 ++- 54 files changed, 587 insertions(+), 493 deletions(-) create mode 100644 include/test/fdt_overlay.h delete mode 100644 include/test/overlay.h delete mode 100644 include/test/suites.h rename test/{overlay => fdt_overlay}/Kconfig (81%) rename test/{overlay => fdt_overlay}/Makefile (89%) rename test/{overlay/cmd_ut_overlay.c => fdt_overlay/cmd_ut_fdt_overlay.c} (56%) rename test/{overlay => fdt_overlay}/test-fdt-base.dts (100%) rename test/{overlay => fdt_overlay}/test-fdt-overlay-stacked.dtso (100%) rename test/{overlay => fdt_overlay}/test-fdt-overlay.dtso (100%) rename test/optee/{cmd_ut_optee.c => optee.c} (70%) -- 2.43.0

2 31

[PATCH v3 0/9] Restore USB and add UMS support for STiH407-B2260
by Patrice Chotard 23 Jan '25

23 Jan '25

This series is : _ restoring USB on STiH410-B2260 which hasn't been tested since a while. _ migrating STi DWC3 glue from proprietary driver to dwc3-generic driver. _ adding UMS support for STiH410-B2260. Changes in v3: - Update comment by adding "Remove useless include files" - Replace debug() by dev_err() - check return value of syscon_regmap_lookup_by_phandle() Changes in v2: - remove useless include files - add dwc3-sti.c DWC3 wrapper as done for dwc3-am62.c Patrice Chotard (9): ARM: dts: sti: Add fixed clock for ehci and ohci nodes in stih410-b2260.dtsi configs: stih410-b2260: Enable DM_REGULATOR flag usb: dwc3-generic: Reorder include usb: dwc3-generic: Add STih407 support configs: stih410-b2260: Enable USB_DWC3_GENERIC and USB_DWC3_STI flags usb: dwc3: Remove dwc3 glue driver support for STi configs: stih410-b2260: Enable DM_USB_GADGET flag board: stih410-b2260: Remove board_usb_init/cleanup() configs: stih410-b2260: Enable CMD_USB_MASS_STORAGE flag MAINTAINERS | 3 +- arch/arm/dts/stih410-b2260-u-boot.dtsi | 10 + board/st/stih410-b2260/board.c | 30 --- configs/stih410-b2260_defconfig | 5 + drivers/usb/dwc3/Kconfig | 6 + drivers/usb/dwc3/Makefile | 1 + drivers/usb/dwc3/dwc3-generic-sti.c | 132 +++++++++++++ drivers/usb/dwc3/dwc3-generic.c | 20 +- drivers/usb/host/Kconfig | 9 - drivers/usb/host/Makefile | 1 - drivers/usb/host/dwc3-sti-glue.c | 253 ------------------------- include/dwc3-sti-glue.h | 41 ---- 12 files changed, 159 insertions(+), 352 deletions(-) create mode 100644 drivers/usb/dwc3/dwc3-generic-sti.c delete mode 100644 drivers/usb/host/dwc3-sti-glue.c delete mode 100644 include/dwc3-sti-glue.h -- 2.25.1

3 12

[PATCH v2] arm: Remove redundant loading of image copy start offse
by 1425075683＠qq.com 23 Jan '25

23 Jan '25

From: Liya Huang <1425075683(a)qq.com> Because the beginning is already computed Signed-off-by: Liya Huang <1425075683(a)qq.com> --- Changes in v2: - Due to an error, the patch was resubmitted, leaving the code unchanged - Sorry for the trouble; Due to the lack of understanding of the process, the previous patch information was Reviewed-by. Please refer to this patch arch/arm/lib/relocate.S | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/arm/lib/relocate.S b/arch/arm/lib/relocate.S index 345e282e3e..bffadfecba 100644 --- a/arch/arm/lib/relocate.S +++ b/arch/arm/lib/relocate.S @@ -83,8 +83,6 @@ relocate_base: add r1, r3 /* r1 <- Run &__image_copy_start */ subs r4, r0, r1 /* r4 <- Run to copy offset */ beq relocate_done /* skip relocation */ - ldr r1, _image_copy_start_ofs - add r1, r3 /* r1 <- Run &__image_copy_start */ ldr r2, _image_copy_end_ofs add r2, r3 /* r2 <- Run &__image_copy_end */ copy_loop: -- 2.25.1

2 1

[PATCH 0/8] sunxi: (early) Allwinner A133 SoC support
by Andre Przywara 23 Jan '25

23 Jan '25

The Allwinner A100 SoC has been around for a while, mostly on cheap tablets, but didn't generate much interest in the community so far. There were some efforts by two Allwinner employees in 2020, which led to basic upstream Linux support for that SoC, although this momentum dried up pretty quickly, leaving a lot of peripherals unsupported. The A100 was silently replaced with the seemingly identical Allwinner A133, which is reportedly a better bin of the A100. So far we assume that both are compatible from a software perspective. There are some more devices with the A133 out there now, so people are working on filling the gaps, and adding U-Boot and TF-A support. This series is a somewhat early version of a series to support boards with the A133 SoC in U-Boot. Since the basic SoC .dtsi and its bindings are upstream in the Linux kernel repository, we can go ahead and add support for the pinctrl and clock drivers: this is handled in patches 4 and 5. Similarly ready are some refactoring patches, which will be needed later, those are the first three patches. Patch 6 adds SPL support for the AXP707/803 PMIC, which is often paired with the A133. Pending some review I am tempted to push those patches rather quickly. Patch 7 is the technically most advanced and challenging patch: to add support for the DRAM controller. Huge thanks and kudos go to Cody, for reverse engineering, debugging and testing this. The patch itself is work in progress, and surely needs some love beyond the missing register bits, to improve formatting, coding style and patch split. However it works for me (TM), and is essential for the SoC support, so I include it here, as an early reference. Cody hinted at sending a proper version, this can then later replace this preliminary patch. Patch 8 then puts the right values for various existing Allwinner specific configuration options in Kconfig, and adds the remaining bits required to enable configuration and build for boards with the A133 SoC. Due to a lack of an upstream DT for the boards floating around at the moment, this lacks any defconfig for now, but adding support for a board just requires providing the defconfig with the DRAM parameters and generic options, plus the respective .dts file. This has been tested locally on a Liontron H-A133L here, I will send both the .dts and the defconfig when they are ready. For now please have a look, comment and review on the patches, so that we can start upstream support for this SoC. Cheers, Andre Andre Przywara (7): sunxi: clock: improve grouping of default clock register values sunxi: pmic_bus: support alternative I2C address sunxi: H616: DRAM: rename Kconfig parameters to be more generic clk: sunxi: Add support for the A100/A133 CCU pinctrl: sunxi: add Allwinner A100/A133 pinctrl description power: pmic: sunxi: add SPL support for the AXP803 sunxi: add support for the Allwinner A100/A133 SoC Cody Eksal (1): sunxi: A133: add DRAM init code [WIP!] arch/arm/cpu/armv8/fel_utils.S | 2 +- .../include/asm/arch-sunxi/clock_sun50i_h6.h | 25 +- .../include/asm/arch-sunxi/cpu_sun50i_h6.h | 4 + arch/arm/include/asm/arch-sunxi/dram.h | 2 + .../include/asm/arch-sunxi/dram_sun50i_a133.h | 210 +++ arch/arm/mach-sunxi/Kconfig | 254 +++- arch/arm/mach-sunxi/Makefile | 2 + arch/arm/mach-sunxi/board.c | 4 + arch/arm/mach-sunxi/clock_sun50i_h6.c | 3 +- arch/arm/mach-sunxi/cpu_info.c | 2 + arch/arm/mach-sunxi/dram_sun50i_a133.c | 1217 +++++++++++++++++ arch/arm/mach-sunxi/dram_sun50i_h616.c | 26 +- arch/arm/mach-sunxi/dram_timings/Makefile | 2 + arch/arm/mach-sunxi/dram_timings/a133_ddr4.c | 80 ++ .../arm/mach-sunxi/dram_timings/a133_lpddr4.c | 102 ++ arch/arm/mach-sunxi/pmic_bus.c | 10 +- board/sunxi/board.c | 13 +- common/spl/Kconfig | 6 +- configs/anbernic_rg35xx_h700_defconfig | 20 +- configs/orangepi_zero2_defconfig | 8 +- configs/orangepi_zero2w_defconfig | 16 +- configs/orangepi_zero3_defconfig | 16 +- configs/tanix_tx1_defconfig | 16 +- configs/transpeed-8k618-t_defconfig | 14 +- configs/x96_mate_defconfig | 14 +- drivers/clk/sunxi/Kconfig | 7 + drivers/clk/sunxi/Makefile | 1 + drivers/clk/sunxi/clk_a100.c | 102 ++ drivers/clk/sunxi/clk_sunxi.c | 5 + drivers/pinctrl/sunxi/Kconfig | 10 + drivers/pinctrl/sunxi/pinctrl-sunxi.c | 47 + drivers/power/Kconfig | 23 +- drivers/power/Makefile | 1 + drivers/power/axp_spl.c | 17 + 34 files changed, 2151 insertions(+), 130 deletions(-) create mode 100644 arch/arm/include/asm/arch-sunxi/dram_sun50i_a133.h create mode 100644 arch/arm/mach-sunxi/dram_sun50i_a133.c create mode 100644 arch/arm/mach-sunxi/dram_timings/a133_ddr4.c create mode 100644 arch/arm/mach-sunxi/dram_timings/a133_lpddr4.c create mode 100644 drivers/clk/sunxi/clk_a100.c -- 2.46.2

4 23

[PATCH 0/2] Clarify DM_FLAG_PROBE_AFTER_BIND behaviour
by Caleb Connolly 23 Jan '25

23 Jan '25

In Simons series reworking autoprobe[1], a discussion came up about DM_FLAG_PROBE_AFTER_BIND, specifically that it wasn't very clear where this flag should be used. This series implements my suggestions made there to clarify the use of this flag, and fixup the two driver which erroneously apply it to their driver struct (this does nothing). [1]: https://lore.kernel.org/u-boot/20241120153642.861633-1-sjg@chromium.org/ --- Caleb Connolly (2): dm: clarify DM_FLAG_PROBE_AFTER_BIND behaviour drivers: remove bogus DM_FLAG_PROBE_AFTER_BIND flags doc/develop/driver-model/design.rst | 6 ++++-- drivers/mailbox/zynqmp-ipi.c | 1 - drivers/watchdog/da9063-wdt.c | 1 - include/dm/device.h | 5 ++++- 4 files changed, 8 insertions(+), 5 deletions(-) --- base-commit: e3f716fa2d58aadf53928475ee7e88eb41cb8031 // Caleb (they/them)

3 7

[PATCH 1/2] spi: ca_sflash: Remove redundant dependency
by Alexander Dahl 23 Jan '25

23 Jan '25

This is inside of an 'if DM_SPI' block, and thus always true. Signed-off-by: Alexander Dahl <ada(a)thorsis.com> --- drivers/spi/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig index 96ea033082b..6555142a41e 100644 --- a/drivers/spi/Kconfig +++ b/drivers/spi/Kconfig @@ -135,7 +135,7 @@ config BCMSTB_SPI config CORTINA_SFLASH bool "Cortina-Access Serial Flash controller driver" - depends on DM_SPI && SPI_MEM + depends on SPI_MEM help Enable the Cortina-Access Serial Flash controller driver. This driver can be used to access the SPI NOR/NAND flash on platforms embedding this -- 2.39.5

2 1