Hi Mark,
Thanks for your response. The problem we had is the dapm is holding an
instance of the regulator and we wanted to control that instance based
on use-case. But I understand your point that we should not be exposing
regulators to userspace but manage it in the driver itself..will have a
On Tue, Sep 08, 2015 at 11:14:09AM +0100, Nikesh Oswal wrote:
> When regulator is defined with SND_SOC_DAPM_REGULATOR_CONTROL_BYPASS
> flag, then a kcontrol will be created which can be used to switch
> regulator to regulated/bypass state. This will help to control the
> behaviour of the regulator
When regulator is defined with SND_SOC_DAPM_REGULATOR_CONTROL_BYPASS
flag, then a kcontrol will be created which can be used to switch
regulator to regulated/bypass state. This will help to control the
behaviour of the regulator based on a usecase. For example voice call
may need a regulated voltag
3 matches
Mail list logo