alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Curtis Malainey <cujomalainey@chromium.org>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] [PATCH 02/11] ucm: docs: Add JackType value
Date: Fri, 29 Nov 2019 17:01:49 +0100	[thread overview]
Message-ID: <0626a79d-4950-ab27-d10a-366cd74da332@perex.cz> (raw)
In-Reply-To: <4b378b2c-fea2-5d77-26ff-0ff409d8e527@perex.cz>

Dne 11. 11. 19 v 14:39 Jaroslav Kysela napsal(a):
> Dne 07. 11. 19 v 2:57 Curtis Malainey napsal(a):
>> Identifies the type of jack and how it should be accessed
>>
>> Signed-off-by: Curtis Malainey <cujomalainey@chromium.org>
>> ---
>>    include/use-case.h | 3 +++
>>    1 file changed, 3 insertions(+)
>>
>> diff --git a/include/use-case.h b/include/use-case.h
>> index 2051bd40..3208cc30 100644
>> --- a/include/use-case.h
>> +++ b/include/use-case.h
>> @@ -322,6 +322,9 @@ int snd_use_case_get_list(snd_use_case_mgr_t *uc_mgr,
>>     *        configuration that doesn't belong to UCM configuration files.
>>     *   - JackName
>>     *      - Input name is the input device name for the jack
>> + *   - JackType
>> + *      - Specifies whether the jack is accessed via hctl or gpio and therefore
>> + *        only carries the possible values of "gpio" or "hctl"
>>     */
>>    int snd_use_case_get(snd_use_case_mgr_t *uc_mgr,
>>                         const char *identifier,
>>
> 
> What is meant with the "gpio" type? The standard input device interface? I
> believe it should be "inputdev" and "ctl" (hctl is just interface on top of
> ctl and the application can access the jack through snd_ctl functions, too.

I see (when I was cleaning this extra Chrome stuff in the ucm profiles) that 
it's related to the gpio (general purpose i/o pin interface) in the linux 
kernel. The JackSwitch is probably also related and defines the pin number 
where the application should watch for the jack state. In this case, it would 
be probably more nice to follow the JackControl and JackDev and define the pin 
number through JackGPIO or something like that. We will cover all three 
posibilities: ALSA control interface, Input interface, GPIO interface .

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-11-29 16:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07  1:57 [alsa-devel] [PATCH 01/11] ucm: docs: Add JackName value Curtis Malainey
2019-11-07  1:57 ` [alsa-devel] [PATCH 02/11] ucm: docs: Add JackType value Curtis Malainey
2019-11-11 13:39   ` Jaroslav Kysela
2019-11-29 16:01     ` Jaroslav Kysela [this message]
2019-12-03  3:22       ` Curtis Malainey
2019-12-03  8:39         ` Jaroslav Kysela
2019-11-07  1:58 ` [alsa-devel] [PATCH 03/11] ucm: docs: add value JackSwitch Curtis Malainey
2019-11-11 13:30   ` Jaroslav Kysela
2019-11-07  1:58 ` [alsa-devel] [PATCH 04/11] ucm: docs: Add EDID File value Curtis Malainey
2019-11-11 15:18   ` Jaroslav Kysela
2019-11-07  1:58 ` [alsa-devel] [PATCH 05/11] ucm: docs: Add MinBufferLevel value Curtis Malainey
2019-11-11 14:55   ` Jaroslav Kysela
2019-11-11 15:19   ` Jaroslav Kysela
2019-11-07  1:58 ` [alsa-devel] [PATCH 06/11] ucm: docs: Add DisableSoftwareVolume Curtis Malainey
2019-11-11 15:22   ` Jaroslav Kysela
2019-11-11 18:51     ` Curtis Malainey
2019-11-11 19:11       ` Curtis Malainey
2019-11-07  1:58 ` [alsa-devel] [PATCH 07/11] ucm: docs: Add CaptureChannelMap Curtis Malainey
2019-11-11 15:30   ` Jaroslav Kysela
2019-11-11 22:08     ` Curtis Malainey
2019-11-07  1:58 ` [alsa-devel] [PATCH 08/11] " Curtis Malainey
2019-11-07  2:02   ` Curtis Malainey
2019-11-11 15:31   ` Jaroslav Kysela
2019-11-11 22:09     ` Curtis Malainey
2019-11-07  1:58 ` [alsa-devel] [PATCH 09/11] ucm: docs: Add EchoReferenceDev Curtis Malainey
2019-11-11 15:36   ` Jaroslav Kysela
2019-11-11 18:42     ` Curtis Malainey
2019-11-07  1:58 ` [alsa-devel] [PATCH 10/11] ucm: docs: Add SoftwareGain Curtis Malainey
2019-11-11 15:33   ` Jaroslav Kysela
2019-11-11 18:46     ` Curtis Malainey
2019-11-07  1:58 ` [alsa-devel] [PATCH 11/11] ucm: docs: Add DefaultNodeGain Curtis Malainey
2019-11-11 15:34   ` Jaroslav Kysela
2019-11-11 18:44     ` Curtis Malainey
2019-11-11  9:44 ` [alsa-devel] [PATCH 01/11] ucm: docs: Add JackName value Kai Vehmanen
2019-11-11 13:26 ` Jaroslav Kysela

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=0626a79d-4950-ab27-d10a-366cd74da332@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=cujomalainey@chromium.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).