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

NRF5x: Don't allocate GPIOTE in DigitalIn #5207

Merged

Conversation

nvlsianpu
Copy link
Contributor

The allocation of GPIOTE channels for DigitalIn is unwanted behavior.
This caused early run-out of GPIOTE channels for InterruptPin.
This patch replacing input configuration that is using gpiote driver by configuration that is
using gpio hal.

Fix for InterruptPin part of ct-test-shield test issue #5133

The allocation of GPIOTE channels for DigitalIn is unwanted behavior.
This caused early run-out of channels for InterruptPin.
This patch replacing input configuration that is using gpiote driver by configuration that is
using gpio hal.
@nvlsianpu
Copy link
Contributor Author

nvlsianpu commented Sep 27, 2017

I also checked that ci-shield tests: TESTS-ASSUMPTIONS-DIGITALIO, TESTS-API-BUSINOUT ,TESTS-API-DIGITALIO were executed successfully with this patch.

This PR combined witch #5200 are fixing #5133.

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 29, 2017

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1440

All builds and test passed!

@theotherjimmy theotherjimmy merged commit 8a3abbc into ARMmbed:master Oct 2, 2017
@theotherjimmy theotherjimmy changed the title Fix: DigitalIn of nRF5x was allocating GPIOTE channel NRF5x: Don't allocate GPIOTE in DigitalIn Oct 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants