All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Bard liao <yung-chuan.liao@linux.intel.com>,
	broonie@kernel.org, tiwai@suse.de
Cc: liam.r.girdwood@linux.intel.com, alsa-devel@alsa-project.org,
	bard.liao@intel.com
Subject: Re: [PATCH 1/2] ASoC: Intel: sof-rt5682: add MCLK support for BYT platform
Date: Tue, 18 Jun 2019 19:49:48 +0200	[thread overview]
Message-ID: <8ee10576-6c07-c532-4142-abded850010f@linux.intel.com> (raw)
In-Reply-To: <20190618002336.5734-1-yung-chuan.liao@linux.intel.com>

On 6/18/19 2:23 AM, Bard liao wrote:
> From: Xun Zhang <xun2.zhang@intel.com>
> 
> The sof-rt5682 machine driver currently uses BCLK on BYT/Minnowboard
> platform. The MCLK signal is available since the Turbot revision, so
> enable MCLK on BYT/Minnowboard Turbot platform.

The commit message is not wrong but for more context the MCLK is enabled 
on all known BYT/CHT platforms except early MinnowBoards and Up where 
the MCLK is not available on the low-speed/HAT connector.

> 
> Signed-off-by: Xun Zhang <xun2.zhang@intel.com>
> Signed-off-by: Bard liao <yung-chuan.liao@linux.intel.com>


>   	if (sof_rt5682_quirk & SOF_RT5682_MCLK_EN) {
> +		if (sof_rt5682_quirk & SOF_RT5682_MCLK_BYTCHT_EN) {
> +			ret = clk_prepare_enable(ctx->mclk);
> +			if (ret < 0) {
> +				dev_err(rtd->dev,
> +					"could not configure MCLK state");
> +				return ret;
> +			}
> +		}

Note that we could technically fallback to using the BCLK only in the 
error case but it's an unlikely scenario which we've never seen, so

Patch 1 and 2

Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>

      parent reply	other threads:[~2019-06-18 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  0:23 [PATCH 1/2] ASoC: Intel: sof-rt5682: add MCLK support for BYT platform Bard liao
2019-06-18  0:23 ` [PATCH 2/2] ASoC: Intel: sof-rt5682: correct naming for dmic16k Bard liao
2019-06-18 17:49 ` Pierre-Louis Bossart [this message]

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=8ee10576-6c07-c532-4142-abded850010f@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=yung-chuan.liao@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.