All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Austin <brian.austin@cirrus.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Cirrus Logic CS42L52 Low power codec
Date: Mon, 18 Feb 2008 08:45:49 -0600	[thread overview]
Message-ID: <1203345949.4063.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20080218143655.GE21314@rakim.wolfsonmicro.main>

I was under the impression that the ASoc v1 ties the codec to a specific
machine, and that v2 eliminates that need.  Is that a correct
assumption?


-----Original Message-----
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Brian Austin <brian.austin@cirrus.com>
Cc: alsa-devel@alsa-project.org <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] Cirrus Logic CS42L52 Low power codec
Date: Mon, 18 Feb 2008 14:36:55 +0000

On Mon, Feb 18, 2008 at 08:17:53AM -0600, Brian Austin wrote:

> I have a codec I would like to submit.  The Cirrus Logic CS42L52 Low
> Power codec.  I have the codec code as well as the machine code for the
> Cirrus Logic EP9407A, but cannot submit that yet.  Is it OK to just
> submit the codec code for now?  This does not use the new API, so a hint
> as to which tree to make the diff from would help.

Assuming that this is an ASoC codec driver please go ahead and submit
the codec by itself - there's no requirement for an in-tree machine
driver.  For ASoC v1 a patch against any of current alsa-driver hg,
Linus' current kernel or the dev branch of the ASoC repository at
git://opensource.wolfsonmicro.com/linux-2.6-asoc should be fine -
whichever you find most convenient.

  reply	other threads:[~2008-02-18 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 14:17 Cirrus Logic CS42L52 Low power codec Brian Austin
2008-02-18 14:36 ` Mark Brown
2008-02-18 14:45   ` Brian Austin [this message]
2008-02-18 15:06     ` Timur Tabi
2008-02-18 15:22     ` Mark Brown
2008-02-18 16:34       ` Brian Austin
2008-02-18 17:07         ` Timur Tabi
2008-02-18 17:35         ` Ben Dooks
2008-02-18 17:58         ` Mark Brown
2008-02-18 18:07           ` Brian Austin
2008-02-18 19:05             ` 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=1203345949.4063.8.camel@localhost.localdomain \
    --to=brian.austin@cirrus.com \
    --cc=alsa-devel@alsa-project.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.