Hi Manish, > This patch introduces new MGMT events to indicate that the controller > has started/stopped tracking a particular device matching one of the > already added Advertisement Monitor. > > --- > > Changes in v4: > - Add Advertisement Monitor Device Found event, make Address_Type 0 as > reserved. > > Changes in v3: > - Discard changes to the Device Found event and notify bluetoothd only > when the controller stops monitoring the device via new Device Lost > event. > > Changes in v2: > - Instead of creating a new 'Device Tracking' event, add a flag 'Device > Tracked' in the existing 'Device Found' event and add a new 'Device > Lost' event to indicate that the controller has stopped tracking that > device. > > doc/mgmt-api.txt | 50 +++++++++++++++++++++++++++++++++++++++++++++++- > 1 file changed, 49 insertions(+), 1 deletion(-) > > diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt > index 5355fedb0..32dd8c0f2 100644 > --- a/doc/mgmt-api.txt > +++ b/doc/mgmt-api.txt > @@ -107,7 +107,8 @@ Configuration command, Default Runtime Configuration Changed event, Get > Device Flags command, Set Device Flags command, Device Flags Changed event, > Read Advertisement Monitor Features command, Add Advertisement Patterns > Monitor command, Remove Advertisement Monitor command, Advertisement Monitor > -Added event and Advertisement Monitor Removed event. > +Added event, Advertisement Monitor Removed event, Advertisement Monitor Device > +Found event and Advertisement Monitor Device Lost event. we need to increase the mgmt version and add the new commands to that section. Leave this out of this patch and put it into a separate one. > > Example > @@ -4910,3 +4911,50 @@ Controller Resume Event > Address_Type. Otherwise, Address and Address_Type will both be zero. > > This event will be sent to all management sockets. > + > + > +Advertisement Monitor Device Found Event > +======================================== > + > + Event code: 0x002f > + Controller Index: <controller_id> > + Event Parameters: Monitor_Handle (2 Octets) > + Address (6 Octets) > + Address_Type (1 Octet) > + > + This event indicates that the controller has started tracking a device > + matching an Advertisement Monitor with handle Monitor_Handle. > + > + The address of the device being tracked will be shared in Address and > + Address_Type. > + > + Possible values for the Address_Type parameter: > + 0 Reserved (not in use) > + 1 LE Public > + 2 LE Random > + > + This event will be sent to all management sockets. My initial thought was actually to include all the fields from Device Found Event here as well. So that in case we are using advertising monitor, we just need to worry about this event only. Thoughts? > + > + > +Advertisement Monitor Device Lost Event > +======================================= > + > + Event code: 0x0030 > + Controller Index: <controller_id> > + Event Parameters: Monitor_Handle (2 Octets) > + Address (6 Octets) > + Address_Type (1 Octet) > + > + This event indicates that the controller has stopped tracking a device > + that was being tracked by an Advertisement Monitor with handle > + Monitor_Handle. > + > + The address of the device being tracked will be shared in Address and > + Address_Type. > + > + Possible values for the Address_Type parameter: > + 0 Reserved (not in use) > + 1 LE Public > + 2 LE Random > + > + This event will be sent to all management sockets. Regards Marcel
