All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Daniel Baluta <daniel.baluta@nxp.com>
Cc: alsa-devel@alsa-project.org, shengjiu.wang@freescale.com,
	patches@opensource.wolfsonmicro.com, lgirdwood@gmail.com,
	linux-kernel@vger.kernel.org, broonie@kernel.org,
	viorel.suman@nxp.com, mihai.serban@nxp.com, tiwai@suse.com
Subject: Re: [PATCH v2 2/2] ASoC: codec: wm8960: Relax bit clock computation
Date: Tue, 21 Mar 2017 12:52:07 +0000	[thread overview]
Message-ID: <20170321125207.GX6986@localhost.localdomain> (raw)
In-Reply-To: <1490090976-25877-3-git-send-email-daniel.baluta@nxp.com>

On Tue, Mar 21, 2017 at 12:09:36PM +0200, Daniel Baluta wrote:
> WM8960 derives bit clock from sysclock using BCLKDIV[3:0] of R8
> clocking register (See WM8960 datasheet, page 71).
> 
> There are use cases, like this:
> aplay -Dhw:0,0 -r 48000 -c 1 -f S20_3LE -t raw audio48k20b_3LE1c.pcm
> 
> where no BCLKDIV applied to sysclock can give us the exact requested
> bitclk, so driver fails to configure clocking and aplay fails to run.
> 
> Fix this by relaxing bitclk computation, so that when no exact value
> can be derived from sysclk pick the closest value greater than
> expected bitclk.
> 
> Suggested-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
> ---
> Changes since v1:
> 	* use a marker to check if a match is found
> 	* didn't removed PLL as Charles suggested because there is
> 	a special PLL mode which explictly uses PLL. We could start
> 	a discussion on not using PLL when deriving bitclk, but this
> 	is to be done in another patch.
> 

Could you elaborate on this a little more am I not sure I follow
100%? There is a mode which explictly requires the PLL to be used
(WM8960_SYSCLK_PLL) but in that case your wm8960_configure_sysclk
code will not be called so I don't see what is causing that to have
an effect on this patch?

Thanks,
Charles

WARNING: multiple messages have this Message-ID (diff)
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Daniel Baluta <daniel.baluta@nxp.com>
Cc: <lgirdwood@gmail.com>, <broonie@kernel.org>, <tiwai@suse.com>,
	<patches@opensource.wolfsonmicro.com>,
	<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
	<shengjiu.wang@freescale.com>, <mihai.serban@nxp.com>,
	<viorel.suman@nxp.com>
Subject: Re: [PATCH v2 2/2] ASoC: codec: wm8960: Relax bit clock computation
Date: Tue, 21 Mar 2017 12:52:07 +0000	[thread overview]
Message-ID: <20170321125207.GX6986@localhost.localdomain> (raw)
In-Reply-To: <1490090976-25877-3-git-send-email-daniel.baluta@nxp.com>

On Tue, Mar 21, 2017 at 12:09:36PM +0200, Daniel Baluta wrote:
> WM8960 derives bit clock from sysclock using BCLKDIV[3:0] of R8
> clocking register (See WM8960 datasheet, page 71).
> 
> There are use cases, like this:
> aplay -Dhw:0,0 -r 48000 -c 1 -f S20_3LE -t raw audio48k20b_3LE1c.pcm
> 
> where no BCLKDIV applied to sysclock can give us the exact requested
> bitclk, so driver fails to configure clocking and aplay fails to run.
> 
> Fix this by relaxing bitclk computation, so that when no exact value
> can be derived from sysclk pick the closest value greater than
> expected bitclk.
> 
> Suggested-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
> ---
> Changes since v1:
> 	* use a marker to check if a match is found
> 	* didn't removed PLL as Charles suggested because there is
> 	a special PLL mode which explictly uses PLL. We could start
> 	a discussion on not using PLL when deriving bitclk, but this
> 	is to be done in another patch.
> 

Could you elaborate on this a little more am I not sure I follow
100%? There is a mode which explictly requires the PLL to be used
(WM8960_SYSCLK_PLL) but in that case your wm8960_configure_sysclk
code will not be called so I don't see what is causing that to have
an effect on this patch?

Thanks,
Charles

  reply	other threads:[~2017-03-21 12:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 10:09 [PATCH v2 0/2] wm8960: Relax bit clock computation Daniel Baluta
2017-03-21 10:09 ` Daniel Baluta
2017-03-21 10:09 ` [PATCH v2 1/2] ASoC: codec: wm8960: Refactor sysclk freq search Daniel Baluta
2017-03-21 10:09   ` Daniel Baluta
2017-03-21 12:43   ` Charles Keepax
2017-03-21 12:43     ` Charles Keepax
2017-03-24 19:16   ` Applied "ASoC: codec: wm8960: Refactor sysclk freq search" to the asoc tree Mark Brown
2017-03-24 19:16     ` Mark Brown
2017-03-21 10:09 ` [PATCH v2 2/2] ASoC: codec: wm8960: Relax bit clock computation Daniel Baluta
2017-03-21 10:09   ` Daniel Baluta
2017-03-21 12:52   ` Charles Keepax [this message]
2017-03-21 12:52     ` Charles Keepax
2017-03-21 14:05     ` Daniel Baluta
2017-03-21 14:05       ` [alsa-devel] " Daniel Baluta
2017-03-21 14:20       ` Charles Keepax
2017-03-21 14:20         ` [alsa-devel] " Charles Keepax
2017-03-21 14:25         ` Daniel Baluta
2017-03-21 14:25           ` [alsa-devel] " Daniel Baluta
2017-03-21 14:31           ` Charles Keepax
2017-03-21 14:31             ` [alsa-devel] " Charles Keepax

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=20170321125207.GX6986@localhost.localdomain \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.serban@nxp.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=shengjiu.wang@freescale.com \
    --cc=tiwai@suse.com \
    --cc=viorel.suman@nxp.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.