On 09/07, Vinod Koul wrote:
On Thu, Sep 07, 2017 at 07:59:24PM +0530, Subhransu S. Prusty wrote:
From: Jaikrishna Nemallapudi jaikrishnax.nemallapudi@intel.com
For certain platforms it is required to start the clocks (mclk/sclk/fs) before the stream start. Example: for few chrome systems, codec needs the mclk/sclk to be enabled early for a successful clock synchronization and for few IVI platforms, clock need to be enabled at boot and should be ON always.
This patch creates virtual clock driver, which allows the machine driver to use the clock interface to send IPCs to DSP to enable/disable the clocks.
Mark, Michael, Stephen,
So this one adds a 'virtual' clock driver for audio clocks (mclk, bclk...) and we have DSP configuring them. The SW (driver) sends messages to DSP for controlling these clocks, that is why we decided to keep this in ASoC, do let us know if that is okay.
I know there's a v2 and I'm replying here but this is fine from clk perspective. I tend to think of it as a "remote" driver instead where the clk control is done by a non-linux processor or "remote" processor, in this case the DSP. I'll ack v2.