alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	Andrew Chant <achant@google.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [RFC, alsa-utils] RFC: alsamixer: Improve description of playback switches
Date: Mon, 26 Mar 2018 23:53:19 +0200	[thread overview]
Message-ID: <185d4bb1-8af6-23a4-5abd-86d91ace83f2@gmail.com> (raw)
In-Reply-To: <e1cb0e74-8372-f342-b38c-9ad4f80c0ffd@sakamocchi.jp>

On 03/26/18 23:44, Takashi Sakamoto wrote:
> Hi,
>
> On Mar 27 2018 06:13, Kirill Marinushkin wrote:
>> On 03/26/18 22:41, Andrew Chant wrote:
>>> On Mon, Mar 26, 2018 at 11:32 AM, Kirill Marinushkin
>>> <k.marinushkin@gmail.com> wrote:
>>>> I faced 2 problems:
>>>>
>>>> * the clock source validity was displayed as [O]. I thought it is a zero, which is the opposite from the real state
>>>> * I couldn't find how to turn the processing feature on. The help doesn't say anything about it
>>> A recent patch of mine changed clock source validity from a mixer to a
>>> global control, so it should no longer show up in alsamixer.
>>
>> Hello Andrew,
>>
>> Nice! One of the problems is solved. However, the second problem is still actual.
>> As you had a recent experience with alsamixer, what is your opinion?
>
> I think Kirill mentions a patch to change the type of 'iface' for such control elements to 'SNDRV_CTL_ELEM_IFACE_CARD' or 'SNDRV_CTL_ELEM_IFACE_PCM', but I cannot find such patches in Iwai-san's tree[1]. I guess they're not merged yet.

Andrew mentioned the patch [2]

>
> In my humble opinion, if so, Kirill's patch is not better in a view of compatibility, because such smixer controls suddenly disappear via alsa-lib's mixer APIs when the patched kernel is released. In a point of backward compatibility, this kind of change should be avoided, as possible (of cource, depending on the cases).

The patch of Andrew and my RFC serve different purposes. They do not replace each other.
Patch of Andrew made the "clock valid" global.
My RFC is to add the string in the help, to clarify how to toggle the switches in alsamixer.

>
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/log/?h=for-next
>

[2] https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=568fa7e087ef98bc85b5aa31ea7c9252c1305c1f

>
> Regards
>
> Takashi Sakamoto

  reply	other threads:[~2018-03-26 21:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  5:11 [RFC, alsa-utils] RFC: alsamixer: Improve description of playback switches Kirill Marinushkin
2018-03-26  7:38 ` Takashi Iwai
2018-03-26 18:32   ` Kirill Marinushkin
2018-03-26 20:41     ` Andrew Chant
2018-03-26 21:13       ` Kirill Marinushkin
2018-03-26 21:44         ` Takashi Sakamoto
2018-03-26 21:53           ` Kirill Marinushkin [this message]
2018-03-27 19:12             ` Kirill Marinushkin
2018-03-26  8:19 ` Takashi Sakamoto
2018-03-26 18:37   ` Kirill Marinushkin
2018-03-26 18:42   ` Kirill Marinushkin
2018-03-26 22:03     ` Takashi Sakamoto
2018-03-26 22:22       ` Kirill Marinushkin

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=185d4bb1-8af6-23a4-5abd-86d91ace83f2@gmail.com \
    --to=k.marinushkin@gmail.com \
    --cc=achant@google.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=o-takashi@sakamocchi.jp \
    --cc=tiwai@suse.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).