On 05/30/2014 12:29 PM, Vinod Koul wrote: [...]
Btw. in this case I think you should just use the default DAPM kcontrol put callback. There doesn't seem to be anything special in here and with the DAPM componentization series the default handler is also able to handle platforms.
Not for this version sure, but future platforms of our need some custom stuff to be done. I will try to minimize those ones and once your component work is complete redo these bits. Would be too happy to remove if it works out that way, which is not the case with today. So till then we need these bits and exporting of the dapm_kcontrol_set_value()
You do not need to call dapm_kcontrol_set_value() from your custom put handler unless the control is auto-muted or a virtual control, of which neither seems to be the case here. So we do not need to export the function.
- Lars