Skip to content

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

Closed
wants to merge 2 commits into from

Conversation

e-rk
Copy link
Collaborator

@e-rk e-rk commented Apr 1, 2025

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.

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]>
Copy link

github-actions bot commented Apr 1, 2025

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
hal_nordic zephyrproject-rtos/hal_nordic@7440d57 (master) zephyrproject-rtos/hal_nordic#287 zephyrproject-rtos/hal_nordic#287/files

DNM label due to: 1 project with PR revision

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@github-actions github-actions bot added manifest manifest-hal_nordic DNM (manifest) This PR should not be merged (controlled by action-manifest) labels Apr 1, 2025
Comment on lines +883 to +886
nrf_802154_receive_at(config->rx_slot.start / NSEC_PER_USEC,
config->rx_slot.duration / NSEC_PER_USEC,
config->rx_slot.channel, slot_id);
Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

Copy link
Collaborator

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]>
@e-rk e-rk force-pushed the update-nrf-802154 branch from 9112242 to 4ea350f Compare April 1, 2025 11:23
@e-rk e-rk closed this May 29, 2025
@e-rk e-rk deleted the update-nrf-802154 branch May 29, 2025 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: IEEE 802.15.4 DNM (manifest) This PR should not be merged (controlled by action-manifest) manifest manifest-hal_nordic platform: nRF Nordic nRFx
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants