February 2024 - U-Boot

HABv4 with SPL and u-boot-dtb.img on i.MX6
by Benjamin Lemouzy 22 Feb '24

22 Feb '24

Hello, I'm trying to make secure boot work on i.MX6 SABRE with SPL and u-boot-dtb.img files and I'm not sure how to do it. I'm using the U-Boot vanilla master branch (2024.04-rc2) with the following configuration: # Remove some stuff to not exceed file size limit $ cat <<EOF >> configs/mx6sabresd_defconfig CONFIG_BOOTMETH_EFILOADER=n CONFIG_CMD_NET=n CONFIG_NET=n EOF # Enable secure boot $ cat <<EOF >> configs/mx6sabresd_defconfig CONFIG_IMX_HAB=y CONFIG_SPL_LOAD_FIT_ADDRESS=0x18000000 EOF $ make ARCH=arm O=build mx6sabresd_defconfig $ make ARCH=arm O=build I have no issue to generate a working SPL-signed file following doc/imx/habv4/guides/mx6_mx7_spl_secure_boot.txt instructions. doc/imx/habv4/guides/mx6_mx7_spl_secure_boot.txt only gives instructions to sign u-boot-ivt.img but this file doesn't contain device trees listed in CONFIG_OF_LIST as u-boot-dtb.img does and I need them. NXP AN4581 lists 2 possible formats to sign additional images: - Image format: ------- +-----------------------------+ <-- *load_address ^ | | | | | | | Image data | Signed | | | Data | | | | +-----------------------------+ | | Padding Next Boundary | | +-----------------------------+ <-- *ivt v | Image Vector Table | ------- +-----------------------------+ <-- *csf | | | Command Sequence File (CSF) | | | +-----------------------------+ | Padding (optional) | +-----------------------------+ - FIT image format: ------- +-----------------------------+ ------- ^ | | ^ | | | | | | FDT FIT | | | | | | Signed data | | | | | +-----------------------------+ | | | Padding Next Boundary | | | +-----------------------------+ | v | Image Vector Table | | ------- +-----------------------------+ | FIT image | | | | Command Sequence File (CSF) | | | | | +-----------------------------+ | | Padding (optional) | | ------- +-----------------------------+ | ^ | | | Signed data | | U-Boot | | v | | v ------- +-----------------------------+ ------- And as u-boot-dtb.img is a FIT image, I probably have to use the FIT image format, right? I manually craft the signed FIT image using doc/imx/habv4/csf_examples/mx8m/csf.sh as reference and everything looks fine: U-Boot SPL 2024.04-rc2-00025-g9e00b6993f-dirty (Feb 19 2024 - 13:17:31 +0100) >>SPL: board_init_r() spl_init Trying to boot from MMC1 fit read offset 11400, size=12800, dst=18000000, count=12800 spl_load_simple_fit_fix_load: ivt: 18001000 offset: 1000 size: 3060 spl_load_simple_fit_fix_load: ivt self: 18001000 hab fuse not enabled Authenticate image from DDR location 0x18000000... ivt_offset = 0x1000, ivt addr = 0x18001000 ivt entry = 0x18000000, dcd = 0x00000000, csf = 0x18001020 Dumping IVT .. @............ ........ ....... Dumping CSF Header ..PC...........P ................ .......<........ ...............8 Calling authenticate_image in ROM ivt_offset = 0x1000 start = 0x18000000 bytes = 0x3060 firmware: 'firmware-1' External data: dst=17800000, offset=3060, size=86138 Image OS is U-Boot fdt: 'fdt-1' Can't get 'load' property from FIT 0x18000000, node: offset 464, name fdt-1 (FDT_ERR_NOTFOUND) External data: dst=17886140, offset=89198, size=ac00 Can't get 'entry' property from FIT 0x18000000, node: offset 464, name fdt-1 (FDT_ERR_NOTFOUND) loadables: 'firmware-1' no string for index 1 Jumping to U-Boot... SPL malloc() used 0x0 bytes (0 KB) image entry point: 0x U-Boot 2024.04-rc2-00025-g9e00b6993f-dirty (Feb 19 2024 - 13:17:31 +0100) CPU: Freescale i.MX6Q rev1.2 996 MHz (running at 792 MHz) CPU: Automotive temperature grade (-40C to 125C) at 35C Reset cause: POR Model: Freescale i.MX6 Quad SABRE Smart Device Board DRAM: 1 GiB Core: 94 devices, 23 uclasses, devicetree: separate WDT: Started watchdog@20c0000 with servicing every 1000ms (128s timeout) MMC: FSL_SDHC: 4, FSL_SDHC: 1, FSL_SDHC: 3 Loading Environment from MMC... *** Warning - bad CRC, using default environment No panel detected: default to Hannstar-XGA Display: Hannstar-XGA (1024x768) In: serial Out: serial Err: serial SEC0: RNG instantiated Hit any key to stop autoboot: 0 => hab_status Secure boot disabled HAB Configuration: 0xf0, HAB State: 0x66 No HAB Events Found! But as only the FDT part of the FIT image is checked through HAB, U-Boot and DTB are only protected by FIT image hashes, right? Using fdtdump shows that crc32 is used as hash algorithm for FIT image which is a super weak one. I tried to pass another algo (sha256) using mkimage -o option but that doesn't work. ./tools/mkimage -f auto -A arm -T firmware -C none -O u-boot -a 0x17800000 -e 0x17800000 -p 0x0 -n "U-Boot 2024.04-rc2-00025-g9e00b6993f-dirty for mx6sabresd board" -E -b arch/arm/dts/imx6q-sabresd.dtb -b arch/arm/dts/imx6qp-sabresd.dtb -b arch/arm/dts/imx6dl-sabresd.dtb -d u-boot-nodtb.bin -o sha256 u-boot-dtb.img Is there any way to change U-Boot FIT image hash? I also try to use image format and force the HAB to verify the whole u-boot-dtb.img file by patching the FIT image size: image_size=$(stat -tc %s u-boot-dtb.img) printf "00000004: %08x" "$image_size" | xxd -r - u-boot-dtb.img SPL starts, authentication looks fine but the boot fails. Is there any chance to make it work or is it insane to try to use this format? Regards, Benjamin

2 2

[PATCH] ecdsa: Avoid null pointer crash in ecdsa-verify due to absent property
by Bob Wolff 22 Feb '24

22 Feb '24

