Use interface instead of driver part of the function
The clock frequency varies between test cases, but remains the same in the same test case
For example: HDMI protocol will use different clocks according to the resolution of the image
Method 1: Separate the clock into a file and include different clocks to achieve
Method 2: Use the set method of config_db to set a variable in the test case, and then use the get method to get the variable in the clock implementation and use it as the clock period.
In the same test case there is a clock frequency shift
For example, the clocks before and after the PLL transition period are different
Method 1: Use the set method of config_db in the test case to set different values for the clock period variable with different times.
This concerns both the clock before and after the transition period, as well as the behavior of the PLL during the transition period, i.e., the clock variable is required to be more than simply variable and sinusoidally varying.
For example: concerned about the behavior of the clock during the transition period of the PLL, the actual work of the clock frequency is also a certain jitter
Method 1: Create a clk interface, and then put the clk driver in a clock component via config_db, so that to implement any driver for clk, you only need to overload this clock component.
https://freedomdefined.org/OSHW/endorsements#Endorsements
https://stellabrinkley.livejournal.com/430.html
https://stellabbe.blogspot.com/2023/05/the-advanced-course-of-practical-route.html
评论
发表评论