Skip to content
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

PDDF v2.0: 1) Support for 2.0 platform APIs, 2) Support for BMC enabled platforms #536

Merged
merged 2 commits into from
Oct 14, 2020

Conversation

FuzailBrcm
Copy link
Contributor

PDDF v2.0 HLD

@FuzailBrcm
Copy link
Contributor Author

PDDF v2.0 HLD

This documents describes the enhancements made to the Platform Driver Development Framework (PDDF). New changes include,

  1. Support for 2.0 Platform APIs:
    Previous PDDF version was based out of 1.0 Platform APIs which use user-space plugins to access the HW SysFS attributes. New version of PDDF provides generic device object-calsses derived form the 2.0 platform base class. Actual per-platform object-classes would further be derived form the above mentioned PDDF generic classes.

  2. Support for BMC platforms:
    New PDDF version supports the attribute get/set for PSU, FAN and thermal components if they are controlled by the BMC.

@xinliu-seattle xinliu-seattle merged commit 38e95f8 into sonic-net:master Oct 14, 2020
jleveque pushed a commit to sonic-net/sonic-buildimage that referenced this pull request Nov 12, 2020
This change introduces PDDF which is described here: sonic-net/SONiC#536

Most of the platform bring up effort goes in developing the platform device drivers, SONiC platform APIs and validating them. Typically each platform vendor writes their own drivers and platform APIs which is very tailor made to that platform. This involves writing code, building, installing it on the target platform devices and testing. Many of the details of the platform are hard coded into these drivers, from the HW spec. They go through this cycle repetitively till everything works fine, and is validated before upstreaming the code.
PDDF aims to make this platform driver and platform APIs development process much simpler by providing a data driven development framework. This is enabled by:

JSON descriptor files for platform data
Generic data-driven drivers for various devices
Generic SONiC platform APIs
Vendor specific extensions for customisation and extensibility

Signed-off-by: Fuzail Khan <fuzail.khan@broadcom.com>
santhosh-kt pushed a commit to santhosh-kt/sonic-buildimage that referenced this pull request Feb 25, 2021
This change introduces PDDF which is described here: sonic-net/SONiC#536

Most of the platform bring up effort goes in developing the platform device drivers, SONiC platform APIs and validating them. Typically each platform vendor writes their own drivers and platform APIs which is very tailor made to that platform. This involves writing code, building, installing it on the target platform devices and testing. Many of the details of the platform are hard coded into these drivers, from the HW spec. They go through this cycle repetitively till everything works fine, and is validated before upstreaming the code.
PDDF aims to make this platform driver and platform APIs development process much simpler by providing a data driven development framework. This is enabled by:

JSON descriptor files for platform data
Generic data-driven drivers for various devices
Generic SONiC platform APIs
Vendor specific extensions for customisation and extensibility

Signed-off-by: Fuzail Khan <fuzail.khan@broadcom.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants