Linux-Bluetooth Archive on lore.kernel.org
 help / color / Atom feed
* bluez A2DP socket reliability
@ 2019-05-18 19:06 Pali Rohár
  2019-05-19  8:13 ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 9+ messages in thread
From: Pali Rohár @ 2019-05-18 19:06 UTC (permalink / raw)
  To: linux-bluetooth

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
transfer configured in bluez? It is reliable with big/infinite
retransmit count? Or in best-effort manner and some packets may be
dropped? And it is possible to change between these two modes for
application which uses bluez DBUS API? I'm asking because some A2DP
audio codecs are designed to deal with packet loss and for those codecs
it would be probably better to configure L2CAP socket to unreliable
mode.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-05-18 19:06 bluez A2DP socket reliability Pali Rohár
@ 2019-05-19  8:13 ` Luiz Augusto von Dentz
  2019-05-19 12:22   ` Pali Rohár
  0 siblings, 1 reply; 9+ messages in thread
From: Luiz Augusto von Dentz @ 2019-05-19  8:13 UTC (permalink / raw)
  To: Pali Rohár; +Cc: linux-bluetooth

Hi Pali,

On Sat, May 18, 2019 at 11:12 PM Pali Rohár <pali.rohar@gmail.com> wrote:
>
> Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
> transfer configured in bluez? It is reliable with big/infinite
> retransmit count? Or in best-effort manner and some packets may be
> dropped? And it is possible to change between these two modes for
> application which uses bluez DBUS API? I'm asking because some A2DP
> audio codecs are designed to deal with packet loss and for those codecs
> it would be probably better to configure L2CAP socket to unreliable
> mode.

We don't use ERTM with AVDTP, both signaling and transport sockets are
using basic mode which don't support retransmissions, there the
concept of flush timeout which iirc we don't currently it.


-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-05-19  8:13 ` Luiz Augusto von Dentz
@ 2019-05-19 12:22   ` Pali Rohár
  2019-06-07 13:00     ` Pali Rohár
  0 siblings, 1 reply; 9+ messages in thread
From: Pali Rohár @ 2019-05-19 12:22 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: linux-bluetooth

[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]

On Sunday 19 May 2019 11:13:09 Luiz Augusto von Dentz wrote:
> Hi Pali,
> 
> On Sat, May 18, 2019 at 11:12 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> >
> > Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
> > transfer configured in bluez? It is reliable with big/infinite
> > retransmit count? Or in best-effort manner and some packets may be
> > dropped? And it is possible to change between these two modes for
> > application which uses bluez DBUS API? I'm asking because some A2DP
> > audio codecs are designed to deal with packet loss and for those codecs
> > it would be probably better to configure L2CAP socket to unreliable
> > mode.
> 
> We don't use ERTM with AVDTP, both signaling and transport sockets are
> using basic mode which don't support retransmissions, there the
> concept of flush timeout which iirc we don't currently it.

On bluez.org site there is no information how to use bluez sockets and
the only documentation/tutorial which I found on internet was this:

  https://people.csail.mit.edu/albert/bluez-intro/x559.html

I do not know how up-to-date it is, but seems that by default bluez
L2CAP sockets are reliable and to change them to unreliable mode it is
needed to issue OGF_HOST_CTL / OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT (0x28)
request. As default is zero = infinity = reliable connection.

I do not understand low level bluetooth details, but is ERTM related to
OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT?

So what are default settings for L2CAP socket used by AVDTP/A2DP
profiles which are transferred to user application via DBUS?

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-05-19 12:22   ` Pali Rohár
@ 2019-06-07 13:00     ` Pali Rohár
  2019-06-07 15:23       ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 9+ messages in thread
From: Pali Rohár @ 2019-06-07 13:00 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: linux-bluetooth

On Sunday 19 May 2019 14:22:23 Pali Rohár wrote:
> On Sunday 19 May 2019 11:13:09 Luiz Augusto von Dentz wrote:
> > Hi Pali,
> > 
> > On Sat, May 18, 2019 at 11:12 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> > >
> > > Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
> > > transfer configured in bluez? It is reliable with big/infinite
> > > retransmit count? Or in best-effort manner and some packets may be
> > > dropped? And it is possible to change between these two modes for
> > > application which uses bluez DBUS API? I'm asking because some A2DP
> > > audio codecs are designed to deal with packet loss and for those codecs
> > > it would be probably better to configure L2CAP socket to unreliable
> > > mode.
> > 
> > We don't use ERTM with AVDTP, both signaling and transport sockets are
> > using basic mode which don't support retransmissions, there the
> > concept of flush timeout which iirc we don't currently it.
> 
> On bluez.org site there is no information how to use bluez sockets and
> the only documentation/tutorial which I found on internet was this:
> 
>   https://people.csail.mit.edu/albert/bluez-intro/x559.html
> 
> I do not know how up-to-date it is, but seems that by default bluez
> L2CAP sockets are reliable and to change them to unreliable mode it is
> needed to issue OGF_HOST_CTL / OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT (0x28)
> request. As default is zero = infinity = reliable connection.
> 
> I do not understand low level bluetooth details, but is ERTM related to
> OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT?
> 
> So what are default settings for L2CAP socket used by AVDTP/A2DP
> profiles which are transferred to user application via DBUS?

Hi! Do you have any idea about OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT? It is
related to ERTM or not?

-- 
Pali Rohár
pali.rohar@gmail.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-06-07 13:00     ` Pali Rohár
@ 2019-06-07 15:23       ` Luiz Augusto von Dentz
  2019-06-10 10:51         ` Pali Rohár
  0 siblings, 1 reply; 9+ messages in thread
From: Luiz Augusto von Dentz @ 2019-06-07 15:23 UTC (permalink / raw)
  To: Pali Rohár; +Cc: linux-bluetooth

Hi Pali,

On Fri, Jun 7, 2019 at 4:00 PM Pali Rohár <pali.rohar@gmail.com> wrote:
>
> On Sunday 19 May 2019 14:22:23 Pali Rohár wrote:
> > On Sunday 19 May 2019 11:13:09 Luiz Augusto von Dentz wrote:
> > > Hi Pali,
> > >
> > > On Sat, May 18, 2019 at 11:12 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> > > >
> > > > Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
> > > > transfer configured in bluez? It is reliable with big/infinite
> > > > retransmit count? Or in best-effort manner and some packets may be
> > > > dropped? And it is possible to change between these two modes for
> > > > application which uses bluez DBUS API? I'm asking because some A2DP
> > > > audio codecs are designed to deal with packet loss and for those codecs
> > > > it would be probably better to configure L2CAP socket to unreliable
> > > > mode.
> > >
> > > We don't use ERTM with AVDTP, both signaling and transport sockets are
> > > using basic mode which don't support retransmissions, there the
> > > concept of flush timeout which iirc we don't currently it.
> >
> > On bluez.org site there is no information how to use bluez sockets and
> > the only documentation/tutorial which I found on internet was this:
> >
> >   https://people.csail.mit.edu/albert/bluez-intro/x559.html
> >
> > I do not know how up-to-date it is, but seems that by default bluez
> > L2CAP sockets are reliable and to change them to unreliable mode it is
> > needed to issue OGF_HOST_CTL / OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT (0x28)
> > request. As default is zero = infinity = reliable connection.
> >
> > I do not understand low level bluetooth details, but is ERTM related to
> > OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT?
> >
> > So what are default settings for L2CAP socket used by AVDTP/A2DP
> > profiles which are transferred to user application via DBUS?
>
> Hi! Do you have any idea about OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT? It is
> related to ERTM or not?

The OCF usually describes an HCI command which may affect the entire
ACL connection, ERTM is a L2CAP channel mode that includes
retransmissions. The A2DP stream transport doesn't ERTM so no
retransmissions shall take place.

-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-06-07 15:23       ` Luiz Augusto von Dentz
@ 2019-06-10 10:51         ` Pali Rohár
  2019-06-10 12:16           ` Luiz Augusto von Dentz
  2019-06-10 16:06           ` Frédéric Danis
  0 siblings, 2 replies; 9+ messages in thread
From: Pali Rohár @ 2019-06-10 10:51 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: linux-bluetooth

