From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
brian.austin@cirrus.com, Paul.Handrigan@cirrus.com,
lgirdwood@gmail.com, robh+dt@kernel.org
Subject: Re: [PATCH 4/4] ASoC: cs35l35: Add multi-device synchronisation
Date: Thu, 1 Jun 2017 12:45:21 +0100 [thread overview]
Message-ID: <20170601114521.GS1594@localhost.localdomain> (raw)
In-Reply-To: <20170530085138.GR1594@localhost.localdomain>
On Tue, May 30, 2017 at 09:51:38AM +0100, Charles Keepax wrote:
> On Mon, May 29, 2017 at 02:53:06PM +0100, Mark Brown wrote:
> > On Thu, May 18, 2017 at 04:32:39PM +0100, Charles Keepax wrote:
> >
> > > + SOC_SINGLE_EXT("SYNC Audio", CS35L35_MULT_DEV_SYNCH2, 1, 1, 0,
> > > + snd_soc_get_volsw, cs35l35_put_sync),
> > > + SOC_SINGLE_EXT("SYNC VPBR", CS35L35_MULT_DEV_SYNCH2, 2, 1, 0,
> > > + snd_soc_get_volsw, cs35l35_put_sync),
> > > + SOC_SINGLE_EXT("SYNC OTW", CS35L35_MULT_DEV_SYNCH2, 3, 1, 0,
> > > + snd_soc_get_volsw, cs35l35_put_sync),
> >
> > I can't tell how this works. It feels like this shouldn't just be being
> > controlled from userspace but rather should be handled in some more
> > standard fashion, or possibly as part of the platform integration but
> > right now it's just some totally undocumented application managed
> > controls.
>
> These activate the individual types of synchronisation between
> the two stereo amps over a proprietary single wire connection
> between the two amps. The audio option synchronises the group
> delay between the two amps. The VPBR links the brown out on the
> two amps and the OTW links the over temperature warning.
>
> The issue is really one of it being use-case specific whether the
> amps are being used independently or in a stereo configuration.
> You could have only a single amp in use in which case the sync
> features are best turned off. Or one might even have use-cases
> with both amps where they are being used independently but at the
> same time.
>
> I guess we could potentially do those as calls from the machine
> driver, although in some cases it might be hard to tell which
> use-case is being used. Alternatively, one could try to actually
> link the two amps in DAPM and control it that way although you
> probably still want some device tree stuff to say which things
> you want to sync and it might cause issues in any cases where you
> had both amps up but didn't want to sync.
Ok turns out there is one other corner case issue here, lets drop
this patch for now and I will try to see if I can come up with
better solution for it.
Thanks,
Charles
next prev parent reply other threads:[~2017-06-01 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 15:32 [PATCH 1/4] ASoC: cs35l35: Add Boost Inductor Calculation Charles Keepax
[not found] ` <1495121559-1063-1-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2017-05-18 15:32 ` [PATCH 2/4] ASoC: cs35l35: Add DT handling for Inductor Charles Keepax
[not found] ` <1495121559-1063-2-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2017-05-19 17:03 ` Applied "ASoC: cs35l35: Add DT handling for Inductor" to the asoc tree Mark Brown
2017-05-18 15:32 ` [PATCH 3/4] ASoC: cs35l35: Correctly handle 0 for bst_ipk Charles Keepax
[not found] ` <1495121559-1063-3-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2017-05-19 17:03 ` Applied "ASoC: cs35l35: Correctly handle 0 for bst_ipk" to the asoc tree Mark Brown
2017-05-19 17:03 ` Applied "ASoC: cs35l35: Add Boost Inductor Calculation" " Mark Brown
2017-05-22 13:18 ` [PATCH 1/4] ASoC: cs35l35: Add Boost Inductor Calculation Austin, Brian
2017-05-18 15:32 ` [PATCH 4/4] ASoC: cs35l35: Add multi-device synchronisation Charles Keepax
[not found] ` <1495121559-1063-4-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2017-05-29 13:53 ` Mark Brown
2017-05-30 8:51 ` Charles Keepax
2017-06-01 11:45 ` Charles Keepax [this message]
[not found] ` <20170530085138.GR1594-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-06-02 17:11 ` 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=20170601114521.GS1594@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=Paul.Handrigan@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=mark.rutland@arm.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=robh+dt@kernel.org \
/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).