GitLab

am: 564211e8

* commit '564211e8':
  Remove const integers from HAL and define undefined structs

Change-Id: If14cb118c7fb980e5f50c3ba1e291ffed7e46964

Bug: 28984011
Change-Id: I6edfe547fbad127db9cbff654b96a476140d9f05

Advertize preamble capabilities of responder.

Change-Id: I5ca478bc608308b7e72990cb2d25d2e1a51922c7

Adding a flag to indicate if the device supports tx power level stats
reporting.

While there,
1. Fix the 2 macros used to determine if a feature is supported or not.
2. Increase the number of tx levels to 256

BUG: 27969673
Change-Id: I314648cfaa7755dc48c1f790193c96254b4db691

BUG: 27969673
Change-Id: I65232f20192a87998d921769501915578d9a54a6

am: 44c39504  -s ours

* commit '44c39504':
  Enabling Nan data path support [DO NOT MERGE]

Change-Id: I3ccafb3919ac952715666fd9286d49f0096abd53

Add APIs and data structures to support nan data path.

Change-Id: I60acc78f1d8a394cab511f4468dbc745a3107ddb

Bug: 27814144
Change-Id: I54b7a73ec318779fd3addb060998f4d94141152d

Add a max tx level which the framework uses to limit the array and is
needed to guard against unitialized value in |num_tx_levels|.

BUG: 27227497
Change-Id: I2438bc1536c65a2c6230bfd6e1267532d9653c8b

am: 13ef8430

* commit '13ef8430':
  WiFi HAL: ND offload enhancement

Modify the existing radio_stat structure to add time spent in each
tranmission power level.

BUG: 27227497
Change-Id: Ifba9f22bc7a404161ae9124c787854ed3431cb8d
cherry-picked from: 
https://partner-android-review.googlesource.com/#/c/543388

Given that there is an explicit enumerated value to indicate
a drop due to lack of buffers, we shouldn't recommend using
the OTHER value for out of buffers.

BUG=27352446
TEST=compile

Change-Id: Id4fdbf530ed9a99e2b9693acb649137d598abf85

For consistency with other packet_fate functions,
wifi_start_pkt_fate_monitoring() should name the first
parameter as |handle|.

BUG=27409524
TEST=compile

Change-Id: Ic6df01e7e80f79eaf5653374106ba6e6a7609e31

Initial check-in of ND offload HAL API support

BUG=27598285

Change-Id: I9f2652de2bb0e22a25fe7c0ded6d1f5e6500de6d
Signed-off-by: Jun Lim <jun.lim@broadcom.com>

Bug: 27562099
Change-Id: Id5af47af3e8e3404c575fbb0ec02cf25378b7089

am: bf5b9bf4

* commit 'bf5b9bf4':
  Enabling responder for rtt

Added minor changes in API for RTT

Change-Id: Ib93305d3246ab501b8389f479d8193f353024f21
Signed-off-by: gautam <gautam.shukla@broadcom.com>

am: 4d0c8f7f

* commit '4d0c8f7f':
  WiFi HAL: add packet fate monitoring API

am: ded9b10b

* commit 'ded9b10b':
  Remove REPORT_EVENT_CONTEXT_HUB gscan option

am: a5c9342b

* commit 'a5c9342b':
  halutil: adding PNO driver events

Adding PNO driver events

BUG=26259438

Change-Id: Iad9ebc5c8b810fa1cf2389c1c2de0e765434fcf1
Signed-off-by: Sreenath Sharma <sreenath.sharma@broadcom.com>

am: 5aa942ee

* commit '5aa942ee':
  Modify the wake reasons accounting API's

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

Since all scan results will now be reported to the context hub this flag
is no longer needed.

Change-Id: I4ea3e88cc891be87660c12b7797819ea861cda26

am: 3febafdf

* commit '3febafdf':
  Rename WIFI_SCAN_DISABLED event to WIFI_SCAN_FAILED

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

am: ee6c9fd9

* commit 'ee6c9fd9':
  WiFi HAL: add additional connectivity events
  WiFi HAL: add driver memory dump API

* changes:
  WiFi HAL: add additional connectivity events
  WiFi HAL: add driver memory dump API

am: 2ad893d0

* commit '2ad893d0':
  Enable RTT Responder Role (3/4).

Change-Id: I14c7a13e423f1a6389449805c86c04d9a8d75440

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