Skip to content
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

nfc: Limit NFCT_IRQ_PRIORITY range if ZERO_LATENCY_IRQS is enabled #103

Closed

Conversation

thomasstenersen
Copy link

This fixes a problem where the NFCT_IRQ_PRIORITY is stuck at 6 if
ZERO_LATENCY_IRQS are enabled after the initial configuration of the
project.

@SebastianBoe

FYI: @kapi-no

This fixes a problem where the NFCT_IRQ_PRIORITY is stuck at 6 if
ZERO_LATENCY_IRQS are enabled after the initial configuration of the
project.

Signed-off-by: Thomas Stenersen <thomas.stenersen@nordicsemi.no>
Copy link
Contributor

@SebastianBoe SebastianBoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocked by the ongoing upmerge.

In our process, downstream repo's can not be patched while an upmerge process is ongoing.

@SebastianBoe
Copy link
Contributor

nrfconnect/sdk-nrf#1430

@grochu
Copy link
Contributor

grochu commented Nov 19, 2019

This PR can be closed. The proposed change is included in nrfconnect/sdk-nrf#1507 after moving Zephyr-related NFC build files and source code to fw_nrfconnect-nrf with #104
Do you agree @thomasstenersen ?

@thomasstenersen
Copy link
Author

@grochu Agree. Closing the PR then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants