Re: [PATCH v2] gatt: Delay D-Bus reply on char discovery

[Chen Ganir <chen.ganir@ti.com>]

Anderson,
On 09/11/2012 03:27 PM, Anderson Lizardo wrote:
> Hi Chen,
>
> On Tue, Sep 11, 2012 at 8:22 AM, Chen Ganir <chen.ganir@ti.com> wrote:
>> The plan is to replace characteristic::format, and add CCC, SCC and any
>> other descriptor we find in the future to this list. This way we have a
>> unified list of descriptors and the data contained in them. This is already
>> done in some patches i already have, which rely on this patch. Next patch
>> set includes notification/indication implementation to the D-Bus API (Auto
>> registration to notification/indication if CCC is found).
>
> Do you have patches ready for adding CCC support on GATT D-Bus API ?
> Are you planning to send soon to the list, or could send it as RFC?
>
> Best Regards,
>
I already have those patches running. Some cleanup is still needed, and 
this patch also needs to be upstreamed.

Basically what i did was discover the CCC, SCC and extended properties. 
I save them (current value and handle) in the descriptor list. Once the 
entire characteristic range is discovered, and a watcher is registered, 
i check the characteristic properties and cross it with the availability 
of the CCC. Then, i try to automatically enable indication or 
notification according to the characteristic properties.

when the watcher is abandoned or unregistered, i unset the 
notification/indication for all the characters of that service.

In addition, i plan to add a property called "Broadcast" which will be 
read/write, and it will set/get the SCC descriptor of the char.



-- 
BR,
Chen Ganir