From: Andreas Dannenberg <dannenberg@ti.com>
To: Petr Kulhavy <petr@barix.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Codec "virtual multiplexer" representation
Date: Wed, 17 Feb 2016 23:30:21 -0600 [thread overview]
Message-ID: <20160218053021.GE6263@borg.dal.design.ti.com> (raw)
In-Reply-To: <56C499A7.2040202@barix.com>
On Wed, Feb 17, 2016 at 05:02:47PM +0100, Petr Kulhavy wrote:
> Hi,
>
> I'm writing an ASoC driver for the TAS5721 amplifier.
> This 2.1 amplifier provides a complex configuration of the audio channels
> (3), PWMs(4) and output(4) mappings.
> However only few (about 6) configurations really make sense.
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
>
> I'm trying to model the output configurations in ALSA. In order to avoid a
> complicated set of switches and multiplexers I would like
> to add just one multiplexer like control which selects one of these 6 output
> configurations and a callback function which sets the proper
> registers accordingly (there are 5 affected registers).
>
> Is there a way to create such a "virtual multiplexer" in ALSA?
>
> Thanks
> Petr
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-02-18 5:30 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 [this message]
2016-02-24 16:57 ` Petr Kulhavy
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=20160218053021.GE6263@borg.dal.design.ti.com \
--to=dannenberg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=petr@barix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).