April 2024 - U-Boot

[PATCH v2] configs: zynqmp_kria: Deactivate CONFIG_SPI_FLASH_BAR
by Tejas Bhumkar 10 Apr '24

10 Apr '24

The Kria board features a recovery application that activates when the FW_EN button is pressed. Upon power-up flash operates in 3B mode, However, the recovery application changes it back to 4B mode. Currently, after a reset, u-boot activates CONFIG_SPI_FLASH_BAR and assumes the flash is in 3B mode. However, there's no code or reset lines connected to the flash that could return it to 3B mode. To resolve this issue, changes were made to disable CONFIG_SPI_FLASH_BAR, which activates 4-byte opcodes. Signed-off-by: Tejas Bhumkar <tejas.arvind.bhumkar(a)amd.com> --- Changes in v2: Updated commit message. configs/xilinx_zynqmp_kria_defconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig index 7cb8b62d32..7af8b27be9 100644 --- a/configs/xilinx_zynqmp_kria_defconfig +++ b/configs/xilinx_zynqmp_kria_defconfig @@ -155,7 +155,6 @@ CONFIG_MMC_HS200_SUPPORT=y CONFIG_MMC_SDHCI=y CONFIG_MMC_SDHCI_ZYNQ=y CONFIG_DM_MTD=y -CONFIG_SPI_FLASH_BAR=y CONFIG_SPI_FLASH_STMICRO=y # CONFIG_SPI_FLASH_USE_4K_SECTORS is not set CONFIG_SPI_FLASH_MTD=y -- 2.27.0

2 1

[GIT PULL] u-boot-riscv/master
by Leo Liang 10 Apr '24

10 Apr '24

Hi Tom, The following changes since commit 069d07396e30aa9be396c1dd3fc158ac199e6843: Merge tag 'efi-2024-07-rc1' of https://source.denx.de/u-boot/custodians/u-boot-efi (2024-04-08 14:33:59 -0600) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-riscv.git for you to fetch changes up to c1f78a4f632276bb4d77f8c79fe203709a9fa397: doc: describe Milk-V Mars board (2024-04-09 11:30:37 +0800) CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/20256 ---------------------------------------------------------------- - RISC-V: Support backtrace and improve isa extension parsing - cpu: Add cv1800b SoC support - board: Add Milk-V Mars board support - board: Add Milk-V Duo SD card support ---------------------------------------------------------------- Ben Dooks (1): riscv: add backtrace support Conor Dooley (2): riscv: don't read riscv, isa in the riscv cpu's get_desc() riscv: support extension probing using riscv, isa-extensions Heinrich Schuchardt (7): riscv: starfive: MMC card detect riscv: do not set default fdt for VisionFive 2 eeprom: starfive: function get_product_id_from_eeprom() riscv: set fdtfile on Milk-V Mars board: starfive: support Milk-V Mars board riscv: starfive: avoid including common.h doc: describe Milk-V Mars board Kongyang Liu (5): riscv: cpu: cv1800b: Add support for cv1800b SoC riscv: cache: Implement dcache for cv1800b mmc: cv1800b: Add sdhci driver support for cv1800b SoC riscv: dts: sophgo: Add clk node and sdhci node configs: milkv_duo: Add SD card configs Łukasz Stelmach (1): riscv: Move virtio scan to board_late_init() arch/riscv/Kconfig | 22 ++++ arch/riscv/Makefile | 4 + arch/riscv/cpu/cpu.c | 60 +++++++---- arch/riscv/cpu/cv1800b/Kconfig | 12 +++ arch/riscv/cpu/cv1800b/Makefile | 7 ++ arch/riscv/cpu/cv1800b/cache.c | 45 ++++++++ arch/riscv/cpu/cv1800b/cpu.c | 9 ++ arch/riscv/cpu/cv1800b/dram.c | 21 ++++ arch/riscv/cpu/start.S | 1 + arch/riscv/dts/cv1800b-milkv-duo.dts | 8 ++ arch/riscv/dts/cv1800b.dtsi | 4 + arch/riscv/dts/cv18xx.dtsi | 22 ++++ arch/riscv/dts/jh7110-starfive-visionfive-2.dtsi | 2 +- arch/riscv/include/asm/arch-jh7110/eeprom.h | 9 ++ arch/riscv/lib/interrupts.c | 35 +++++++ board/emulation/qemu-riscv/qemu-riscv.c | 12 +-- board/sophgo/milkv_duo/Kconfig | 4 +- board/starfive/visionfive2/spl.c | 100 +++++++++++++++--- board/starfive/visionfive2/starfive_visionfive2.c | 48 ++++++--- .../starfive/visionfive2/visionfive2-i2c-eeprom.c | 9 +- configs/milkv_duo_defconfig | 10 ++ configs/starfive_visionfive2_defconfig | 1 - doc/board/starfive/index.rst | 1 + doc/board/starfive/milk-v_mars.rst | 111 ++++++++++++++++++++ doc/board/starfive/visionfive2.rst | 18 ++++ drivers/cpu/riscv_cpu.c | 8 +- drivers/mmc/Kconfig | 13 +++ drivers/mmc/Makefile | 1 + drivers/mmc/cv1800b_sdhci.c | 116 +++++++++++++++++++++ 29 files changed, 649 insertions(+), 64 deletions(-) create mode 100644 arch/riscv/cpu/cv1800b/Kconfig create mode 100644 arch/riscv/cpu/cv1800b/Makefile create mode 100644 arch/riscv/cpu/cv1800b/cache.c create mode 100644 arch/riscv/cpu/cv1800b/cpu.c create mode 100644 arch/riscv/cpu/cv1800b/dram.c create mode 100644 doc/board/starfive/milk-v_mars.rst create mode 100644 drivers/mmc/cv1800b_sdhci.c Best regards, Leo

2 1

FIT image parameters question - kernel load address, entry point.
by Lev Olshvang 09 Apr '24

09 Apr '24

Hi List, My board - Armada 3720 Expressobin extended with marvell switch and couple of other network interfaces, running Linux 4.19 Our platform has 2GB RAM, TIM-1.0 WTMI-armada-17.10.5-7de3572 WTMI: system early-init DDR topology parameters: ======================== ddr type DDR3 ddr speedbin 12 bus width 16-bits cs num 2 cs[0] - group num 0 cs[0] - bank num 8 cs[0] - capacity 1024MiB cs[1] - group num 0 cs[1] - bank num 8 cs[1] - capacity 1024MiB SVC REV: 5, CPU VDD voltage: 1.143V DRAM windows: ============= WIN[0] - base addr 0x60000000 WIN[0] - size 0x40000000 WIN[1] - base addr 0xa0000000 WIN[1] - size 0x20000000 =================== Recently I spent several days trying to figure out what kernel load address and entry point to use as FIT image parameters. I started by adding printk to arch/arm64/mm/mmu.c:436 and got kernel start address 0x80000 when board was booted from /boot/Image I then put FIT image into memory 0x500000 and applied bootm with a single argument - bootm 0x5000000 Uboot successfully verified signature but freeze after messages > Loading Kernel Image ... OK > Using Device Tree in place at 0000000004f00000, end > 0000000004f05c7e > > Starting kernel ... Kernel is compiled with RELOCATABLE config on, Some uboot specialists make claim that the memory is corrupted, but there are no other running actors So I return to my questions : Question 1. What is the magic, how load address and entry could be figured ? I tried more then 20 different addresses to no success, except thet some addresses immediately reset board Question 2. What should I choose as load fdt address? Question 3. On what address FIT image should be loaded, I load it with tftp command? Question 4. What form of bootm command to use; cause bootm may accept 3 parameters (fortunately IU do not have initrd) Question 5. I cconfused by DRAM windows base adddr & size that uboot reports (see 30 lines above) Should I just ignore it, cause higher up I see 2 banks of 1GB each and I am OK with It.

1 0

[PATCH v4 0/3] Add pcf2131 rtc support
by Joy Zou 09 Apr '24

09 Apr '24

The patchset supports pcf2131 rtc. For the details, please check the patch commit log. Joy Zou (3): drivers: rtc: add pcf2131 rtc driver imx: imx93_evk: add rtc PCF2131 imx93_11x11_evk: Add PCF2131 RTC support arch/arm/dts/imx93-11x11-evk-u-boot.dtsi | 34 ++++++ configs/imx93_11x11_evk_defconfig | 1 + drivers/rtc/pcf2127.c | 146 ++++++++++++++++++++--- 3 files changed, 167 insertions(+), 14 deletions(-) -- 2.37.1

2 4

[PATCH] doc: build: update docker image to latest
by Mattijs Korpershoek 09 Apr '24

09 Apr '24

commit cacc0b2678c0 ("CI: Move to latest container image") updated the docker container image. Reflect the change in the documentation. Signed-off-by: Mattijs Korpershoek <mkorpershoek(a)baylibre.com> --- Note: maybe we can consider doing the doc change each time we update .gitlab-ci.yml ? --- doc/build/docker.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/docker.rst b/doc/build/docker.rst index 953d1b28a063..45659b3b89dc 100644 --- a/doc/build/docker.rst +++ b/doc/build/docker.rst @@ -11,4 +11,4 @@ Or to use an existing container .. code-block:: bash - sudo docker pull trini/u-boot-gitlab-ci-runner:bionic-20200807-02Sep2020 + sudo docker pull trini/u-boot-gitlab-ci-runner:jammy-20240227-14Mar2024 --- base-commit: cdfcc37428e06f4730ab9a17cc084eeb7676ea1a change-id: 20240405-doc-container-img-904d56d5efcb Best regards, -- Mattijs Korpershoek <mkorpershoek(a)baylibre.com>

3 3

[PATCH] mtd: spi-nor: Add support for Infineon S25FS-S family
by tkuw584924＠gmail.com 09 Apr '24

09 Apr '24

From: Takahiro Kuwano <Takahiro.Kuwano(a)infineon.com> The S25FS064S, S25FS128S, and S25FS256S are the same family of SPI NOR Flash devices with S25FS512S. Some difference depending on the device densities are taken care in fixup hooks. Signed-off-by: Takahiro Kuwano <Takahiro.Kuwano(a)infineon.com> --- Datasheets: https://www.infineon.com/dgdl/Infineon-S25FS064S_64_Mb_8_MB_FS-S_Flash_SPI_… https://www.infineon.com/dgdl/Infineon-S25FS128S_S25FS256S_1.8_V_Serial_Per… --- drivers/mtd/spi/spi-nor-core.c | 28 +++++++++++++++++++++------- drivers/mtd/spi/spi-nor-ids.c | 7 +++++-- 2 files changed, 26 insertions(+), 9 deletions(-) diff --git a/drivers/mtd/spi/spi-nor-core.c b/drivers/mtd/spi/spi-nor-core.c index f86003ca8c..9b81b31e8e 100644 --- a/drivers/mtd/spi/spi-nor-core.c +++ b/drivers/mtd/spi/spi-nor-core.c @@ -3299,8 +3299,10 @@ static int s25fs_s_quad_enable(struct spi_nor *nor) static int s25fs_s_erase_non_uniform(struct spi_nor *nor, loff_t addr) { + u8 opcode = nor->addr_width == 4 ? SPINOR_OP_BE_4K_4B : SPINOR_OP_BE_4K; + /* Support 8 x 4KB sectors at bottom */ - return spansion_erase_non_uniform(nor, addr, SPINOR_OP_BE_4K_4B, 0, SZ_32K); + return spansion_erase_non_uniform(nor, addr, opcode, 0, SZ_32K); } static int s25fs_s_setup(struct spi_nor *nor, const struct flash_info *info, @@ -3354,12 +3356,24 @@ static int s25fs_s_post_bfpt_fixup(struct spi_nor *nor, static void s25fs_s_post_sfdp_fixup(struct spi_nor *nor, struct spi_nor_flash_parameter *params) { - /* READ_1_1_2 is not supported */ - params->hwcaps.mask &= ~SNOR_HWCAPS_READ_1_1_2; - /* READ_1_1_4 is not supported */ - params->hwcaps.mask &= ~SNOR_HWCAPS_READ_1_1_4; - /* PP_1_1_4 is not supported */ - params->hwcaps.mask &= ~SNOR_HWCAPS_PP_1_1_4; + /* + * The S25FS064S(8MB) supports 1-1-2 and 1-1-4 commands, but params for + * read ops in SFDP are wrong. The other density parts do not support + * 1-1-2 and 1-1-4 commands. + */ + if (params->size == SZ_8M) { + spi_nor_set_read_settings(&params->reads[SNOR_CMD_READ_1_1_2], + 0, 8, SPINOR_OP_READ_1_1_2, + SNOR_PROTO_1_1_2); + spi_nor_set_read_settings(&params->reads[SNOR_CMD_READ_1_1_4], + 0, 8, SPINOR_OP_READ_1_1_4, + SNOR_PROTO_1_1_4); + } else { + params->hwcaps.mask &= ~SNOR_HWCAPS_READ_1_1_2; + params->hwcaps.mask &= ~SNOR_HWCAPS_READ_1_1_4; + params->hwcaps.mask &= ~SNOR_HWCAPS_PP_1_1_4; + } + /* Use volatile register to enable quad */ params->quad_enable = s25fs_s_quad_enable; } diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c index 4e83b8c94c..9ca1f244f0 100644 --- a/drivers/mtd/spi/spi-nor-ids.c +++ b/drivers/mtd/spi/spi-nor-ids.c @@ -338,9 +338,12 @@ const struct flash_info spi_nor_ids[] = { */ { INFO("s25sl032p", 0x010215, 0x4d00, 64 * 1024, 64, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, { INFO("s25sl064p", 0x010216, 0x4d00, 64 * 1024, 128, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, - { INFO("s25fl256s0", 0x010219, 0x4d00, 256 * 1024, 128, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, - { INFO("s25fl256s1", 0x010219, 0x4d01, 64 * 1024, 512, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, + { INFO6("s25fl256s0", 0x010219, 0x4d0080, 256 * 1024, 128, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, + { INFO6("s25fl256s1", 0x010219, 0x4d0180, 64 * 1024, 512, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, { INFO6("s25fl512s", 0x010220, 0x4d0080, 256 * 1024, 256, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, + { INFO6("s25fs064s", 0x010217, 0x4d0181, 64 * 1024, 128, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, + { INFO6("s25fs128s", 0x012018, 0x4d0181, 64 * 1024, 256, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, + { INFO6("s25fs256s", 0x010219, 0x4d0181, 64 * 1024, 512, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, { INFO6("s25fs512s", 0x010220, 0x4d0081, 256 * 1024, 256, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, { INFO("s25fl512s_256k", 0x010220, 0x4d00, 256 * 1024, 256, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, { INFO("s25fl512s_64k", 0x010220, 0x4d01, 64 * 1024, 1024, SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR) }, -- 2.34.1

