Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Jaroslav Kysela <perex@perex.cz>
Subject: [PATCH 0/7] Kirkwood ASoC updates
Date: Thu, 26 Jun 2014 15:22:31 +0100	[thread overview]
Message-ID: <20140626142231.GR32514@n2100.arm.linux.org.uk> (raw)

Mark,

Here are a set of patches I've had for a while as part of my DPCM work.
I think it's worth getting these merged.

The first patch fixes a bug at ASoC level with debugfs handling - it is
not permitted to create more than one debugfs directory with the same
name in the same parent directory - and this can happen when the dummy
platform and codec are used.

The second patch adds a helper definition to handle both I2S and SPDIF
bits in the RECCTL register in the same way that we already do with the
PLAYCTL register.

Patch 3 fixes the RECCTL enable masking - we would accumulate enable bits
but never clear any of them.

Patch 4 makes the driver's handling of the PLAYCTL register slightly more
conformant to the documentation - which requires that the appropriate mute
bits are set while the respective output interface is disabled.

Patch 5 updates my previous attempt to properly fix this.  The previous
attempt did stop things going wrong from the hardware perspective, but
we are left with the occasional stuck-busy.  Although that was harmless,
this patch stops this occuring in addition to the previous fix.

Patch 6 lifts some of the driver restrictions on the period size and
number of periods - there's no reason to restrict these values, so
let's give userspace more flexibility.

Patch 7 adds NO_PERIOD_WAKEUP support for kirkwood, permitting
interrupt-less operation.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

             reply	other threads:[~2014-06-26 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 14:22 Russell King - ARM Linux [this message]
2014-06-26 14:22 ` [PATCH 1/7] ASoC: fix debugfs directory creation bug Russell King
2014-06-27  2:45   ` Lars-Peter Clausen
2014-06-28 12:46     ` Mark Brown
2014-06-26 14:22 ` [PATCH 2/7] ASoC: kirkwood-i2s: provide helper KIRKWOOD_RECCTL_ENABLE_MASK definition Russell King
2014-06-26 14:23 ` [PATCH 3/7] ASoC: kirkwood-i2s: fix RECCTL masking Russell King
2014-06-26 14:23 ` [PATCH 4/7] ASoC: kirkwood-i2s: fix mute handling Russell King
2014-06-26 14:23 ` [PATCH 5/7] ASoC: kirkwood-i2s: fix pause handling some more Russell King
2014-06-26 14:23 ` [PATCH 6/7] ASoC: kirkwood: allow smaller audio periods and smaller number of periods Russell King
2014-06-26 14:23 ` [PATCH 7/7] ASoC: kirkwood: implement NO_PERIOD_WAKEUP support Russell King
2014-06-26 18:10 ` [PATCH 0/7] Kirkwood ASoC updates Andrew Lunn
2014-06-26 18:22   ` Russell King - ARM Linux
2014-06-28 12:47 ` 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=20140626142231.GR32514@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    /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