On Tue, Nov 17, 2026 at 03:53:14PM +0100, Vincent Jardin via B4 Relay wrote: > From: Vincent Jardin <[email protected]> > > The LX2160A muxes its IIC, XSPI, SDHC, UART, IRQ and EVT pads from > fields of the RCW, read-only in RCWSR12..14 of DCFG and changed at > runtime through the same fields of the override registers in its DCSR > view, which read 0 until written. > > Since commit 8a1365c7bbc1 ("arm64: dts: lx2160a: add pinmux and i2c > gpio to support bus recovery") Linux drives them with pinctrl-single on > the override registers, so its first pin state clears every other field > of the word: a board whose RCW programs a non-zero pad mux loses those > pads at the first I2C probe.
Yeah, pinctrl-single is pretty unfit for purpose here. > Add a generic Layerscape driver for the pad mux as a child of the DCFG > node. The fields and their encoding are per-SoC tables selected by > the compatible, so that other Layerscape SoCs can be added to it. > > Only the LX2160A is done: the fields of RCWSR12..14 and the EC1, EC2, > USB_EXT, GTX_CLK and SDHC1_DS ones of RCWSR27. > > Then pin states select them with the generic function and groups > properties, and every change goes through the RCW override > of fsl-guts, which reads the status register, writes the override and > waits for the status register to follow. > > Reviewed-by: Frank Li <[email protected]> > Signed-off-by: Vincent Jardin <[email protected]> > --- Reviewed-by: Vladimir Oltean <[email protected]> # HW perspective
