From: sudarshan bisht <bisht.sudarshan@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA Mixer issue
Date: Tue, 3 Aug 2010 10:35:22 +0300 [thread overview]
Message-ID: <AANLkTi=QOc3_9SnKSD_ethGS+eTG8vEorUFn=yencSD1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinG4CJi5k1DqJFNneDk+7Crk+k7zp+evPuFEPdQ@mail.gmail.com>
Thanks Jaroslav ,
It works for me !!!
On Fri, Jul 30, 2010 at 5:36 PM, sudarshan bisht
<bisht.sudarshan@gmail.com>wrote:
> Thanks for the reply , I will try the same soon .
>
> On Fri, Jul 30, 2010 at 7:00 PM, Jaroslav Kysela <perex@perex.cz> wrote:
>
>> On Fri, 30 Jul 2010, sudarshan bisht wrote:
>>
>> Hi ,
>>>
>>> I wanted to know that can we use multiple handlers for the same ALSA
>>> mixer ?
>>>
>>> My use case is something like this .
>>>
>>> I have two modules and having two different handlers for ALSA mixer.
>>> First
>>> module does some volume change , and I try to read the latest volume
>>> using
>>> my second handler ( of first second module) .
>>>
>>> But I am not getting the most recent value in second handler ( the volume
>>> set by the first module ) so I feel there is some inconsistency when I
>>> use
>>> two handlers from two different modules in order to fetch volume
>>> information
>>> from the ALSA mixer.
>>>
>>
>> You must sync the cached information using poll() or select() on file
>> descriptors returned by snd_mixer_poll_descriptors_*() functions and call
>> snd_mixer_handle_events() if any events are waiting.
>>
>> Jaroslav
>>
>> -----
>> Jaroslav Kysela <perex@perex.cz>
>> Linux Kernel Sound Maintainer
>> ALSA Project, Red Hat, Inc.
>>
>>
>
>
> --
> Regards,
>
> Sudarshan Bisht
>
--
Regards,
Sudarshan Bisht
next prev parent reply other threads:[~2010-08-03 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 13:23 ALSA Mixer issue sudarshan bisht
2010-07-30 13:30 ` Jaroslav Kysela
2010-07-30 14:36 ` sudarshan bisht
2010-08-03 7:35 ` sudarshan bisht [this message]
2010-08-06 8:05 ` sudarshan bisht
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='AANLkTi=QOc3_9SnKSD_ethGS+eTG8vEorUFn=yencSD1@mail.gmail.com' \
--to=bisht.sudarshan@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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;
as well as URLs for NNTP newsgroup(s).