If mixed rsa and ecdsa keys are specified in dtsi, an rsa key can be sent into the ecdsa verify. Without the ecdsa,curve property, this function will crash due to lack of checking the null pointer return. Signed-off-by: Bob Wolff <bob.wolff68(a)gmail.com> --- lib/ecdsa/ecdsa-verify.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lib/ecdsa/ecdsa-verify.c b/lib/ecdsa/ecdsa-verify.c index 0601700c4f..01ffc3477c 100644 --- a/lib/ecdsa/ecdsa-verify.c +++ b/lib/ecdsa/ecdsa-verify.c @@ -31,6 +31,11 @@ static int fdt_get_key(struct ecdsa_public_key *key, const void *fdt, int node) int x_len, y_len; key->curve_name = fdt_getprop(fdt, node, "ecdsa,curve", NULL); + if (!key->curve_name) { + printf("Error: ecdsa cannot get 'ecdsa,curve' property from key. Likely not an ecdsa key.\n"); + return -ENOMSG; + } + key->size_bits = ecdsa_key_size(key->curve_name); if (key->size_bits == 0) { debug("Unknown ECDSA curve '%s'", key->curve_name); -- 2.39.3 (Apple Git-145)

2 1

[PATCH 00/11] board/ti: k3 boards: Stop using findfdt
by Nishanth Menon 21 Feb '24

21 Feb '24

Hi, Hopefully the last time. Apologies on the screw ups. Ran CI loop[1] to be doubly sure that I have'nt yet again fat fingered something. This is a wide cleanup to switch to setting fdtfile using env_set instead of scripted magic. 'fdtfile' is expected to be set by default. This allows the stdboot triggered efi loaders to find the correct OS device tree file even if regular boot process is interrupted by user intervention. Fixes since V3: * fix up missing header for am62x evm (I seemed to have dropped the fixup somehow) based on: master e8f2404e093d Merge branch 'master-779h0-r2' of https://source.denx.de/u-boot/custodians/u-boot-sh Since this impacts out of box distro support, will be great to get it as part of 2024.04 release. Testing (decided to retest it all): https://gist.github.com/nmenon/b9d49d752c27988aabdc062dcdc41e67 V3: https://lore.kernel.org/all/20240130130615.670783-1-nm@ti.com/ V2: https://lore.kernel.org/all/20240109191506.3820908-1-nm@ti.com/ V1: https://lore.kernel.org/all/20240108173301.2692332-1-nm@ti.com/ Nishanth Menon (11): board: ti: Add missing common/Kconfig references board: ti: common: Introduce a common fdt ops library board: ti: am62ax: Set fdtfile from C code instead of findfdt script board: ti: am62x: Set fdtfile from C code instead of findfdt script board: ti: am64x: Set fdtfile from C code instead of findfdt script board: ti: am65x: Set fdtfile from C code instead of findfdt script board: ti: j721e: Set fdtfile from C code instead of findfdt script board: ti: j721s2: Set fdtfile from C code instead of findfdt script board: beagle: beagleboneai64: Set fdtfile from C code instead of findfdt script board: beagle: beagleplay: Set fdtfile from C code instead of findfdt script include: env: ti: Drop default_findfdt board/beagle/beagleboneai64/beagleboneai64.c | 14 ++++ .../beagle/beagleboneai64/beagleboneai64.env | 1 - board/beagle/beagleplay/beagleplay.c | 14 ++++ board/beagle/beagleplay/beagleplay.env | 1 - board/ti/am62ax/am62ax.env | 1 - board/ti/am62ax/evm.c | 10 +++ board/ti/am62x/am62x.env | 1 - board/ti/am62x/evm.c | 10 +++ board/ti/am64x/am64x.env | 9 --- board/ti/am64x/evm.c | 8 +++ board/ti/am65x/am65x.env | 3 - board/ti/am65x/evm.c | 2 + board/ti/common/Kconfig | 12 ++++ board/ti/common/Makefile | 1 + board/ti/common/fdt_ops.c | 64 +++++++++++++++++++ board/ti/common/fdt_ops.h | 42 ++++++++++++ board/ti/j721e/evm.c | 8 +++ board/ti/j721e/j721e.env | 10 --- board/ti/j721s2/evm.c | 8 +++ board/ti/j721s2/j721s2.env | 8 --- board/ti/omap3evm/Kconfig | 2 + board/ti/panda/Kconfig | 2 + board/ti/sdp4430/Kconfig | 2 + configs/am62ax_evm_a53_defconfig | 1 + configs/am62x_beagleplay_a53_defconfig | 3 +- configs/am62x_evm_a53_defconfig | 1 + configs/j721e_beagleboneai64_a72_defconfig | 3 +- include/env/ti/default_findfdt.env | 12 ---- 28 files changed, 205 insertions(+), 48 deletions(-) create mode 100644 board/ti/common/fdt_ops.c create mode 100644 board/ti/common/fdt_ops.h delete mode 100644 include/env/ti/default_findfdt.env [1] https://github.com/u-boot/u-boot/pull/487 base-commit: e8f2404e093daf6cc3ac2b3233e3c6770d13e371 -- 2.43.0

2 12

[PATCH v4 00/39] Qualcomm generic board support
by Caleb Connolly 21 Feb '24

21 Feb '24

Historically, Qualcomm boards in U-Boot have all had their own board/qualcomm/xyz directory, their own CONFIG_TARGET_XYZ option, their own hardcoded sysmap-xyz.c file, and their own U-Boot specific devicetree with little/no compatibility with upstream DT. This series makes a few final prepatory changes, and then replaces almost all of the board specific code with generic alternatives. The end result is that all Qualcomm boards both current and future (with the exception of the db410c and db820c) can be supported by a single U-Boot binary by just providing the correct DT. New boards can be added without introducing any addition mach/ or board/ code or config options. Due to the nature of this change, the patch ("mach-snapdragon: generalise board support") has become pretty big, I tried a few different ways to represent this in git history, but the other methods (e.g. adding a stub "generic" target and removing it again) were more confusing and made for much messier git history. The current patch is mostly atomic, but requires regenerating the config. The QCS404 EVB board had some code to enable the USB VBUS regulator, this is dropped in favour of a adding a new vbus-supply property to the dwc3-generic driver. This will also be used by the dragonboard845c in a future patch. This handles the common case of a board requiring some regulator be enabled for USB host mode. A more detailed description of the changes is below. == Memory map == The memory map was historically hardcoded into U-Boot, this meant that U-Boot had to be built for a specific variant of a device. This is changed to instead read the memory map from the DT /memory node. Additionally, most boards mapped addresss 0x0 as valid, as a result if a null pointer access happens then it will cause a bus stall (and board hang). This is fixed so that null pointer accesses will now correctly throw an exception. == DT loading == Previously, boards used the FDT blob embedded into U-Boot (via OF_SEPARATE). However, most Qualcomm boards run U-Boot as a secondary bootloader, so we can instead rely on the first-stage bootloader to populate some useful FDT properties for us (notably the /memory node and KASLR seed) and fetch the DTB that it provides. Combined with the memory map changes above, this let's us entirely avoid configuring the memory map explicitly. == defconfig == Most of the board defconfigs and config headers were quite similar, to simplify maintenance going forward, all the fully generic boards (sdm845 and qcs404-evb so far) are adapted to use the new qcom_defconfig. Going forward, all new Qualcomm boards should be supported by this defconfig. A notable exception is for specific usecases (like U-Boot as the primary bootloader). == The older dragonboards == The db410c and db820c both have some custom board init code, as a result they aren't yet binary compatible. mach-snapdragon is adjusted so that all the necessary config options (e.g. CONFIG_SYS_BOARD) can be set from their defconfigs, this makes it possible to enable support for new boards without introducing additional config options. The db410c can run U-Boot either chainloaded like the other boards, or as a first-stage bootloader replacing aboot. However it was hardcoded to only build for the latter option. This series introduces a new "chainloaded" defconfig to enable easier testing via fastboot. == dynamic environment variables == This series also introduces runtime-allocated load addresses via the lmb allocator. This allows for booting on boards with vastly different memory layouts without any pre-calculation or macro magic in the config header. This feature is based on similar code in mach-apple. The soc, board, and fdtfile environment variables are also generated automatically. Many Qualcomm boards follow a similar scheme for DTB naming such that the name can often be derived from the root compatible properties. This is intended to cover the most common cases and be a simple solution for booting generic distro images without having to explicitly choose the right DTB. The U-Boot DTS can be tweaked if necessary to produce the correct name, the variable can be overwritten, or a bootloader like GRUB can load the devicetree instead. == Upstream DT == All Qualcomm boards have had their devicetree files replaced with the upstream versions. Previous patch series made the necessary driver adjustments to fully support the upstream DT format. All future Qualcomm boards should use upstream DTS by default. Once Sumit's work to import dt-rebasing has been merged, we will drop the imported DT and bindings again. --- I have tested this series on the Dragonboard410c, Dragonboard820c, and Dragonboard845c. I unfortunately don't have access to a QCS404 EVB board to test. This series is based on the qcom-next branch [1] and depends on my PMIC fixes series [2], an integration branch for testing can be found at [3]. The non-qualcomm-specific changes (patches 1 and 2) don't have any dependencies. [1]: https://source.denx.de/u-boot/custodians/u-boot-snapdragon [2]: https://lore.kernel.org/u-boot/20231114-b4-qcom-dt-compat-v3-0-88a92f8f00ba… [3]: https://source.denx.de/u-boot/custodians/u-boot-snapdragon/-/tree/b4/qcom-c… --- Changes in v4: - Drop unreachable return in ehci_usb_of_bind() - Adjust error reporting in msm_sdc_clk_init() to not print ret which will always be 0. - Simplify qcom_pmic_gpio and associated pinctrrl driver. - Fix the bit clock divider on QCS404 (thanks Sumit). - Make QCS404 pinctrl driver compatible with upstream DT. - Fix qcs404_clk_set_rate() return values + move some things that should be in enable. - Optimise reserved memory carveout algorithm and fix the last regions always getting skipped. - Adjust APQ8016 to probe the pinctrl driver pre-relocation so that UART can be initialised. - Stub in support for special pins in the Qualcomm pinctrl driver - we don't support them yet but in most cases they're already configured correctly and can be safely skipped. - Improve readability of sdhci msm_sdc_clk_init() and use log_warning() instead of printf(). - Add missing CONFIG_SAVE_PREV_BL options to qcom_defconfig - Document known issue only affecting qcs404 where in the msm_sdhci driver the xo_board clock somehow becomes associated with the qcom_clock device resulting in qcs404_clk_set_rate() being called for clock id 0. This doesn't seem to cause any issues but has proven somewhat elusive to debug. - Add a link to the APQ8016 TRM in doc/board/qualcomm/dragonboard410c.rst - Link to v3: https://lore.kernel.org/r/20240130-b4-qcom-common-target-v3-0-e523cbf9e556@… Changes in v3: - Remove dragonboard410c.dts file - Introduce generic board_usb_init() function. - Remove db410c specific dead code (smem RAM layout) - Fix pinctrl DT compatibility for msm8916/msm8996 - Reference git tag where DT and headers were taken from Linux. - Adjust ramdisk allocation size to 128M - Improve documentation wording, reference buildman - Fix mapping for reserved regions to avoid speculative pre-fetching - Apply quicksort to memory banks read from DT to ensure ordering - Link to v2: https://lore.kernel.org/r/20231219-b4-qcom-common-target-v2-0-b6dd9704219e@… Changes in v2: - Split DTS changes to reduce patch size. - Import full board DTS files from Linux too, and introduce -u-boot.dtsi files where necessary to make any U-Boot specific changes. - Add a pinctrl driver for qcom PMIC GPIOs - Always enable LINUX_KERNEL_IMAGE_HEADER - Link to v1: https://lore.kernel.org/r/20231121-b4-qcom-common-target-v1-0-9492198e0c15@… To: Neil Armstrong <neil.armstrong(a)linaro.org> To: Sumit Garg <sumit.garg(a)linaro.org> To: Ramon Fried <rfried.dev(a)gmail.com> Cc: Marek Vasut <marex(a)denx.de> To: Dzmitry Sankouski <dsankouski(a)gmail.com> To: Caleb Connolly <caleb.connolly(a)linaro.org> To: Peng Fan <peng.fan(a)nxp.com> To: Jaehoon Chung <jh80.chung(a)samsung.com> To: Rayagonda Kokatanur <rayagonda.kokatanur(a)broadcom.com> To: Lukasz Majewski <lukma(a)denx.de> To: Sean Anderson <seanga2(a)gmail.com> To: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz(a)gmail.com> To: Stephan Gerhold <stephan(a)gerhold.net> Cc: <u-boot(a)lists.denx.de> --- Caleb Connolly (39): arm: init: export prev_bl_fdt_addr usb: dwc3-generic: support external vbus regulator mmc: msm_sdhci: use modern clock handling dt-bindings: drop msm_sdhci binding clk/qcom: use upstream compatible properties clock/qcom: qcs404: fix clk_set_rate serial: msm: add debug UART serial: msm: fix clock handling and pinctrl gpio: qcom_pmic: 1-based GPIOs gpio: qcom_pmic: add a quirk to skip GPIO configuration gpio: qcom_pmic: add pinctrl driver sandbox: dts: fix qcom pmic gpio pinctrl: qcom: stub support for special GPIOs pinctrl: qcom: fix DT compatibility pinctrl: qcom: apq8016: init pre-reloaction board: dragonboard410c: add chainloaded config fragment board: dragonboard410c: upstream DT compat board: dragonboard410c: import board code from mach-snapdragon board: dragonboard820c: use LINUX_KERNEL_IMAGE_HEADER mach-snapdragon: generalise board support mach-snapdragon: dynamic load addresses mach-snapdragon: generate fdtfile automatically mach-snapdragon: carve out no-map regions board: qcs404-evb: drop board code doc: board/qualcomm: document generic targets doc: board/qualcomm: link to APQ8016 TRM dt-bindings: import headers for SDM845 dts: sdm845: import supporting dtsi files dts: sdm845: replace with upstream DTS dt-bindings: import headers for MSM8916 dts: msm8916: import PMIC dtsi files dts: msm8916: replace with upstream DTS dt-bindings: import headers for MSM8996 dts: msm8996: import PMIC dtsi files dts: dragonboard820c: use correct bindings for clocks dts: msm8996: replace with upstream DTS dt-bindings: import headers for qcs404 dts: qcs404-evb: replace with upstream DT MAINTAINERS: Qualcomm: add some missing paths MAINTAINERS | 12 +- arch/arm/Kconfig | 4 + arch/arm/dts/Makefile | 9 +- arch/arm/dts/apq8016-sbc-u-boot.dtsi | 20 + arch/arm/dts/apq8016-sbc.dts | 729 +++ arch/arm/dts/apq8096-db820c-u-boot.dtsi | 14 + arch/arm/dts/apq8096-db820c.dts | 1137 ++++ arch/arm/dts/dragonboard410c-uboot.dtsi | 44 - arch/arm/dts/dragonboard410c.dts | 209 - arch/arm/dts/dragonboard820c-uboot.dtsi | 32 - arch/arm/dts/dragonboard820c.dts | 151 - arch/arm/dts/dragonboard845c-uboot.dtsi | 26 - arch/arm/dts/dragonboard845c.dts | 48 - arch/arm/dts/msm8916-pm8916.dtsi | 157 + arch/arm/dts/msm8916.dtsi | 2702 +++++++++ arch/arm/dts/msm8996.dtsi | 3884 +++++++++++++ arch/arm/dts/pm8916.dtsi | 178 + arch/arm/dts/pm8994.dtsi | 152 + arch/arm/dts/pm8998.dtsi | 130 + arch/arm/dts/pmi8994.dtsi | 65 + arch/arm/dts/pmi8998.dtsi | 98 + arch/arm/dts/pms405.dtsi | 149 + arch/arm/dts/qcs404-evb-4000-u-boot.dtsi | 48 + arch/arm/dts/qcs404-evb-4000.dts | 96 + arch/arm/dts/qcs404-evb-uboot.dtsi | 30 - arch/arm/dts/qcs404-evb.dts | 390 -- arch/arm/dts/qcs404-evb.dtsi | 389 ++ arch/arm/dts/qcs404.dtsi | 1829 ++++++ arch/arm/dts/sdm845-db845c.dts | 1190 ++++ .../arm/dts/sdm845-samsung-starqltechn-u-boot.dtsi | 16 + arch/arm/dts/sdm845-samsung-starqltechn.dts | 460 ++ arch/arm/dts/sdm845-wcd9340.dtsi | 86 + arch/arm/dts/sdm845.dtsi | 5801 +++++++++++++++++++- arch/arm/dts/starqltechn-uboot.dtsi | 27 - arch/arm/dts/starqltechn.dts | 68 - arch/arm/lib/save_prev_bl_data.c | 5 + arch/arm/mach-snapdragon/Kconfig | 95 +- arch/arm/mach-snapdragon/Makefile | 8 +- arch/arm/mach-snapdragon/board.c | 468 ++ arch/arm/mach-snapdragon/dram.c | 99 - arch/arm/mach-snapdragon/include/mach/dram.h | 12 - arch/arm/mach-snapdragon/include/mach/gpio.h | 2 + arch/arm/mach-snapdragon/include/mach/misc.h | 13 - arch/arm/mach-snapdragon/init_sdm845.c | 73 - arch/arm/mach-snapdragon/misc.c | 55 - arch/arm/mach-snapdragon/sysmap-apq8016.c | 31 - arch/arm/mach-snapdragon/sysmap-apq8096.c | 31 - arch/arm/mach-snapdragon/sysmap-qcs404.c | 43 - arch/arm/mach-snapdragon/sysmap-sdm845.c | 31 - arch/sandbox/dts/sandbox.dtsi | 9 +- board/qualcomm/dragonboard410c/Kconfig | 15 - board/qualcomm/dragonboard410c/Makefile | 2 +- .../dragonboard410c/configs/chainloaded.config | 7 + board/qualcomm/dragonboard410c/dragonboard410c.c | 130 +- board/qualcomm/dragonboard820c/Kconfig | 15 - board/qualcomm/dragonboard820c/Makefile | 1 - board/qualcomm/dragonboard820c/dragonboard820c.c | 39 +- board/qualcomm/dragonboard820c/head.S | 33 - board/qualcomm/dragonboard820c/u-boot.lds | 111 - board/qualcomm/dragonboard845c/Kconfig | 12 - board/qualcomm/qcs404-evb/Kconfig | 15 - board/qualcomm/qcs404-evb/Makefile | 6 - board/qualcomm/qcs404-evb/qcs404-evb.c | 62 - configs/dragonboard410c_defconfig | 8 +- configs/dragonboard820c_defconfig | 8 +- configs/dragonboard845c_defconfig | 29 - configs/qcom_defconfig | 67 + configs/qcs404evb_defconfig | 55 - configs/starqltechn_defconfig | 41 - doc/board/qualcomm/board.rst | 125 + doc/board/qualcomm/debugging.rst | 61 + doc/board/qualcomm/dragonboard410c.rst | 2 + doc/board/qualcomm/index.rst | 4 +- doc/board/qualcomm/qcs404.rst | 79 - doc/board/qualcomm/sdm845.rst | 167 - doc/device-tree-bindings/mmc/msm_sdhci.txt | 25 - doc/device-tree-bindings/usb/ehci-msm.txt | 10 - drivers/clk/qcom/clock-apq8016.c | 9 +- drivers/clk/qcom/clock-apq8096.c | 7 +- drivers/clk/qcom/clock-qcs404.c | 25 +- drivers/gpio/msm_gpio.c | 20 + drivers/gpio/qcom_pmic_gpio.c | 275 +- drivers/mmc/msm_sdhci.c | 69 +- drivers/phy/qcom/msm8916-usbh-phy.c | 4 +- drivers/pinctrl/qcom/pinctrl-apq8016.c | 29 +- drivers/pinctrl/qcom/pinctrl-apq8096.c | 16 +- drivers/pinctrl/qcom/pinctrl-qcom.c | 12 + drivers/pinctrl/qcom/pinctrl-qcs404.c | 58 +- drivers/serial/Kconfig | 8 + drivers/serial/serial_msm.c | 62 +- drivers/usb/dwc3/dwc3-generic.c | 12 + drivers/usb/host/ehci-msm.c | 22 +- include/configs/dragonboard845c.h | 20 - include/configs/qcom.h | 21 + include/configs/qcs404-evb.h | 20 - include/configs/sdm845.h | 26 - include/dt-bindings/arm/coresight-cti-dt.h | 37 + include/dt-bindings/clock/qcom,camcc-sdm845.h | 116 + include/dt-bindings/clock/qcom,dispcc-sdm845.h | 56 + include/dt-bindings/clock/qcom,gcc-msm8916.h | 179 + include/dt-bindings/clock/qcom,gcc-msm8996.h | 362 ++ include/dt-bindings/clock/qcom,gpucc-sdm845.h | 24 + include/dt-bindings/clock/qcom,lpass-sdm845.h | 15 + include/dt-bindings/clock/qcom,mmcc-msm8996.h | 295 + include/dt-bindings/clock/qcom,rpmcc.h | 174 + include/dt-bindings/clock/qcom,rpmh.h | 37 + include/dt-bindings/clock/qcom,turingcc-qcs404.h | 15 + include/dt-bindings/clock/qcom,videocc-sdm845.h | 35 + include/dt-bindings/dma/qcom-gpi.h | 11 + include/dt-bindings/firmware/qcom,scm.h | 39 + include/dt-bindings/iio/qcom,spmi-vadc.h | 300 + include/dt-bindings/interconnect/qcom,msm8916.h | 100 + .../dt-bindings/interconnect/qcom,msm8996-cbf.h | 12 + include/dt-bindings/interconnect/qcom,msm8996.h | 163 + include/dt-bindings/interconnect/qcom,osm-l3.h | 15 + include/dt-bindings/interconnect/qcom,sdm845.h | 150 + include/dt-bindings/phy/phy-qcom-qmp.h | 20 + include/dt-bindings/phy/phy-qcom-qusb2.h | 37 + include/dt-bindings/pinctrl/qcom,pmic-gpio.h | 164 + include/dt-bindings/pinctrl/qcom,pmic-mpp.h | 106 + include/dt-bindings/power/qcom-rpmpd.h | 412 ++ .../dt-bindings/regulator/qcom,rpmh-regulator.h | 36 + include/dt-bindings/reset/qcom,gcc-msm8916.h | 100 + include/dt-bindings/reset/qcom,sdm845-aoss.h | 17 + include/dt-bindings/reset/qcom,sdm845-pdc.h | 22 + include/dt-bindings/soc/qcom,apr.h | 28 + include/dt-bindings/soc/qcom,rpmh-rsc.h | 14 + include/dt-bindings/sound/apq8016-lpass.h | 9 + include/dt-bindings/sound/qcom,lpass.h | 46 + include/dt-bindings/sound/qcom,q6afe.h | 9 + include/dt-bindings/sound/qcom,q6asm.h | 26 + include/dt-bindings/sound/qcom,q6dsp-lpass-ports.h | 234 + include/dt-bindings/sound/qcom,wcd9335.h | 15 + include/init.h | 11 + 134 files changed, 23997 insertions(+), 2643 deletions(-) --- base-commit: 22f391e8be11986bae824509470cf11e7bac31b0 // Caleb (they/them)

7 97

[PATCH V6 00/20] board: ti: Add support for BeaglePlay
by Nishanth Menon 21 Feb '24

21 Feb '24

Alright, 6th time is a charm ;) Hopefully this takes care of all the un-addressed concerns we have had. Thanks all for pitching in, reviewing and improving and I will stop finding things to cleanup (promise). Baseline: 7c6b18fb5494 (origin/next) Merge branch '2023-08-24-enable-more-features-in-qemu-arm' into next Full series available: https://github.com/nmenon/fix-k3-dt-u-boot/commits/beagleplay-v6 Boot Logs: https://gist.github.com/nmenon/8be4106e2d0b572aa5e77d93476095b4 Caveats: * Networking: pending https://lore.kernel.org/all/20230822121350.51324-1-rogerq@kernel.org/ * 32kclk and usb: pending: https://lore.kernel.org/u-boot/20230725185253.2123433-4-nm@ti.com/ OR https://github.com/nmenon/fix-k3-dt-u-boot/commit/853b29d63c1ca642be316f1af… being properly resolved (NOTE: without this patch, wlan is broken in Linux as the 32kclk from SoC is incorrectly supplied to wlan as 25MHz) * There seems to be a bug in Linux kernel with sdhci that seems to depend on u-boot initialization of sdhci for functionality (TI internal actions already triggered). * buildman discussion about config fragments: https://lore.kernel.org/all/CAPnjgZ14CUVt=rM943hh9PQUhK9LJDgZYPxUsATYQe3wwO… * Documentation that we can copy paste: https://lore.kernel.org/all/20230824154036.3650607-1-nm@ti.com/ and followon in kernel.org: https://lore.kernel.org/all/149528e1-062b-ebed-aa25-d37be5fe5894@iogearbox.… if it all percolates back down to u-boot tree, should be trivial cleanup. * Build fails with binman implementation for TI SoCs - Neha will take care of https://lore.kernel.org/all/227d74cf-9e95-4f5f-af96-49d054cde7aa@ti.com/ * This series picks up Jan's patch for working around Device Manager not compliant with EFI specification reqs and applies it to am62x_sk (TI internal action already triggered) https://lore.kernel.org/all/20230825011623.c74qqidp6wgvc5kl@plaza/ * I noticed that when drivers like the am654_sdhci.c uses deffered_probe, the default probe function does'nt fail https://source.denx.de/u-boot/u-boot/-/blob/master/boot/bootflow.c#L279 So ends up attempting for each of the boot_targets even if mmc dev dev_id would fail. Not really sure how to solve it, so will leave it here. (the https://gist.github.com/nmenon/8be4106e2d0b572aa5e77d93476095b4#file-beagle… should show a bunch of 'MMC: no card present' each of which costs around 1 second. Changes since V5: * New patches to clean up mmc.env to sync with BOOTSTD operations yet enable easier non-U-Boot developer experience for uEnv.txt and optimize access to non-plugged in sd-card. * Picked up Jan's patch[1] as part of this series. * Introduced default_findfdt.env as review comment * Saw Simon's feedback on uSD boot, and documented that as well, will be good for new devs to have that info in one flow. * Quick overall diff: https://gist.github.com/nmenon/6d934f4e1092aa293a771d26b0f2bff7 V5: https://lore.kernel.org/all/20230824031101.3460411-1-nm@ti.com/ V4: https://lore.kernel.org/all/20230822184135.2328409-1-nm@ti.com/ V3: https://lore.kernel.org/all/20230815164440.2713726-1-nm@ti.com/ V2: https://lore.kernel.org/u-boot/20230727234446.3651836-1-nm@ti.com/ V1: https://lore.kernel.org/all/20230725185253.2123433-1-nm@ti.com/ Jan Kiszka (1): configs: am62x_evm_a53_defconfig: Disable semi-functional PSCI reset support Nishanth Menon (18): include: env: ti: mmc: envboot/mmcboot: Check result of mmc dev before proceeding include: env: ti: mmc: envboot: Only attempt boot.scr if BOOTSTD is not enabled include: configs: ti_armv7_common: Add documentation for protected section include: configs: am62x_evm: Drop unused SDRAM address include: configs: am62x_evm: Wrap distroboot with CONFIG_DISTRO_DEFAULTS board: ti: am62x: am62x.env: Add explicit boot_targets configs: am62x_evm_a53_defconfig: Switch to bootstd include: configs: am62x_evm: Drop distro_bootcmd usage include: env: ti: ti_armv7_common.env: Rename to ti_common.env include: env: ti: Add a generic default_findfdt.env board: ti: am62x: am62x.env: Use default findfdt arm: mach-k3: am625_init: Use IS_ENABLED() arm: mach-k3: am625_init: Convert rtc_erratumi2327_init to static configs: am62x_evm*: Enable EMMC_BOOT configuration arm: mach-k3: am625: Add support for UDA FS arm: dts: k3-am625-sk-binman: Add labels for unsigned binary board: ti: am62x: Add am62x_beagleplay_* defconfigs and env file doc: board: ti: Add BeaglePlay documentation Robert Nelson (1): arm: dts: Add k3-am625-beagleplay arch/arm/dts/Makefile | 2 + .../dts/k3-am625-beagleplay-ddr4-1600MTs.dtsi | 2195 +++++++++++++++++ arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi | 195 ++ arch/arm/dts/k3-am625-beagleplay.dts | 758 ++++++ arch/arm/dts/k3-am625-r5-beagleplay.dts | 86 + arch/arm/dts/k3-am625-sk-binman.dtsi | 4 +- arch/arm/mach-k3/am625_init.c | 49 +- board/siemens/iot2050/iot2050.env | 2 +- board/ti/am62ax/am62ax.env | 2 +- board/ti/am62x/MAINTAINERS | 7 + board/ti/am62x/am62x.env | 8 +- board/ti/am62x/beagleplay.env | 19 + board/ti/am62x/beagleplay_a53.config | 55 + board/ti/am62x/beagleplay_r5.config | 15 + board/ti/am64x/am64x.env | 2 +- board/ti/am65x/am65x.env | 2 +- board/ti/j721e/j721e.env | 2 +- board/ti/j721s2/j721s2.env | 2 +- board/ti/ks2_evm/k2e_evm.env | 2 +- board/ti/ks2_evm/k2g_evm.env | 2 +- board/ti/ks2_evm/k2hk_evm.env | 2 +- board/ti/ks2_evm/k2l_evm.env | 2 +- configs/am62x_evm_a53_defconfig | 7 +- configs/am62x_evm_r5_defconfig | 1 + doc/board/ti/am62x_beagleplay.rst | 322 +++ doc/board/ti/img/beagleplay_emmc.svg | 697 ++++++ doc/board/ti/k3.rst | 1 + include/configs/am62x_evm.h | 6 - include/configs/ti_armv7_common.h | 2 +- include/env/ti/default_findfdt.env | 12 + include/env/ti/mmc.env | 12 +- .../ti/{ti_armv7_common.env => ti_common.env} | 0 32 files changed, 4419 insertions(+), 54 deletions(-) create mode 100644 arch/arm/dts/k3-am625-beagleplay-ddr4-1600MTs.dtsi create mode 100644 arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi create mode 100644 arch/arm/dts/k3-am625-beagleplay.dts create mode 100644 arch/arm/dts/k3-am625-r5-beagleplay.dts create mode 100644 board/ti/am62x/beagleplay.env create mode 100644 board/ti/am62x/beagleplay_a53.config create mode 100644 board/ti/am62x/beagleplay_r5.config create mode 100644 doc/board/ti/am62x_beagleplay.rst create mode 100644 doc/board/ti/img/beagleplay_emmc.svg create mode 100644 include/env/ti/default_findfdt.env rename include/env/ti/{ti_armv7_common.env => ti_common.env} (100%) [1] https://lore.kernel.org/all/c93b19ed-43fe-44a2-9726-371fb9d2f825@web.de/ -- 2.40.0

6 46

[PATCH] dma: ti: k3-udma: Fix ring_idx to pair k3 nav rings"
by Udit Kumar 21 Feb '24

21 Feb '24

ring_idx was not correctly assigned in case of tflow_id is zero. Which leads to wrong pairing of DMA for drivers like OSPI. Fixes: 4312a1dfca26 ("dma: ti: k3-udma: Use ring_idx to pair k3 nav rings") Signed-off-by: Udit Kumar <u-kumar1(a)ti.com> --- drivers/dma/ti/k3-udma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/dma/ti/k3-udma.c b/drivers/dma/ti/k3-udma.c index eea9ec9659..39866ffff8 100644 --- a/drivers/dma/ti/k3-udma.c +++ b/drivers/dma/ti/k3-udma.c @@ -884,10 +884,10 @@ static int udma_alloc_tx_resources(struct udma_chan *uc) return ret; tchan = uc->tchan; - if (tchan->tflow_id >= 0) + if (tchan->tflow_id > 0) ring_idx = tchan->tflow_id; else - ring_idx = ud->bchan_cnt + tchan->id; + ring_idx = tchan->id; ret = k3_nav_ringacc_request_rings_pair(ud->ringacc, ring_idx, -1, &uc->tchan->t_ring, -- 2.34.1

2 1

[PATCH v2 0/6] video: Add UTF-8 support for UEFI applications
by Janne Grunau via B4 Relay 21 Feb '24

21 Feb '24

Andre submitted 2 years ago DM_VIDEO improvements for UEFI applications using UEFI's EFI_SIMPLE_TEXT_OUTPUT_PROTOCOL but did not follow with suggested changes. This series takes care of the UTF-8 support which required to draw symbol and box drawing characters used by UEFI applications like grub2 and sd-boot correctly. Compared to Andre's version this version has the following changes: - use and extend existing conversion functions from lib/charset.c - convert to Unicode code points for truetype console support - conversion is conditional on CONFIG_CHARSET - use escape sequences in tests as proposed by Heinrich Link: https://lore.kernel.org/u-boot/20220110005638.21599-1-andre.przywara@arm.co… Signed-off-by: Janne Grunau <j(a)jannau.net> --- Changes in v2: - use "CONFIG_IS_ENABLED(CHARSET)" instead of EFI_LOADER - rewritten commit message for mapping CP437 cp 1-31 - extended utf8_to_utf32_stream() documentation as suggested by Heinrich - Link to RFC: https://lore.kernel.org/r/20240117-vidconsole-utf8-uefi-v1-0-539f7ce74fb9@j… --- Andre Przywara (2): efi_selftest: Add international characters test efi_selftest: Add box drawing character selftest Janne Grunau (4): lib: charset: Fix and extend utf8_to_utf32_stream() documentation video: console: Parse UTF-8 character sequences lib/charset: Map Unicode code points to CP437 code points 0-31 efi_selftest: Add symbol character selftest drivers/video/console_normal.c | 6 +++-- drivers/video/console_rotate.c | 16 +++++++++----- drivers/video/console_truetype.c | 8 +++---- drivers/video/vidconsole-uclass.c | 18 ++++++++++----- drivers/video/vidconsole_internal.h | 15 +++++++++++++ include/charset.h | 16 +++++++++++--- include/cp1250.h | 12 ++++++++-- include/cp437.h | 12 ++++++++-- include/video_console.h | 10 +++++---- lib/charset.c | 9 +++++--- lib/efi_loader/efi_unicode_collation.c | 2 +- lib/efi_selftest/efi_selftest_textoutput.c | 35 ++++++++++++++++++++++++++++++ 12 files changed, 127 insertions(+), 32 deletions(-) --- base-commit: 866ca972d6c3cabeaf6dbac431e8e08bb30b3c8e change-id: 20240117-vidconsole-utf8-uefi-fa23b4ac65d6 Best regards, -- Janne Grunau <j(a)jannau.net>

3 13

[PATCH v3] test/py: saveenv: Add a test for saveenv command
by Love Kumar 20 Feb '24

20 Feb '24

Add test case for saveenv command in non-JTAG bootmode which saves the u-boot environment variables in persistent storage. Signed-off-by: Love Kumar <love.kumar(a)amd.com> --- Changes in v2: - Set bootmode through boardenv if modeboot is not defined Changes in v3: - Fix the issue with bad patterns and escape sequence warning --- test/py/tests/test_saveenv.py | 136 ++++++++++++++++++++++++++++++++++ 1 file changed, 136 insertions(+) create mode 100644 test/py/tests/test_saveenv.py diff --git a/test/py/tests/test_saveenv.py b/test/py/tests/test_saveenv.py new file mode 100644 index 000000000000..fa0863f6d314 --- /dev/null +++ b/test/py/tests/test_saveenv.py @@ -0,0 +1,136 @@ +# SPDX-License-Identifier: GPL-2.0 +# (C) Copyright 2023, Advanced Micro Devices, Inc. + +""" +Note: This test doesn't rely on boardenv_* configuration value but they can +change test behavior. + +For example: + +# Setup env__saveenv_test_skip to True if saveenv test is not possible or +# desired and should be skipped. +env__saveenv_test_skip = True + +# Setup env__saveenv_test to set the bootmode if 'modeboot' u-boot environment +# variable is not set. Test will be skipped if bootmode is not set in both +# places i.e, boardenv and modeboot u-boot environment variable +env__saveenv_test = { + 'bootmode': 'qspiboot', +} + +# This test will be also skipped if the bootmode is detected to JTAG. +""" + +import pytest +import random +import ipaddress +import string +import uuid + +# Setup the env +def setup_saveenv_env(u_boot_console): + if u_boot_console.config.env.get('env__saveenv_test_skip', False): + pytest.skip('saveenv test is not enabled') + + output = u_boot_console.run_command('echo $modeboot') + if output: + bootmode = output + else: + f = u_boot_console.config.env.get('env__saveenv_test', None) + if not f: + pytest.skip('bootmode cannot be determined') + bootmode = f.get('bootmode', 'jtagboot') + + if 'jtag' in bootmode: + pytest.skip('skipping saveenv test due to jtag bootmode') + +# Check return code +def ret_code(u_boot_console): + return u_boot_console.run_command('echo $?') + +# Verify env variable +def check_env(u_boot_console, var_name, var_value): + if var_value: + output = u_boot_console.run_command(f'printenv {var_name}') + var_value = str(var_value) + if (var_value.startswith("'") and var_value.endswith("'")) or ( + var_value.startswith('"') and var_value.endswith('"') + ): + var_value = var_value.split(var_value[-1])[1] + assert var_value in output + assert ret_code(u_boot_console).endswith('0') + else: + u_boot_console.p.send(f'printenv {var_name}\n') + output = u_boot_console.p.expect(['not defined']) + assert output == 0 + assert ret_code(u_boot_console).endswith('1') + +# Set env variable +def set_env(u_boot_console, var_name, var_value): + u_boot_console.run_command(f'setenv {var_name} {var_value}') + assert ret_code(u_boot_console).endswith('0') + check_env(u_boot_console, var_name, var_value) + +(a)pytest.mark.buildconfigspec('cmd_saveenv') +def test_saveenv(u_boot_console): + """Test the saveenv command in non-JTAG bootmode. + It saves the U-Boot environment in persistent storage. + """ + setup_saveenv_env(u_boot_console) + + # Set env for random mac address + rand_mac = '%02x:%02x:%02x:%02x:%02x:%02x' % ( + random.randint(0, 255), + random.randint(0, 255), + random.randint(0, 255), + random.randint(0, 255), + random.randint(0, 255), + random.randint(0, 255), + ) + set_env(u_boot_console, 'mac_addr', rand_mac) + + # Set env for random IPv4 address + rand_ipv4 = ipaddress.IPv4Address._string_from_ip_int( + random.randint(0, ipaddress.IPv4Address._ALL_ONES) + ) + set_env(u_boot_console, 'ipv4_addr', rand_ipv4) + + # Set env for random IPv6 address + rand_ipv6 = ipaddress.IPv6Address._string_from_ip_int( + random.randint(0, ipaddress.IPv6Address._ALL_ONES) + ) + set_env(u_boot_console, 'ipv6_addr', rand_ipv6) + + # Set env for random number + rand_num = random.randrange(1, 10**9) + set_env(u_boot_console, 'num_var', rand_num) + + # Set env for uuid + uuid_str = uuid.uuid4().hex.lower() + set_env(u_boot_console, 'uuid_var', uuid_str) + + # Set env for random string including special characters + sc = "!#%&()*+,-./:;<=>?@[\\]^_`{|}~" + rand_str = ''.join( + random.choices(' ' + string.ascii_letters + sc + string.digits, k=300) + ) + set_env(u_boot_console, 'str_var', f'"{rand_str}"') + + # Set env for empty string + set_env(u_boot_console, 'empty_var', '') + + # Save the env variables + u_boot_console.run_command('saveenv') + assert ret_code(u_boot_console).endswith('0') + + # Reboot + u_boot_console.run_command('reset', wait_for_reboot=True) + + # Verify the saved env variables + check_env(u_boot_console, 'mac_addr', rand_mac) + check_env(u_boot_console, 'ipv4_addr', rand_ipv4) + check_env(u_boot_console, 'ipv6_addr', rand_ipv6) + check_env(u_boot_console, 'num_var', rand_num) + check_env(u_boot_console, 'uuid_var', uuid_str) + check_env(u_boot_console, 'str_var', rand_str) + check_env(u_boot_console, 'empty_var', '') -- 2.25.1

2 1

[PULL] u-boot-usb/master
by Marek Vasut 20 Feb '24

20 Feb '24

The following changes since commit 3e6f2a94bfc25f1782ce2d45db27f47ec781feb1: Merge tag 'u-boot-imx-master-20240219' of https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2024-02-19 08:55:17 -0500) are available in the Git repository at: git://source.denx.de/u-boot-usb.git master for you to fetch changes up to d9a20fea2ba53db3a999827d3e50e181d5513e09: usb: ehci-mx6: Add i.MX93 support (2024-02-19 20:08:51 +0100) ---------------------------------------------------------------- Mathieu Othacehe (1): usb: ehci-mx6: Add i.MX93 support Shantur Rathore (1): common: usb-hub: Reset USB 3.0 hubs only common/usb_hub.c | 6 ++++-- drivers/usb/host/Kconfig | 6 +++--- drivers/usb/host/ehci-mx6.c | 2 +- 3 files changed, 8 insertions(+), 6 deletions(-)

