Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, Geoffrey Wossum <geoffrey@pager.net>,
	Haavard Skinnemoen <hskinnemoen@atmel.com>,
	Frank Mandarino <fmandarino@endrelia.com>
Subject: Re: [PATCH]ASoC: Create a common directory for AVR32 and ARM9 atmel boards.
Date: Fri, 03 Oct 2008 16:22:01 +0200	[thread overview]
Message-ID: <48E62A89.8070803@atmel.com> (raw)
In-Reply-To: <20081003131411.GC26035@sirena.org.uk>

Mark Brown a écrit :
> On Fri, Oct 03, 2008 at 02:44:43PM +0200, Sedji Gaouaou wrote:
> 
>>> Ah, right.  While I understand that the hardware is pretty much identical
>>> are you sure that the APIs for accessing it are the same on both AVR32
>>> and AT91?  My understanding was that there was some work required to
> 
>> Actually I based my patch on the at32-pcm and at32-ssc files which were 
>> based on at91-ssc and at91-pcm files, so I don't think there should be 
>> any differences.
> 
> Right, they're based on each other but they use different APIs to access
> the hardware - this is the most substantial difference between them.
> Are you sure that the API you have chosen to use is availiable for both
> architectures?  It's possible that it is but there's no mention of this
> issue in your patch description and I'd like to confirm.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 
If you are talking about the API to access ssc(ssc_writel and 
ssc_readl), it was basically why I needed a new driver in the first 
place. Indeed we wanted to use the same API across all atmel platforms.

  reply	other threads:[~2008-10-03 14:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02  7:50 [PATCH]ASoC: Create a common directory for AVR32 and ARM9 atmel boards Sedji Gaouaou
2008-10-02 15:07 ` Mark Brown
2008-10-02 16:00   ` Sedji Gaouaou
2008-10-02 18:12     ` Mark Brown
2008-10-03 12:44       ` Sedji Gaouaou
2008-10-03 13:14         ` Mark Brown
2008-10-03 14:22           ` Sedji Gaouaou [this message]
2008-10-03 14:35             ` Mark Brown
2008-10-03 14:39               ` Sedji Gaouaou
2008-10-03 14:41               ` Geoffrey Wossum
2008-10-03 14:49               ` Haavard Skinnemoen
2008-10-03 14:51                 ` Sedji Gaouaou
2008-10-03 15:06                   ` Haavard Skinnemoen
2008-10-03 15:12                     ` Sedji Gaouaou
2008-10-06 14:17                       ` Haavard Skinnemoen
2008-10-06 14:27                         ` Mark Brown
2008-10-06 14:04               ` Geoffrey Wossum
  -- strict thread matches above, loose matches on Subject: below --
2008-10-01 16:21 [PATCH] ASoC: " Sedji Gaouaou

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=48E62A89.8070803@atmel.com \
    --to=sedji.gaouaou@atmel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=fmandarino@endrelia.com \
    --cc=geoffrey@pager.net \
    --cc=hskinnemoen@atmel.com \
    /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