From: "Pali Rohár" <pali@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>,
"David Heidelberg" <david@ixit.cz>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Undocumented property "DelayReporting" (Was: Re: [PATCH BlueZ 1/4] doc/media-api: Add RegisterApplication method)
Date: Wed, 15 Apr 2020 01:07:05 +0200 [thread overview]
Message-ID: <20200414230705.7cwffdkal34efyag@pali> (raw)
In-Reply-To: <20191114112753.4h7xifkvpjpzgm7x@pali>
On Thursday 14 November 2019 12:27:53 Pali Rohár wrote:
> On Wednesday 09 October 2019 15:20:40 Pali Rohár wrote:
> > On Sunday 06 October 2019 14:02:45 Pali Rohár wrote:
> > > On Sunday 06 October 2019 13:53:37 Luiz Augusto von Dentz wrote:
> > > > Hi Pali,
> > > >
> > > > It is just another D-Bus method, the only difference is that it
> > > > carries the entire object tree, btw I did add an example of how to
> > > > register Endpoints in python:
> > > >
> > > > https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/test/example-endpoint
> > >
> > > This example uses undocumented property "DelayReporting". What it is doing?
> >
> > And I would like to know what is that undocumented DelayReporting is
> > doing? And to which value should I initialize it in pulseaudio?
>
> Luiz, any comments on this?
Luiz, could you please tell me some information about this undocumented
property to which value should I set it? I really need it for proper
implementation of endpoints in pulseaudio.
I was not able to decode its meaning from source code nor found any
other information about it.
prev parent reply other threads:[~2020-04-14 23:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 15:13 [PATCH BlueZ 1/4] doc/media-api: Add RegisterApplication method Luiz Augusto von Dentz
2019-07-12 15:13 ` [PATCH BlueZ 2/4] media: Add implementation of RegisterApplication Luiz Augusto von Dentz
2019-07-12 15:13 ` [PATCH BlueZ 3/4] test: Add example-endpoint Luiz Augusto von Dentz
2019-07-12 15:13 ` [PATCH BlueZ 4/4] test: Add example-player Luiz Augusto von Dentz
2019-07-13 14:52 ` [PATCH BlueZ 1/4] doc/media-api: Add RegisterApplication method Luiz Augusto von Dentz
2019-07-18 10:00 ` Pali Rohár
2019-07-21 15:55 ` Pali Rohár
2019-08-10 6:54 ` Luiz Augusto von Dentz
2019-08-29 12:57 ` Pasi Kärkkäinen
2019-08-29 20:05 ` Pali Rohár
2019-10-03 18:18 ` Pasi Kärkkäinen
2019-10-06 10:05 ` Pali Rohár
2019-10-06 10:53 ` Luiz Augusto von Dentz
2019-10-06 10:56 ` Pali Rohár
2019-10-06 11:14 ` Luiz Augusto von Dentz
2019-10-06 11:17 ` Pali Rohár
2019-10-06 18:02 ` Pali Rohár
2019-10-06 12:02 ` Pali Rohár
2019-10-07 14:33 ` Pali Rohár
2019-10-08 10:28 ` Luiz Augusto von Dentz
2019-10-08 10:33 ` Pali Rohár
2019-10-09 13:15 ` Luiz Augusto von Dentz
2019-10-09 13:19 ` Pali Rohár
2019-10-17 9:59 ` Pali Rohár
2019-10-18 8:37 ` Pasi Kärkkäinen
2019-10-18 10:55 ` Luiz Augusto von Dentz
2019-10-18 11:30 ` Pali Rohár
2019-10-09 13:20 ` Pali Rohár
2019-11-14 11:27 ` Pali Rohár
2020-04-14 23:07 ` Pali Rohár [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=20200414230705.7cwffdkal34efyag@pali \
--to=pali@kernel.org \
--cc=david@ixit.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pasik@iki.fi \
/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