Return-Path: MIME-Version: 1.0 In-Reply-To: References: From: Alfonso Acosta Date: Mon, 8 Jan 2018 10:32:04 +0100 Message-ID: Subject: Re: Overhead reduction in LE connection establishment To: Jamie Mccrae Cc: "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Jamie, >>For the application=E2=80=99s purpose, it=E2=80=99s critical that the not= ification is recieved with the minimum latency. > > Is there any reason why you wish to have the button in a disconnected sta= te when inactive over having it in a connected state but with a high connec= tion interval and a large slave latency? A high slave latency means it can = stay in sleep mode if there is nothing to report back to the central device= for a specified number of packets so is perfect for battery powered device= s. The only reason is: very high expectations of battery life. I recall we played with the slave latency in the past, but we will reevaluate and see if it's a feasible option. Thanks for the suggestion. Regardless, I am still curious to know if disconnecting and sending the notification right away (as Luiz suggests) isn't racy with respect to StartNotify().