On Fri, Oct 19, 2018 at 11:50 AM Charles Keepax
<ckeepax@xxxxxxxxxxxxxxxxxxxxx> wrote:
> + gf-aif2-txdat, usb-aif1, usb-aif2, adat-aif, soundcard-aif,
> +
> + - aif-master : Specifies that an AIF group will be used as a master
> + interface (either this or aif-slave is required if a group is
> + being muxed to an AIF)
> + - aif-slave : Specifies that an AIF group will be used as a slave
> + interface (either this or aif-master is required if a group is
> + being muxed to an AIF)
This is not properly described as pin config parameters, but that is how
they are used in the driver. Please describe that this is supposed to
augment the pin config of the pins.
But I think it looks bogus. If the pins are already mixed to groups
like that:
> + pin-settings: pin-settings {
> + ap-aif {
> + aif-slave;
> + groups = "gf-aif1";
> + function = "codec-aif3";
> + };
> + codec-aif {
> + aif-master;
> + groups = "codec-aif3";
> + function = "gf-aif1";
> + };
> + };
OK so what the "special properties" above indicates is really the
direction of the pins, whether out (master) or in (slave".
Just use the standard bool pin config properties:
input-enable;
output-enable;
Reference
Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
For this. If you want users to see that this is master and slave,
just /* Write a comment */ in the device tree.
Yours,
Linus Walleij