2 1

Please pull u-boot-samsung master
by Minkyu Kang 20 Feb '24

20 Feb '24

Dear Tom, The following changes since commit 15e7927b5a2d33666af19879577bf0c30ab088fe: Merge patch series "omap3: Make SPL_OMAP3_ID_NAND depend on NAND_OMAP_GPMC" (2024-01-22 14:18:55 -0500) are available in the git repository at: git@source.denx.de:u-boot/custodians/u-boot-samsung.git master for you to fetch changes up to 1e81d12e34e874319e041652198a4ba561d751ab: MAINTAINERS: Add new Samsung subsystems (2024-01-24 11:23:20 +0900) ---------------------------------------------------------------- Sam Protsenko (13): dt-bindings: soc: samsung: Add Exynos USI dt-bindings: soc: samsung: Add Exynos PMU dt-bindings: clock: Add Exynos850 clock controller soc: samsung: Add Exynos USI driver soc: samsung: Add Exynos PMU driver clk: exynos: Move pll code into clk-exynos7420 clk: exynos: Add Samsung clock framework clk: exynos: Add Exynos850 clock driver pinctrl: exynos: Add pinctrl support for Exynos850 serial: s5p: Add Exynos850 compatible arm: exynos: Add Exynos850 SoC support board: samsung: Add support for E850-96 board MAINTAINERS: Add new Samsung subsystems MAINTAINERS | 25 + arch/arm/dts/Makefile | 1 + arch/arm/dts/exynos-pinctrl.h | 79 +++ arch/arm/dts/exynos850-e850-96-u-boot.dtsi | 37 ++ arch/arm/dts/exynos850-e850-96.dts | 273 +++++++++ arch/arm/dts/exynos850-pinctrl.dtsi | 663 ++++++++++++++++++++++ arch/arm/dts/exynos850.dtsi | 809 ++++++++++++++++++++++++++ arch/arm/mach-exynos/Kconfig | 28 +- arch/arm/mach-exynos/mmu-arm64.c | 34 ++ board/samsung/e850-96/Kconfig | 16 + board/samsung/e850-96/MAINTAINERS | 9 + board/samsung/e850-96/Makefile | 6 + board/samsung/e850-96/e850-96.c | 22 + configs/e850-96_defconfig | 21 + doc/board/samsung/e850-96.rst | 87 +++ doc/board/samsung/img/exynos850-boot-architecture.svg | 1283 ++++++++++++++++++++++++++++++++++++++++++ doc/board/samsung/index.rst | 1 + doc/device-tree-bindings/clock/samsung,exynos850-clock.yaml | 307 ++++++++++ doc/device-tree-bindings/soc/samsung/exynos-pmu.yaml | 85 +++ doc/device-tree-bindings/soc/samsung/exynos-usi.yaml | 162 ++++++ drivers/clk/exynos/Kconfig | 7 + drivers/clk/exynos/Makefile | 11 +- drivers/clk/exynos/clk-exynos7420.c | 25 +- drivers/clk/exynos/clk-exynos850.c | 189 +++++++ drivers/clk/exynos/clk-pll.c | 167 +++++- drivers/clk/exynos/clk-pll.h | 16 +- drivers/clk/exynos/clk.c | 121 ++++ drivers/clk/exynos/clk.h | 228 ++++++++ drivers/pinctrl/exynos/Kconfig | 8 + drivers/pinctrl/exynos/Makefile | 1 + drivers/pinctrl/exynos/pinctrl-exynos850.c | 125 ++++ drivers/serial/serial_s5p.c | 1 + drivers/soc/Kconfig | 1 + drivers/soc/Makefile | 1 + drivers/soc/samsung/Kconfig | 33 ++ drivers/soc/samsung/Makefile | 4 + drivers/soc/samsung/exynos-pmu.c | 102 ++++ drivers/soc/samsung/exynos-usi.c | 208 +++++++ include/configs/e850-96.h | 12 + include/dt-bindings/clock/exynos850.h | 337 +++++++++++ include/dt-bindings/soc/samsung,exynos-usi.h | 17 + 41 files changed, 5538 insertions(+), 24 deletions(-) create mode 100644 arch/arm/dts/exynos-pinctrl.h create mode 100644 arch/arm/dts/exynos850-e850-96-u-boot.dtsi create mode 100644 arch/arm/dts/exynos850-e850-96.dts create mode 100644 arch/arm/dts/exynos850-pinctrl.dtsi create mode 100644 arch/arm/dts/exynos850.dtsi create mode 100644 board/samsung/e850-96/Kconfig create mode 100644 board/samsung/e850-96/MAINTAINERS create mode 100644 board/samsung/e850-96/Makefile create mode 100644 board/samsung/e850-96/e850-96.c create mode 100644 configs/e850-96_defconfig create mode 100644 doc/board/samsung/e850-96.rst create mode 100644 doc/board/samsung/img/exynos850-boot-architecture.svg create mode 100644 doc/device-tree-bindings/clock/samsung,exynos850-clock.yaml create mode 100644 doc/device-tree-bindings/soc/samsung/exynos-pmu.yaml create mode 100644 doc/device-tree-bindings/soc/samsung/exynos-usi.yaml create mode 100644 drivers/clk/exynos/clk-exynos850.c create mode 100644 drivers/clk/exynos/clk.c create mode 100644 drivers/clk/exynos/clk.h create mode 100644 drivers/pinctrl/exynos/pinctrl-exynos850.c create mode 100644 drivers/soc/samsung/Kconfig create mode 100644 drivers/soc/samsung/Makefile create mode 100644 drivers/soc/samsung/exynos-pmu.c create mode 100644 drivers/soc/samsung/exynos-usi.c create mode 100644 include/configs/e850-96.h create mode 100644 include/dt-bindings/clock/exynos850.h create mode 100644 include/dt-bindings/soc/samsung,exynos-usi.h Thanks, Minkyu Kang.

2 1