snd_soc_dapm_force_enable_pin question

snd_soc_dapm_force_enable_pin question

[Koul, Vinod]

Hi,

I have a Vibra controller on the codec which can be programmed using
alsa controls. Now after configuration I added an enable control which
when turned On, forces the Vibra Pin to be ON. The Pin is on, but not
the path, I need the DAC and amplifier connected to be ON as well?

Is this not what the force_enable_pin() is supposed to do?
If not how should I ensure this path and codec BIAS is on when Vibra is
activated by user?


-- 
~Vinod

Re: snd_soc_dapm_force_enable_pin question

[Mark Brown]

On Fri, Mar 25, 2011 at 04:15:30PM +0530, Koul, Vinod wrote:

> I have a Vibra controller on the codec which can be programmed using
> alsa controls. Now after configuration I added an enable control which
> when turned On, forces the Vibra Pin to be ON. The Pin is on, but not
> the path, I need the DAC and amplifier connected to be ON as well?

> Is this not what the force_enable_pin() is supposed to do?

No, it's there to force a pin to be on when there's no audio path - the
main use is for microphone biases, to ensure they're enabled in order to
allow jack detection to work.  The purpose is to ignore routing so it
won't affect any other widgets.

> If not how should I ensure this path and codec BIAS is on when Vibra is
> activated by user?

Your above scenario sounds like you're just doing a regular playback of
some kind - if that is the case I'd expect things to power up when you
start playing through the DAC.

Otherwise I'd suggest creating an input widget, connecting it as an
input to the DAC and then using regular enable_pin() to enable that and
the output.

Re: snd_soc_dapm_force_enable_pin question

[Koul, Vinod]

On Fri, 2011-03-25 at 17:10 +0530, Mark Brown wrote:
> On Fri, Mar 25, 2011 at 04:15:30PM +0530, Koul, Vinod wrote:
> 
> > I have a Vibra controller on the codec which can be programmed using
> > alsa controls. Now after configuration I added an enable control which
> > when turned On, forces the Vibra Pin to be ON. The Pin is on, but not
> > the path, I need the DAC and amplifier connected to be ON as well?
> 
> > Is this not what the force_enable_pin() is supposed to do?
> 
> No, it's there to force a pin to be on when there's no audio path - the
> main use is for microphone biases, to ensure they're enabled in order to
> allow jack detection to work.  The purpose is to ignore routing so it
> won't affect any other widgets.
> 
> > If not how should I ensure this path and codec BIAS is on when Vibra is
> > activated by user?
> 
> Your above scenario sounds like you're just doing a regular playback of
> some kind - if that is the case I'd expect things to power up when you
> start playing through the DAC.
No, its Vibra PWM controller no playback here
> 
> Otherwise I'd suggest creating an input widget, connecting it as an
> input to the DAC and then using regular enable_pin() to enable that and
> the output.
This sounds the way for me, let me try this

Thanks
-- 
~Vinod

Re: snd_soc_dapm_force_enable_pin question

[Mark Brown]

On Fri, Mar 25, 2011 at 05:50:07PM +0530, Koul, Vinod wrote:
> On Fri, 2011-03-25 at 17:10 +0530, Mark Brown wrote:

> > Your above scenario sounds like you're just doing a regular playback of
> > some kind - if that is the case I'd expect things to power up when you
> > start playing through the DAC.

> No, its Vibra PWM controller no playback here

So the DAC gets its input from some internal source?  In that case that
source maps very directly onto the input widget.

Re: snd_soc_dapm_force_enable_pin question

[Koul, Vinod]

On Fri, 2011-03-25 at 18:26 +0530, Mark Brown wrote:
> On Fri, Mar 25, 2011 at 05:50:07PM +0530, Koul, Vinod wrote:
> > On Fri, 2011-03-25 at 17:10 +0530, Mark Brown wrote:
> 
> > > Your above scenario sounds like you're just doing a regular playback of
> > > some kind - if that is the case I'd expect things to power up when you
> > > start playing through the DAC.
> 
> > No, its Vibra PWM controller no playback here
> 
> So the DAC gets its input from some internal source?  In that case that
> source maps very directly onto the input widget.
Yes the Vibra PWM controller should be treated as source. ahhhh, this
sounds so obvious in hindsight...

Thanks
-- 
~Vinod