[26.04_linux-nvidia-bos] PCI: mirror PI7C9X3G606GPC Port 4 BAR0#443
Draft
nirmoy wants to merge 1 commit into
Draft
[26.04_linux-nvidia-bos] PCI: mirror PI7C9X3G606GPC Port 4 BAR0#443nirmoy wants to merge 1 commit into
nirmoy wants to merge 1 commit into
Conversation
Some Pericom/Diodes PI7C9X3G606GPC switches require downstream Port 4 BAR0 to mirror the upstream port BAR0. Firmware may apply this during boot, but Linux PCI resource assignment can move the upstream BAR0 and leave Port 4 without the required mirror. Add a final and resume quirk for downstream Port 4. The quirk verifies that the immediate upstream bridge is the same switch, then writes Port 4 BAR0 from the upstream BAR0 after resource assignment and after resume. Port 4 BAR0 may read back as zero even after a successful write, so the write must be validated by platform-specific means. BugLink: https://nvbugspro.nvidia.com/bug/6205517 BugLink: https://nvbugspro.nvidia.com/bug/6134331 Signed-off-by: Nirmoy Das <nirmoyd@nvidia.com> (cherry picked from commit 31881cf)
Contributor
PR Validation ReportPatchscan ✅ No Missing FixesAll cherry-picked commits checked — no missing upstream fixes found. PR Lint ❌ Errors foundDetailsChecking 1 commits...
Cherry-pick digest:
E: ed7f4baa94f3 ("NVIDIA: SAUCE: PCI: quirks: mirror PI7C9"): patch-ID mismatch with upstream 31881cfa3dda
E: ed7f4baa94f3 ("NVIDIA: SAUCE: PCI: quirks: mirror PI7C9"): SoB chain problem: MISSING: no Signed-off-by after (cherry picked from commit ...)
┌──────────────┬──────────────────────────────────────────────────────────────────┬────────────┬─────────┬───────────────────────────┐
│ Local │ Referenced upstream / Patch subject │ Patch-ID │ Subject │ SoB chain │
├──────────────┼──────────────────────────────────────────────────────────────────┼────────────┼─────────┼───────────────────────────┤
│ ed7f4baa94f3 │ 31881cfa3dda NVIDIA: SAUCE: PCI: quirks: mirror PI7C9X3G606GPC P │ MISMATCH │ match │ MISSING: no Signed-off-by │
└──────────────┴──────────────────────────────────────────────────────────────────┴────────────┴─────────┴───────────────────────────┘
Lint: all checks passed.
PR metadata:
E: PR targets 26.04_linux-nvidia-bos but body has no https://bugs.launchpad.net/... link
|
Collaborator
Author
Boro reviewLatest watcher review: open review Head: This comment is maintained by nv-pr-bot. It is updated when the GitHub watcher publishes a newer review. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Validation
Fresh BOS package/boot validation is still pending.
References
6.17 PR: #442
BugLink: https://nvbugspro.nvidia.com/bug/6205517
BugLink: https://nvbugspro.nvidia.com/bug/6134331