diff options
| author | Hsiu-Chang Chen <hsiuchangchen@google.com> | 2022-12-20 10:31:40 +0530 |
|---|---|---|
| committer | Hsiu-Chang Chen <hsiuchangchen@google.com> | 2023-04-13 15:13:00 +0800 |
| commit | 1a70f36dccb039707201036a009ae35da0a02956 (patch) | |
| tree | a52e88aceff7270613603ddfc0476763bb607b23 /cnss2/qmi.c | |
| parent | adcf51862ac43461e22d23f0d5454514c0b6d013 (diff) | |
| download | cnss2-1a70f36dccb039707201036a009ae35da0a02956.tar.gz | |
cnss2: Validate maximum number of memory segments
For WIN use case maximum number of memory segments requested
by FW is increased to 52 in QMI layer. Since CNSS2 driver uses
same QMI header files and message structures the same maximum
number of segment is applicable for CNSS2. It means for memory
allocation, FW can request 52 memory segments to CNSS2 via QMI
indication but local CNSS2 variable which get segment info from
indication supports maximum 32 segments.
To fix it, change CNSS2 array variable size to same as number of
maximum segment supported in QMI layer.
Bug: 276750584
Test: Regression Test
Change-Id: I661b55b53cb31327da12f064d0a516884159eb5b
CRs-Fixed: 3355665
Signed-off-by: Hsiu-Chang Chen <hsiuchangchen@google.com>
Diffstat (limited to 'cnss2/qmi.c')
0 files changed, 0 insertions, 0 deletions