On 20/06/18 10:31, Vinod wrote:
Here clock will be enabled twice but disable will be called only once when
count = 0.
This will make the clock always enabled. So, I think we should keep either
mutex lock or atomic variable to synchronize this.
we are using DPCM here right?
We should probably model this clk as DAPM widget so we do not need to
handle this in machine code.
--srini
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
