Rockchip/rk3399-gru-sound: Use 48KHz sample rate for all devices#201
Open
alpernebbi wants to merge 1 commit intoalsa-project:masterfrom
Open
Rockchip/rk3399-gru-sound: Use 48KHz sample rate for all devices#201alpernebbi wants to merge 1 commit intoalsa-project:masterfrom
alpernebbi wants to merge 1 commit intoalsa-project:masterfrom
Conversation
The rk3399-gru-kevin board has problems when trying to simultaneously
playback and record audio with the default PulseAudio sample rate of
44.1KHz. When the following command is run, the playback starts a few
seconds after the recording finishes.
arecord -vvv -d 4 /dev/null & sleep 0.2; \
speaker-test -l 1 -p 100000 -t sine
When the sample rates are set to 48KHz either with PA configuration or
in the UCM, playback and recording both start immediately. Another
example is when a music player is running and we start `arecord`, the
music starts stuttering but `arecord` can't record anything either.
Apparently, this is a hardware limitation due to the I2S lines being
shared between the devices. Set all the device rates to 48KHz like
Chrome OS does to make things work smoothly.
[1] https://chromium-review.googlesource.com/389695
[2] https://chromium-review.googlesource.com/898682
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Member
|
It should be handled in the driver - if the rate is already set in one direction, the driver should lock this rate for the other direction, too. I would fix the driver at first. |
Contributor
Author
That sounds reasonable, I'll try to do it. But setting all rates to |
Member
|
If you can reproduce the problem using different applications and ALSA utilities, it looks like a driver issue. |
90b4ed1 to
67998e1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The rk3399-gru-kevin board has problems when trying to simultaneously playback and record audio with the default PulseAudio sample rate of 44.1KHz. When the following command is run, the playback starts a few seconds after the recording finishes.
When the sample rates are set to 48KHz either with PA configuration or in the UCM, playback and recording both start immediately. Another example is when a music player is running and we start
arecord, the music starts stuttering butarecordcan't record anything either.Apparently, this is a hardware limitation due to the I2S lines being shared between the devices. Set all the device rates to 48KHz like Chrome OS does to make things work smoothly.
[1] https://chromium-review.googlesource.com/389695
[2] https://chromium-review.googlesource.com/898682