28 Sep
2013
28 Sep
'13
2:53 p.m.
On Fri, Sep 27, 2013 at 09:37:01PM -0700, Andrey Smirnov wrote:
Since the driver doesn't expose any controls to userspace the only things that can cause register writes are the operations provided by the CODEC driver, they could take the lock for their runtime (which is about the level the v4l stuff is running at AIUI).
Do you mean moving it to si476x_codec_set_dai_fmt and si476x_codec_hw_params? If those are the only two places where register read and write are called by SoC sound subsystem then I think that would work.
Yes, exactly. Unless you provide controls or DAPM nothing outside of the callbacks in your driver is going to interact with registers.