November 2023 - U-Boot

[PATCH] usb: xhci: Replace terrible formatting with different terrible formatting
by Marek Vasut 03 Dec '23

03 Dec '23

Replace one type of terrible code formatting with a different type of terrible code formatting. No functional change. Signed-off-by: Marek Vasut <marex(a)denx.de> --- Cc: Bin Meng <bmeng.cn(a)gmail.com> Cc: Hector Martin <marcan(a)marcan.st> --- drivers/usb/host/xhci-ring.c | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c index dabe6cf86af..be3e35102d6 100644 --- a/drivers/usb/host/xhci-ring.c +++ b/drivers/usb/host/xhci-ring.c @@ -543,9 +543,8 @@ static void reset_ep(struct usb_device *udev, int ep_index) if (!event) return; - BUG_ON(TRB_TO_SLOT_ID(le32_to_cpu(event->event_cmd.flags)) - != udev->slot_id || GET_COMP_CODE(le32_to_cpu( - event->event_cmd.status)) != COMP_SUCCESS); + BUG_ON(TRB_TO_SLOT_ID(le32_to_cpu(event->event_cmd.flags)) != udev->slot_id || + GET_COMP_CODE(le32_to_cpu(event->event_cmd.status)) != COMP_SUCCESS); xhci_acknowledge_event(ctrl); } @@ -578,8 +577,7 @@ static void abort_td(struct usb_device *udev, int ep_index) field = le32_to_cpu(event->trans_event.flags); BUG_ON(TRB_TO_SLOT_ID(field) != udev->slot_id); BUG_ON(TRB_TO_EP_INDEX(field) != ep_index); - BUG_ON(GET_COMP_CODE(le32_to_cpu(event->trans_event.transfer_len - != COMP_STOP))); + BUG_ON(GET_COMP_CODE(le32_to_cpu(event->trans_event.transfer_len != COMP_STOP))); xhci_acknowledge_event(ctrl); event = xhci_wait_for_event(ctrl, TRB_COMPLETION); @@ -593,9 +591,8 @@ static void abort_td(struct usb_device *udev, int ep_index) comp = GET_COMP_CODE(le32_to_cpu(event->event_cmd.status)); BUG_ON(type != TRB_COMPLETION || - TRB_TO_SLOT_ID(le32_to_cpu(event->event_cmd.flags)) - != udev->slot_id || (comp != COMP_SUCCESS && comp - != COMP_CTX_STATE)); + TRB_TO_SLOT_ID(le32_to_cpu(event->event_cmd.flags)) != udev->slot_id || + (comp != COMP_SUCCESS && comp != COMP_CTX_STATE)); xhci_acknowledge_event(ctrl); addr = xhci_trb_virt_to_dma(ring->enq_seg, @@ -605,9 +602,8 @@ static void abort_td(struct usb_device *udev, int ep_index) if (!event) return; - BUG_ON(TRB_TO_SLOT_ID(le32_to_cpu(event->event_cmd.flags)) - != udev->slot_id || GET_COMP_CODE(le32_to_cpu( - event->event_cmd.status)) != COMP_SUCCESS); + BUG_ON(TRB_TO_SLOT_ID(le32_to_cpu(event->event_cmd.flags)) != udev->slot_id || + GET_COMP_CODE(le32_to_cpu(event->event_cmd.status)) != COMP_SUCCESS); xhci_acknowledge_event(ctrl); } -- 2.42.0

2 2

[PATCH] watchdog: Correct watchdog timeout print message
by Chanho Park 03 Dec '23

03 Dec '23

The wdt_start function takes timeout_ms as a parameter and starts the watchdog with this value. However, when you output the message, it shows the default timeout value for the watchdog device. So this patch fixes that part to output the correct timeout value. Before --> StarFive # wdt start 3000 WDT: Started watchdog@13070000 without servicing (60s timeout) After --> StarFive # wdt start 3000 WDT: Started watchdog@13070000 without servicing (3s timeout) Fixes: c2fd0ca1a822 ("watchdog: Integrate watchdog triggering into the cyclic framework") Signed-off-by: Chanho Park <chanho61.park(a)samsung.com> --- drivers/watchdog/wdt-uclass.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/wdt-uclass.c b/drivers/watchdog/wdt-uclass.c index ed329284decb..65a4bc1f90ed 100644 --- a/drivers/watchdog/wdt-uclass.c +++ b/drivers/watchdog/wdt-uclass.c @@ -141,7 +141,7 @@ int wdt_start(struct udevice *dev, u64 timeout_ms, ulong flags) printf("WDT: Started %s with%s servicing %s (%ds timeout)\n", dev->name, IS_ENABLED(CONFIG_WATCHDOG) ? "" : "out", - str, priv->timeout); + str, (u32)(timeout_ms / 1000)); } return ret; -- 2.39.2

