u-boot.git/doc/device-tree-bindings, branch master Unnamed repository; edit this file 'description' to name the repository. doc: remove u-boot,boot-led and u-boot,error-led from "binding" 2025-12-03T17:03:45+00:00 Quentin Schulz quentin.schulz@cherry.de 2025-11-12T17:48:16+00:00 eb02d87c7579f83f6fe153c80d420e5f53bde4c1 We're aiming to reduce the amount of U-Boot-specific and out-of-spec Device Tree additions. Those two properties haven't been doing anything for a long time already, except when read by board files manually. This is still the case for STM32 boards but those will be migrated in the near future according to their maintainer. In any case, let's not encourage people to add either of these properties to new or existing Device Trees and remove it from the bindings. Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> 
We're aiming to reduce the amount of U-Boot-specific and out-of-spec
Device Tree additions.

Those two properties haven't been doing anything for a long time
already, except when read by board files manually. This is still the
case for STM32 boards but those will be migrated in the near future
according to their maintainer. In any case, let's not encourage people
to add either of these properties to new or existing Device Trees and
remove it from the bindings.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
doc: dt-bindings: remove duplicates with dts/upstream 2025-12-03T17:03:45+00:00 Quentin Schulz quentin.schulz@cherry.de 2025-11-12T17:48:09+00:00 b0f39c085dc8f99becd7b2a83d43958c5e6fa936 doc/device-tree-bindings/leds/leds-bcm6328.txt can be found at dts/upstream/Bindings/leds/leds-bcm6328.yaml. doc/device-tree-bindings/leds/leds-bcm6358.txt can be found at dts/upstream/Bindings/leds/leds-bcm6358.txt. doc/device-tree-bindings/leds/leds-gpio.txt can be found at dts/upstream/Bindings/leds/leds-gpio.yaml. doc/device-tree-bindings/leds/leds-lp5562.txt can be found at dts/upstream/Bindings/leds/leds-lp55xx.yaml. Only two LED dt-bindings are left in U-Boot: leds-bcm6858.txt and leds-pwm.txt. The former is partially supported by dts/upstream/Bindings/leds/leds-bcm63138.yaml but is lacking all optional properties we have listed in "downstream" dt-binding in U-Boot. However, there doesn't seem to exist any user of that compatible. The latter is partially supported by dts/upstream/Bindings/leds/leds-pwm.yaml but is missing the u-boot,default-brightness property, which is used by arch/arm/dts/rk3326-odroid-go2-u-boot.dtsi at the moment. The default-brightness property is probably not what we want here as it defaults to max-brightness if missing. I'm assuming we want a different value for U-Boot (127) and the kernel (255 via max-brightness as a default), which would prevent us from upstreaming this property, which doesn't change the status quo, so let it be for now. Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> 
doc/device-tree-bindings/leds/leds-bcm6328.txt can be found at
dts/upstream/Bindings/leds/leds-bcm6328.yaml.

doc/device-tree-bindings/leds/leds-bcm6358.txt can be found at
dts/upstream/Bindings/leds/leds-bcm6358.txt.

doc/device-tree-bindings/leds/leds-gpio.txt can be found at
dts/upstream/Bindings/leds/leds-gpio.yaml.

doc/device-tree-bindings/leds/leds-lp5562.txt can be found at
dts/upstream/Bindings/leds/leds-lp55xx.yaml.

Only two LED dt-bindings are left in U-Boot: leds-bcm6858.txt and
leds-pwm.txt. The former is partially supported by
dts/upstream/Bindings/leds/leds-bcm63138.yaml but is lacking all
optional properties we have listed in "downstream" dt-binding in U-Boot.
However, there doesn't seem to exist any user of that compatible.
The latter is partially supported by
dts/upstream/Bindings/leds/leds-pwm.yaml but is missing the
u-boot,default-brightness property, which is used by
arch/arm/dts/rk3326-odroid-go2-u-boot.dtsi at the moment. The
default-brightness property is probably not what we want here as it
defaults to max-brightness if missing. I'm assuming we want a different
value for U-Boot (127) and the kernel (255 via max-brightness as a
default), which would prevent us from upstreaming this property, which
doesn't change the status quo, so let it be for now.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
doc: bindings: fix aquantia-phy.txt typo 2025-10-22T09:16:10+00:00 Beiyan Yun root@infi.wang 2025-09-23T07:12:59+00:00 efaadc02b736da82ef9868d11960a63faae9b3fe Fix typo: "weays" -> "ways" Signed-off-by: Beiyan Yun <root@infi.wang> 
Fix typo: "weays" -> "ways"

Signed-off-by: Beiyan Yun <root@infi.wang>
remoteproc: k3: update compatible for am654 syscon 2025-08-25T18:46:33+00:00 Anshul Dalal anshuld@ti.com 2025-08-14T15:21:43+00:00 bd5036ddf2f3d9198f4054fc1a807c8f8960b281 The existing compatible name for U-Boot's k3 system controller driver i.e "ti,am625-system-controller" has been added to linux[1] device-tree. This compatible in kernel is meant for configuring the Control Module registers (CTRL_MMR0). However in U-Boot, the matching driver was being used to load the system firmware on the secure M-cores by the R5 SPL and therefore must be updated to a different compatible to avoid conflicts. Therefore, this patch renames all references of the compatible to "ti,am654-tisci-rproc-r5". The "-r5" is appended so as to avoid any future conflicts since r5 specific compatibles should only be useful for U-Boot. [1]: 5959618631fe ("dt-bindings: mfd: ti,j721e-system-controller: Add compatible string for AM654") https://lore.kernel.org/r/20250421214620.3770172-2-afd@ti.com Signed-off-by: Anshul Dalal <anshuld@ti.com> 
The existing compatible name for U-Boot's k3 system controller driver
i.e "ti,am625-system-controller" has been added to linux[1] device-tree.
This compatible in kernel is meant for configuring the Control Module
registers (CTRL_MMR0).

However in U-Boot, the matching driver was being used to load the system
firmware on the secure M-cores by the R5 SPL and therefore must be
updated to a different compatible to avoid conflicts.

Therefore, this patch renames all references of the compatible to
"ti,am654-tisci-rproc-r5". The "-r5" is appended so as to avoid any
future conflicts since r5 specific compatibles should only be useful for
U-Boot.

[1]: 5959618631fe ("dt-bindings: mfd: ti,j721e-system-controller: Add compatible string for AM654")
     https://lore.kernel.org/r/20250421214620.3770172-2-afd@ti.com

Signed-off-by: Anshul Dalal <anshuld@ti.com>
arch: arm: agilex5: Enable power manager for Agilex5 2025-07-30T09:45:31+00:00 Alif Zakuan Yuslaimi alif.zakuan.yuslaimi@altera.com 2025-06-12T08:08:00+00:00 9f689086863dfae693551a68fc9dc426bca5727e Agilex5 FSBL is required to disable the power of unused peripheral SRAM blocks to reduce power consumption. Introducing a new power manager driver for Agilex5 which will be called as part of Agilex5 SPL initialization process. This driver will read the peripheral handoff data obtained from the bitstream and will power off the specified peripheral's SRAM from the handoff data values. Signed-off-by: Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@altera.com> Reviewed-by: Tien Fong Chee <tien.fong.chee@altera.com> 
Agilex5 FSBL is required to disable the power of unused peripheral SRAM
blocks to reduce power consumption.

Introducing a new power manager driver for Agilex5 which will be called
as part of Agilex5 SPL initialization process.

This driver will read the peripheral handoff data obtained from the
bitstream and will power off the specified peripheral's SRAM from the
handoff data values.

Signed-off-by: Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@altera.com>
Reviewed-by: Tien Fong Chee <tien.fong.chee@altera.com>
env: Rename ENV_MMC_PARTITION to ENV_MMC_SW_PARTITION 2025-06-20T18:15:08+00:00 Marek Vasut marek.vasut+renesas@mailbox.org 2025-06-09T19:26:41+00:00 ffc4914703a2b897d51e3412703b1d4f42081b42 Rename the variable and add ENV_ prefix, so that all configuration options which are related to environment would have an CONFIG_ENV_ prefix. No functional change. Use ENV_MMC_SW_PARTITION to clarify this is the SD/MMC software partition table entry selector. Update the help text accordingly. Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org> 
Rename the variable and add ENV_ prefix, so that all configuration
options which are related to environment would have an CONFIG_ENV_
prefix. No functional change.

Use ENV_MMC_SW_PARTITION to clarify this is the SD/MMC software
partition table entry selector. Update the help text accordingly.

Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
env: Rename SYS_MMC_ENV_DEV to ENV_MMC_DEVICE_INDEX 2025-06-20T18:15:08+00:00 Marek Vasut marek.vasut+renesas@mailbox.org 2025-06-09T19:26:39+00:00 0f44d5549ed814744b95b2450fbacfa14192587d Rename the variable and add ENV_ prefix, so that all configuration options which are related to environment would have an CONFIG_ENV_ prefix. No functional change. Use ENV_MMC_DEVICE_INDEX to clarify this is the SD/MMC device index, a number, as enumerated by U-Boot. Update the help text accordingly. Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org> 
Rename the variable and add ENV_ prefix, so that all configuration
options which are related to environment would have an CONFIG_ENV_
prefix. No functional change.

Use ENV_MMC_DEVICE_INDEX to clarify this is the SD/MMC device
index, a number, as enumerated by U-Boot. Update the help text
accordingly.

Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
Merge branch 'nand-next' of https://source.denx.de/u-boot/custodians/u-boot-nand-flash into next 2025-03-17T16:18:18+00:00 Tom Rini trini@konsulko.com 2025-03-17T16:18:18+00:00 4101b56d0bf041336cdda10d63be7acdfc92a61b CI: https://source.denx.de/u-boot/custodians/u-boot-nand-flash/-/pipelines/25178 This merge request add support for cadence raw nand driver for agilex board and add a fix to meson driver. 
CI: https://source.denx.de/u-boot/custodians/u-boot-nand-flash/-/pipelines/25178

This merge request add support for cadence raw nand driver for agilex
board and add a fix to meson driver.
dt: nand: add cadence nand dt-bindings 2025-03-15T09:35:00+00:00 Dinesh Maniyam dinesh.maniyam@intel.com 2025-02-26T16:18:15+00:00 1ae1e9c55ec42d5176aa5f4a88efc62c63863e43 The Cadence NAND is a configurable mtd raw block which supports multiple options for chipsets, clocking and reset structure, and feature list. Signed-off-by: Dinesh Maniyam <dinesh.maniyam@intel.com> 
The Cadence NAND is a configurable mtd raw block which
supports multiple options for chipsets, clocking and reset structure, and
feature list.

Signed-off-by: Dinesh Maniyam <dinesh.maniyam@intel.com>
doc: Add dt-bindings and descriptions for ADI SC5xx-family pinctrl 2025-03-12T16:24:58+00:00 Greg Malysa malysagreg@gmail.com 2025-02-26T17:30:24+00:00 a0ffd8d7cd8efb8b348c07fa18a610a4534f9bea This adds the necessary dt-bindings and documentation to use the ADI SC5xx pinctrl driver in a device tree. It is not yet available upstream in the Linux kernel. Eventually, it will be moved there. Signed-off-by: Vasileios Bimpikas <vasileios.bimpikas@analog.com> Signed-off-by: Utsav Agarwal <utsav.agarwal@analog.com> Signed-off-by: Arturs Artamonovs <arturs.artamonovs@analog.com> Signed-off-by: Greg Malysa <malysagreg@gmail.com> 
This adds the necessary dt-bindings and documentation to use the ADI
SC5xx pinctrl driver in a device tree. It is not yet available upstream
in the Linux kernel. Eventually, it will be moved there.

Signed-off-by: Vasileios Bimpikas <vasileios.bimpikas@analog.com>
Signed-off-by: Utsav Agarwal <utsav.agarwal@analog.com>
Signed-off-by: Arturs Artamonovs <arturs.artamonovs@analog.com>
Signed-off-by: Greg Malysa <malysagreg@gmail.com>