-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Initialize PCIe for the second CPU #77
Merged
krystian-hebel
merged 4 commits into
raptor-cs_talos-2/develop
from
raptor-cs_talos-2/pcie_2nd_cpu
Feb 7, 2022
Merged
Initialize PCIe for the second CPU #77
krystian-hebel
merged 4 commits into
raptor-cs_talos-2/develop
from
raptor-cs_talos-2/pcie_2nd_cpu
Feb 7, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
81457d3
to
84f6d7d
Compare
In addition to addressing comments also made 14.3 use chip for group ID in one place (the other one is address extension group ID which is always zero). I had this on OCC branch, but didn't apply here until now. |
7b79b81
to
e88aa67
Compare
84f6d7d
to
8f45921
Compare
e88aa67
to
719dffa
Compare
8f45921
to
a8cb8d0
Compare
719dffa
to
3cfdfae
Compare
a8cb8d0
to
05474af
Compare
For now keep among other constants, but they are to be extracted into a header of their own. Change-Id: Ia913e6d00df816bc98ba07bdb50c6c6784aca84e Signed-off-by: Sergii Dmytruk <[email protected]>
05474af
to
88566a9
Compare
* MAX_CHIPS constant * fix header guards in pci.h * CPU-specific PCIe masks * CPU-specific IOP swap * chip-specific SCOM operations * now computed PCIe is returned as an array of structures Change-Id: Ib39b9f97ed8dfb0b77bc0001cd1a951b44e58a32 Signed-off-by: Sergii Dmytruk <[email protected]>
Use chip-specific SCOM accesses. Change-Id: Id6c782d6ad1a956855d7e0a8b5faff248fbe3b26 Signed-off-by: Sergii Dmytruk <[email protected]>
88566a9
to
619afc4
Compare
Chip-specific SCOM accesses and values computed in istep 10.10. Change-Id: Ic5b4932cfe3fe960ea5464b0df71603a528ca4ed Signed-off-by: Sergii Dmytruk <[email protected]>
krystian-hebel
approved these changes
Feb 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates isteps 10.10, 10.12 and 14.3 with CPU-specific configuration and chip-specific SCOM accesses.