Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

topology2: Revisit period and buffer size settings #8925

Merged
merged 3 commits into from
Apr 24, 2024
Merged

topology2: Revisit period and buffer size settings #8925

merged 3 commits into from
Apr 24, 2024

Commits on Apr 17, 2024

  1. topology2: common: pcm_caps: Increase periods_max from 16 to 1024 

    There is no technical reason to limit how many periods applications use.
Generic sound cards tends to allow 32768 periods (period size range
is 16 - 524288) but that is an overshot, let's raise the limit to 1024.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
    @ujfalusi
    ujfalusi committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    dde0e80 View commit details
    Browse the repository at this point in the history

  2. topology2: common: pcm_caps: Revisit default period and buffer sizes 

    Increase the default period_size_max to a much larger value which is
commonly used by sound cards from 16384 to 2097152.

Adjust the buffer_size limits to minimum 384 (2 * period_size_min) and the
maximum to 4194304 (2 * period_size_max).

Applications do not need to use these large buffers, but there is no
technical reason to not allow them, like they available on other sound
hardware.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
    @ujfalusi
    ujfalusi committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    c6f0b61 View commit details
    Browse the repository at this point in the history

  3. topology2: intel: deep-buffer: Adjust the buffer_size_min only 

    There is no benefit on changing the period/buffer size_max as it is set
by default to a reasonably large value already.
What matters is the buffer_size_min: it needs to be larger than the
amount of data that one DMA burst will transfer, which is equal to the
DeepBuffer size. For safety reasons the minimum buffer size has to be
larger than this.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
    @ujfalusi
    ujfalusi committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    402ae25 View commit details
    Browse the repository at this point in the history