All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Kulhavy <petr@barix.com>
To: Andreas Dannenberg <dannenberg@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Codec "virtual multiplexer" representation
Date: Wed, 24 Feb 2016 17:57:30 +0100	[thread overview]
Message-ID: <56CDE0FA.8000905@barix.com> (raw)
In-Reply-To: <20160218053021.GE6263@borg.dal.design.ti.com>


On 18.02.2016 06:30, Andreas Dannenberg wrote:
>
> Petr,
> on a related note, I'm currently working on a combined driver (85%
> complete) for TAS5720/TAS5722 which are nice but relatively simple
> Class-D mono amplifiers. Despite almost having the same P/N there is
> little to no similarity with TAS5721 (which gives a another example why
> one should be careful with wildcard 'x' in driver names) so there is no
> case for a combined driver here but let's make sure we align our
> namespace to avoid collision:
>
> tas5720.[c|h] - Driver for TAS5720/TAS5722 (WIP by Andreas)
> tas5721.[c|h] - Driver for TAS5721 (WIP by Petr)
>
> Regards,
>
> --
> Andreas Dannenberg
> Texas Instruments Inc
>
Hi Andreas,

thanks for letting me know! In the meantime I have found there is a 
driver for TAS5711, TAS5717 and TAS5719.
The TAS5721 is very similar to the 5711, so I will just update that 
driver rather than creating a new one.

One question came to my mind, which you can perhaps help me to answer as 
you are more familiar with these amplifiers:
what is the usual representation of a 2.1 system in controls? I'm 
wondering that the TAS5711 has just master volume and a double slider 
for Ch1/Ch2, but there is no Ch3 control.
Surely that is needed as well, isn't it?

Regards
Petr

      reply	other threads:[~2016-02-24 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 16:02 Codec "virtual multiplexer" representation Petr Kulhavy
2016-02-18  5:30 ` Andreas Dannenberg
2016-02-24 16:57   ` Petr Kulhavy [this message]

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=56CDE0FA.8000905@barix.com \
    --to=petr@barix.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dannenberg@ti.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.