From: Clemens Ladisch <clemens@ladisch.de>
To: kshemanth.vasireddi@wipro.com
Cc: alsa-devel@alsa-project.org
Subject: Re: Copy call back for capture substream
Date: Thu, 28 Apr 2011 11:29:45 +0200 [thread overview]
Message-ID: <4DB93389.3060103@ladisch.de> (raw)
In-Reply-To: <A3D770027F3D024D8AA74E0D0C630813030CA7E7@PNE-HJN-MBX02.wipro.com>
kshemanth.vasireddi@wipro.com wrote:
> I had registered a copy call back.
>
> all call backs are invoked, but copy call back is not
> getting invoked. Can you please let me know when will copy call back
> shall be invoked, is there any condition for it.
It's right there in the source code.
The copy callback is called exactly when in the same circumstances when
the data of a 'normal' driver would be copied out of the device's
buffer, i.e., when some data is available.
I'd guess that your pointer callback does not return the correct values.
> The information contained in this electronic message ...
This e-mail contains public information intended for any subscriber of
this mailing list and for anybody else who bothers to read it; it will
be copied, disclosed and distributed to the public. If you think you
are not the intended recipient, please commit suicide immediately.
These terms apply also to any e-mails quoted in, referenced from, or
answering this e-mail, and supersede any confidentiality notices in
those e-mails. Additionally, confidentiality notices in those e-mails
will incur legal processing fees of $42 per line; you have agreed to
this by reading this confidentiality notice.
Regards,
Clemens
next prev parent reply other threads:[~2011-04-28 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 9:04 Copy call back for capture substream kshemanth.vasireddi
2011-04-28 9:29 ` Clemens Ladisch [this message]
2011-04-29 10:51 ` kshemanth.vasireddi
2011-04-29 15:22 ` Clemens Ladisch
2011-05-02 11:17 ` kshemanth.vasireddi
2011-05-02 12:42 ` Clemens Ladisch
2011-05-03 6:03 ` kshemanth.vasireddi
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=4DB93389.3060103@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=kshemanth.vasireddi@wipro.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.