On Thu, Apr 27, 2017 at 7:16 PM, William Hermans <yyrk...@gmail.com> wrote: > > > On Thu, Apr 27, 2017 at 5:06 PM, Robert Nelson <robertcnel...@gmail.com> > wrote: >> >> It's a little more then that, the first 0 comes from parent: >> >> /sys/class/pwm/pwmchip0/pwm-0:0 >> >> /sys/class/pwm/pwmchipA/pwm-A:B >> > > Right, with my implementation as it sits. pwm(x, y) where pwmchipx, -> pwmy. > x being the pwmchip numerical number, y being the actual pwm channel( 0 or 1 > ) in relation to that pwmchip. So if I passed in something like pwm(0, 0), I > could use the first zero as the pwmchipx number, and then use both numbers > to build the channel y number . . .javascript makes this really easy, almost > too easy. > > It's pretty awesome this will be fixed though. So when all said and done, > this could be fixed by installing a new kernel, without contaminating the > rest of the system. right ? I'm kind of cringing at the idea of a kernel > change right now, I have everything exactly how I want it :/
it's a pretty small patch: https://patchwork.kernel.org/patch/9177249/raw/ Documentation/pwm.txt | 6 ++++-- drivers/pwm/sysfs.c | 15 ++++++++++++--- 2 files changed, 16 insertions(+), 5 deletions(-) I tried pinging the author David Hsu, but his email address is disabled. Regards, -- Robert Nelson https://rcn-ee.com/ -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYg7bezyGsMFpY2N4GWV2nTbax9NgSsGY1F2L%3D1S8WM-7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
