From: Marcel Holtmann <marcel@holtmann.org>
To: Alfonso Acosta <fons@spotify.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: Add HCI_AUTO_CONN_DIRECT_REPORT_IND
Date: Mon, 29 Sep 2014 10:37:19 +0200 [thread overview]
Message-ID: <24D2CD11-D43B-4F53-8A7C-175934A54C87@holtmann.org> (raw)
In-Reply-To: <1411746855-9936-1-git-send-email-fons@spotify.com>
Hi Alfonso,
> HCI_AUTO_CONN_DIRECT_REPORT_IND (associated to a new autoconnect
> action, 0x03) treats advertising reports like a combination of
> HCI_AUTO_CONN_DIRECT and HCI_AUTO_CONN_REPORT:
>
> * Autoconnects on ADV_DIRECT_IND reports.
> * Notifies userland (MGMT_EV_DEVICE_FOUND) about ADV_IND reports.
>
> This is useful to communicate with autoconnectable devices which
> advertise meaningful ADV_IND reports.
>
> HCI_AUTO_CONN_DIRECT_REPORT_IND requires being able to simultaneously
> have a pending report and connection action. I merged pend_le_reports
> and pend_le_conns into the new pend_le_actions in order to make that
> possible while maintaining a unique list_head in hci_conn_parameters
> (action). This results in simpler handling of pending actions.
I am not really convinced that this is a good idea. In general either you really want Action 0x01 and only accept incoming connection or you want Action 0x02 and connect to the device no matter what.
Originally I had the idea that the advertising data that you receive from ADV_IND when Action 0x02 is in play gets also included in Device Connected event. My thinking there was that the Service Data might have changed and it would be useful to know ahead of time before starting any GATT procedures. However then it seems that was not really useful after all and I stopped considering it. Maybe this idea needs to be picked up again.
Regards
Marcel
next prev parent reply other threads:[~2014-09-29 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:54 [PATCH v3] Bluetooth: Add HCI_AUTO_CONN_DIRECT_REPORT_IND Alfonso Acosta
2014-09-29 8:37 ` Marcel Holtmann [this message]
2014-09-29 10:59 ` Alfonso Acosta
2014-09-29 11:34 ` Marcel Holtmann
2014-09-29 13:33 ` Alfonso Acosta
2014-09-29 14:29 ` Marcel Holtmann
2014-09-29 14:49 ` Alfonso Acosta
2014-09-29 14:54 ` Marcel Holtmann
2014-10-03 8:37 ` Alfonso Acosta
2014-10-03 9:55 ` Marcel Holtmann
2014-10-09 1:01 ` Alfonso Acosta
2014-09-29 14:35 ` Johan Hedberg
2014-09-29 15:25 ` Alfonso Acosta
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=24D2CD11-D43B-4F53-8A7C-175934A54C87@holtmann.org \
--to=marcel@holtmann.org \
--cc=fons@spotify.com \
--cc=linux-bluetooth@vger.kernel.org \
/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.