3 4

[PATCH 0/7] efi: Partial attempt at a test for EFI bootmeth
by Simon Glass 02 Dec '23

02 Dec '23

The test coverage for the EFI bootmeth is incomplete since it does not actually boot the application. This series makes an attempt at this. However there are at least two problems: 1. The test does not set up the loaded image properly, so it isn't found by the app. 2. The test needs to use USB instead of mmc, so that usb_stop() is called Simon Glass (7): efi: Use puts() in cout so that console recording works efi: Show the vendor in helloworld efi: test: Create a disk image with and EFI app in it WIP: efi: Disable ANSI output WIP: efi: Add a test for the EFI bootmeth WIP: efi: Allow helloworld to exit boot services WIP: efi: debugging arch/sandbox/dts/test.dts | 10 ++++++- boot/bootflow.c | 2 ++ boot/bootmeth_efi.c | 1 + cmd/bootefi.c | 1 + include/efi_loader.h | 14 +++++++-- lib/efi_loader/efi_boottime.c | 5 ++++ lib/efi_loader/efi_console.c | 19 +++++------- lib/efi_loader/efi_setup.c | 2 +- lib/efi_loader/helloworld.c | 39 ++++++++++++++++++++++++- test/boot/bootflow.c | 55 ++++++++++++++++++++++++++++++++++- test/py/tests/test_ut.py | 32 ++++++++++++++++++++ 11 files changed, 163 insertions(+), 17 deletions(-) -- 2.43.0.rc1.413.gea7ed67945-goog

3 21

[PATCH 1/5] qe: Add <config.h> to linux/immap_qe.h
by Tom Rini 02 Dec '23

02 Dec '23

Given how we define QE_MURAM_SIZE today, this header needs to have <config.h> added to it. Signed-off-by: Tom Rini <trini(a)konsulko.com> --- include/linux/immap_qe.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/immap_qe.h b/include/linux/immap_qe.h index 45307f51c103..a692f5dfb373 100644 --- a/include/linux/immap_qe.h +++ b/include/linux/immap_qe.h @@ -11,6 +11,8 @@ #ifndef __IMMAP_QE_H__ #define __IMMAP_QE_H__ +#include <config.h> + #ifdef CONFIG_MPC83xx #if defined(CONFIG_ARCH_MPC8360) #define QE_MURAM_SIZE 0xc000UL -- 2.34.1

2 15

[PATCH 1/2] nvme: Fix error code and log to indicate busy
by Moritz Fischer 02 Dec '23

02 Dec '23

Return -EBUSY if controller is found busy rather than -ENOMEM and update the error message accordingly. Fixes: 982388eaa991 ("nvme: Add NVM Express driver support") Signed-off-by: Moritz Fischer <moritzf(a)google.com> --- drivers/nvme/nvme.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/nvme/nvme.c b/drivers/nvme/nvme.c index c39cd41aa3..ec45f831a3 100644 --- a/drivers/nvme/nvme.c +++ b/drivers/nvme/nvme.c @@ -835,8 +835,8 @@ int nvme_init(struct udevice *udev) ndev->udev = udev; INIT_LIST_HEAD(&ndev->namespaces); if (readl(&ndev->bar->csts) == -1) { - ret = -ENODEV; - printf("Error: %s: Out of memory!\n", udev->name); + ret = -EBUSY; + printf("Error: %s: Controller not ready!\n", udev->name); goto free_nvme; } -- 2.43.0.rc1.413.gea7ed67945-goog

2 3

How to use I2C in U-Boot SPL
by Thomas Thielemann 02 Dec '23

02 Dec '23

