All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Matt Campbell <mcampbell@izotope.com>, alsa-devel@alsa-project.org
Subject: Re: Questions about ASoC driver implementation
Date: Wed, 12 Aug 2015 17:14:57 +0200	[thread overview]
Message-ID: <55CB62F1.3010805@metafoo.de> (raw)
In-Reply-To: <CAMDowVVj26LdUz5hgp6J9kfB=g5gEfq1L_ycGbHymEYJ-_k+MQ@mail.gmail.com>

Hi,


On 08/12/2015 04:01 PM, Matt Campbell wrote:
> Hi All,
> 
> I'm diving into adding support for a new codec (AK4621) targeting IMX6 SoC
> and as this is my first dive into ALSA driver code (and first deep dive in
> to Linux driver development) I've come up with a few questions. I've done a
> lot of digging in available documentation as well as reading a lot of code,
> but some things remain unclear.
> 
> First, I'm a little confused with what appears to be inconsistent
> terminology. The SoC overview.txt lists three types of component drivers:
> codec, platform and machine. However, in the code there are four types of
> snd_soc_register_* functions: card, platform, codec and component. From
> looking at the underlying structs and how these are used in existing code
> this is my best guess but please correct me if I'm wrong:
> 
> codec -> snd_soc_register_codec
> machine -> snd_soc_register_card
> platform -> snd_soc_register_component and snd_soc_register_platform? (not
> sure about this, from what I can gather at some point there was an API
> switch to using component rather than platforms for the DAIs)

There used to be a lot of similarity between platforms and CODECs and some
code duplication. snd_soc_component was introduced is a new common base
class for both CODEC and platform. It can also be used standalone if none of
the platform or CODEC specific functionality is need.

> 
> My second question is around adding support for an amplifier external to
> the codec. The amplifier is a PGA controlled over SPI. One possible way I
> can see to adding this is to create a SPI based codec driver for the PGA
> that exposes an ALSA control for the gain level and give it a dummy DAI
> then add it to the card as an aux_dev. This feels a little kludgy as the
> PGA isn't a perfect fit for the codec class.

You don't need to register a DAI with your CODEC it will work just fine
without. Although in this case you don't need any CODEC specific features so
the best is to just go with snd_soc_component. There are a few examples of
snd_soc_component based drivers for external analog amplifiers, e.g. max9768
or lm4857.

- Lars

  reply	other threads:[~2015-08-12 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 14:01 Questions about ASoC driver implementation Matt Campbell
2015-08-12 15:14 ` Lars-Peter Clausen [this message]
2015-08-12 16:56   ` Matt Campbell

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=55CB62F1.3010805@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=mcampbell@izotope.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.