test-case: manual: Simple probes functionality test #923
Conversation
jsarha
force-pushed
the
probe-capture-manual-test
branch
from
c43759a to
8a791ed
Compare
There was a problem hiding this comment.
@jsarha Are those configurations in this document all supported by thesofproject/sof and thesofproject/linux? So I can try manually.
Yes, they are. Also the both PRs fixing the problems related to this are now merged. I wrote the test descriptions based on how I got the feature working last week, so I think it should be good. |
|
The form looks great but I'm ignorant about the content. @jsarha could you get a couple more reviewers? |
jsarha
force-pushed
the
probe-capture-manual-test
branch
from
8a791ed to
9dcf2d6
Compare
| CONFIG_PROBE_POINTS_MAX=16 | ||
| CONFIG_PROBE_DMA_MAX=4 | ||
|
|
||
| In fact PROBE_DMA_MAX is ignored as inection is not currently supported |
There was a problem hiding this comment.
s/inection/injection
Why mention CONFIG_PROBE_DMA_MAX in the first place?
There was a problem hiding this comment.
If CONFIG_PROBE is enabled through menuconfig the CONFIG_PROBE_DMA_MAX option appears with the default value of 4, so I think it causes less confusion to mention it than leaving it out.
There was a problem hiding this comment.
For me it comes with 0 as default, but never checked the kconfig file to be honest..
There was a problem hiding this comment.
I think you have put the zero there. If enabled for the first time (I think I had not touched the items before), the two numeric options appear as above.
Signed-off-by: Jyri Sarha <[email protected]>
jsarha
force-pushed
the
probe-capture-manual-test
branch
from
9dcf2d6 to
256272a
Compare
Signed-off-by: Jyri Sarha [email protected]
This is very simple and fast put together test for probe capture functionality.