diff options
| author | Ping-Ke Shih <pkshih@realtek.com> | 2024-02-04 09:26:26 +0800 |
|---|---|---|
| committer | Kalle Valo <kvalo@kernel.org> | 2024-02-06 20:06:13 +0200 |
| commit | 12ff5e1cca33b32fae0b183203f5b58a610e137e (patch) | |
| tree | 8cd233531ef8bf73f867176e09f3cdff89db23b8 /arch/m68k | |
| parent | 5462b8505f538b00d287a6de9a0fb2be6059bfc4 (diff) | |
wifi: rtw89: fw: parse secure section from firmware file
A firmware file can contains more than one section with secure type, so
use secure information from efuse to choose the one with matched
cryptography method. Then choose key data from MSS poll (multiple security
section pool; see below picture) according to key_index from efuse.
Note that the size of MSS pool isn't included in section size defined
in firmware header, so we also need to parse header of MSS pool to get
its size as shift to parse next section.
If secure boot isn't supported by current hardware, the first secure
section will be adopted, and no need additional process to key data.
+---------------------------+
| firmware header |
| |
| +-----------------------+ |
| | section type/size * N-|-|-------+
| | ... | | |
| +-----------------------+ | |
+---------------------------+ |
: : |
+---------------------------+ -\ |
| secure section type (ID:9)| | |
| | | <--+
| | |
+---------------------------+ -/
|MSS Pool for above section |
| |
| |
+---------------------------+
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://msgid.link/20240204012627.9647-4-pkshih@realtek.com
Diffstat (limited to 'arch/m68k')
0 files changed, 0 insertions, 0 deletions