On Fri, Dec 29, 2017 at 8:22 AM, Henner Zeller <[email protected]> wrote: > On 27 December 2017 at 13:48, Leonardo Romor <[email protected]> wrote: >> Hello, >> >> could someone explain me why running this code freezes the kernel? >> >> https://gist.github.com/lromor/e303c88cfb8a065d411f2ba0bc52324b > > 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.
Let's see, your mmap'ing a clock that "was" being handled by the kernel's pwm subsystem, and now the system freezes... Well, stop mmap'ing or disable the pwm driver.. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYioMBP4g8BbPrCwbVzFmYPX%2BE5eWkaCZaiAUOeeWkpbOQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
