Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: alsa-devel@alsa-project.org
Cc: peter.ujfalusi@ti.com, liam.r.girdwood@linux.intel.com,
	broonie@kernel.org, Jyri Sarha <jsarha@ti.com>
Subject: [PATCH v2 0/3] Calculate BCLK using TDM slots and remove channels rule
Date: Thu, 23 Apr 2015 16:16:03 +0300	[thread overview]
Message-ID: <cover.1429794271.git.jsarha@ti.com> (raw)

The first and the last patch are excatly the same as in the first
series, but in the middle thee is a new patch to constraint out
unsupported channel counts in multiple serializers case.

- The first patch is a bug fix and also fixes Dan Carpenter's concern
  about stack usage in davinci_mcasp_hw_rule_channels()

- The second is also a bug fix, even thou the bug has existed in the
  dirver for a very long time. It is just that nobody has used
  multiple serializers before.

- The last patch is a simple optimization

All the patches have been tested are internally reviewed.

Jyri Sarha (3):
  ASoC: davinci-mcasp: Calculate BCLK using TDM slots and remove
    channels rule
  ASoC: davinci-mcasp: Channel count constraints for multi-serializer
    case
  ASoC: davinci-macsp: Optimize implicit BLCK sample-rate rule

 sound/soc/davinci/davinci-mcasp.c | 167 ++++++++++++++++++++------------------
 1 file changed, 90 insertions(+), 77 deletions(-)

-- 
1.9.1

             reply	other threads:[~2015-04-23 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 13:16 Jyri Sarha [this message]
2015-04-23 13:16 ` [PATCH v2 1/3] ASoC: davinci-mcasp: Calculate BCLK using TDM slots and remove channels rule Jyri Sarha
2015-04-23 13:16 ` [PATCH v2 2/3] ASoC: davinci-mcasp: Channel count constraints for multi-serializer case Jyri Sarha
2015-04-23 13:16 ` [PATCH v2 3/3] ASoC: davinci-macsp: Optimize implicit BLCK sample-rate rule Jyri Sarha
2015-04-30 19:47 ` [PATCH v2 0/3] Calculate BCLK using TDM slots and remove channels rule Mark Brown

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=cover.1429794271.git.jsarha@ti.com \
    --to=jsarha@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=peter.ujfalusi@ti.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