On Wed, May 11, 2016 at 10:28:12PM +0200, Peter Rosin wrote:
> On 2016-05-11 17:29, Mark Brown wrote:
> > On Tue, May 10, 2016 at 05:06:37PM +0200, Peter Rosin wrote:
> >> + if (master) {
> >> + switch (max9860->pclk_rate) {
> >> + case 12000000:
> >> + sysclk = MAX9860_FREQ_12MHZ;
> >> + break;
> >> + case 13000000:
> >> + sysclk = MAX9860_FREQ_13MHZ;
> >> + break;
> >> + case 19200000:
> >> + sysclk = MAX9860_FREQ_19_2MHZ;
> >> + break;
> >> + }
> > What if we have another PCLK rate?
> In that case the sysclk variable will remain cleared (0) and the
> code that follows will trigger the PLL section with the N divider
> for clock master mode (that mode is always used in clock slave mode).
The code needs to make it clear that this is an intentional fallthrough,
an explicit default case would help a lot.
> > We didn't go into cache only mode on suspend? I'd also expect to see
> > the regulators disabled over suspend and some system PM ops.
> Ooops, that is a leftover, and I think it can be removed. However, your
> comment suggests that I have misunderstood the workings of
> SND_SOC_DAPM_REGULATOR_SUPPLY. I thought dapm would take care of the
> regulators (and the clocks for SND_SOC_DAPM_CLOCK_SUPPLY) so that
> disabling regulators over suspend was handled by the asoc core?
It will disable the regulators but that's not going to end well if
you're including core supplies required to maintain the register map,
it'll disable before runtime suspend and enable after runtime resume.
The regulator supply widget is intended for supplies that power
particular components on the CODEC.
> >> + ret = clk_prepare_enable(mclk);
> >> + if (ret) {
> >> + dev_err(dev, "Failed to enable MCLK: %d\n", ret);
> >> + clk_put(mclk);
> >> + return ret;
> >> + }
> >> + *mclk_rate = clk_get_rate(mclk);
> >> + clk_disable_unprepare(mclk);
> > This is definitely confused too. Enabling the clock to read the
> > programmed frequency is at best odd, and obviously if we do get the rate
> > this will ensure that MCLK is disabled which probably isn't ideal.
> This is the same situation as for the regulators, I thought dapm
> handled it and would prep/enable clocks when they were needed?
That still doesn't explain the bouncing on and off here.
Attachment:
signature.asc
Description: PGP signature
