On Sat, Feb 03, 2018 at 12:47:48PM +1100, Jonathan Gray wrote: > On Sun, Jan 28, 2018 at 01:54:25PM -0500, Tom Rini wrote: > > On Tue, Jan 23, 2018 at 06:05:21PM +0100, Alexander Graf wrote: > > > > > The bcm283x family of SoCs have a GPIO controller that also acts as > > > pinctrl controller. > > > > > > This patch introduces a new pinctrl driver that can actually properly mux > > > devices into their device tree defined pin states and is now the primary > > > owner of the gpio device. The previous GPIO driver gets moved into a > > > subdevice of the pinctrl driver, bound to the same OF node. > > > > > > That way whenever a device asks for pinctrl support, it gets it > > > automatically from the pinctrl driver and GPIO support is still available > > > in the normal command line phase. > > > > > > Signed-off-by: Alexander Graf <ag...@suse.de> > > > > Applied to u-boot/master, thanks! > > It seems one of the recent commits here has broken booting on rpi_3 with > the vendor supplied device tree via efi_loader. > > last working commit seems to be: > > 8996975ff8422e07f43eb8b3b0c7ed8c2b35442f > powerpc: Drop CONFIG_WALNUT and other related dead code > > After that were > > caf2233b281c03e3e359061a3dfa537d8a25c273 > bcm283x: Add pinctrl driver > > c8a73a26d6dd9b7d489e66529fe1412425d8f2d1 > mmc: Add bcm2835 sdhost controller > > These can't easily be reverted due to other changes.
This turns out to have been efi loader changes, and is resolved by 'efi_loader: correct efi_disk_register' https://lists.denx.de/pipermail/u-boot/2018-February/320043.html Still not clear on why git bisect kept pointing at these pinctrl changes on rpi_3. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot