On Tue, May 02, 2023 at 09:26:32AM +0200, Krzysztof Kozlowski wrote: > On 26/04/2023 09:36, Herve Codina wrote: > > Rob Herring <robh@xxxxxxxxxx> wrote: > >> On Fri, Apr 21, 2023 at 02:41:19PM +0200, Herve Codina wrote: > >>> simple-iio-aux allows to consider these Industrial I/O devices as > >>> auxliary audio devices. > >> What makes it simple? Any binding called simple or generic is a trigger > >> for me. Best to avoid those terms. :) > > I choose simple-iio-aux because some simple-* already exists. > > For instance simple-audio-amplifier or simple-audio-mux. > > Do you prefer audio-iio-aux ? > > Let me know if I should change. > It means that often what people call "simple" and "generic" works only > for their specific case, because it is not really simple and generic. > After some time the "simple" and "generic" becomes "complicated" and > "huge". Conclusion: sometimes simple and generic bindings are bad idea > and you should have something specific. > Your description in the binding also does not help to match it to > specific, real device. Provide the examples, as Rob asked. I don't understand what you are looking for here. IIO is a subsystem which represents generic DACs and ADCs (along with other I/O things). Audio devices also have DACs and ADCs, somewhat specialised for use in audio but more limited by specs and interfaces than by anything fundamental. The goal here is to map DACs and ADCs described as IIO for use in an audio context. ADCs are devices that convert analog signals into digital values, DACs are devices that convert digital values into analog signals. > >> How do support multiple instances? Say you have 2 sound cards (or 1 > >> sound card with multiple audio paths) each with different sets of IIO > >> channels associated with it. You'd need a link to each 'aux' node. Why > >> not just add io-channels to the sound card nodes directly? That's > >> already just a virtual, top-level container node grouping all the > >> components. I don't see why we need another virtual node grouping a > >> subset of them. > > I don't see what you mean. > > I use a simple-audio-card and here is a full example using several > > instances: > Just like Rob said: "You'd need a link to each 'aux' node" > and you did it... > So now the rest of Rob's answer: > "Why not just add io-channels to the sound card nodes directly? That's > already just a virtual, top-level container node grouping all the > components. I don't see why we need another virtual node grouping a > subset of them." > Why do you need another node if it is not really representing a real, > separate device? If nothing else I would expect it to be useful from a comprehensibility point of view to bundle multiple IIO devices into a single multi-channel audio stream, an individual IIO device is likely to only present a single channel of data but it is common to group multiple channels of audio data.
Attachment:
signature.asc
Description: PGP signature
