The trouble is, I don't know what to expect. I will look and see whats
there to see if I can make sense out of it.
I looked at the universal overlay when you sent the link to it and it
seemed overwhelming because of the number of entries for each pin. Now
that I have a little more experience with it I can go back and see if I can
figure it out.
All I need to do is comment out the pins in exclusive-use section that I
don't want to use and comment out all of the entries for those pins in the
fragment. Then comment out the sections for the modes I don't want for the
pins I do want?
On Wednesday, October 8, 2014 9:27:28 AM UTC-7, Charles Steinkuehler wrote:
>
> On 10/8/2014 11:10 AM, Ray Madigan wrote:
> > After reading lots of stuff I have what I thought might work.
> >
> > Segments from my .dts
> >
> > exclusive-use =
> > "p9.25"; /* R30[7] */
> >
> >
> > fragment@0 {
> > target = <&am33xx_pinmux>;
> > __overlay__ {
> > mygpio: pinmux_mygpio{
> > pinctrl-single,pins = <
> > 0x1AC 0x25 /* P9.25 mode 5 pulldown output */
> > >;
> > };
> > };
> > };
> >
> > If I do nothing in my pru code this pin is always high even after I
> reboot
> > the bbb.
> >
> > I tried
> > CLR R30.T7
> >
> > and the pin still remained high.
> >
> > Is there something else I need to do.
>
> Browse the live device tree (/proc/device-tree) and make sure it's what
> you expect. Typically, you create a pinctrl-single,pin entry and refer
> to that in some other device. When that device is loaded, the kernel
> will implement the pinmux settings referred to.
>
> Is there some reason you're not just using config-pin and loading one of
> the universal overlays?
>
> --
> Charles Steinkuehler
> [email protected] <javascript:>
>
--
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].
For more options, visit https://groups.google.com/d/optout.
