diff options
author | Charles Keepax <[email protected]> | 2018-08-27 14:26:47 +0100 |
---|---|---|
committer | Mark Brown <[email protected]> | 2018-08-28 19:35:49 +0100 |
commit | e33ffbd9cd39da09831ce62c11025d830bf78d9e (patch) | |
tree | 9e33da4db43e6c87e1129051dc64a8e555de7536 /tools/perf/scripts/python/stackcollapse.py | |
parent | a5cd7e9cf587f51a84b86c828b4e1c7b392f448e (diff) |
ASoC: dpcm: Properly initialise hw->rate_max
If the CPU DAI does not initialise rate_max, say if using
using KNOT or CONTINUOUS, then the rate_max field will be
initialised to 0. A value of zero in the rate_max field of
the hardware runtime will cause the sound card to support no
sample rates at all. Obviously this is not desired, just a
different mechanism is being used to apply the constraints. As
such update the setting of rate_max in dpcm_init_runtime_hw
to be consistent with the non-DPCM cases and set rate_max to
UINT_MAX if nothing is defined on the CPU DAI.
Signed-off-by: Charles Keepax <[email protected]>
Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions