Well, that is what I meant by mode, which is pinmux Mode1 through Mode7, plus the pullup, pulldown, direction, etc. Rather than starting from scratch, I think it would be simple to add this to gpiolib. Also, gpiolib has uses debugfs to display info about the gpio pins. Look at /sys/kernel/debug/gpio. Not sure how you would implement this in a generic way so that it would apply to other architectures. Without this, I don’t believe it will be accepted by mainline.
Regards, John > On Mar 3, 2016, at 10:25 PM, TJF <jeli.freih...@gmail.com> wrote: > > 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 > <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 > <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 beagleboard+unsubscr...@googlegroups.com > <mailto:beagleboard+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