On Friday 07 June 2019 18:23:41 Luiz Augusto von Dentz wrote:
> Hi Pali,
> 
> On Fri, Jun 7, 2019 at 4:00 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> >
> > On Sunday 19 May 2019 14:22:23 Pali Rohár wrote:
> > > On Sunday 19 May 2019 11:13:09 Luiz Augusto von Dentz wrote:
> > > > Hi Pali,
> > > >
> > > > On Sat, May 18, 2019 at 11:12 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> > > > >
> > > > > Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
> > > > > transfer configured in bluez? It is reliable with big/infinite
> > > > > retransmit count? Or in best-effort manner and some packets may be
> > > > > dropped? And it is possible to change between these two modes for
> > > > > application which uses bluez DBUS API? I'm asking because some A2DP
> > > > > audio codecs are designed to deal with packet loss and for those codecs
> > > > > it would be probably better to configure L2CAP socket to unreliable
> > > > > mode.
> > > >
> > > > We don't use ERTM with AVDTP, both signaling and transport sockets are
> > > > using basic mode which don't support retransmissions, there the
> > > > concept of flush timeout which iirc we don't currently it.
> > >
> > > On bluez.org site there is no information how to use bluez sockets and
> > > the only documentation/tutorial which I found on internet was this:
> > >
> > >   https://people.csail.mit.edu/albert/bluez-intro/x559.html
> > >
> > > I do not know how up-to-date it is, but seems that by default bluez
> > > L2CAP sockets are reliable and to change them to unreliable mode it is
> > > needed to issue OGF_HOST_CTL / OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT (0x28)
> > > request. As default is zero = infinity = reliable connection.
> > >
> > > I do not understand low level bluetooth details, but is ERTM related to
> > > OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT?
> > >
> > > So what are default settings for L2CAP socket used by AVDTP/A2DP
> > > profiles which are transferred to user application via DBUS?
> >
> > Hi! Do you have any idea about OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT? It is
> > related to ERTM or not?
> 
> The OCF usually describes an HCI command which may affect the entire
> ACL connection, ERTM is a L2CAP channel mode that includes
> retransmissions. The A2DP stream transport doesn't ERTM so no
> retransmissions shall take place.

Fine, no retransmission is good for A2DP.

And how it is with delivering packets? It is possible that may be
delivered to other side in wrong order?

