public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>,
	"martin.peres@linux.intel.com" <martin.peres@linux.intel.com>
Cc: "Peres, Martin" <martin.peres@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v3 09/10] tests/kms_chamelium: add a flatline audio test
Date: Tue, 4 Jun 2019 11:22:50 +0000	[thread overview]
Message-ID: <95c39416baffa8d012596c91c8a3802d6d4f99a5.camel@intel.com> (raw)
In-Reply-To: <3cf10740-7774-5372-55ff-4381bc1cb8f3@linux.intel.com>

On Tue, 2019-06-04 at 09:38 +0100, Tvrtko Ursulin wrote:
> On 27/05/2019 15:34, Simon Ser wrote:
> > This commit adds a flatline test alongside the existing frequencies test.
> > 
> > The test sends a constant value and checks that the amplitude is correct. A
> > window is used to check that each sample is within acceptable bounds. The test
> > is stopped as soon as 3 audio pages pass the test.
> > 
> > Signed-off-by: Simon Ser <simon.ser@intel.com>
> > Reviewed-by: Martin Peres <martin.peres@linux.intel.com>
> > ---
> >   tests/kms_chamelium.c | 101 ++++++++++++++++++++++++++++++++++++++++++
> >   1 file changed, 101 insertions(+)
> > 
> > diff --git a/tests/kms_chamelium.c b/tests/kms_chamelium.c
> > index 40ca93687c20..451a616f1a2e 100644
> > --- a/tests/kms_chamelium.c
> > +++ b/tests/kms_chamelium.c
> > @@ -772,6 +772,9 @@ test_display_frame_dump(data_t *data, struct chamelium_port *port)
> >   /* A streak of 3 gives confidence that the signal is good. */
> >   #define MIN_STREAK 3
> >   
> > +#define FLATLINE_AMPLITUDE 0.9 /* normalized, ie. in [0, 1] */
> 
> I assume the test is making triple sure it only ever outputs this signal 
> to connectors connected to Chamelium, in all possible scenarios? (I am 
> thinking it could be dangerous to some amps/speakers if by some kind of 
> accident.)

Not at all. The signal is sent to all HDMI/DP ports.

I have to check whether it's easy to match ALSA outputs to monitor
names.

Martin, is this a concern?

