linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] EP93xx: Add i2s audio support
Date: Wed, 9 Jun 2010 11:17:43 +0100	[thread overview]
Message-ID: <20100609101742.GA5618@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1275991272-30122-1-git-send-email-ryan@bluewatersys.com>

On Tue, Jun 08, 2010 at 10:01:09PM +1200, Ryan Mallon wrote:
> Repost of the i2s audio series for ep93xx. Patch 2/3 is unchanged. The
> core support has been modified to move setting of the SPOL and ORIDE
> bits of the i2sclkdiv register, as well as the i2s pin strapping
> configuration, to a new function called ep93xx_i2s_acquire which is
> called from the audio board drivers.

I've now applied both patches.  There was a trivial fixup required for
the clocks due to an add/add overlap with the SPI clock - I think it's
OK but please check.

  parent reply	other threads:[~2010-06-09 10:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 10:01 [PATCH 0/3] EP93xx: Add i2s audio support Ryan Mallon
2010-06-08 10:01 ` [PATCH 1/3] EP93xx: Add i2s core support Ryan Mallon
2010-06-08 15:01   ` H Hartley Sweeten
2010-06-08 19:27     ` Ryan Mallon
2010-06-08 23:21       ` Mark Brown
2010-06-08 23:26         ` Ryan Mallon
2010-06-08 23:29           ` Mark Brown
2010-06-08 23:32             ` Ryan Mallon
2010-06-08 23:26       ` H Hartley Sweeten
2010-06-08 10:01 ` [PATCH 2/3] EP93xx: Add i2s audio driver Ryan Mallon
2010-06-08 10:05   ` Mark Brown
2010-06-08 10:09     ` [alsa-devel] " Ryan Mallon
2010-06-08 10:24       ` Mark Brown
2010-06-08 10:01 ` [PATCH 3/3] EP93xx: Add Snapper CL15 i2s audio support Ryan Mallon
2010-06-09 10:17 ` Mark Brown [this message]
2010-06-09 21:40   ` [PATCH 0/3] EP93xx: Add " Ryan Mallon
2010-06-09 22:22     ` Mark Brown
2010-06-10 20:46       ` Ryan Mallon
2010-06-11  9:35         ` [alsa-devel] " 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=20100609101742.GA5618@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).