On Mon, Feb 24, 2020 at 11:28:57AM +0000, Jon Hunter wrote:
On 21/02/2020 16:55, Mark Brown wrote:I don't think so, I'd not expect the individual drivers to be doing
The ideal thing in a component model would be to represent those sampleI assume that it would be OK for the sample rate converter itself to
rate convertors directly to usrspace so the routing and rewriting is
explicit.
expose mixer controls to configure its input and output rates so the
user could configure as needed?
anything user visible here - if we know what a digital transformation
looks like the framework should be offering anything that's needed to
users (and hiding controls that don't have any practical control in a
given system).
Internal testing often requires things that can't be exposed to users,Is there any *need* for these to be user configurable? What's normallyI can see that in most cases there are a finite set of configurations
happening at the minute is that either the external DAIs are fixed
configuration and the DSP just converts everything or there's no format
conversion done and things get passed through.
that the end user may use. However, we would like to make the
configuration flexible as possible and this also allow us to test lots
of different configurations for verification purposes as well.
the extreme examples are things like battery chargers with health and
safety issues if the full range of control is available.