Thanks Leonardo to measure and put together this report of this issue
when using 4.4.91-ti-r137.
>
> It should turn on the beaglebone TIMER4.
> I have tested this code on 3.8 kernel and it works.
This currently prevents PWM to work in BeagleG in newer kernels; so it
would be good to know from some of the people familiar with the
kernel/GPIO interaction could chime in and explain what is going on
and if there is a way to work-around it or if the initialization
should be different altogether.
Thanks
Henner.
Robert Nelson
unread,
Dec 29, 2017, 9:53:28 AM12/29/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Beagle Board
Let's see, your mmap'ing a clock that "was" being handled by the
kernel's pwm subsystem, and now the system freezes...
The folder I assumed to be filled (/sys/class/pwm) when the drivers are enabled is empty.
Also:
Does the kernel manages the timer and pwm with same driver?
Thank you,
-l
Henner Zeller
unread,
Jan 5, 2018, 12:35:59 PM1/5/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Beagle Board
Ping - it would be really interesting to know if disabling the kernel
driver is simple thing that can be configured from user-space, or
maybe if there are alternatives.
So far I enjoyed that it is possible to relatively simply just read
the datasheet and set the registers, but that seems to increasingly
getting complicated with the kernel doing its own thing. Which is fine
I suppose, but is there a documentation how to use the PWM subsystem
in that case ?