-- 
Pali Rohár
pali.rohar@gmail.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-06-10 10:51         ` Pali Rohár
@ 2019-06-10 12:16           ` Luiz Augusto von Dentz
  2019-06-10 16:06           ` Frédéric Danis
  1 sibling, 0 replies; 9+ messages in thread
From: Luiz Augusto von Dentz @ 2019-06-10 12:16 UTC (permalink / raw)
  To: Pali Rohár; +Cc: linux-bluetooth

Hi Pali,

On Mon, Jun 10, 2019 at 1:51 PM Pali Rohár <pali.rohar@gmail.com> wrote:
>
> On Friday 07 June 2019 18:23:41 Luiz Augusto von Dentz wrote:
> > Hi Pali,
> >
> > On Fri, Jun 7, 2019 at 4:00 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> > >
> > > On Sunday 19 May 2019 14:22:23 Pali Rohár wrote:
> > > > On Sunday 19 May 2019 11:13:09 Luiz Augusto von Dentz wrote:
> > > > > Hi Pali,
> > > > >
> > > > > On Sat, May 18, 2019 at 11:12 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> > > > > >
> > > > > > Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
> > > > > > transfer configured in bluez? It is reliable with big/infinite
> > > > > > retransmit count? Or in best-effort manner and some packets may be
> > > > > > dropped? And it is possible to change between these two modes for
> > > > > > application which uses bluez DBUS API? I'm asking because some A2DP
> > > > > > audio codecs are designed to deal with packet loss and for those codecs
> > > > > > it would be probably better to configure L2CAP socket to unreliable
> > > > > > mode.
> > > > >
> > > > > We don't use ERTM with AVDTP, both signaling and transport sockets are
> > > > > using basic mode which don't support retransmissions, there the
> > > > > concept of flush timeout which iirc we don't currently it.
> > > >
> > > > On bluez.org site there is no information how to use bluez sockets and
> > > > the only documentation/tutorial which I found on internet was this:
> > > >
> > > >   https://people.csail.mit.edu/albert/bluez-intro/x559.html
> > > >
> > > > I do not know how up-to-date it is, but seems that by default bluez
> > > > L2CAP sockets are reliable and to change them to unreliable mode it is
> > > > needed to issue OGF_HOST_CTL / OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT (0x28)
> > > > request. As default is zero = infinity = reliable connection.
> > > >
> > > > I do not understand low level bluetooth details, but is ERTM related to
> > > > OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT?
> > > >
> > > > So what are default settings for L2CAP socket used by AVDTP/A2DP
> > > > profiles which are transferred to user application via DBUS?
> > >
> > > Hi! Do you have any idea about OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT? It is
> > > related to ERTM or not?
> >
> > The OCF usually describes an HCI command which may affect the entire
> > ACL connection, ERTM is a L2CAP channel mode that includes
> > retransmissions. The A2DP stream transport doesn't ERTM so no
> > retransmissions shall take place.
>
> Fine, no retransmission is good for A2DP.
>
> And how it is with delivering packets? It is possible that may be
> delivered to other side in wrong order?

It is a single hop with guaranteed ordering at L2CAP channel, you can
control the priority on a per socket manner but afaik PA is already
setting that to high priority which helps when dealing with
congestions due to other traffic like OBEX, etc.

-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-06-10 10:51         ` Pali Rohár
  2019-06-10 12:16           ` Luiz Augusto von Dentz
@ 2019-06-10 16:06           ` Frédéric Danis
  2019-06-14  7:16             ` Pali Rohár
  1 sibling, 1 reply; 9+ messages in thread
From: Frédéric Danis @ 2019-06-10 16:06 UTC (permalink / raw)
  To: Pali Rohár, Luiz Augusto von Dentz; +Cc: linux-bluetooth

Hi,

Le 10/06/2019 à 12:51, Pali Rohár a écrit :
> On Friday 07 June 2019 18:23:41 Luiz Augusto von Dentz wrote:
>> Hi Pali,
>>
>> On Fri, Jun 7, 2019 at 4:00 PM Pali Rohár<pali.rohar@gmail.com>  wrote:
>>> On Sunday 19 May 2019 14:22:23 Pali Rohár wrote:
>>>> On Sunday 19 May 2019 11:13:09 Luiz Augusto von Dentz wrote:
>>>>> Hi Pali,
>>>>>
>>>>> On Sat, May 18, 2019 at 11:12 PM Pali Rohár<pali.rohar@gmail.com>  wrote:
>>>>>> Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
>>>>>> transfer configured in bluez? It is reliable with big/infinite
>>>>>> retransmit count? Or in best-effort manner and some packets may be
>>>>>> dropped? And it is possible to change between these two modes for
>>>>>> application which uses bluez DBUS API? I'm asking because some A2DP
>>>>>> audio codecs are designed to deal with packet loss and for those codecs
>>>>>> it would be probably better to configure L2CAP socket to unreliable
>>>>>> mode.
>>>>> We don't use ERTM with AVDTP, both signaling and transport sockets are
>>>>> using basic mode which don't support retransmissions, there the
>>>>> concept of flush timeout which iirc we don't currently it.
>>>> On bluez.org site there is no information how to use bluez sockets and
>>>> the only documentation/tutorial which I found on internet was this:
>>>>
>>>>    https://people.csail.mit.edu/albert/bluez-intro/x559.html
>>>>
>>>> I do not know how up-to-date it is, but seems that by default bluez
>>>> L2CAP sockets are reliable and to change them to unreliable mode it is
>>>> needed to issue OGF_HOST_CTL / OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT (0x28)
>>>> request. As default is zero = infinity = reliable connection.
>>>>
>>>> I do not understand low level bluetooth details, but is ERTM related to
>>>> OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT?
>>>>
>>>> So what are default settings for L2CAP socket used by AVDTP/A2DP
>>>> profiles which are transferred to user application via DBUS?
>>> Hi! Do you have any idea about OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT? It is
>>> related to ERTM or not?
>> The OCF usually describes an HCI command which may affect the entire
>> ACL connection, ERTM is a L2CAP channel mode that includes
>> retransmissions. The A2DP stream transport doesn't ERTM so no
>> retransmissions shall take place.
> Fine, no retransmission is good for A2DP.

I am not sure there is no retransmission with current implementation.
AFAIU, ERTM and automatic flush timeout are not linked. ERTM operates at 
L2CAP level while automatic flush timeout [1] operates at ACL level.
When I read the automatic flush timeout set for an A2DP SBC connection 
it returns 0, which means that the connection uses an infinite timeout. 
So, even if higher levels set packets as flushable, the ACL policy 
requests baseband to indefinitely try to send data [3]:
   "The default Flush Timeout shall be infinite,
     i.e. re-transmissions are carried out until
     physical link loss occurs. This is also
     referred to as a 'reliable channel.'"

[1] Bluetooth core Vol 2, Part E, 6.19
[2] Bluetooth core Vol 2, Part E, 7.3.29
[3] Bluetooth core Vol 2, Part B, 7.6.3

-- 
Frédéric Danis                       Embedded Linux Consultant
frederic.danis.oss@gmail.com


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: bluez A2DP socket reliability
  2019-06-10 16:06           ` Frédéric Danis
