From: Mark Brown <broonie@sirena.org.uk>
To: Sedji Gaouaou <sedji.gaouaou@atmel.com>
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: Thu, 2 Oct 2008 19:12:12 +0100 [thread overview]
Message-ID: <20081002181211.GA3345@sirena.org.uk> (raw)
In-Reply-To: <48E4F025.80907@atmel.com>
On Thu, Oct 02, 2008 at 06:00:37PM +0200, Sedji Gaouaou wrote:
> Yes my mistake!! I will change change right now. Nevertheless I don't
> even have a AVR compiler so I can't really test the AVR code....
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
handle both but I've no familiarity with either architecture.
CCing in Haavard Skinnemoen for AVR32 advice: Haavard, Sedji is submitting
patches which unify the audio support for AT91 and AVR32.
> Ok, no worries. I will create:
> a patch that contains the atmel_ssc_dai.c and .h file,
> a patch for the atmel-pcm.c/.h files
> a patch playback_wm8510.c and sam9g20_wm8731.c files.
> a patch for the Makefile and the Kconfig.
> Is that ok?
That's certainly good for review. We can always squash the patches down
when they go to git in order to try to preserve the history. No need to
keep reposting the patch to remove the old drivers, either (unless you
switch to using git format-patch -M to show the code moving around).
next prev parent reply other threads:[~2008-10-02 18:12 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 [this message]
2008-10-03 12:44 ` Sedji Gaouaou
2008-10-03 13:14 ` Mark Brown
2008-10-03 14:22 ` Sedji Gaouaou
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=20081002181211.GA3345@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=fmandarino@endrelia.com \
--cc=geoffrey@pager.net \
--cc=hskinnemoen@atmel.com \
--cc=sedji.gaouaou@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 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.