Re: Pinmux bindings proposal V2

From: Shawn Guo
Date: Fri Feb 03 2012 - 08:50:15 EST

On Fri, Feb 03, 2012 at 04:07:23AM +0800, Dong Aisheng wrote:
> However If IMX uses the data model i described above, the binding is
> then a little different from tegra. that means we may need to change
> to let each soc's pinctrl driver do real pinmux map parsing (maybe
> add a callback in pinctrl.ops) based on their soc specific pinctrl
> configuration node like pmx_usdhc4 above instread of let pinctrl core
> do a standard pinmux map parsing which is our target we discussed so
> long for.
Yeah, this seems a reasonable alternative to me. Pushing the pinmux_map
construction down to individual pinctrl driver, who can interpret 'mux'
property best, will relieve the pinctrl core from understanding the
property for different cases, so that we can even save the property
'mux-unit' I asked for. And doing so somehow aligns with non-dt case,
where the pinmux_map is constructed by individual pinctrl driver too
(with help from PINMUX_MAP_* macros in board file).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at