All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: meta-freescale@yoctoproject.org
Subject: Audio glitch with SGTL5000
Date: Wed, 21 Jan 2015 00:12:56 +0200	[thread overview]
Message-ID: <54BED2E8.70901@mail.bg> (raw)

Hi guys,

I'm observing a specific issue with SGTL5000 - after I stop the audio
playback, after several seconds there's a single strong audio glitch
(thump, pulse). In my case the audio codec is directly connected to the
product speaker amps (without any attenuators) and the experience can
be hardly described as pleasant...

I traced this behavior to the Linux kernel DAPM (Dynamic Audio Power
Management), which turns off all the analog and digital circuitry after
there's no audio stream for several seconds.

It looks like DAPM is not designed to be switched off, so I had to do
some (brutal) surgery to quick-solve the issue. I still have the
following gut feelings:
1. If this is an widespread issue, others should have seen it already.
2. If not, than maybe I have issue with my device tree and/or kernel
config.

Some info about my setup - imx6d, kernel 3.10.17-1.0.0ga, yocto daisy,
direct ALSA playback. Here's an extract of my DT audio settings:

sound {
	compatible = "fsl,imx-audio-sgtl5000";
	model = "imx6-myboard-sgtl5000";
	ssi-controller = <&ssi1>;
	audio-codec = <&codec>;
	audio-routing =
		"MIC_IN", "Mic Jack",
		"Mic Jack", "Mic Bias",
		"Headphone Jack", "HP_OUT";
	mux-int-port = <1>;
	mux-ext-port = <3>;
};

&ssi1 {
	fsl,mode = "i2s-slave";
	status = "okay";
};

Please share if you have observed similar behavior on your boards.
Thanks in advance!

Kind regards,
Nikolay


             reply	other threads:[~2015-01-20 22:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 22:12 Nikolay Dimitrov [this message]
2015-01-20 22:23 ` Audio glitch with SGTL5000 Fabio Estevam
2015-01-21  0:34   ` Nikolay Dimitrov
2015-01-21  0:38     ` Nikolay Dimitrov
2015-01-21  0:51       ` Fabio Estevam
2015-01-21  0:50     ` Fabio Estevam
2015-01-21  2:30       ` Nikolay Dimitrov
2015-01-21  2:56         ` Fabio Estevam
2015-01-21  2:59           ` Fabio Estevam
2015-01-21 23:55             ` Nikolay Dimitrov
2015-01-22  0:00               ` Fabio Estevam
2015-01-22  4:59                 ` Nikolay Dimitrov
2015-01-22 13:24                 ` Gary Thomas
2015-01-22 18:32                   ` Nikolay Dimitrov
2015-01-22 18:35                     ` Gary Thomas
2015-01-22 19:05                       ` Eric Nelson
2015-01-22 19:20                         ` Nikolay Dimitrov
2015-01-22 19:33                           ` Fabio Estevam
2015-01-22 19:49                             ` Nikolay Dimitrov
2015-01-22 19:52                               ` Fabio Estevam
2015-02-28 18:53                                 ` Eric Nelson
2015-02-28 20:29                                   ` Otavio Salvador
2015-03-01 15:08                                   ` Gary Thomas
2015-06-24 18:12                                     ` Nikolay Dimitrov
2015-07-02 21:37                                       ` Otavio Salvador
2015-07-02 22:21                                         ` Nikolay Dimitrov
2015-03-01 21:29                                   ` Nikolay Dimitrov
2015-03-01 22:40                                     ` Eric Nelson
2015-01-22 19:21                         ` Gary Thomas
2015-01-22 19:46                           ` Gary Thomas
2015-01-22 19:49                             ` Fabio Estevam
2015-01-22 20:16                               ` Gary Thomas
2015-01-22 20:28                                 ` Nikolay Dimitrov
2015-01-22 20:38                                   ` Gary Thomas

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=54BED2E8.70901@mail.bg \
    --to=picmaster@mail.bg \
    --cc=meta-freescale@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.