Kernel stats show DSP not enabled for multimedia acceleration
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
Hi all,
I'm trying to use Rowboat for DSP-based multimedia acceleration on a
Beagleboard rev. C4 with OMAP3530. I built Rowboat using the instructions found
on the wiki page
(http://code.google.com/p/rowboat/wiki/DSP#Building_and_Testing_DSP_stack) for
building and testing the DSP stack. I configured the SD Card and got Rowboat to
boot using the exact instructions found on the previously mentioned web page.
Then, I tried playing a video and an mp3 as directed by the instructions in the
"Test" section.
Because I am interested in measuring power consumption as well, I have been
reading from files in the power management debugfs (e.g.
/sys/kernel/debug/pm_debug/time) to determine how long each core is in
particular power states (OFF, RETENTION, INACTIVE, ON). When looking at the
output, it shows that the DSP never enters the ON state during video or audio
playback.
Clearly, if the DSP is doing processing, it should enter the ON state at some
point during playback, but the stats show that it doesn't. Is there anything I
have to do to actually enable the DSP? Did I do something wrong in the Rowboat
build process? As I mentioned before, I followed the directions on the wiki
link posted above from beginning to end, so I'm not sure what the problem is.
Any help/suggestions would be greatly appreciated. Thanks.
George
```
Original issue reported on code.google.com by `gvlemin...@gmail.com` on 3 May 2011 at 6:38
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Rowboat DSP build and testing instructions linked in the issue, then reproduce video or MP3 playback on the Beagleboard while reading /sys/kernel/debug/pm_debug/time. Compare the DSP power-state statistics with expected activity and determine whether the build or runtime setup enables DSP processing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100