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 audio test frequencies
Date: Fri, 17 May 2019 13:46:53 +0300 [thread overview]
Message-ID: <20190517104653.22477-1-simon.ser@intel.com> (raw)
Explain that they can get dropped depending on the sampling rate and why.
Signed-off-by: Simon Ser <simon.ser@intel.com>
---
tests/kms_chamelium.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/tests/kms_chamelium.c b/tests/kms_chamelium.c
index c8b6b22d7b4a..0dd8c41ad2d5 100644
--- a/tests/kms_chamelium.c
+++ b/tests/kms_chamelium.c
@@ -785,12 +785,20 @@ static int test_sampling_rates[] = {
static int test_sampling_rates_count = sizeof(test_sampling_rates) / sizeof(int);
+/* Test frequencies (Hz): a sine signal will be generated for each.
+ *
+ * Depending on the sampling rate chosen, it might not be possible to properly
+ * detect the generated sine (see Nyquist–Shannon sampling theorem).
+ * Frequencies that can't be reliably detected will be automatically pruned in
+ * #audio_signal_add_frequency. For instance, the 80KHz frequency can only be
+ * tested with a 192KHz sampling rate.
+ */
static int test_frequencies[] = {
300,
600,
1200,
- 80000,
10000,
+ 80000,
};
static int test_frequencies_count = sizeof(test_frequencies) / sizeof(int);
--
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:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 10:46 Simon Ser [this message]
2019-05-17 12:00 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_chamelium: document audio test frequencies Patchwork
2019-05-17 12:17 ` [igt-dev] [PATCH i-g-t] " Arkadiusz Hiler
2019-05-17 16:42 ` [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=20190517104653.22477-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