From: Lars-Peter Clausen <lars@metafoo.de>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sound/soc/adi/axi-spdif.c: Support programmable master clock
Date: Wed, 10 Dec 2014 10:34:36 +0100 [thread overview]
Message-ID: <548813AC.1080105@metafoo.de> (raw)
In-Reply-To: <1417783029-22492-1-git-send-email-mike.looijmans@topic.nl>
On 12/05/2014 01:37 PM, Mike Looijmans wrote:
> If the master clock supports programmable rates, program it to generate
> the desired frequency. Only apply constraints when the clock is fixed.
> This allows proper clock generation for both 44100 and 48000 Hz based
> sampling rates if the platform supports it.
>
> The clock frequency must be set before enabling it. Enabling the clock
> was done in "startup", but that occurs before "hw_params" where the rate
> is known. Enabling a programmable clock without first setting a valid
> frequency may harm the system. Move the clock start to the hw_params
> routine, and keep track of whether the clock has been started, because
> shutdown may be called without having called hw_params first.
> Starting the clock and enabling the SPDIF output AFTER programming the
> dividers is a more logical order anyway.
>
> To detect if the source clock is fixed, the driver calls clk_round_rate
> for two frequencies. If the results are equal, or if the call returns
> an error, the driver assumes the clock is fixed.
>
> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
Hi,
Sorry for the delay.
[...]
>
> + /* Try to set the master clock */
> + clk_set_rate(spdif->clk_ref, rate * 128);
> +
> clkdiv = DIV_ROUND_CLOSEST(clk_get_rate(spdif->clk_ref),
> rate * 64 * 2) - 1;
> clkdiv <<= AXI_SPDIF_CTRL_CLKDIV_OFFSET;
> @@ -103,6 +108,14 @@ static int axi_spdif_hw_params(struct snd_pcm_substream *substream,
> regmap_update_bits(spdif->regmap, AXI_SPDIF_REG_CTRL,
> AXI_SPDIF_CTRL_CLKDIV_MASK, clkdiv);
>
> + ret = clk_prepare_enable(spdif->clk_ref);
I'm still not convinced this is the right place. I do see your point. But it
just feels wrong to enable the clock in hw_params. It's a bit of a dilemma.
the startup callback is to early, hw_params is the wrong place and we can't
put it in the trigger callback as the trigger callback can not sleep.
But in any way hwparmas can be called multiple times, so you need to handle
the case where the clock is already enabled.
> + if (ret)
> + return ret;
> + spdif->clk_ref_running = true;
> +
> + regmap_update_bits(spdif->regmap, AXI_SPDIF_REG_CTRL,
> + AXI_SPDIF_CTRL_TXEN, AXI_SPDIF_CTRL_TXEN);
This should probably be moved to the trigger callback though.
> +
> return 0;
> }
next prev parent reply other threads:[~2014-12-10 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 6:52 [PATCH] sound/soc/adi/axi-spdif.c: Support programmable master clock Mike Looijmans
2014-12-04 12:45 ` Lars-Peter Clausen
2014-12-04 14:18 ` Mike Looijmans
2014-12-04 16:54 ` Lars-Peter Clausen
2014-12-05 12:37 ` [PATCH v2] " Mike Looijmans
2014-12-10 9:34 ` Lars-Peter Clausen [this message]
2014-12-11 6:44 ` Mike Looijmans
2014-12-11 7:44 ` [PATCH v3] " Mike Looijmans
2014-12-18 15:07 ` Lars-Peter Clausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=548813AC.1080105@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox