u-boot.git/doc/device-tree-bindings, branch v2021.10

doc: Complete the list of available runtime-config options

2021-09-11T09:02:02Z

The current list is missing a few items. Add them. Reviewed-by: Marcel Ziswiler Signed-off-by: Simon Glass Acked-by: Heinrich Schuchardt

doc: Tidy up the bindings for the config/ node

2021-09-11T09:02:02Z

Sort these and add a type so it is clear how to set the value. Add a note about usage to the top. Correct the 'no-keyboard' binding which is missing a prefix. Signed-off-by: Simon Glass Reviewed-by: Marcel Ziswiler Signed-off-by: Heinrich Schuchardt

bootcount: add a new driver with syscon as backend

2021-08-22T09:04:52Z

The driver will use a syscon regmap as backend and supports both 16 and 32 size value. The value will be stored in the CPU's endianness. Signed-off-by: Nandor Han Reviewed-by: Simon Glass

doc: stm32mp1: add page for device tree bindings

2021-08-14T18:54:41Z

With device tree binding migration to yaml it is difficult to synchronize the binding from Linux kernel to U-Boot. Instead of maintaining the same dt bindings, this patch adds in the U-Boot documentation the path to the device tree bindings in Linux kernel for STMicroelectronics devices, when they are used without modification. Signed-off-by: Patrick Delaunay Signed-off-by: Patrice Chotard Add links for referenced text files. Signed-off-by: Heinrich Schuchardt

arm64: a37xx: pinctrl: Correct PWM pins definitions

2021-07-31T07:59:58Z

The PWM pins on North Bridge on Armada 37xx can be configured into PWM or GPIO functions. When in PWM function, each pin can also be configured to drive low on 0 and tri-state on 1 (LED mode). The current definitions handle this by declaring two pin groups for each pin: - group "pwmN" with functions "pwm" and "gpio" - group "ledN_od" ("od" for open drain) with functions "led" and "gpio" This is semantically incorrect. The correct definition for each pin should be one group with three functions: "pwm", "led" and "gpio". Change the "pwmN" groups to support "led" function. Remove "ledN_od" groups. This cannot break backwards compatibility with older device trees: no device tree uses it since there is no PWM driver for this SOC yet. Also "ledN_od" groups are not even documented. Signed-off-by: Marek Behún Reviewed-by: Stefan Roese

reboot-mode: read the boot mode from RTC memory

2021-07-23T14:16:39Z

RTC devices could provide battery-backed memory that can be used for storing the reboot mode magic value. Add a new reboot-mode back-end that uses RTC to store the reboot-mode magic value. The driver also supports both endianness modes. Signed-off-by: Nandor Han Reviewed-by: Simon Glass

reboot-mode: read the boot mode from GPIOs status

2021-07-23T14:16:39Z

A use case for controlling the boot mode is when the user wants to control the device boot by pushing a button without needing to go in user-space. Add a new backed for reboot mode where GPIOs are used to control the reboot-mode. The driver is able to scan a predefined list of GPIOs and return the magic value. Having the modes associated with the magic value generated based on the GPIO values, allows the reboot mode uclass to select the proper mode. Signed-off-by: Nandor Han Reviewed-by: Simon Glass

x86: pci: Allow binding of some devices before relocation

2021-07-15T11:49:50Z

At present only bridge devices are bound before relocation, to save space in pre-relocation memory. In some cases we do actually want to bind a device, e.g. because it provides the console UART. Add a devicetree binding to support this. Use the PCI_VENDEV() macro to encode the cell value. This is present in U-Boot but not used, so move it to the binding header-file. Signed-off-by: Simon Glass Reviewed-by: Bin Meng

firmware: ti_sci: Add support for Resoure Management at R5 SPL stage.

2021-06-11T13:48:52Z

On J721e and J7200, MCU R5 core (boot master) itself would run Device Manager (DM) Firmware and interact with TI Foundational Security (TIFS) firmware to enable DMA and such other Resource Management (RM) services. So, during R5 SPL stage there is no such RM service available and ti_sci driver will have to directly interact with TIFS using DM to DMSC channels to request RM resources. Therefore add DT binding and driver for the same. This driver will handle Resource Management services at R5 SPL stage. Signed-off-by: Vignesh Raghavendra Signed-off-by: Lokesh Vutla Link: https://lore.kernel.org/r/20210607141753.28796-4-vigneshr@ti.com

dt-bindings: memory-controller: Add K3 AM64 DDRSS compatible

2021-05-12T11:00:52Z

Update the k3-ddrss DT binding document to include compatible for k3,am64-ddrss. Signed-off-by: Dave Gerlach