From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Yoran Brondsema <yoran.brondsema@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Driver for AK4555 codec
Date: Thu, 29 Jul 2010 19:42:34 +0100 [thread overview]
Message-ID: <20100729184233.GA9469@sirena.org.uk> (raw)
In-Reply-To: <AANLkTimnYLEe-sK2_DcYQAGqVYd+JnsJaSpRfdKBbeEi@mail.gmail.com>
On Thu, Jul 29, 2010 at 09:18:43AM +0200, Yoran Brondsema wrote:
> There is a driver available for the LPC3250 but none for the AK4555 codec,
> so I have to write it myself. I checked the document "Writing an ALSA
> Driver" by Takashi Iwai but it seems to focus on full-featured sound cards;
> I'm just dealing with a "simple" codec. I checked at the code of the uda1380
> in linux/sound/soc/lpc3xxx/lpc3xxx-uda1380.c and it seems to be calling some
> functions like platform_device_alloc, platform_set_drvdata,... but I can't
> find the documentation of what these functions do.
> Can someone give me some pointers to some documentation or some rough idea
> of how it needs to be done?
The documentation for ASoC is in:
Documentation/sound/alsa/soc
which should give you a reasonable structural overview of things.
Probably the easiest thing for you to do is to clone the driver for a
simple I2C controlled CODEC such as the WM8523 and then replace all the
specifics of the register access with those for your CODEC.
next prev parent reply other threads:[~2010-07-29 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 7:18 Driver for AK4555 codec Yoran Brondsema
2010-07-29 18:42 ` Mark Brown [this message]
[not found] ` <AANLkTinWJT36u99_vxOqXOADRNBT9VMy_5mOsBLE1PLO@mail.gmail.com>
2010-07-30 6:59 ` Mark Brown
2010-07-30 8:00 ` Yoran Brondsema
2010-08-03 15: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=20100729184233.GA9469@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=yoran.brondsema@gmail.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.