drivers: ieee802154: telink: Update B9X & TLX IEEE802.15.4

[andriy-bilynskyy]

• Add CSL receiver functionality for B9X
• Increment frame counter before sending instead of after ACK

[pulin1103]

LGTM
I have a suggestion: the ACK with frame counter should also increment the frame counter before tlx/b9x_mac_keys_frame_cnt_get.
Otherwise, the next packet's frame counter will be incremented by 2 instead of 1.
One more question: Is it okay for the frame counter to start from 1?

[andriy-bilynskyy]

LGTM I have a suggestion: the ACK with frame counter should also increment the frame counter before tlx/b9x_mac_keys_frame_cnt_get. Otherwise, the next packet's frame counter will be incremented by 2 instead of 1. One more question: Is it okay for the frame counter to start from 1?

Good point. Added increment before preparing ACK data.
Additionally fixed CSL phase in ACK frames was zero always since updated in local variable.
| The sender must never reuse the same frame counter value for two different frames with the same key.
Incrementing frame counter doesn't lead to issues - that's the reason why it present in frame.
Loosing one frame (as result incrementing frame counter to 2) shouldn't destroy feature encryption. The important is just not use same frame counter for different frames.

[pulin1103]

It looks fine, and there’s no problem when compiling and testing the firmware.