Ok  I am slightly confused her on the pinmux signal directions.

In the BB-BONE-AUDI-02-00A0.dts file we have all pins set to inputs

fragment@0 {
        target = <&am33xx_pinmux>;
        __overlay__ {
            bone_audio_cape_audio_pins: pinmux_bone_audio_cape_audio_pins {
                pinctrl-single,pins = <
                    0x190 (PIN_INPUT_PULLDOWN | MUX_MODE0)    /*
mcasp0_aclkx.mcasp0_aclkx */
                    0x194 (PIN_INPUT_PULLDOWN | MUX_MODE0)    /*
mcasp0_fsx.mcasp0_fsx, INPUT */
                    0x198 (PIN_INPUT_PULLDOWN | MUX_MODE0)    /*
mcasp0_axr0.mcasp0_axr0 */
                    0x19c (PIN_INPUT_PULLDOWN | MUX_MODE2)    /*
mcasp0_ahclkr.mcasp0_axr2 */
                    0x1ac (PIN_INPUT_PULLDOWN | MUX_MODE0)    /*
MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
                >;
            };
        };
    };

Am i missing something here ? All pins should be outputs except the
audio input on axr0.mcasp0 which should be an input.

On the UARTS the signal directions are correct.

Is there some black magic that i am missing ?


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/89a7327f-23fc-3b59-958a-1d4b741575c9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to