Dear All, The GATT client interface (bt_gatt_client.h) has API's like listen (for start\stop advetisement) as well as Multi adv enable\disable\data set API's (although Multi Adv api'S are not currently supported) Although, GAP peripheral\central roles are not tied to GATT server\CLient roles, but it seems as per HAL interface, an application implementing GATT server role by using HAL Gatt server interface, can not do advertising, whereas, an application implementing GAP client role can by using listen() API? Normally it is GATT server which hosts services and does advertisement and eventually listens to incoming connection. Therefore, is the above design of API's has some specific meaning in the bluedroid stack context? Please help me understand. Apart from above, the advertisement related fucntions are LE adapter specific and ideAlly should be separated from GATT interfaces Perhaps, the upstream AOSP project has already separated out the LE Adv functionalities except the listen() function which is still present in GATT client interface explained above. Do we have any plan to separate them out in near future for BFA? Thank You in advance for your valuable inputs. BR, -Anupam Roy Signed-off-by: Anupam Roy <anupam.r@xxxxxxxxxxx> --- mail | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 mail diff --git a/mail b/mail new file mode 100644 index 0000000..e69de29 -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