@ 2019-06-14  7:16             ` Pali Rohár
  0 siblings, 0 replies; 9+ messages in thread
From: Pali Rohár @ 2019-06-14  7:16 UTC (permalink / raw)
  To: Frédéric Danis; +Cc: Luiz Augusto von Dentz, linux-bluetooth

On Monday 10 June 2019 18:06:53 Frédéric Danis wrote:
> Hi,
> 
> Le 10/06/2019 à 12:51, Pali Rohár a écrit :
> > On Friday 07 June 2019 18:23:41 Luiz Augusto von Dentz wrote:
> > > Hi Pali,
> > > 
> > > On Fri, Jun 7, 2019 at 4:00 PM Pali Rohár<pali.rohar@gmail.com>  wrote:
> > > > On Sunday 19 May 2019 14:22:23 Pali Rohár wrote:
> > > > > On Sunday 19 May 2019 11:13:09 Luiz Augusto von Dentz wrote:
> > > > > > Hi Pali,
> > > > > > 
> > > > > > On Sat, May 18, 2019 at 11:12 PM Pali Rohár<pali.rohar@gmail.com>  wrote:
> > > > > > > Hello! How is L2CAP layer of bluetooth socket used for A2DP audio
> > > > > > > transfer configured in bluez? It is reliable with big/infinite
> > > > > > > retransmit count? Or in best-effort manner and some packets may be
> > > > > > > dropped? And it is possible to change between these two modes for
> > > > > > > application which uses bluez DBUS API? I'm asking because some A2DP
> > > > > > > audio codecs are designed to deal with packet loss and for those codecs
> > > > > > > it would be probably better to configure L2CAP socket to unreliable
> > > > > > > mode.
> > > > > > We don't use ERTM with AVDTP, both signaling and transport sockets are
> > > > > > using basic mode which don't support retransmissions, there the
> > > > > > concept of flush timeout which iirc we don't currently it.
> > > > > On bluez.org site there is no information how to use bluez sockets and
> > > > > the only documentation/tutorial which I found on internet was this:
> > > > > 
> > > > >    https://people.csail.mit.edu/albert/bluez-intro/x559.html
> > > > > 
> > > > > I do not know how up-to-date it is, but seems that by default bluez
> > > > > L2CAP sockets are reliable and to change them to unreliable mode it is
> > > > > needed to issue OGF_HOST_CTL / OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT (0x28)
> > > > > request. As default is zero = infinity = reliable connection.
> > > > > 
> > > > > I do not understand low level bluetooth details, but is ERTM related to
> > > > > OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT?
> > > > > 
> > > > > So what are default settings for L2CAP socket used by AVDTP/A2DP
> > > > > profiles which are transferred to user application via DBUS?
> > > > Hi! Do you have any idea about OCF_WRITE_AUTOMATIC_FLUSH_TIMEOUT? It is
> > > > related to ERTM or not?
> > > The OCF usually describes an HCI command which may affect the entire
> > > ACL connection, ERTM is a L2CAP channel mode that includes
> > > retransmissions. The A2DP stream transport doesn't ERTM so no
> > > retransmissions shall take place.
> > Fine, no retransmission is good for A2DP.
> 
> I am not sure there is no retransmission with current implementation.
> AFAIU, ERTM and automatic flush timeout are not linked. ERTM operates at
> L2CAP level while automatic flush timeout [1] operates at ACL level.
> When I read the automatic flush timeout set for an A2DP SBC connection it
> returns 0, which means that the connection uses an infinite timeout. So,
> even if higher levels set packets as flushable, the ACL policy requests
> baseband to indefinitely try to send data [3]:
>   "The default Flush Timeout shall be infinite,
>     i.e. re-transmissions are carried out until
>     physical link loss occurs. This is also
>     referred to as a 'reliable channel.'"
> 
> [1] Bluetooth core Vol 2, Part E, 6.19
> [2] Bluetooth core Vol 2, Part E, 7.3.29
> [3] Bluetooth core Vol 2, Part B, 7.6.3

Mhm... I feeling quite lost. Is A2DP socket reliable with enabled
retransmission or not?

-- 
Pali Rohár
pali.rohar@gmail.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, back to index

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-18 19:06 bluez A2DP socket reliability Pali Rohár
2019-05-19  8:13 ` Luiz Augusto von Dentz
2019-05-19 12:22   ` Pali Rohár
2019-06-07 13:00     ` Pali Rohár
2019-06-07 15:23       ` Luiz Augusto von Dentz
2019-06-10 10:51         ` Pali Rohár
2019-06-10 12:16           ` Luiz Augusto von Dentz
2019-06-10 16:06           ` Frédéric Danis
2019-06-14  7:16             ` Pali Rohár

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox