From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC PATCH] docs: sound: kernel-api: writing-an-alsa-driver.rst: add FIXMEs
Date: Fri, 21 Apr 2023 11:11:55 +0200 [thread overview]
Message-ID: <ZEJTW13Vm6PK7VIq@ugly> (raw)
In-Reply-To: <87leilsjgk.wl-tiwai@suse.de>
On Fri, Apr 21, 2023 at 10:55:23AM +0200, Takashi Iwai wrote:
>> i suppose we'd have to add SNDRV_CTL_ELEM_ACCESS_{PLAYBACK,CAPTURE}.
>> both could be set for unspecific and actually bidirectional
>> controls. if neither is set, user space would fall back to the keyword
>> based rules (and exceptions ...) - that would be backwards compatible
>> and would enable a gradual migration.
>
>The backward compatibility isn't really easy as you wrote, I'm
>afraid. If you run an old user-space stuff on the new kernel, you
>must not fill that new information bit but translate it to the string
>suffix instead; and that has to be done inside the kernel
>automagically.
>
right, i didn't mention it, but i imagined the strings to remain the
same, both for backwards compat, and because they serve a "label"
function regardless of semantic interpretation. of course that would
make them partially redundant with the newly added bits, but that
doesn't seem too bad to me.
anyway, i think i have enough background info now to write a nice
paragraph for the docu.
thanks!
next prev parent reply other threads:[~2023-04-21 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 20:12 [RFC PATCH] docs: sound: kernel-api: writing-an-alsa-driver.rst: add FIXMEs Oswald Buddenhagen
2023-04-06 6:42 ` Takashi Iwai
2023-04-20 12:47 ` Oswald Buddenhagen
2023-04-20 12:54 ` Takashi Iwai
2023-04-20 13:44 ` Oswald Buddenhagen
2023-04-20 14:27 ` Takashi Iwai
2023-04-20 16:18 ` Oswald Buddenhagen
2023-04-21 8:55 ` Takashi Iwai
2023-04-21 9:11 ` Oswald Buddenhagen [this message]
2023-04-21 9:14 ` 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=ZEJTW13Vm6PK7VIq@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=alsa-devel@alsa-project.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.