On 24. 01. 22 16:32, Mark Brown wrote:
This series adds verification that values written to registers are in bounds for controls since the core doesn't validate for us.
As discussed, those conditions should be optional to eventually catch the wrong applications. I don't see any benefit to report the range error back when there is value masking code already. The users will note when the unwanted values are written to the hardware, or not?
Thanks, Jaroslav -- Jaroslav Kysela <perex@xxxxxxxx> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
