Re: [RFC PATCH] docs: sound: kernel-api: writing-an-alsa-driver.rst: add FIXMEs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 20 Apr 2023 14:47:11 +0200,
Oswald Buddenhagen wrote:
> 
> On Thu, Apr 06, 2023 at 08:42:27AM +0200, Takashi Iwai wrote:
> > On Wed, 05 Apr 2023 22:12:20 +0200, Oswald Buddenhagen wrote:
> >>  The ``name`` is the name identifier string. Since ALSA 0.9.x, the
> >>  control name is very important, because its role is classified from
> >>  its name. There are pre-defined standard control names. The details
> >>  are described in the `Control Names`_ subsection.
> >> +// This is a questionable design, IMO. Why user-space heuristics when
> >> +// the driver could set the roles/capabilities? This would avoid
> >> +// problems like the Tone Control sliders (unlike the switch?!) being
> >> +// misclassified as applying also to capture.
> > 
> > Why this has to be discussed here and now...?
> > 
> why not?

Because it is the already defined rule, and you're complaining the
documentation.  You are free to start a new discussion, but not it
shouldn't be along with the documentation patch at all.

> > It's the thing that was *defined* over two decades ago.
> > 
> that may be so, but this doesn't explain anything.
> it's a somewhat surprising choice, and it does in fact sometimes cause
> problems. so at least it should be thoroughly explained.

Again, you're barking at a wrong place.  The whole control name ruling
is explained in another document; there is another document covering
control name rules.


Takashi



[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Pulse Audio]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux