All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Rick Mann <rmann@latencyzero.com>, alsa-devel@alsa-project.org
Subject: Re: Driver for audio power amplifier ICs?
Date: Thu, 01 Oct 2015 11:04:02 +0200	[thread overview]
Message-ID: <560CF702.4000106@metafoo.de> (raw)
In-Reply-To: <999B71E1-5FDB-4EFD-8E69-975C8A09A0C7@latencyzero.com>

On 10/01/2015 10:49 AM, Rick Mann wrote:
> I've been working on this Beaglebone Black custom audio cape. It has a tlv320aic3104 codec (that I'm still trying to get working properly), and connected to its line outs is a tpa3140d2 analog 2x10W power amplifier. This chip has very little in the way of CPU interface, but it does have /shutdown and /fault lines.
> 
> I'm wondering how ALSA becomes aware of that chip, in order to enable it when it enables certain routes in the tlv320aic3104, and to inform application software if the /fault line asserts.
> 
> I don't mind writing a driver, if necessary, I just don't know where such a thing would fit. I also wonder what the device tree entries for the amp might look like.

Hi,

There are a couple of existing amplifier driver like e.g. max9877 or lm4857.
While those two examples have I2C control interface it is no problem to
implement a driver with just a GPIO control interface. Generally the input
and output pins of the amplifier should be modeled as DAPM widgets with a
widget for the amplifier function in between. You can use a callback
function for the amplifier widget to get notified when the amplifier needs
to be enabled and when not and can use this to control the GPIO.

The connections between the CODEC and the amplifier need to be specified in
the board driver.

- Lars

  reply	other threads:[~2015-10-01  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01  8:49 Driver for audio power amplifier ICs? Rick Mann
2015-10-01  9:04 ` Lars-Peter Clausen [this message]
2015-10-01  9:08   ` Rick Mann
2015-10-01 10:20     ` Lars-Peter Clausen

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=560CF702.4000106@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=rmann@latencyzero.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.