New Pwm

[Vido]

Changes discussed on the topic: PWM pins

1) The abstractmethod decorator from _get_pwm_duty_cycle will be dropped
So the _get_pwm_duty_cycle will have a implementation. It will hold the last set value.
If some Board can probe its hardware, then this Board should overwrite this method.

2) PwmPin will recive the "frequency||period" property;
This property can be read and write.
Each board should implement its own default values.

3) PwmOutputCapable recives a new abstractmethod _set_pwm_frequency and a _get_pwm_frequency
Each driver take care of his own _set_pwm_frequency. But _get_pwm_frequency has a default implementation (hold the last set value). If a Board has a better method, this should be overwritten.

[coveralls]

Coverage increased (+1.33%) when pulling 72ed3e0 on Vido:new_pwm into b448d5e on garoa:master.

[Vido]

Now, we should do some onboard testing.

[ramalho]

Thanks, @Vido !

[ramalho]

I merged your pull request. Thanks, @Vido!

Wrapping up my book in the next few weeks. Then we can have a sprint!

Cheers,

Luciano

On Fri, Jan 16, 2015 at 10:08 AM, Lucas Vido notifications@github.com
wrote:

Now, we should make some onboard testing.

—
Reply to this email directly or view it on GitHub
https://github.com/garoa/pingo/pull/67#issuecomment-70245209.

Luciano Ramalho
Twitter: @ramalhoorg

Professor em: http://python.pro.br
Twitter: @pythonprobr