Hello U-Boot, I was able to use the I2C commands from within U-Boot to control my I2C device: Configured the Processor GPIOs for the I2C bus in device tree Enabled the I2C bus in device tree Added my device to the I2C bus in device tree Wrote my script into a U-Boot variable Run my script Now I want to do the same from within the U-Boot SPL. I extended int board_early_init_f(void) in board.c for my hardware. The debug output is printed at run time. But the I2C device is not found. How do I review whether the I2C bus is using the right GPIOs and whether my device is configured right? static int i2c_get_dev(uint bus_num, uint dev_num, struct udevice **i2c_dev) { int ret; if (!i2c_led_bus) { ret = uclass_get_device_by_seq(UCLASS_I2C, bus_num, &i2c_led_bus); if (ret) { printf("I2C bus %i not found (%d)\n", dev_num, ret); return -ENODEV; } } return i2c_get_chip(i2c_led_bus, dev_num, bus_num, i2c_dev); } #endif static int i2c_enable_leds(void) { log_info("i2c_enable_leds\n"); const uint bus_num = 1; // i2c bus const uint dev_num = 0x28; // i2c chip address const uint dev_addr = 0x00; // write all bytes in one junk from start const uint dev_addr_len = 1; int ret; const uint cmd_len = 29; // cmd_len is the number of bytes. uchar cmd[29] = { 0x40, 0x3c, // init 0x00, 0x00, 0x00, 0x00, 0x00, // unused 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, // set intensitiy to max 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // unused 0xff, 0x00, 0x00, // RGB LED 0xff, 0x00, 0x00 // RGB LED }; #if CONFIG_IS_ENABLED(DM_I2C) struct udevice *i2c_dev; struct dm_i2c_chip *i2c_chip; #endif #if CONFIG_IS_ENABLED(DM_I2C) ret = i2c_get_dev(bus_num, dev_num, &i2c_dev); if (!ret) ret = i2c_set_chip_offset_len(i2c_dev, dev_addr_len); if (ret) { log_err("Failed to write to 0x28 (%d)\n", ret); return ret; } i2c_chip = dev_get_parent_plat(i2c_dev); if (!i2c_chip) { log_err("Failed to write to 0x28 (%d)\n", ret); return ret; } #endif #if CONFIG_IS_ENABLED(DM_I2C) i2c_chip->flags &= ~DM_I2C_CHIP_WR_ADDRESS; ret = dm_i2c_write(i2c_dev, dev_addr, cmd, cmd_len); #else ret = i2c_write(dev_num, dev_addr, dev_addr_len, cmd, cmd_len); #endif if (ret) log_err("Failed to write to 0x28 (%d)\n", ret); return 0; } int board_early_init_f(void) { i2c_enable_leds(); return 0; } Regards, Thomas

2 1

[PATCH v8 0/2] arm64: Add a build target for Flat Image Tree
by Simon Glass 01 Dec '23

01 Dec '23

Flat Image Tree (FIT) is a widely used file format for packaging a kernel and associated devicetree files[1]. It is not specific to any one bootloader, as it is supported by U-Boot, coreboot, Linuxboot, Tianocore and Barebox. This series adds support for building a FIT as part of the kernel build. This makes it easy to try out the kernel - just load the FIT onto your tftp server and it will run automatically on any supported arm64 board. The script is written in Python, since it is easy to build a FIT using the Python libfdt bindings. For now, no attempt is made to compress files in parallel, so building the 900-odd files takes a while, about 6 seconds with my testing. The series also includes a few minor clean-up patches. [1] https://github.com/open-source-firmware/flat-image-tree Changes in v8: - Drop compatible string in FDT node - Correct sorting of MAINTAINERS to before ARM64 PORT - Turn compress part of the make_fit.py comment in to a sentence - Add two blank lines before parse_args() and setup_fit() - Use 'image.fit: dtbs' instead of BUILD_DTBS var - Use '$(<D)/dts' instead of '$(dir $<)dts' - Add 'mkimage' details Documentation/process/changes.rst - Allow changing the compression used - Tweak cover letter since there is only one clean-up patch Changes in v7: - Drop the kbuild tag - Add Image as a dependency of image.fit - Drop kbuild tag - Add dependency on dtbs - Drop unnecessary path separator for dtbs - Rebase to -next Changes in v6: - Drop the unwanted .gz suffix Changes in v5: - Drop patch previously applied - Correct compression rule which was broken in v4 Changes in v4: - Use single quotes for UIMAGE_NAME Changes in v3: - Drop temporary file image.itk - Drop patch 'Use double quotes for image name' - Drop double quotes in use of UIMAGE_NAME - Drop unnecessary CONFIG_EFI_ZBOOT condition for help - Avoid hard-coding "arm64" for the DT architecture Changes in v2: - Drop patch previously applied - Add .gitignore file - Move fit rule to Makefile.lib using an intermediate file - Drop dependency on CONFIG_EFI_ZBOOT - Pick up .dtb files separately from the kernel - Correct pylint too-many-args warning for write_kernel() - Include the kernel image in the file count - Add a pointer to the FIT spec and mention of its wide industry usage - Mention the kernel version in the FIT description Simon Glass (2): arm64: Add BOOT_TARGETS variable arm64: boot: Support Flat Image Tree Documentation/process/changes.rst | 9 + MAINTAINERS | 7 + arch/arm64/Makefile | 11 +- arch/arm64/boot/.gitignore | 1 + arch/arm64/boot/Makefile | 9 +- scripts/Makefile.lib | 13 ++ scripts/make_fit.py | 291 ++++++++++++++++++++++++++++++ 7 files changed, 338 insertions(+), 3 deletions(-) create mode 100755 scripts/make_fit.py -- 2.43.0.rc2.451.g8631bc7472-goog

