20/10/2021 11:32, Akhil Goyal: > > 20/10/2021 11:15, Akhil Goyal: > > > > 17/10/2021 18:16, Hemant Agrawal: > > > > > This patch add support for raw API tests for > > > > > dpaa_sec and dpaa2_sec platforms. > > > > > > > > Why do we have tests specific to some drivers? > > > > Is there a plan to remove them? > > > > > > > > > > The testsuites are common and there is no driver specific test. > > > The test command is different for each of the PMD, > > > that is why it is registered for each PMD. > > > For Raw data path APIs, all of the testsuite is run with a global flag > > > set. > > > Currently only 3 PMDs support raw APIs, we can get rid of this global > > > flag in > > future if more > > > PMDs start supporting these APIs. > > > > No there is something wrong. > > It shows that it is not generic enough for any app. > > What is missing to make the same calls no matter the driver? > > Do we need to add some capability flags? > > Capability flags are there for raw data path APIs but the PMD can support > both APIs. > And we need to test both data paths. > So for this we have a global variable to enable raw data path and we register > a new > Command for the PMD and enable that global flag while doing that. > The tests, however have the capability flags checks in place but we decide to > enable > Raw APIs only when the PMD support that and that global flag is set. > I hope it is clear now.
No sorry, it is not clear. How may I know that the raw API is supported in a PMD? If there is such info, no need for specific tests?