3 2

Pull request efi-2024-07-rc1
by Heinrich Schuchardt 09 Apr '24

09 Apr '24

Dear Tom, The following changes since commit 9cba29b19f43f9450117e8bc89e7dda691ed5ab5: Merge tag 'u-boot-imx-master-20240405' of https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2024-04-05 17:23:58 -0400) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-efi.git tags/efi-2024-07-rc1 for you to fetch changes up to 3f8d13044b32ddd906bb9f2fc705b988ec93df35: efi_loader: access __efi_runtime_rel_start/stop without & (2024-04-08 13:05:50 +0200) Gitlab CI showed no issues: https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/20252 ---------------------------------------------------------------- Pull request efi-2024-07-rc1 Documentation: * improve description of FAT partition name generation * add missing :: in doc/usage/cmd/itest.rst UEFI: * fix address mode for __efi_runtime_start/stop, __efi_runtime_rel_start/stop * fix size of variable attribute constants * enable booting via EFI boot manager by default * correct the sequence of the EFI boot methods * correct finding the default EFI binary * don't delete variable from memory if update failed * fix append write behavior to non-existent variable * Use binman for testing capsule updates on the sandbox * Consider capsule test files in .gitignore and make clean ---------------------------------------------------------------- Heinrich Schuchardt (9): doc: missing :: in doc/usage/cmd/itest.rst doc: improve description of FAT partition name generation efi_loader: all variable attributes are 32bit efi_loader: EFI_VARIABLE_READ_ONLY should be 32bit efi_loader: handle EFI_VARIABLE_ENHANCED_AUTHENTICATED_ACCESS boot: correct the default sequence of boot methods boot: enable booting via EFI boot manager by default efi_loader: move HOST_ARCH to version_autogenerated.h boot: correct finding the default EFI binary Ilias Apalodimas (3): efi_loader: Don't delete variable from memory if adding a new one failed efi_loader: access __efi_runtime_start/stop without & efi_loader: access __efi_runtime_rel_start/stop without & Masahisa Kojima (1): efi_loader: fix append write behavior to non-existent variable Sughosh Ganu (4): sandbox: capsule: remove capsule related configs sandbox: capsule: binman: generate some capsules as part of build capsule: add the generated capsules to gitignore capsule: Makefile: add the generated files to CLEAN_FILES list .gitignore | 3 + Makefile | 4 +- arch/sandbox/config.mk | 2 - arch/sandbox/dts/sandbox.dts | 4 + arch/sandbox/dts/sandbox_capsule.dtsi | 169 +++++++++++++++++++++ arch/sandbox/dts/test.dts | 4 + boot/Kconfig | 10 ++ boot/Makefile | 2 +- boot/bootmeth_efi.c | 46 +----- boot/bootmeth_efi_mgr.c | 2 +- boot/bootmeth_pxe.c | 2 +- configs/sandbox64_defconfig | 5 - configs/sandbox_noinst_defconfig | 2 - configs/sandbox_spl_defconfig | 2 - configs/sandbox_vpl_defconfig | 2 - doc/usage/cmd/itest.rst | 2 + doc/usage/partitions.rst | 17 ++- include/efi.h | 18 ++- include/efi_variable.h | 2 +- include/host_arch.h | 2 + lib/efi_loader/Kconfig | 1 - lib/efi_loader/Makefile | 3 +- lib/efi_loader/efi_memory.c | 4 +- lib/efi_loader/efi_runtime.c | 6 +- lib/efi_loader/efi_var_common.c | 2 +- lib/efi_loader/efi_variable.c | 45 ++++-- lib/efi_selftest/efi_selftest_variables.c | 48 +++++- test/boot/bootflow.c | 6 +- .../tests/test_efi_capsule/capsule_gen_binman.dts | 167 +------------------- test/py/tests/test_efi_capsule/conftest.py | 1 + 30 files changed, 326 insertions(+), 257 deletions(-) create mode 100644 arch/sandbox/dts/sandbox_capsule.dtsi

