From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Timur Karaldin <karaldin@mcsplus.ru>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
Jyri Sarha <jsarha@ti.com>, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: ASoC: TLV320AIC3x: Adding additional functionality for 3106 with [Patch] for discuss
Date: Tue, 15 Mar 2016 13:47:19 +0200 [thread overview]
Message-ID: <56E7F647.7060500@ti.com> (raw)
In-Reply-To: <56E7E145.5010904@mcsplus.ru>
On 03/15/16 12:17, Timur Karaldin wrote:
> 14.03.2016 19:38, Peter Ujfalusi пишет:
>> On 03/14/2016 04:57 PM, Timur Karaldin wrote:
>>> Hi, Peter!
>>> What's about placing capture controls in the Playback section of Alsamixer
>>> view?
>> Yeah, it is annoying. They can be fixed by:
>> "Line1L Switch" -> "Line1L Capture Switch" and so on. On the other hand we had
>> these unfortunate control names I think since the beginning and it is kind of
>> an ABI for existing products. I don't have issue changing them, but existing
>> setups relying on the control names might break...
>>
>>> Does resetting of some registers during start/stop of recording
>>> connect with it?
>> Not sure what you mean.
>>
> I mean current situation:
>
> #i2cdump -f -y -r 13-13 1 0x1b
> Result: 0x00
> #arecord test.wav &
> #i2cdump -f -y -r 13-13 1 0x1b
> Result: 0x00
> # amixer sset 'Headset Detect Enable' *on*
> #i2cdump -f -y -r 13-13 1 0x1b
> Result:*0x80*
> #killall arecord
> #i2cdump -f -y -r 13-13 1 0x1b
> Result: 0x00
> #arecord test.wav &
> #i2cdump -f -y -r 13-13 1 0x1b
> Result:*0x00
> *#killall arecord*
> *amixer sset 'Headset Detect Enable'*on**
> *#i2cdump -f -y -r 13-13 1 0x1b
> Result:**0x00
> **#amixer sset 'Headset Detect Enable' off
> *amixer: Invalid command!*
>
> So state of 'Headset Detect Enable' and others of my controls were not stored
> during arecord/aplay restart (open and close device).
aic3x_set_power() will soft reset the codec on power off which resets also the
headset detect registers.
--
Péter
_______________________________________________
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-03-15 11:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 11:06 ASoC: TLV320AIC3x: Adding additional functionality for 3106 with [Patch] for discuss Timur Karaldin
2016-03-14 14:47 ` Peter Ujfalusi
[not found] ` <56E6D177.5050108@mcsplus.ru>
2016-03-14 16:38 ` Peter Ujfalusi
2016-03-15 10:17 ` Timur Karaldin
2016-03-15 11:47 ` Peter Ujfalusi [this message]
2016-03-15 12:12 ` Timur Karaldin
2016-03-15 12:40 ` Peter Ujfalusi
2016-03-15 16:13 ` Timur Karaldin
2016-03-16 8:57 ` Peter Ujfalusi
2016-03-16 10:26 ` Timur Karaldin
2016-03-16 15:23 ` Peter Ujfalusi
2016-03-16 16:53 ` Timur Karaldin
2016-03-17 9:26 ` Peter Ujfalusi
2016-03-18 15:45 ` Timur Karaldin
2016-03-23 15:21 ` Timur Karaldin
2016-03-31 12:58 ` Peter Ujfalusi
2016-04-18 16:28 ` [PATCH V2 1/2] ASoC: TLV320AIC3x: Adding additional functionality for 3106 Timur Karaldin
2016-04-18 16:28 ` [PATCH V2 2/2] " Timur Karaldin
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=56E7F647.7060500@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@bitmer.com \
--cc=jsarha@ti.com \
--cc=karaldin@mcsplus.ru \
--cc=lars@metafoo.de \
/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).