u-boot.git/drivers/misc, branch v2026.04-rc1

misc: ele_api: Add Voltage change start and finish APIs

2026-01-17T18:00:23Z

On GDET enabled part, need to call voltage change start and finish APIs when adjust the voltage more than 100mv. Otherwise GDET will be triggered and system is reset Reviewed-by: Peng Fan Signed-off-by: Ye Li Signed-off-by: Peng Fan

misc: Add fixed-layout support

2026-01-13T15:42:44Z

The "fixed-layout" nvmem controller subnode used to be optional wrapper around nvmem controller cells subnodes. The "fixed-layout" node is now mandatory in most cases, but in order to support both recent and legacy DTs, both variants have to be supported. Implement support for the "fixed-layout" node in the most trivial manner, check whether the nvmem cell supernode is compatible with "fixed-layout" and if it is, proceed one level above it to find the nvmem controller. Signed-off-by: Marek Vasut

led: remove support for red LED in legacy API

2025-12-05T19:38:09Z

To the exception of red_led_on in the arm-specific assembly code, all code interacting with the red status LED was guarded by the CONFIG_LED_STATUS_RED symbol, which is enabled in none of the upstream defconfigs. Since the last board which overrode the weak red_led_on function got migrated to the new LED mechanism, there's also no user of the arm-specific assembly code anymore, therefore it can be removed along the other unreachable code sections. Signed-off-by: Quentin Schulz Reviewed-by: Heiko Schocher

led: remove support for green status led in legacy API

2025-12-05T19:38:09Z

The last user of it was removed in a previous commit so let's remove its support entirely. Signed-off-by: Quentin Schulz Reviewed-by: Heiko Schocher

led: remove coloured_LED_init, yellow and blue status LEDs in legacy API

2025-12-05T16:34:52Z

The last user of coloured_LED_init has been recently removed, so we can remove all places it's called and defined as it does nothing now. Nobody makes use of the yellow and blue status LEDs from the legacy API, so let's remove all references to it. Signed-off-by: Quentin Schulz

qfw/acpi: do not zero out XSDT address

2025-11-06T22:26:27Z

On RISC-V QEMU provides an XSDT table. The RSDP table points to it. We must not zero out this pointer because otherwise no ACPI table can be found. Fixes: 15ca25e31ed5 ("x86: emulation: Support BLOBLIST_TABLES properly") Reviewed-by: Bin Meng Signed-off-by: Heinrich Schuchardt

misc: introduce Qcom GENI wrapper

2025-10-30T17:04:51Z

Qualcomm peripherals like UART, SPI, I2C, etc are all exposed under a common GENI Serial Engine wrapper device. Replace the stub driver we use for this currently with a full-on misc device and implement support for loading peripheral firmware. Each of the peripherals has it's own protocol-specific firmware, this is stored on the internal storage of the device with a well-known partition type GUID. To support this, GENI will bind peripherals in two stages. First the ones that already have firmware loaded (such as the serial port) are bound in the typical way. But devices that require firmware loading are deferred until EVT_LAST_STAGE_INIT. At this point we can be sure that the storage device is available, so we load the firmware and then bind and probe the remaining children. Child devices are expected to determine if firmware loading is necessary and call qcom_geni_load_firmware(). Since Linux currently doesn't support loading firmware (and firmware may not be available), we probe all GENI peripherals to ensure that they always load firmware if necessary. Signed-off-by: Casey Connolly Link: https://patch.msgid.link/20250714-geni-load-fw-v5-3-5abbc0d29838@linaro.org Signed-off-by: Casey Connolly

x86: Rename arch/x86/include/asm/pnp_def.h to include/pnp_def.h

2025-10-28T18:24:03Z

There is nothing x86-centric in this include file, and moving it will allow for some drivers to be compile-tested on sandbox. Signed-off-by: Tom Rini

fw_loader: Split from fs_loader into separate library file

2025-10-09T19:50:40Z

The script based firmware loader does not use anything from the fs_loader implementation. Separate it into its own library source file and convert the mediatek PHY to use this separate code. This should reduce the amount of code that is pulled in alongside the firmware loader, as the FS loader is no longer included. Signed-off-by: Marek Vasut

misc: ti: k3: Tighten K3_FUSE dependencies

2025-10-08T22:13:02Z

This driver cannot build without access to some platform specific header files. Express those requirements in Kconfig as well. Signed-off-by: Tom Rini