2 1

Issues reading large files from nand ubifs ARM64
by Matthew Rainey 08 Apr '24

08 Apr '24

Hello U-Boot community, I am having issues reading large files (~20 MiB and larger) from nand flash on an arm64 development board. Smaller files load and work as intended. I have tested this in linux, which also works as intended. However, in U-Boot, it gives the following error: ubifsload 0x90000000 "core-image-minimal-ls1046afrwy.cpio.gz.u-boot" Loading file 'core-image-minimal-ls1046afrwy.cpio.gz.u-boot' to addr 0x90000000... UBIFS error (ubi0:0 pid 0): do_readpage: cannot read page 5553 of inode 66, error -12 Error reading file 'core-image-minimal-ls1046afrwy.cpio.gz.u-boot' ** File not found core-image-minimal-ls1046afrwy.cpio.gz.u-boot ** It seems to fail on a random page between 300 and 6000. Nand reads after this error cause U-Boot to panic. Digging a bit deeper, error -12 (-ENOMEM) seems to come from line 274 and 413 in tnc_misc.c. It seems to alternate between the two. https://github.com/u-boot/u-boot/blob/master/fs/ubifs/tnc_misc.c I looked around and don’t see an obvious memory leak. I have 4 GiB of ram, which should be plenty. This issue also doesn’t exist using just UBI (not ubifs) to the same location, so It feels like the ubifs driver is messing up. I have tried U-Boot 2019.10 and 2022.04, and they both present the same issue. I’m using this to load a rootfs ramdisk (~141 MiB) into ram. As an absolute last resort, I could split the rootfs into 16 MiB files, and stitch them together in u-boot. Hopefully I won’t have to do that 😊 If you need additional information, please do not hesitate to contact me. Thank you, Matt

1 0

[PATCH v3 0/6] Add SE HMBSC board support
by Sumit Garg 08 Apr '24

08 Apr '24

