From: Simon Ser <simon.ser@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: martin.peres@intel.com
Subject: [igt-dev] [PATCH i-g-t] tests/kms_chamelium: document capture audio buffer size constraints
Date: Fri, 17 May 2019 13:27:09 +0300 [thread overview]
Message-ID: <20190517102709.22026-1-simon.ser@intel.com> (raw)
Explain why we need to choose a big enough buffer for audio capture.
Signed-off-by: Simon Ser <simon.ser@intel.com>
---
tests/kms_chamelium.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tests/kms_chamelium.c b/tests/kms_chamelium.c
index c8b6b22d7b4a..4db604d32cae 100644
--- a/tests/kms_chamelium.c
+++ b/tests/kms_chamelium.c
@@ -924,7 +924,14 @@ do_test_display_audio(data_t *data, struct chamelium_port *port,
/* Needs to be a multiple of 128, because that's the number of samples
* we get per channel each time we receive an audio page from the
- * Chamelium device. */
+ * Chamelium device.
+ *
+ * Additionally, this value needs to be high enough to guarantee we
+ * capture a full period of each sine we generate. If we capture 2048
+ * samples at a 192KHz sampling rate, we get a full period for a >94Hz
+ * sines. For lower sampling rates, the capture duration will be
+ * longer.
+ */
channel_len = CAPTURE_SAMPLES;
channel = malloc(sizeof(double) * channel_len);
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-05-17 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 10:27 Simon Ser [this message]
2019-05-17 11:20 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_chamelium: document capture audio buffer size constraints Patchwork
2019-05-17 11:52 ` [igt-dev] [PATCH i-g-t] " Martin Peres
2019-05-17 14:43 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190517102709.22026-1-simon.ser@intel.com \
--to=simon.ser@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox