Posts copied from https://groups.google.com/d/msg/beagleboard/Ie-gxRfFJTc/RyGQf1ShAgAJ:
You mean like this? > > https://www.kernel.org/doc/Documentation/gpio/sysfs.txt > > Regards, > John > ... That should read add mode feature Yes and no ... The user space aspect is what I mean. But I'm speaking about pin muxing. That is - all that GPIO stuff in your document, as well as - the ball mode feature (GPIO, CAP, PWM, ...) and - pullup /pulldown restistor settings. Instead of several folders and files in sysfs and human readable parameters, I'd like to see - a single entry that - gets opened once and can - controll all free pins by a single write access, - receiving a single parameter that is a combination of ball#/value (or register offset/value - like in the device tree source). The pins to operate on could get defined in the device tree. But it'd be better when the driver could auto-determine them (the not reserved one). In short, I'm searching for a solution to set the parameters of a device tree entry like B08_28: 08_28 {pinctrl-single,pins = <0x020 0x28>;}; at run time via sysfs. Regards, Thomas -- 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.
