u-boot.git/doc/device-tree-bindings/pinctrl, branch v2022.04

k210: use the board vendor name rather than the marketing name

2022-03-15T09:43:11Z

"kendryte" is the marketing name for the K210 RISC-V SoC produced by Canaan Inc. Rather than "kendryte,k210", use the usual "canaan,k210" vendor,SoC compatibility string format in the device tree files and use the SoC name for file names. With these changes, the device tree files are more in sync with the Linux kernel DTS and drivers, making uboot device tree usable by the kernel. Signed-off-by: Damien Le Moal Signed-off-by: Niklas Cassel Reviewed-by: Leo Yu-Chi Liang

pinctrl: Add Apple pinctrl driver

2021-11-17T22:04:58Z

This driver supports both pin muxing and GPIO support for the pin control logic found on Apple SoCs. Signed-off-by: Mark Kettenis

WS cleanup: remove SPACE(s) followed by TAB

2021-09-30T13:08:16Z

Signed-off-by: Wolfgang Denk

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

dt-bindings: pinctrl: at91-pio4: add slew-rate

2021-03-02T07:28:33Z

Document slew-rate DT binding for SAMA7G5. Signed-off-by: Claudiu Beznea

dt-bindings: pinctrl: at91-pio4: add property for drive strength

2021-01-22T13:09:59Z

Add drive strength property which is equivalent with the one in Linux Signed-off-by: Eugen Hristev

pinctrl: k210: Rename power domains to match datasheet

2020-11-17T07:09:28Z

This renames power domains to match the names on the k210 datasheet. Signed-off-by: Sean Anderson Reported-by: Damien Le Moal Reviewed-by: Rick Chen

pinctrl: Add support for Kendryte K210 FPIOA

2020-10-08T15:42:36Z

The Fully-Programmable Input/Output Array (FPIOA) device controls pin multiplexing on the K210. The FPIOA can remap any supported function to any multifunctional IO pin. It can also perform basic GPIO functions, such as reading the current value of a pin. However, GPIO functionality remains largely unimplemented (in favor of the dedicated GPIO peripherals). Signed-off-by: Sean Anderson Reviewed-by: Simon Glass

pinctrl: Add pinmux property support to pinctrl-generic

2020-10-08T15:42:36Z

The pinmux property allows for smaller and more compact device trees, especially when there are many pins which need to be assigned individually. Instead of specifying an array of strings to be parsed as pins and a function property, the pinmux property contains an array of integers representing pinmux groups. A pinmux group consists of the pin identifier and mux settings represented as a single integer or an array of integers. Each individual pin controller driver specifies the exact format of a pinmux group. As specified in the Linux documentation, a pinmux group may be multiple integers long. However, no existing drivers use multi-integer pinmux groups, so I have chosen to omit this feature. This makes the implementation easier, since there is no need to allocate a buffer to do endian conversions. Support for the pinmux property is done differently than in Linux. As far as I can tell, inversion of control is used when implementing support for the pins and groups properties to avoid allocating. This results in some duplication of effort; every property in a config node is parsed once for each pin in that node. This is not such an overhead with pins and groups properties, since having multiple pins in one config node does not occur especially often. However, the semantics of the pinmux property make such a configuration much more appealing. A future patch could parse all config properties at once and store them in an array. This would make it easier to create drivers which do not function solely as callbacks from pinctrl-generic. This commit increases the size of the sandbox build by approximately 48 bytes. However, it also decreases the size of the K210 device tree by 2 KiB from the previous version of this series. The documentation has been updated from the last Linux commit before it was split off into yaml files. Signed-off-by: Sean Anderson Reviewed-by: Simon Glass