-
Notifications
You must be signed in to change notification settings - Fork 7.4k
drivers: ieee802154: nrf5: new RX window cancels previous RX #87964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The hal_nordic was updated to bring the new open source revision of the nrf-802154 radio driver. Signed-off-by: Rafał Kuźnia <[email protected]>
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 1 project with PR revision Note: This message is automatically posted and updated by the Manifest GitHub Action. |
nrf_802154_receive_at(config->rx_slot.start / NSEC_PER_USEC, | ||
config->rx_slot.duration / NSEC_PER_USEC, | ||
config->rx_slot.channel, slot_id); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nrf_802154_receive_at
returns bool
. What with the result?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous implementation didn't use the return result. I kept the previous approach.
If proper error handling is desired, I would suggest that it's done more holistically in the entire file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I'm not forcing a change.,(void)nrf_802154_receive_at
would be enough, to possibly satisfy some lint.
According to the documentation of IEEE802154_CONFIG_RX_SLOT, if the previous RX slot hasn't begun yet, but a new one is scheduled, then the previous RX slot must be cancelled. The new RX slot effectively replaces the old one. If the previous slot is currently ongoing, then it is not affected. The new RX slot can be scheduled while the previous slot is still ongoing. Signed-off-by: Rafał Kuźnia <[email protected]>
According to the documentation of IEEE802154_CONFIG_RX_SLOT,
if the previous RX slot hasn't begun yet, but a new one is scheduled,
then the previous RX slot must be cancelled. The new RX slot effectively
replaces the old one.
If the previous slot is currently ongoing, then it is not affected. The
new RX slot can be scheduled while the previous slot is still ongoing.