On 1/27/2014 11:36 PM, William Hermans wrote:
> Ok, this is what I was thinking was the case, but at the same time I was
> hoping it was for 3.12.x . . .

It should work with little or no modification with 3.12 once the cape
manager gets fixed up.  It would probably work if manually appended to
the system device tree instead of compiling it as an overlay.  The
pinmux helper and gpio-of-helper needed are both in the mainline kernel,
it's just the cape manager that's not.

> Did i read your original post correctly in that you plan on documenting
> this fully ( eventually ) ?

Well, I'm not sure about "fully", but there will be a lot more
documentation than what exists now (virtually zero).  I'm mostly still
mulling over project names, so I can start a repository on github.

I'm currently leaning towards 'dt-bone-universal', but I'm open to
suggestions.

I intend to at least provide a list of the available devices, a chart
indicating which pins support which modes, and a shell script or other
runnable program that allows configuration of GPIO pins without
consulting a bunch of tables...probably something like:

  setup-gpio P8_15 high    # P8 pin 15 is GPIO output driving high
  setup-gpio P8_16 pruin   # P8 pin 16 is a dedicated PRU input

...instead of what you currently have to do, which is:

  echo gpio > /sys/devices/ocp.*/P8_15_pinmux.*/state
  echo high > /sys/class/gpio/gpio47/direction

  echo pruin > /sys/devices/ocp.*/P8_16_pinmux.*/state

-- 
Charles Steinkuehler
[email protected]

-- 
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