-
Notifications
You must be signed in to change notification settings - Fork 88
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
Return allocated IRQ from FDT #39
Conversation
This passes all tests internally including tests with SMP enabled on rockpro64 |
|
how long did you wait? it might take a while. |
Well, I looked and it's now up to |
ok I expected it will take a while. similar story on hikey when all 8 cores are enabled. |
|
some logs? |
If I run the multicore tests on their own they pass without issue |
hmm, how about IPC and Multicore tests together? |
I reran all of the tests and they all passed this time so 🤷 |
|
040ccee
to
fd58ecf
Compare
This traverses the FDT directly when initialising the driver for the rockpro64 timer so that the IRQ for the second timer can be derived from the IRQ allocated to the first device. Signed-off-by: Curtis Millar <[email protected]>
fd58ecf
to
28c378b
Compare
@kent-mcleod updated the changes per your recommendation. |
@ssrg-bamboo |
Hello, I'm a bot! I'll bring this PR into Trustworthy Systems and run some tests |
All the tests we ran have passed! Nice job! |
When allocating an IRQ from the FDT the IRQ that was allocated should be passed back to the caller in addition to the IRQ handler ID.
For
rockpro64
, theltimer
implementation for its second timer should use the IRQ number one greater that the first timer's IRQ number (rather than the first timer's IRQ handler ID).Fixes seL4/sel4test#25.