Re: [beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-04-03 Thread Jelena Freiherr
Hi Justin! Thanks for the info on the rt needs. Am 02.04.2017 um 20:32 schrieb Justin Pearson: > Thank you for mentioning libpruio. I don't know very much about how device > tree overlays interact with linux kernel drivers, so until I can find a > good description of that, I'm inclined to use a m

Re: [beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-04-02 Thread Justin Pearson
Hi Jelena, thanks for your message. See my inline responses: On Sun, Apr 2, 2017 at 9:39 AM, Jelena Freiherr wrote: > Am Sonntag, 2. April 2017 17:26:10 UTC+2 schrieb Justin Pearson: > > On the 3.18 kernel, I was able to control the PWM with the PRU > without needing the PRU to initialize th

Re: [beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-04-02 Thread Jelena Freiherr
Hi Justin! I just tried to answer you mail, but the google board doesn't work (once again). I try to answer from my mail client, which I never did before. Am Sonntag, 2. April 2017 17:26:10 UTC+2 schrieb Justin Pearson: > On the 3.18 kernel, I was able to control the PWM with the PRU without

Re: [beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-04-02 Thread Justin Pearson
Thank you TJF, I never would have known about that register if you hadn't mentioned it. One more question (see below): On Sat, Apr 1, 2017 at 9:20 PM, TJF wrote: > Am Samstag, 1. April 2017 22:18:30 UTC+2 schrieb Justin Pearson: >> >> Are you saying that the only way to get PWM in a 4.x kernel i

[beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-04-01 Thread TJF
Am Samstag, 1. April 2017 22:18:30 UTC+2 schrieb Justin Pearson: > > Are you saying that the only way to get PWM in a 4.x kernel is by > modifying am33xx-clocks.dtsi? > No. The kernel driver should also work (untested). But in your case (controlling the PWM subsystem by PRU code) you have to m

[beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-04-01 Thread Justin Pearson
Hi TJF, thanks for your note. Are you saying that the only way to get PWM in a 4.x kernel is by modifying am33xx-clocks.dtsi? Also, how can I verify whether the register is set correctly? Thanks, Justin On Friday, March 31, 2017 at 9:48:33 AM UTC-7, TJF wrote: > > Hi Justin! > > The initial dev

[beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-03-31 Thread TJF
Hi Justin! The initial device tree changed between kernel 3.8 and 4.x. In 4.x the Control Module register *pwmss_ctrl* (@664h) gets cleared at boot. This register can get used to sychronize several PWM subsystems. A feature that isn't supported by the kernel nor by any of it's drivers. So no re

[beagleboard] Re: Using PRU to control PWM peripheral on kernel 4.1 - DTO problem?

2017-03-30 Thread Justin Pearson
Sorry, I'm using # uname -a Linux beaglebone 4.1.12-bone-rt-r16 #3 Mon Jan 9 19:44:59 PST 2017 armv7l GNU/Linux # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.7 (jessie) Release: 8.7 Codename: jessie On Thursday, March 30, 2017 at 12:21: