From: Sameer Pujar <spujar@nvidia.com>
To: Jaroslav Kysela <perex@perex.cz>,
broonie@kernel.org, lgirdwood@gmail.com, tiwai@suse.com
Cc: linux-tegra@vger.kernel.org, alsa-devel@alsa-project.org,
thierry.reding@gmail.com, linux-kernel@vger.kernel.org,
jonathanh@nvidia.com
Subject: Re: [PATCH] ASoC: tegra: Add master volume/mute control support
Date: Fri, 29 Oct 2021 20:38:54 +0530 [thread overview]
Message-ID: <18b61046-ac0b-0fb3-669c-6524a03eecf0@nvidia.com> (raw)
In-Reply-To: <8cb777f9-b73b-136c-f560-de4c31af931e@nvidia.com>
On 10/26/2021 11:53 AM, Sameer Pujar wrote:
>
>
> On 10/25/2021 6:28 PM, Jaroslav Kysela wrote:
>> On 25. 10. 21 13:06, Sameer Pujar wrote:
>>
>>> @@ -150,11 +186,22 @@ static int tegra210_mvc_put_mute(struct
>>> snd_kcontrol *kcontrol,
>>
>> ...
>>>
>>> return 1;
>>
>> It's a bit unrelated comment to this change, but it may be worth to
>> verify all
>> kcontrol put callbacks in the tegra code. Ensure that value 1 is
>> returned only
>> when something was really changed in hardware.
There are cases when the mixer control update is not immediately written
to HW, instead the update is ACKed (stored in variable) and writen to HW
at a later point of time. Do these cases qualify for "return 1" as well?
>>
>> The tegra210_i2s_put_control() has opposite problem for example -
>> returns
>> always 0 which means that the change notifications are not send to
>> subscribed
>> applications.
>>
>
> Thanks Jaroslav for review. I will keep a note to review put() calls
> in Tegra drivers and send fixes accordingly.
next prev parent reply other threads:[~2021-10-29 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 11:06 [PATCH] ASoC: tegra: Add master volume/mute control support Sameer Pujar
2021-10-25 12:58 ` Jaroslav Kysela
2021-10-26 6:23 ` Sameer Pujar
2021-10-29 15:08 ` Sameer Pujar [this message]
2021-10-29 15:22 ` Mark Brown
2021-10-29 15:26 ` Jaroslav Kysela
2021-11-03 5:12 ` Sameer Pujar
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=18b61046-ac0b-0fb3-669c-6524a03eecf0@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.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