All of lore.kernel.org
 help / color / mirror / Atom feed
From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] ep93xx i2s audio
Date: Wed, 19 May 2010 09:06:20 +1200	[thread overview]
Message-ID: <4BF3014C.9010001@bluewatersys.com> (raw)
In-Reply-To: <20100518182202.GB22554@sirena.org.uk>

Mark Brown wrote:
> On Tue, May 18, 2010 at 04:45:27PM +1200, Ryan Mallon wrote:
> 
>> The following patch series adds support for i2s audio on the ep93xx,
>> with the Snapper CL15 used as an example implementation. The driver is
>> basically working, but still incomplete and needs some tidy up before it
>> will be accepted for mainline. I am posting the patches to get feedback
>> from others as to how well it works on their boards and ideas to improve
>> the code.
> 
> Please do always CC the maintainers for relevant subsystems and also the
> relevant mailing lists when posting patches, even if just as RFC.  In
> this case you've done neither.

Sorry about this, I was mostly getting this out to a bunch of people who
had expressed interested in it. I should have CC'ed the alsa people
though. Thanks for your comments.

>> The following issues still exist:
>>  - The setting of SDIV/LRDIV is ugly since it requires modifying one of
>> the clock registers from the audio driver.
> 
> Clock API perhaps?

Yes, Hartley has suggested the same thing.

~Ryan

-- 
Bluewater Systems Ltd - ARM Technology Solution Centre

Ryan Mallon         		5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com         	PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com	New Zealand
Phone: +64 3 3779127		Freecall: Australia 1800 148 751
Fax:   +64 3 3779135			  USA 1800 261 2934

  reply	other threads:[~2010-05-18 21:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  4:45 [RFC PATCH 0/3] ep93xx i2s audio Ryan Mallon
2010-05-18  4:53 ` [RFC PATCH 1/3] ep93xx i2s driver Ryan Mallon
2010-05-18 12:45   ` Chase Douglas
2010-05-18 18:37     ` Mark Brown
2010-05-18 21:21     ` Ryan Mallon
2010-05-18 17:54   ` H Hartley Sweeten
2010-05-18 21:34     ` Ryan Mallon
2010-05-18 18:33   ` Mark Brown
2010-05-18  4:54 ` [RFC PATCH 2/3] ep93xx i2s core support Ryan Mallon
2010-05-18 12:46   ` Chase Douglas
2010-05-18 21:23     ` Ryan Mallon
2010-05-18 18:26   ` H Hartley Sweeten
2010-05-18  4:55 ` [RFC PATCH 3/3] ep93xx i2s snapper cl15 support Ryan Mallon
2010-05-18 12:46   ` Chase Douglas
2010-05-18 18:37   ` H Hartley Sweeten
2010-05-18 18:44   ` Mark Brown
2010-05-18 12:44 ` [RFC PATCH 0/3] ep93xx i2s audio Chase Douglas
2010-05-18 18:22 ` Mark Brown
2010-05-18 21:06   ` Ryan Mallon [this message]
2010-05-18 18:46 ` Mark Brown
2010-05-18 21:04   ` Ryan Mallon

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=4BF3014C.9010001@bluewatersys.com \
    --to=ryan@bluewatersys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.