> Regards,
> 
> Tvrtko
> 
> > +#define FLATLINE_ACCURACY 0.001 /* ± 0.1% of the full amplitude */
> > +
> >   /* TODO: enable >48KHz rates, these are not reliable */
> >   static int test_sampling_rates[] = {
> >   	32000,
> > @@ -1138,6 +1141,103 @@ static bool test_audio_frequencies(struct audio_state *state)
> >   	return success;
> >   }
> >   
> > +static int audio_output_flatline_callback(void *data, void *buffer,
> > +					     int samples)
> > +{
> > +	struct audio_state *state = data;
> > +	double *tmp;
> > +	size_t len, i;
> > +
> > +	len = samples * state->playback.channels;
> > +	tmp = malloc(len * sizeof(double));
> > +	for (i = 0; i < len; i++)
> > +		tmp[i] = FLATLINE_AMPLITUDE;
> > +	audio_convert_to(buffer, tmp, len, state->playback.format);
> > +	free(tmp);
> > +
> > +	return state->run ? 0 : -1;
> > +}
> > +
> > +static bool detect_flatline_amplitude(double *buf, size_t buf_len)
> > +{
> > +	double min, max;
> > +	size_t i;
> > +	bool ok;
> > +
> > +	min = max = NAN;
> > +	for (i = 0; i < buf_len; i++) {
> > +		if (isnan(min) || buf[i] < min)
> > +			min = buf[i];
> > +		if (isnan(max) || buf[i] > max)
> > +			max = buf[i];
> > +	}
> > +
> > +	ok = (min >= FLATLINE_AMPLITUDE - FLATLINE_ACCURACY &&
> > +	      max <= FLATLINE_AMPLITUDE + FLATLINE_ACCURACY);
> > +	if (ok)
> > +		igt_debug("Flatline detected\n");
> > +	else
> > +		igt_debug("Flatline not detected (min=%f, max=%f)\n",
> > +			  min, max);
> > +	return ok;
> > +}
> > +
> > +static bool test_audio_flatline(struct audio_state *state)
> > +{
> > +	bool success;
> > +	int32_t *recv;
> > +	size_t recv_len, i, channel_len;
> > +	int streak, capture_chan;
> > +	double *channel;
> > +
> > +	alsa_register_output_callback(state->alsa,
> > +				      audio_output_flatline_callback, state,
> > +				      PLAYBACK_SAMPLES);
> > +
> > +	audio_state_start(state, "flatline");
> > +
> > +	recv = NULL;
> > +	recv_len = 0;
> > +	success = false;
> > +	while (!success && state->msec < AUDIO_TIMEOUT) {
> > +		audio_state_receive(state, &recv, &recv_len);
> > +
> > +		igt_debug("Detecting audio signal, t=%d msec\n", state->msec);
> > +
> > +		for (i = 0; i < state->playback.channels; i++) {
> > +			capture_chan = state->channel_mapping[i];
> > +			igt_assert(capture_chan >= 0);
> > +			igt_debug("Processing channel %zu (captured as "
> > +				  "channel %d)\n", i, capture_chan);
> > +
> > +			channel_len = audio_extract_channel_s32_le(NULL, 0,
> > +								   recv, recv_len,
> > +								   state->capture.channels,
> > +								   capture_chan);
> > +			channel = malloc(channel_len * sizeof(double));
> > +			audio_extract_channel_s32_le(channel, channel_len,
> > +						     recv, recv_len,
> > +						     state->capture.channels,
> > +						     capture_chan);
> > +
> > +			if (detect_flatline_amplitude(channel, channel_len))
> > +				streak++;
> > +			else
> > +				streak = 0;
> > +
> > +			free(channel);
> > +		}
> > +
> > +		success = streak == MIN_STREAK * state->playback.channels;
> > +	}
> > +
> > +	audio_state_stop(state, success);
> > +
> > +	free(recv);
> > +
> > +	return success;
> > +}
> > +
> >   static bool check_audio_configuration(struct alsa *alsa, snd_pcm_format_t format,
> >   				      int channels, int sampling_rate)
> >   {
> > @@ -1235,6 +1335,7 @@ test_display_audio(data_t *data, struct chamelium_port *port,
> >   			audio_state_init(&state, data, alsa, port,
> >   					 format, channels, sampling_rate);
> >   			success &= test_audio_frequencies(&state);
> > +			success &= test_audio_flatline(&state);
> >   			audio_state_fini(&state);
> >   
> >   			alsa_close_output(alsa);
> > 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-06-04 11:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 14:34 [igt-dev] [PATCH i-g-t v3 00/10] tests/kms_chamelium: add pulse test Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 01/10] lib/igt_chamelium: introduce CHAMELIUM_MAX_AUDIO_CHANNELS Simon Ser
2019-05-27 14:41   ` Peres, Martin
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 02/10] tests/kms_chamelium: refactor audio test Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 03/10] tests/kms_chamelium: introduce audio_state_receive Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 04/10] tests/kms_chamelium: rename do_test_display_audio and test_audio_configuration Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 05/10] tests/kms_chamelium: explain why 8-channel tests aren't performed Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 06/10] lib/igt_audio: introduce audio_convert_to Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 07/10] tests/kms_chamelium: add name parameter to audio_state_start Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 08/10] lib/igt_audio: make audio_extract_channel_s32_le support a NULL dst Simon Ser
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 09/10] tests/kms_chamelium: add a flatline audio test Simon Ser
2019-06-04  8:38   ` Tvrtko Ursulin
2019-06-04 11:22     ` Ser, Simon [this message]
2019-06-04 12:26       ` Peres, Martin
2019-06-04 12:59         ` Tvrtko Ursulin
2019-06-04 14:06           ` Ser, Simon
2019-06-05 10:51             ` Tvrtko Ursulin
2019-06-05 13:04               ` Ser, Simon
2019-06-05 13:30                 ` Tvrtko Ursulin
2019-06-04 14:11         ` Ser, Simon
2019-05-27 14:34 ` [igt-dev] [PATCH i-g-t v3 10/10] tests/kms_chamelium: add audio channel alignment test Simon Ser
2019-05-27 16:03 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_chamelium: add pulse test (rev3) Patchwork
2019-05-28  4:48 ` [igt-dev] ✓ Fi.CI.IGT: " 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=95c39416baffa8d012596c91c8a3802d6d4f99a5.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@intel.com \
    --cc=martin.peres@linux.intel.com \
    --cc=tvrtko.ursulin@linux.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