alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@nxp.com>
To: lgirdwood@gmail.com, broonie@kernel.org, tiwai@suse.com
Cc: shengjiu.wang@freescale.com, patches@opensource.wolfsonmicro.com,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	viorel.suman@nxp.com, mihai.serban@nxp.com,
	ckeepax@opensource.wolfsonmicro.com
Subject: [RFC PATCH 0/2] wm8960: Relax bit clock computation
Date: Wed, 15 Mar 2017 17:33:04 +0200	[thread overview]
Message-ID: <1489591986-6302-1-git-send-email-daniel.baluta@nxp.com> (raw)

This patch series allows running S20_3LE encoded samples on wm8960 codec.

First patch does a small refactoring of sysclk frequency search because
wm8960_configure_sysclk was getting pretty convoluted.

The second patch allows relaxing bitclock computation in the way that
if an exact bitclk couldn't be derived from sysclk it chooses the
smalles available bitclk greater than the desired bitclk.

For a better reviewing experience you can checked the squashed version
of this patches here:

http://pastebin.com/gBJ3DBSu

Note that this is a follow up of:

"ASoC: wm8960: Use physical width for bclk"

discussion archived here:

http://mailman.alsa-project.org/pipermail/alsa-devel/2017-March/118735.html

Daniel Baluta (2):
  ASoC: codec: wm8960: Refactor sysclk freq search
  ASoC: codec: wm8960: Relax bit clock computation

 sound/soc/codecs/wm8960.c | 113 +++++++++++++++++++++++++++++++++++++---------
 1 file changed, 91 insertions(+), 22 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-03-15 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 15:33 Daniel Baluta [this message]
2017-03-15 15:33 ` [RFC PATCH 1/2] ASoC: codec: wm8960: Refactor sysclk freq search Daniel Baluta
2017-03-15 16:22   ` Charles Keepax
2017-03-16  8:49     ` Daniel Baluta
2017-03-15 15:33 ` [RFC PATCH 2/2] ASoC: codec: wm8960: Relax bit clock computation Daniel Baluta
2017-03-15 17:17   ` Charles Keepax
2017-03-16  9:34     ` Daniel Baluta

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=1489591986-6302-1-git-send-email-daniel.baluta@nxp.com \
    --to=daniel.baluta@nxp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).