Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: preetam <preetamsashankreddy@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/1] ASoC: core: cache index fix
Date: Sun, 07 Aug 2011 09:48:08 +0530	[thread overview]
Message-ID: <4E3E1200.1010808@gmail.com> (raw)
In-Reply-To: <4E3E1095.3090809@gmail.com>

On Sunday 07 August 2011 09:42 AM, preetam wrote:
> On Sunday 07 August 2011 08:32 AM, Mark Brown wrote:
>> On Sun, Aug 07, 2011 at 12:31:07AM +0530, preetam wrote:
>>
>> Don't start a new thread by replying to completely unrelated mails,
>> write a new mail to the list.
>>
>>> I am writing an SoC driver. I have the need to power up the Playback 
>>> and
>>> Capture parts of the device separately depending on the call to codec
>>> structure. How can I identify the stream as playback or capture in
>>> set_bias call back. It only gets a codec pointer and a state.
>> You can't.  You should be using DAPM for this, not set_bias_level().
> Then what is the ideal use case of set_bias_level ?
I am asking this because, I was using set_bias to enable the clocks to 
the DAC and ADC blocks. This device has two independednt clock sources 
for DAC and ADC blocks. I would like  to power up only one of them 
depending on which steam the calls are being made for. So do I do this?

  reply	other threads:[~2011-08-07  4:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 11:38 [PATCH 1/1] ASoC: core: cache index fix Dong Aisheng
2011-08-01 11:51 ` Mark Brown
2011-08-02  8:03   ` Dong Aisheng-B29396
2011-08-02  8:38     ` Mark Brown
2011-08-02  9:41       ` Dong Aisheng-B29396
2011-08-02 10:34         ` Takashi Iwai
2011-08-02 10:55           ` Dong Aisheng-B29396
2011-08-02 11:09             ` Takashi Iwai
2011-08-02 11:15               ` Dong Aisheng-B29396
2011-08-02 12:10                 ` Takashi Iwai
2011-08-02 12:29                   ` Dong Aisheng-B29396
2011-08-02 12:52                     ` Takashi Iwai
2011-08-02 15:48                       ` Mark Brown
2011-08-02 16:13                         ` Takashi Iwai
2011-08-02 16:40                           ` Mark Brown
2011-08-02 18:06                             ` Takashi Iwai
2011-08-03  5:23                               ` [alsa-devel] " Mark Brown
2011-08-03  6:20                                 ` Takashi Iwai
2011-08-03  9:00                                   ` Mark Brown
2011-08-03  7:03                                 ` Dong Aisheng-B29396
2011-08-03  7:39                             ` Dong Aisheng-B29396
2011-08-03  9:31                               ` Mark Brown
2011-08-03 11:11                                 ` Dong Aisheng-B29396
2011-08-06 19:01                         ` preetam
2011-08-07  3:02                           ` Mark Brown
2011-08-07  4:12                             ` preetam
2011-08-07  4:18                               ` preetam [this message]
2011-08-07  9:51                                 ` Mark Brown
2011-08-02 12:58           ` Mark Brown
2011-08-02 13:17         ` Dong Aisheng-B29396
2011-08-02 15:27           ` Mark Brown
2011-08-02 16:05         ` Mark Brown
2011-08-02  9:51       ` Wolfram Sang
2011-08-02 10:38         ` Takashi Iwai
2011-08-02 15:29         ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E3E1200.1010808@gmail.com \
    --to=preetamsashankreddy@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox