From: Nikolay Dimitrov <picmaster@mail.bg>
To: Fabio Estevam <festevam@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Audio glitch with SGTL5000
Date: Wed, 21 Jan 2015 04:30:24 +0200 [thread overview]
Message-ID: <54BF0F40.6030407@mail.bg> (raw)
In-Reply-To: <CAOMZO5AxfEEC_gBbfLNh41n=n1kXq0_2Sb7X+GOi0BN6WVF3Eg@mail.gmail.com>
Hi Fabio,
On 01/21/2015 02:50 AM, Fabio Estevam wrote:
> Hi Nikolay,
>
> On Tue, Jan 20, 2015 at 10:34 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>
>> I tried to reproduce the issue also with the integrated headphone amp,
>> just to find out that my board design has an issue (oops!) - the
>> headphones' ground is connected to the power supply ground instead of
>> the virtual ground, so I can't test the VAG ramp fix this way. So I can
>> only speculate that you tested your fix on a properly wired headphone
>> output, and that's where it worked OK.
>
> I tested on headphone output on a mx28evk.
>
> Here is a better link to the patch:
> https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/patch/sound/soc/codecs/sgtl5000.c?id=c251ea7bd7a04f1f2575467e0de76e803cf59149
>
> The previous one only showed the change to sgtl5000.c.
Thanks. But now I don't understand the logic of this patch. Here's the
prototype of the helper function:
int snd_soc_update_bits(struct snd_soc_codec *codec, unsigned int reg,
unsigned int mask, unsigned int value);
3rd argument is a mask, and you're passing there SGTL5000_SMALL_POP,
which is now 0.
> Does the problem also happens on 3.19-rc5?
Can't use mainline for this specific project, as I need VPU support.
Kind regards,
Nikolay
next prev parent reply other threads:[~2015-01-21 2:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 22:12 Audio glitch with SGTL5000 Nikolay Dimitrov
2015-01-20 22:23 ` 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 [this message]
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=54BF0F40.6030407@mail.bg \
--to=picmaster@mail.bg \
--cc=festevam@gmail.com \
--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.