2 5

[PATCH 0/5] Add anti-rollback validation feature
by seanedmond＠linux.microsoft.com 01 Dec '23

01 Dec '23

From: Sean Edmond <seanedmond(a)microsoft.com> Adds Add anti-rollback version protection. Images with an anti-rollback counter value "rollback" declared in the kernel FDT will be compared against the current device anti-rollback counter value, and older images will not pass signature validation. If the image is newer, the device anti-rollback counter value will be updated. The "rollback" value is stored/retrieved using the newly added security driver. A "TPM backed" and "sandbox backed" security driver have been provided as examples. Adds new configs: - CONFIG_DM_ROLLBACK : enable security device support - CONFIG_ROLLBACK_SANDBOX : enables "rollback-sandbox" driver - CONFIG_ROLLBACK_TPM : Enables "rollback-tpm" driver - CONFIG_FIT_ROLLBACK_CHECK : enable enforcement of OS anti-rollback counter during image loading - CONFIG_FIT_ROLLBACK_CHECK_GRACE : adds a one unit grace version to OS anti-rollback protection changes in v2: - arbvn -> rollback_idx - rollback-tpm is a child of TPM device - tpm_rollback_counter_init() tries to read NV index, defines and writes 0 if it fails - tpm_rollback_counter_init() moved to tpm-v2.c - Use tpm_auto_start() - No error checking in rollback_idx_get()/rollback_idx_set() (intelligence is in fit_image_verify_rollback()) - assume "rollback" of 0 if FIT property not found - "grace period" -> "grace version" - drop "dm_" prefix in header - Fix for tpm2_nv_define_space() (add "auth" parameter) - Make NV index consistent across APIs (define/read/write/lock). IS THIS CORRECT?! - Add documentation Sean Edmond (1): dm: test: Add a test for security driver Stephen Carlson (4): drivers: security: Add security devices to driver model drivers: security: Add TPM2 implementation of security devices common: Add OS anti-rollback validation using security devices common: Add OS anti-rollback grace period MAINTAINERS | 9 ++ arch/sandbox/dts/test.dts | 8 ++ boot/Kconfig | 19 +++ boot/image-fit-sig.c | 94 +++++++++++++++ boot/image-fit.c | 23 ++++ configs/sandbox_defconfig | 3 + drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/security/Kconfig | 25 ++++ drivers/security/Makefile | 7 ++ drivers/security/sandbox_security.c | 65 +++++++++++ drivers/security/security-tpm.c | 173 ++++++++++++++++++++++++++++ drivers/security/security-uclass.c | 30 +++++ include/dm-security.h | 44 +++++++ include/dm/uclass-id.h | 1 + include/image.h | 4 + include/tpm-v2.h | 1 + test/dm/Makefile | 1 + test/dm/security.c | 78 +++++++++++++ 19 files changed, 588 insertions(+) create mode 100644 drivers/security/Kconfig create mode 100644 drivers/security/Makefile create mode 100644 drivers/security/sandbox_security.c create mode 100644 drivers/security/security-tpm.c create mode 100644 drivers/security/security-uclass.c create mode 100644 include/dm-security.h create mode 100644 test/dm/security.c -- 2.40.0

3 12

[PATCH v2 0/2] *** Add support for phyCORE-AM62x ***
by Wadim Egorov 01 Dec '23

01 Dec '23

