Skip to content

cache gpio chip detection when properly initialized #962

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.

Sign up for GitHub

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

Jump to bottom
Merged
2bndy5 merged 1 commit into from
Mar 19, 2024
Merged

cache gpio chip detection when properly initialized #962

2bndy5 merged 1 commit into from
Mar 19, 2024

Conversation

@2bndy5
Copy link
Member

@2bndy5 2bndy5 commented Mar 19, 2024 •
edited
Loading

This will prevent falling back to /dev/gpiochip0 when /dev/gpiochipX was previously opened successfully.

This is designed to alert users when multiple processes are simultaneously using /dev/gpiochipX, but it should only happen if either

  1. another process is spamming/hogging the gpiochipX.
  2. the rare occurrence when RF24 needs to open gpiochipX while it is still used by another process.
@2bndy5
cache gpio chip detection when properly initialized
72264d5 
This will prevent falling back to `/dev/gpiochip0` when `/dev/gpiochipX` was previously opened successfully.

This is designed to alert users when multiple processes are simultaneously using `/dev/gpiochipX`, but it should only happen if either
1. another process is spamming the gpiochipX.
2. the rare occurrence when RF24 needs to open gpiochipX while it is still used by another process.
@2bndy5 2bndy5 merged commit a5a2087 into master Mar 19, 2024
@2bndy5
Copy link
Member Author

2bndy5 commented Mar 19, 2024

This was just a follow-up to #961 which I should've included there. Hardware tests showed no problems.
@2bndy5 2bndy5 deleted the static-chip-cache branch March 19, 2024 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants

@2bndy5