From: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>
To: Pavan Savoy <pavan_savoy@sify.com>
Cc: Lucas De Marchi <lucas.demarchi@profusion.mobi>,
linux-bluetooth@vger.kernel.org
Subject: Re: AVRCPv1.3 NOTIFY from CT per notification from TG
Date: Sun, 22 Jul 2012 12:11:02 +0300 [thread overview]
Message-ID: <CACumGOJ==Ca2C9xRvYFMPio3ospNWf+0erO8MemgZrfcDTDCcA@mail.gmail.com> (raw)
In-Reply-To: <CABUK1aht5D2zW7wW22QaLLJWOkBpD9B+pK9aU_rcYkFByFYZyA@mail.gmail.com>
Hi Pavan
On Sun, Jul 22, 2012 at 5:07 AM, Pavan Savoy <pavan_savoy@sify.com> wrote:
> Now, I am interested to know whether the "Playing" needs to be
> displayed or something like "Paused" along with another bit of info,
> which is My-Song.
> So, say to begin with I register for track-changed notification, now
> to read the attributes of song again, but If I have to display
> "Paused" then I will have to register for "Play Status" & I can get
> only 1 of them at a time ?
You can register multiple events simultaneously, the only problem is
that you need to register again every time it changes. Apparently this
idea of registration not being persistent came from AV/C spec, while
doing support for VolumeChanged event I actually step in it see patch:
AVRCP: Fix not registering to VolumeChanged event again when notified
Its pretty broken design if you ask me, but one that we have to live with...
prev parent reply other threads:[~2012-07-22 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 20:39 AVRCPv1.3 NOTIFY from CT per notification from TG Pavan Savoy
2012-07-21 16:45 ` Lucas De Marchi
2012-07-22 2:07 ` Pavan Savoy
2012-07-22 9:11 ` Von Dentz, Luiz [this message]
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='CACumGOJ==Ca2C9xRvYFMPio3ospNWf+0erO8MemgZrfcDTDCcA@mail.gmail.com' \
--to=luiz.von.dentz@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=pavan_savoy@sify.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 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).