On Tue, Sep 16, 2014 at 11:19:28AM -0700, Nicolin Chen wrote:
So I think, if it's a shared clock, we should not define it as a rate-changeable one in the SoC level, as we might still have some SoCs provide a dedicated clock to S/PDIF so as to get the maximum range of clock support for users.
@Shawn Sorry to involve you in this topic. I'm not so sure if we can do this in the clock driver so that the clock rate would be fixed even if the driver is trying to change it. If we can, I think we may use a better solution here instead.
I tend to agree here. My first thought here is that we should have support in the clock API for constraining clocks in the clock API so we can still set the clock where there's a possibility to do that. Not trivail to implement though.