[BlueZ,0/1] Adapter1.ConnectDevice

Message ID	20230728052506.582394-1-simon.mikuda@streamunlimited.com
Headers	show Return-Path: <linux-bluetooth-owner@vger.kernel.org> From: Simon Mikuda <simon.mikuda@streamunlimited.com> To: linux-bluetooth@vger.kernel.org Cc: Simon Mikuda <simon.mikuda@streamunlimited.com> Subject: [PATCH BlueZ 0/1] Adapter1.ConnectDevice Date: Fri, 28 Jul 2023 07:25:05 +0200 Message-Id: <20230728052506.582394-1-simon.mikuda@streamunlimited.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	Adapter1.ConnectDevice \| expand [BlueZ,0/1] Adapter1.ConnectDevice [BlueZ,1/1] adapter: Be able to use ConnectDevice for discovered devices

Message ID

20230728052506.582394-1-simon.mikuda@streamunlimited.com

Headers

From: Simon Mikuda <simon.mikuda@streamunlimited.com>
To: linux-bluetooth@vger.kernel.org
Cc: Simon Mikuda <simon.mikuda@streamunlimited.com>
Subject: [PATCH BlueZ 0/1] Adapter1.ConnectDevice
Date: Fri, 28 Jul 2023 07:25:05 +0200
Message-Id: <20230728052506.582394-1-simon.mikuda@streamunlimited.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Series

Adapter1.ConnectDevice | expand

Message

Simon Mikuda July 28, 2023, 5:25 a.m. UTC

I added some minor addition to documentation and also I tested calling
function via DBus in parallel to same device.

In both case of BR/EDR both DBus calls will be pending and they will
finish at same time when Page Timeout arrives or connection. I think
this can be considered as correct behaviour.

In case of LE first one will be pending and second one will get
"org.bluez.Error.Failed: Connect failed" immediately. Later first
one will timeout.

Simon Mikuda (1):
  adapter: Be able to use ConnectDevice for discovered devices

 doc/adapter-api.txt | 2 +-
 src/adapter.c       | 3 ---
 2 files changed, 1 insertion(+), 4 deletions(-)