u-boot.git/drivers/pinctrl, branch v2020.01-rc4

drivers: bcm283x: Set pre-location flag for OF_BOARD

2019-11-24T09:46:27Z

U-Boot support on Raspberry Pi 4 relies on the device-tree provided by the firmware. The blob does not contain the U-Boot specific pre-loc-rel properties. The result is, that the U-Boot banner is not printed. We fix this by setting the DM_FLAG_PRE_RELOC flag in the driver, if we rely on a device-tree provided by the firmware. Reported-by: Heinrich Schuchardt Signed-off-by: Matthias Brugger

pinctrl: bcm283x: Add compatible for RPi4

2019-11-24T09:46:27Z

The Raspberry Pi 4 upstream kernel device tree instroduces a new compatible for the pinctroller. Add this to the driver so that we can boot with the upstream kernel DT. Signed-off-by: Matthias Brugger

Merge tag 'u-boot-rockchip-20191118' of https://gitlab.denx.de/u-boot/custodians/u-boot-rockchip

2019-11-18T02:15:57Z

- Add support for rockchip SoC: PX30, RK3308 - Add and migrate to use common dram driver: PX30, RK3328, RK3399 - Add rk3399 board Tinker-s support - Board config update for Rock960, Rockpro64

pinctrl: rockchip: add px30 pinctrl driver

2019-11-17T09:23:04Z

Add the necessary glue code to allow pinctrl setting on px30 socs. Signed-off-by: David Wu Signed-off-by: Heiko Stuebner Reviewed-by: Kever Yang

pinctrol: dm: remove the function pinctrl_decode_pin_config

2019-11-14T13:09:34Z

Remove the pinctrl_decode_pin_config() API, because this function is unused and not compatible with livetree (it uses fdtdec_get_bool instead of ofnode API). Signed-off-by: Patrick Delaunay Reviewed-by: Simon Glass

pinctrl: imx8m: support i.MX8MN

2019-11-05T09:27:18Z

Support i.MX8MN in imx8m pinctrl driver Signed-off-by: Peng Fan

pinctrl: add support for MediaTek MT7628

2019-10-25T15:20:44Z

This patch adds pinctrl support for mt7628, with a file for common pinmux functions and a file for mt7628 which has additional support for pinconf. Signed-off-by: Weijie Gao

dm: pinctrl: fix for introduce PINCONF_RECURSIVE option

2019-10-21T13:40:54Z

Correct the name of the define used CONFIG_IS_ENABLED which is not aligned with Kconfig name: CONFIG_$(SPL_)PINCONF_RECURSIVE. The recursive calls is conditional only for UCLASS_PINCONFIG "pinconfig" driver. It is always needed to call pinctrl_post_bind for UCLASS_PINCTRL "pinctrl", the test CONFIG_IS_ENABLED(PINCONF_RECURSIVE) need to be removed for this driver. This correct a regression introduced because the same patch is applied twice times in u-boot-dm branch: - commit e878b53a79d1 ("dm: pinctrl: introduce PINCONF_RECURSIVE option") - commit c20851b3d850 ("dm: pinctrl: introduce PINCONF_RECURSIVE option") Signed-off-by: Patrick Delaunay

pinctrl: Kconfig: remove duplicated nodes

2019-10-21T13:40:50Z

Remove the duplicated configs introduced when the same patch is applied twice times: - commit e878b53a79d1 ("dm: pinctrl: introduce PINCONF_RECURSIVE option") - commit c20851b3d850 ("dm: pinctrl: introduce PINCONF_RECURSIVE option") Signed-off-by: Patrick Delaunay

dm: pinctrl: introduce PINCONF_RECURSIVE option

2019-10-15T14:40:03Z

In the Linux pinctrl binding, the pin configuration nodes don't need to be direct children of the pin controller device (may be grandchildren for example). This behavior is managed with the pinconfig u-class which recursively bind all the sub-node of the pin controller. But for some binding (when pin configuration is only children of pin controller) that is not necessary. U-Boot can save memory and reduce the number of pinconf instance when this feature is deactivated (for arch stm32mp for example for SPL). This patch allows to control this feature with a new option CONFIG_PINCONF_RECURSIVE when it is possible for each individual pin controller device. Signed-off-by: Patrick Delaunay Reviewed-by: Simon Glass Fixed CONFIG_IF_ENABLED() condition, added __maybe_unused: Signed-off-by: Simon Glass