All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Mallon <ryan@bluewatersys.com>
To: Sergey Lapin <slapin@ossfans.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	gwossum@acm.org, Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Sedji Gaouaou <sedji.gaouaou@atmel.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC PATCH] Add combined clock support to Atmel SoC audio
Date: Tue, 07 Jun 2011 22:29:13 +1000	[thread overview]
Message-ID: <4DEE1999.70208@bluewatersys.com> (raw)
In-Reply-To: <20110607100321.GB14633@build.ihdev.net>

On 07/06/11 20:03, Sergey Lapin wrote:
> Hi, Ryan!
> 
> On Wed, Nov 24, 2010 at 11:05:11AM +1300, Ryan Mallon wrote:
>> The following patch is one that has been floating around in various
>> forms in our own internal trees for a while.
>>
>> The Atmel SSC peripheral has seperate TX and RX clocks which use
>> separate pins from the the micro. TF (frame) and TK (clock) for transmit
>> and RF and RK for receive. Not all codecs have separate frame and bit
>> clocks for transmit and receive so we want to be able to do both
>> playback and capture using a single set of pins.
>>
>> This patch introduces a combined clock mode for the Atmel SSC
>> peripheral. Which allows playback and capture to use a single set of
>> pins. Currently combined clock is only supported on the TF/TK pins (some
>> incomplete support exists for using RF/RK).
>>
>> I have tested this patch on our AT91SAM9G45 + TLV320AIC26 platform.
>> Playback and capture work individually. Simultaneous playback and
>> capture have been tested by connecting a loopback cable on the linein
>> and lineout jacks and then doing:
>>
>>   arecord -c 2 -f S16_LE -r 44100 > recording.wav &
>>   aplay 500hz_sine.wav
>>
>> This patch is posted as RFC since the approach is incomplete and a bit
>> hackish. I am mostly interested in knowing if this is a sensible
>> approach, and could be cleaned up for mainline inclusion, or if there is
>> a better way to do this.
>>
>> Signed-off-by: Ryan Mallon <ryan@bluewatersys.com>
> 
> I think it is also important to submit code, which uses it.
> If you can't do it I might try to do this in a few days.
> Also worth mentioning codec slave mode requirement for this to work.

Agreed. I don't have any hardware at the moment. I had intended to post
support for audio on the Bluewater Systems Snapper 9260 and 9G20 modules
(this patch being a precursor to that support), but I am no longer
working at Bluewater. Did you manage to get your hardware working in the
end?

I don't think the patch is ready for merging as is. It is incomplete
(though I suspect support for tx on the rx pins probably isn't needed)
and Mark also had some comments last time round: Use symmetric_rates,
replace atomic type with proper lock, etc. I think I may have done some
of this already, so can try and dig it out.

Also, this email address will cease to exist soon. Can you please use my
rmallon@gmail.com account instead. I'll have a kernel patch out soon to
fix my mail address up.

~Ryan

      reply	other threads:[~2011-06-07 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 22:05 [RFC PATCH] Add combined clock support to Atmel SoC audio Ryan Mallon
2010-11-23 23:29 ` Mark Brown
2010-11-24  4:02   ` Ryan Mallon
2010-11-24 12:58     ` Mark Brown
2011-06-07  9:51 ` Sergey Lapin
2011-06-07 10:03 ` Sergey Lapin
2011-06-07 12:29   ` Ryan Mallon [this message]

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=4DEE1999.70208@bluewatersys.com \
    --to=ryan@bluewatersys.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gwossum@acm.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=nicolas.ferre@atmel.com \
    --cc=rmallon@gmail.com \
    --cc=sedji.gaouaou@atmel.com \
    --cc=slapin@ossfans.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.