SE HMIBSC board is based on Qcom APQ8016 SoC. One of the major difference from db410c is serial port where HMIBSC board uses UART1 as the debug console with an RS232 port, patch #2 - #5 adds corresponding driver support. Patch #6 adds main HMIBSC board specific bits, features: - Qualcomm Snapdragon 410C SoC - APQ8016 (4xCortex A53, Adreno 306) - 2GiB RAM - 64GiB eMMC, SD slot - WiFi and Bluetooth - 2x Host, 1x Device USB port - HDMI - Discrete TPM2 chip over SPI Features enabled in U-Boot: - RAUC updates (refer [2] for more details) - Environment protection - USB based ethernet adaptors Feedback is very much welcome. Changes in v3: - Rebased on top of qcom-next [1]. - Collected some review tags. - Incorporated misc. comments from Caleb and Stephen. - Split patch#4 as requested. - Linux HMIBSC board DTS has already been reviewed here [3], I have incorporated that for U-Boot too. Changes in v2: - Rebased on top on qcom-next [1]. - Added patch#1 as a fix for generic qcom board support. - Added patch#4 to enable driving GPIO pins based on pinctrl configuration. This replaces the custom GPIO configuration. - Added proper DTS file for HMIBSC board based on Linux DT pattern. - Merged board support patches into a single patch#5. [1] https://source.denx.de/u-boot/custodians/u-boot-snapdragon/-/commits/qcom-n… [2] https://rauc.readthedocs.io/en/latest/ [3] https://lore.kernel.org/linux-kernel/20240403043416.3800259-4-sumit.garg@li… Sumit Garg (6): qcom: Don't enable LINUX_KERNEL_IMAGE_HEADER by default apq8016: Add support for UART1 clocks and pinmux serial_msm: Enable RS232 flow control pinctrl: qcom: Add support for driving GPIO pins output pinctrl: qcom: apq8016: Add GPIO pinctrl function board: add support for Schneider HMIBSC board arch/arm/Kconfig | 2 +- arch/arm/dts/apq8016-schneider-hmibsc.dts | 491 ++++++++++++++++++++++ board/schneider/hmibsc/MAINTAINERS | 6 + configs/hmibsc_defconfig | 86 ++++ doc/board/index.rst | 1 + doc/board/schneider/hmibsc.rst | 45 ++ doc/board/schneider/index.rst | 9 + drivers/clk/qcom/clock-apq8016.c | 38 +- drivers/pinctrl/qcom/pinctrl-apq8016.c | 2 + drivers/pinctrl/qcom/pinctrl-qcom.c | 25 +- drivers/serial/serial_msm.c | 24 +- include/configs/hmibsc.h | 57 +++ 12 files changed, 760 insertions(+), 26 deletions(-) create mode 100644 arch/arm/dts/apq8016-schneider-hmibsc.dts create mode 100644 board/schneider/hmibsc/MAINTAINERS create mode 100644 configs/hmibsc_defconfig create mode 100644 doc/board/schneider/hmibsc.rst create mode 100644 doc/board/schneider/index.rst create mode 100644 include/configs/hmibsc.h -- 2.34.1

3 10

[PATCH 0/4] qcom: pinctrl drivers for qcm2290/sm6115/sm8250
by Caleb Connolly 08 Apr '24

08 Apr '24

Introduce pinctrl drivers for three new SoCs and enable them. Signed-off-by: Caleb Connolly <caleb.connolly(a)linaro.org> --- Caleb Connolly (4): pinctrl: qcom: add qcm2290 pinctrl driver pinctrl: qcom: add sm6115 pinctrl driver pinctrl: qcom: add sm8250 pinctrl driver qcom_defconfig: enable pinctrl for new qcm2290/sm6115/sm8250 configs/qcom_defconfig | 3 + drivers/pinctrl/qcom/Kconfig | 21 ++++ drivers/pinctrl/qcom/Makefile | 3 + drivers/pinctrl/qcom/pinctrl-qcm2290.c | 67 +++++++++++ drivers/pinctrl/qcom/pinctrl-sm6115.c | 197 +++++++++++++++++++++++++++++++++ drivers/pinctrl/qcom/pinctrl-sm8250.c | 96 ++++++++++++++++ 6 files changed, 387 insertions(+) --- change-id: 20240408-b4-qcom-rbx-soc-44ee99c8b799 base-commit: 072eacb0c7a2d7a621b581d238422f0254c78cb2 Caleb Connolly <caleb.connolly(a)linaro.org>

2 6