On Wed, Feb 05, 2014 at 10:19:22AM +0100, Lars-Peter Clausen wrote:
On 02/05/2014 10:11 AM, Jean-Francois Moine wrote:
So, in the CODEC, I don't see how I could update the parameters dictated by the EDID otherwise in changing the DAI driver parameters.
The startup function is the right place. But instead of modifying the DAI use snd_pcm_hw_constraint_mask64(), snd_pcm_hw_constraint_list(), etc. to setup the additional constraints that come from the EDID.
Right.
Bonus points for making this a generic helper function that takes a runtime and a EDID and then applies the EDID constraints on the runtime.
...as previously requested. I know there was some discusion of broader moves to factor this stuff out but it'd still be good to keep it separated out even prior to a final non-EDID based solution so it's easier to refactor.