From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] Add AC'97 driver for AT91SAM9263ek atmel board.
Date: Thu, 02 Oct 2008 11:45:54 +0200 [thread overview]
Message-ID: <48E49852.2010504@atmel.com> (raw)
In-Reply-To: <20081002092430.GB2848@sirena.org.uk>
Hi,
Mark Brown a écrit :
> On Thu, Oct 02, 2008 at 11:19:48AM +0200, Takashi Iwai wrote:
>> Sedji Gaouaou wrote:
>>> Sedji Gaouaou a ?crit :
>
>>> When I was writing this patch I was wondering if it should actually be
>>> in the sound/arm directory or in a sound/soc/atmel directory?
>
>> sound/arm looks correct unless the driver is based on the ASoC
>> framework.
>
> Indeed.
>
> If you look at pxa2xx-ac97 you'll see that for that there's actually two
> drivers (both of which now share most of the actual hardware access code
> thanks to some good work by Dmitry Baryshkov), one for the non-ASoC AC97
> framework and one for use within ASoC. Both can be useful, though the
> ASoC one is only useful if people design boards which can make use of
> the extra features it provides.
>
Should I provide the same thing?
This driver is not based on the ASoC.
Nevertheless I can see that there is a ac97 driver in sound/soc/codec,
so should I do the same as pxa, I mean create 2 drivers?
next prev parent reply other threads:[~2008-10-02 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 16:24 [PATCH] Add AC'97 driver for AT91SAM9263ek atmel board Sedji Gaouaou
2008-10-02 8:51 ` Sedji Gaouaou
2008-10-02 9:19 ` Takashi Iwai
2008-10-02 9:24 ` Mark Brown
2008-10-02 9:45 ` Sedji Gaouaou [this message]
2008-10-02 9:52 ` Mark Brown
2008-10-02 9:53 ` Takashi Iwai
2009-01-05 17:39 ` 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=48E49852.2010504@atmel.com \
--to=sedji.gaouaou@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=tiwai@suse.de \
/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.