PDDF: Add MultiFPGA support to PDDF subsystem#22671
Closed
nate-nexthop wants to merge 1 commit intosonic-net:masterfrom
Closed
PDDF: Add MultiFPGA support to PDDF subsystem#22671nate-nexthop wants to merge 1 commit intosonic-net:masterfrom
nate-nexthop wants to merge 1 commit intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
nate-nexthop
force-pushed
the
pddf-multifpga
branch
from
498fd4a to
afea771
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
In our Nexthop device we have more than one FPGA and the FPGAs use common IP blocks for various busses, most notably I2C. Some I2C devices are attached to one FPGA, and some another. We want to re-use the drivers between FPGAs. Create a system where we can describe our multi-FPGA setup using pddf-device.json and assign devices to the correct FPGA "parent" the same as the rest of the PDDF hierarchy of devices.
lotus-nexthop
force-pushed
the
pddf-multifpga
branch
from
e9b69db to
99789da
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
nate-nexthop
force-pushed
the
pddf-multifpga
branch
from
99789da to
2e1daf4
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
nate-nexthop
force-pushed
the
pddf-multifpga
branch
from
2e1daf4 to
99789da
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
This PR was split into ten PRs. Closing this PR. [PDDF] Multiple FPGAs w/ I2C IP blocks |
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
3 participants
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.
Why I did it
In our Nexthop device we have more than one FPGA and the FPGAs use common IP blocks for various busses, most notably I2C. Some I2C devices are attached to one FPGA, and some another. We want to re-use the drivers between FPGAs.
See #22666 for an example of how this is used the pddf-device.json.
Work item tracking
How I did it
Create a system where we can describe our multi-FPGA setup using pddf-device.json and assign devices to the correct FPGA "parent" the same as the rest of the PDDF hierarchy of devices.
How to verify it
TBD
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)