Skip to content
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.

Explain how to handle drivers that utilize interrupts #95

Open
kammce opened this issue Jul 30, 2023 · 1 comment
Open

Explain how to handle drivers that utilize interrupts #95

kammce opened this issue Jul 30, 2023 · 1 comment
Labels
📚 contributor Documentation for contributors documentation Improvements or additions to documentation

Comments

@kammce
Copy link
Contributor

kammce commented Jul 30, 2023

Should include:

  • Why manual move constructors are necessary
  • Why a bool m_moved or std::bitset<N> flags is necessary
  • Tips for making this easiser
@kammce kammce added documentation Improvements or additions to documentation 📚 contributor Documentation for contributors labels Jul 30, 2023
@kammce
Copy link
Contributor Author

kammce commented Jul 30, 2023

Call this "Interrupt Relocation". And failure to do this correctly is, "Failed interrupt relocation". This comes in two flavors:

  1. Interrupts disabled after move: Typically, this leads to the driver's inability to receive an interrupt due to the interrupt being deactivated.
  2. Missed interrupt relocation: usually results in a dropped interrupt, system halt, or a fault.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
📚 contributor Documentation for contributors documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant