The NanSRFState enum was incorrectly specifying NAN_DO_NOT_USE_SRF
as 1 which was not insync with the wifi firmware expected value
causing the case of active subscribe and solicited publish to fail.
This commit updates the enum type appropriately.
Bug: 30898004
Change-Id: I89f092964daeeb962b57ea474131bb58984a4d43
The service instance Id needs to match the handle received during
the match indication. The current match handle is 32bit,fixing
the service instance id.
The status of the transmit follow up is not
notified, enabling an indication to notify
the status of transmit in progress.
Change-Id: I91fab766d7265ef6538c003ac454291efd0ec462
1) Remove schedule update API and data structures.
2) Add Nan Data Path error codes.
3) Provide channel configuration option.
Bug: 27916896
Bug: 26562610
Change-Id: Id2fbc8af398ee312b8c0dd61388d57cf2e7efcdd
Initial check-in of ND offload HAL API support
BUG=27598285
Change-Id: I9f2652de2bb0e22a25fe7c0ded6d1f5e6500de6d
Signed-off-by: Jun Lim <jun.lim@broadcom.com>
Modify the existing wake accounting reasons HAL API so that the
individual wake accounting reason array buffers are allocated
and freed by framework.
BUG:26902794
Change-Id: Iea74e61890f785107b05f9b4a3a58449ba449f0d
disabled was not very clear as to the actual meaning of the event and
left the implication that the scan could be reenabled.
Change-Id: I3f53b13a958cd35e93fde7bf9690d84744ffe63a
When a connection attempt fails, we're often unable
to determine the cause from existing log files. This
is because our log files only report the view from user
space. From this vantage point, we can't tell if,
e.g., an outbound frame was ever sent over the air.
(Or, for inbound frames: if they were heard by our
radio.)
To give ourselves a broader view, we add the packet fate
monitoring API. This API will let us determine, e.g.,
if an outbound frame was transmitted by our radio.
BUG: 26807558
Change-Id: I197729117f9086ece8cf00313bb9d3e7c0197b97
The current list of events supported by the wifi_connectivity_event
ring buffer omits some important events. Add three new events, so
that we can log the events for driver/firmware that support them.
BUG: 26832275
Change-Id: I2a4e674e5f7b52cc630eac32191fdc0b75d60422
Add API for dumping state of WiFi driver. This API
will be used in combination with the (existing)
firmware memory dump API, to identify inconsistent
state between driver and firmware.
BUG: 26803847
Change-Id: Ie65f095ca6be4203f8aad0b541c1903dc6cce1f5
Changes related to NAN APIs and structures.
1) Remove NanHeader
2) Replace wifi_handle with wifi_interface_handle in NAN APIs
3) Add publish/subscribe id
4) Remove match_handle and name it as requestor_instance_id
5) Add NanPublishResponse/NanSubscribeResponse structures
6) Remove user_context
7) Add appropriate enums
8) Remove unused structures
9) Add new NAN status types for TCA, Transmit, and invalid
configuration of Band, DW/DB intervals, random factor
update and scan period.
10) Add new fields in Publish/Subscribe Stats.
11) Replace wifi_request_id with transaction_id to have a
common interface across all layers.
Bug: 26216681
Change-Id: Ife7cf7e7ed64d2f8db236f23919cd6412dc8b496
Correct the comments on exponential back off scan formula.
Rename "exponent" to "base" to match the formula.
Also make the meaning of AP (Access Point vs. Apps Processor)
explicit for struct wifi_scan_cmd_params.
Bug: 26236392
Change-Id: I5873e1c8667dd964d125e37e2f0eeddec79eda13
To enable the vendor implementation of the vibrator HAL, it is needed
to use hardware modules, a default one for AOSP and the vendor one.
The legacy implementation is no more needed so let's remove it.
This change is related to other changes in:
- hardware/libhardware
- frameworks/base
Change-Id: I844279f5535289f079d412fdc44c5cb3c9c1130c
Author: Vincent Becker <vincentx.becker@intel.com>
Signed-off-by: Vincent Becker <vincentx.becker@intel.com>
Signed-off-by: Shuo Gao <shuo.gao@intel.com>
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
Signed-off-by: Jack Ren <jack.ren@intel.com>
Signed-off-by: David Wagner <david.wagner@intel.com>
Author-tracking-BZ: 49760
Reserved a bit for RSSI monitor feature in the feature bitmask
Change-Id: Ied470f65c26bed25f7ccc4faa3ac8fbac1e74009
Signed-off-by: Ashwin <ashwin.bhat@broadcom.com>
e28e2bb Introduce REPORT_EVENTS_NO_BATCH flag for ePNO
ddcab17 WifiLogger: Add new events and tags
1abb250 change wifi Logging header
bd14c1c add pointers to new roaming HAL functions
Change-Id: I4645ceb57de34109d417bc9b84ff6d2cb202a78d
When GSscan and ePNO are being executed together, we
don't want APs on additional channels from ePNO to be
cached. Making this requirement explicit by adding
REPORT_EVENTS_NO_BATCH flag on bucket.
Change-Id: I61dcd608d3be8acb697508607dbe5077ebe836c0
As part of the Debug Framework development new events and tags
are required in G_SCAN. Additional generic tags are also being
added to support various events.
Change-Id: Ia5bc8dc1a5310818c3fcf3f9e166ffc5341f032c