From: Ryan Mallon <ryan@bluewatersys.com>
To: linux-arm-kernel@lists.infradead.org
Cc: john.cooper@third-harmonic.com, alsa-devel@alsa-project.org,
broonie@opensource.wolfsonmicro.com, chasedouglas@gmail.com,
Ryan Mallon <ryan@bluewatersys.com>,
r&d4@dave-tech.it, hartleys@visionengravers.com,
dhuggins@cs.cmu.edu, buytenh@wantstofly.org, lrg@slimlogic.co.uk
Subject: [RFC PATCH v2 0/3] ep93xx i2s audio
Date: Wed, 26 May 2010 17:09:45 +1200 [thread overview]
Message-ID: <1274850588-30460-1-git-send-email-ryan@bluewatersys.com> (raw)
The following patch series adds support for i2s audio on the ep93xx,
with the Snapper CL15 used as an example implementation.
I have created psuedo clocks for sclk and lrclk as suggested by
Hartley/Mark. This moves the sdiv/lrdiv calculation into
ep93xx_i2s_hw_parms. The ep93xx documentation implies that lrclk is
gated for unused bits (ie if lrdiv > word length). If this is true for
all ep93xx i2s setups then the lrclk/sclk's could be replaced by a
single audio rate clock.
I have fixed the enabling/disabling of the i2s peripheral, which
corrects the problem I was having with playback sometimes resulting in
noise.
I have also made a number of changes suggested from the first round of
patches.
Ryan Mallon (3):
ep93xx i2s audio driver
ep93xx i2s core support
ep93xx i2s audio snapper cl15 support
arch/arm/mach-ep93xx/clock.c | 69 ++++-
arch/arm/mach-ep93xx/core.c | 31 ++
arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h | 10 +
arch/arm/mach-ep93xx/include/mach/platform.h | 1 +
arch/arm/mach-ep93xx/snappercl15.c | 1 +
sound/soc/Kconfig | 1 +
sound/soc/Makefile | 1 +
sound/soc/ep93xx/Kconfig | 18 +
sound/soc/ep93xx/Makefile | 11 +
sound/soc/ep93xx/ep93xx-i2s.c | 489 +++++++++++++++++++++++
sound/soc/ep93xx/ep93xx-i2s.h | 25 ++
sound/soc/ep93xx/ep93xx-pcm.c | 323 +++++++++++++++
sound/soc/ep93xx/ep93xx-pcm.h | 22 +
sound/soc/ep93xx/snappercl15.c | 143 +++++++
14 files changed, 1144 insertions(+), 1 deletions(-)
create mode 100644 sound/soc/ep93xx/Kconfig
create mode 100644 sound/soc/ep93xx/Makefile
create mode 100644 sound/soc/ep93xx/ep93xx-i2s.c
create mode 100644 sound/soc/ep93xx/ep93xx-i2s.h
create mode 100644 sound/soc/ep93xx/ep93xx-pcm.c
create mode 100644 sound/soc/ep93xx/ep93xx-pcm.h
create mode 100644 sound/soc/ep93xx/snappercl15.c
next reply other threads:[~2010-05-26 5:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 5:09 Ryan Mallon [this message]
2010-05-26 5:09 ` [RFC PATCH v2 1/3] ep93xx i2s audio driver Ryan Mallon
2010-05-26 11:07 ` Liam Girdwood
2010-05-26 11:16 ` Peter Ujfalusi
2010-05-26 12:54 ` Chase Douglas
2010-05-26 13:08 ` Lothar Waßmann
2010-05-27 2:13 ` Mark Brown
2010-05-26 5:09 ` [RFC PATCH v2 2/3] ep93xx i2s core support Ryan Mallon
2010-05-26 5:09 ` [RFC PATCH v2 3/3] ep93xx i2s audio snapper cl15 support Ryan Mallon
2010-05-26 12:59 ` [RFC PATCH v2 0/3] ep93xx i2s audio Chase Douglas
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=1274850588-30460-1-git-send-email-ryan@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=buytenh@wantstofly.org \
--cc=chasedouglas@gmail.com \
--cc=dhuggins@cs.cmu.edu \
--cc=hartleys@visionengravers.com \
--cc=john.cooper@third-harmonic.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--cc=r&d4@dave-tech.it \
/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).