Hi Simon,
On Tue, Jul 12, 2016 at 10:02:43AM -0600, Simon Glass wrote:
+Stephen
Hi Benjamin,
On 20 June 2016 at 12:26, Benjamin Tietz uboot@dresden.micronet24.de wrote:
From: Benjamin Tietz benjamin@micronet24.de
Currently, clocks can be enabled, only. To be feature-complete - and allow a bit of power-saving in applications - disabling a clock should be possible, too.
This extend the API of the DM clock driver to allow a clock to be disabled.
The corresponding operation is optional for not breaking existing drivers.
What does this mean? I can't see how it is optional.
What was meant was: If a driver can't handling disabling of peripherals, the request will be ignored silently - I think, the expected behaviour.
Also please can you rebase to mainline and resend, as the API has changed (sorry).
... including a clk_disable. So at least this patch can be dropped.
regards Benjamin