On 04/19/2014 05:25 PM, Joachim Eastwood wrote:
Hello,
Playing around with an old OMAP pwm driver from NeilBrown. I get the
following warning:
[ 0.979522] omap-pwm omap-pwm.14: omap_dm_timer_set_load
[ 0.979553] [ cut here ]
[ 0.979583] WARNING: CPU: 0 PID: 0 at
On 21 April 2014 17:40, Joel Fernandes jo...@ti.com wrote:
On 04/19/2014 05:25 PM, Joachim Eastwood wrote:
Hello,
Playing around with an old OMAP pwm driver from NeilBrown. I get the
following warning:
[ 0.979522] omap-pwm omap-pwm.14: omap_dm_timer_set_load
[ 0.979553] [ cut
On 04/21/2014 11:36 AM, Joel Fernandes wrote:
On 04/21/2014 10:57 AM, Joachim Eastwood wrote:
On 21 April 2014 17:40, Joel Fernandes jo...@ti.com wrote:
On 04/19/2014 05:25 PM, Joachim Eastwood wrote:
Hello,
Playing around with an old OMAP pwm driver from NeilBrown. I get the
following
On 21 April 2014 18:36, Joel Fernandes jo...@ti.com wrote:
On 04/21/2014 10:57 AM, Joachim Eastwood wrote:
On 21 April 2014 17:40, Joel Fernandes jo...@ti.com wrote:
On 04/19/2014 05:25 PM, Joachim Eastwood wrote:
Hello,
Playing around with an old OMAP pwm driver from NeilBrown. I get the
On 04/21/2014 12:04 PM, Joachim Eastwood wrote:
[..]
Note that the warning I got might be cause by the pwm-omap and it's
use of dmtimer api. I will investigate further.
But either way add a check to enable/disable is a good idea.
Sure, I added the check. The patch depends on a few other
Hello,
Playing around with an old OMAP pwm driver from NeilBrown. I get the
following warning:
[ 0.979522] omap-pwm omap-pwm.14: omap_dm_timer_set_load
[ 0.979553] [ cut here ]
[ 0.979583] WARNING: CPU: 0 PID: 0 at drivers/bus/omap_l3_noc.c:113
