Hey guys,

I had a similar scenario - I ended up writing a trivial driver with help
from the guys on #beagle
 that can be found here: https://gist.github.com/17twenty/6998348

You can diff my dtsi file against that in the kernel sources to see how it
comes together.

If you are using device tree overlays I recommend watching and reading
Derek Molloys material on it
http://derekmolloy.ie/beaglebone/beaglebone-gpio-programming-on-arm-embedded-linux/

HTH,
Nick


On 16 October 2013 20:41, Hauke E <[email protected]> wrote:

>
> Hello,
>
> we are currently working on a Beaglebone Black project and we are having
> problems with our device tree overlays. In our project we continued another
> groups work but they worked with a Beaglebone White and with an older
> kernel version where sys/kernel/debug/omap_mux was still there. We tried to
> create the same functionality with device trees. we got several sensors on
> a self made cape running and we need to set the pinmodes correctly for the
> cape.
>
> (for reference our new dts file:  http://pastebin.com/MD0LzHqX
> and the old script: http://pastebin.com/QUX7in4j)
>
> Compiling and activating our overlay works fine. (we also disabled the
> hdmi framer and other unused capes)
> But when we manually check the pinmux setting for the pins (cat
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pins)  nothing changed and the
> pinmodes from the dts aren't set.
>
> Why can't we set the pinmodes via our dts file?
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Reply via email to