Hi, On Mon, Mar 5, 2018 at 1:41 PM, Jaganath K <jaganath.k.os@xxxxxxxxx> wrote: > Hi, > > On Fri, Feb 23, 2018 at 4:38 PM, Jaganath Kanakkassery > <jaganath.k.os@xxxxxxxxx> wrote: >> The patch set implements extended scanning and conection and use it >> based on the controller support. >> >> This also implements PHY configuration mgmt commands and events >> to set defualt PHY and PHYs to be used for scan and connect. >> >> One downside of this approch is user cannot force kernel to use >> legacy comands if controller is 5.0. >> >> Jaganath Kanakkassery (11): >> Bluetooth: Introduce helpers for LE set scan start and complete >> Bluetooth: Use extended scanning if controller supports >> Bluetooth: Process extended ADV report event >> Bluetooth: Introduce helpers for le conn status and complete >> Bluetooth: Use extended LE Connection if supported >> Bluetooth: Define PHY flags in hdev and set 1M as default >> Bluetooth: Implement Get PHY Configuration mgmt command >> Bluetooth: Implement Set PHY Confguration command >> Bluetooth: Set Scan PHYs based on selected PHYs by user >> Bluetooth: Handle extended ADV PDU types >> Bluetooth: Use selected PHYs in extended connect >> >> include/net/bluetooth/hci.h | 110 ++++++++++++ >> include/net/bluetooth/hci_core.h | 15 ++ >> include/net/bluetooth/mgmt.h | 31 ++++ >> net/bluetooth/hci_conn.c | 103 +++++++++-- >> net/bluetooth/hci_core.c | 17 ++ >> net/bluetooth/hci_event.c | 371 ++++++++++++++++++++++++++++++++------- >> net/bluetooth/hci_request.c | 156 +++++++++++----- >> net/bluetooth/hci_sock.c | 1 + >> net/bluetooth/mgmt.c | 231 ++++++++++++++++++++++++ >> 9 files changed, 914 insertions(+), 121 deletions(-) >> >> -- > > Ping. > > Thanks, > Jaganath Actually i need to fix data type issues in two of the patches reported by kbuild. I was just waiting if any comments are there so that i can incorporate it in the next patch. I will update it soon. Thanks, Jaganath -- 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
