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: Thu, 20 Apr 2023 18:18:46 +0200 [thread overview]
Message-ID: <ZEFl5hlFL/VAIVTB@ugly> (raw)
In-Reply-To: <87leimtyqw.wl-tiwai@suse.de>
On Thu, Apr 20, 2023 at 04:27:35PM +0200, Takashi Iwai wrote:
>But why this has to be buried in the middle of a patch containing lots
>of other changes...? Better to split out and start a new thread.
>
this "patch" doesn't contain any changes, only a bunch of questions.
given the expected audience, i don't think that "burying" it was
detrimental.
>IIRC, this was a result after struggles with the structured control
>implementations. It became too complex, and the plain array with
>string representation can cover all complexity, while it still allows
>the grouping in user-space side.
>
i can see how a keyword based interface description is appealing - it
keeps the kernel interface slim and flexible. but of course that comes
at a steep cost in user space - i for one got completely lost and was
unable to debug the bug described in the OP.
maybe a middle way would have been the best option?
>Again, the choice was done in a quarter century ago, and if you change
>it, you'll certainly break the whole things badly. We must keep the
>compatibility.
>
i don't intend to actually change it. but suppose we did.
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.
regards
next prev parent reply other threads:[~2023-04-20 16:20 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 [this message]
2023-04-21 8:55 ` Takashi Iwai
2023-04-21 9:11 ` Oswald Buddenhagen
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=ZEFl5hlFL/VAIVTB@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.