As requested by Dhruva, this patch set comes now with a cover-letter :). This is a rebase on top of -next to address recent K3 updates. It should be noted that the huge files are generated or copy pasted from TI's evm. So I do not think they need big attention in the review process. - All yaml files are identical to TI's evm - k3-am62-phycore-som-ddr4-2gb.dtsi generated with TI's SysConfig DDR Tool - k3-am62-phycore-som.dtsi & k3-am625-phyboard-lyra-rdk.dts are 1:1 copies from Linux v6.7-rc3 v2: - Add cover-letter & mention Linux version I took the DTs from - Move board selection to mach-k3 - Add missing SPL_LDSCRIPT definition - Refactore binman file for templated FITs & drop key overrides - Drop SoC provided bootph params from dt files Note: Later we can drop more bootph params after we added them to Linux - Drop CONFIG_TI_SECURE_DEVICE as it is set as default for K3 - Drop cpsw3g custom DT property 'mac_efuse' and custom DT node cpsw-phy-sel as driver picks these from standard property/node (-u-boot.dtsi) - Add a53 cluster power to control from the rproc driver (a53 dt node) v1: https://lists.denx.de/pipermail/u-boot/2023-October/535750.html Wadim Egorov (2): board: phytec: am62x: Add PHYTEC phyCORE-AM62x SoM doc: board: phytec: Add phyCORE-AM62x arch/arm/dts/Makefile | 4 +- .../arm/dts/k3-am62-phycore-som-ddr4-2gb.dtsi | 2190 +++++++++++++++++ arch/arm/dts/k3-am62-phycore-som.dtsi | 324 +++ .../k3-am625-phyboard-lyra-rdk-u-boot.dtsi | 166 ++ arch/arm/dts/k3-am625-phyboard-lyra-rdk.dts | 266 ++ arch/arm/dts/k3-am625-phycore-som-binman.dtsi | 380 +++ arch/arm/dts/k3-am625-r5-phycore-som-2gb.dts | 118 + arch/arm/mach-k3/am62x/Kconfig | 17 + board/phytec/phycore_am62x/Kconfig | 33 + board/phytec/phycore_am62x/MAINTAINERS | 15 + board/phytec/phycore_am62x/Makefile | 8 + board/phytec/phycore_am62x/board-cfg.yaml | 36 + board/phytec/phycore_am62x/phycore-am62x.c | 59 + board/phytec/phycore_am62x/phycore_am62x.env | 23 + board/phytec/phycore_am62x/pm-cfg.yaml | 12 + board/phytec/phycore_am62x/rm-cfg.yaml | 1088 ++++++++ board/phytec/phycore_am62x/sec-cfg.yaml | 379 +++ configs/phycore_am62x_a53_defconfig | 115 + configs/phycore_am62x_r5_defconfig | 130 + doc/board/phytec/index.rst | 1 + doc/board/phytec/phycore-am62x.rst | 125 + doc/board/ti/k3.rst | 1 + include/configs/phycore_am62x.h | 15 + 23 files changed, 5504 insertions(+), 1 deletion(-) create mode 100644 arch/arm/dts/k3-am62-phycore-som-ddr4-2gb.dtsi create mode 100644 arch/arm/dts/k3-am62-phycore-som.dtsi create mode 100644 arch/arm/dts/k3-am625-phyboard-lyra-rdk-u-boot.dtsi create mode 100644 arch/arm/dts/k3-am625-phyboard-lyra-rdk.dts create mode 100644 arch/arm/dts/k3-am625-phycore-som-binman.dtsi create mode 100644 arch/arm/dts/k3-am625-r5-phycore-som-2gb.dts create mode 100644 board/phytec/phycore_am62x/Kconfig create mode 100644 board/phytec/phycore_am62x/MAINTAINERS create mode 100644 board/phytec/phycore_am62x/Makefile create mode 100644 board/phytec/phycore_am62x/board-cfg.yaml create mode 100644 board/phytec/phycore_am62x/phycore-am62x.c create mode 100644 board/phytec/phycore_am62x/phycore_am62x.env create mode 100644 board/phytec/phycore_am62x/pm-cfg.yaml create mode 100644 board/phytec/phycore_am62x/rm-cfg.yaml create mode 100644 board/phytec/phycore_am62x/sec-cfg.yaml create mode 100644 configs/phycore_am62x_a53_defconfig create mode 100644 configs/phycore_am62x_r5_defconfig create mode 100644 doc/board/phytec/phycore-am62x.rst create mode 100644 include/configs/phycore_am62x.h -- 2.34.1

