config-pin does not have the functionality necessary, especially for the PRU pins. We lack the ability to allow pull ups and pull downs with the pin functions. In general, I believe it would make more sense to allow or-ing of speed | input | up/down | enable pull | mode.
Should config-pin be changed to allow more flexibility?
config-pin is just a helper that reads these points from sysfs:
For the PRU's would it actually be useful? For pretty much for-ever,
we've had the pru output set as:
PIN_OUTPUT_PULLDOWN | INPUT_EN | MUX_MODE5
and pru input as:
PIN_INPUT | MUX_MODE6
Mark/Jason, would this make sense to extend it.. ?
For PRU pinmuxing use libpruio. It doesn’t use pre-configured settings, but generates the setting on-time. This means:
- Much faster boot time.
- Lower memory foot print.
- No restrictions in pinmux setting.
- Single source pinmuxing (all done in your code)