2 5

[PATCH v5 0/9] Qualcomm PMIC fixes
by Caleb Connolly 01 Dec '23

01 Dec '23

This series addresses some long-standing issues with the SPMI arb driver, the PMIC, and the PMIC GPIO. It fixes compatibility with upstream Linux devicetrees, and simplifies pwrkey/resin support by rewriting the pon driver to be a button driver rather than a GPIO driver. Existing users are adjusted to use the new button driver in their oard init code. This series is based on the pinctrl [1] and clock [2] cleanup series. There may be some DTS conflicts applying it standalone. [1]: https://lore.kernel.org/u-boot/20231106-b4-qcom-pinctrl-v2-0-406e8d8689ca@l… [2]: https://lore.kernel.org/u-boot/20231103-b4-qcom-clk-v3-0-8d2d460ece84@linar… --- Changes in v5: - Split "rework pwrkey driver into a button driver" into multiple commits - Split "qcom_pmic: fix support for upstream DT" into multiple commits - Link to v4: https://lore.kernel.org/r/20231128-b4-qcom-dt-compat-v4-0-949d0982d1de@lina… Changes in v4: * Remove some now unsupported DT binding docs * Fix qcs404 SPMI arb dts * Link to v3: https://lore.kernel.org/r/20231114-b4-qcom-dt-compat-v3-0-88a92f8f00ba@lina… Changes in v3: * Remove now-unneeded header includes in dragonboard{410,820}c-uboot.dtsi * Drop non-standard DTS support from PMIC GPIO driver * Also remove old gpio-keys nodes from starqltechn-uboot.dtsi * Link to v2: https://lore.kernel.org/r/20231108-b4-qcom-dt-compat-v2-0-713233c72948@lina… Changes in v2: * Avoid using non-standard "label" and "linux,code" properties for buttons * Add missing sdm845 DTS parts * Put button driver in drivers/button * Link to v1: https://lore.kernel.org/r/20231106-b4-qcom-dt-compat-v1-0-0ccbb7841241@lina… --- Caleb Connolly (9): gpio: qcom_pmic: fix silent dev_read_addr downcast button: qcom-pmic: introduce Qualcomm PMIC button driver mach-snapdragon: switch to PMIC button driver gpio: qcom_pmic: drop pon GPIO driver gpio: qcom_pmic: support upstream DT dts: qcom: adjust pmic gpio to use upstream bindings gpio: qcom_pmic: drop gpio-count property spmi: msm: fix register range names pmic: qcom: dont use dev_read_addr to get USID MAINTAINERS | 1 + arch/arm/dts/dragonboard410c-uboot.dtsi | 11 -- arch/arm/dts/dragonboard410c.dts | 25 +++- arch/arm/dts/dragonboard820c-uboot.dtsi | 12 -- arch/arm/dts/dragonboard820c.dts | 26 ++-- arch/arm/dts/dragonboard845c-uboot.dtsi | 11 -- arch/arm/dts/dragonboard845c.dts | 4 + arch/arm/dts/qcs404-evb.dts | 9 +- arch/arm/dts/sdm845.dtsi | 28 ++-- arch/arm/dts/starqltechn-uboot.dtsi | 10 -- arch/arm/dts/starqltechn.dts | 20 +-- arch/arm/mach-snapdragon/Kconfig | 3 + arch/arm/mach-snapdragon/init_sdm845.c | 45 ++----- board/qualcomm/dragonboard410c/dragonboard410c.c | 31 ++--- board/qualcomm/dragonboard820c/dragonboard820c.c | 29 ++-- doc/device-tree-bindings/gpio/pm8916_gpio.txt | 48 ------- doc/device-tree-bindings/pmic/qcom,spmi-pmic.txt | 94 ------------- doc/device-tree-bindings/spmi/spmi-msm.txt | 26 ---- drivers/button/Kconfig | 9 ++ drivers/button/Makefile | 1 + drivers/button/button-qcom-pmic.c | 165 +++++++++++++++++++++++ drivers/gpio/Kconfig | 3 +- drivers/gpio/qcom_pmic_gpio.c | 146 +++++--------------- drivers/power/pmic/pmic_qcom.c | 13 +- drivers/spmi/spmi-msm.c | 46 +++---- 25 files changed, 341 insertions(+), 475 deletions(-) --- base-commit: 4d5dd7090b5ad770974a377f704907893469ebb3 // Caleb (they/them)

3 20