From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Audio glitch with SGTL5000
Date: Thu, 22 Jan 2015 06:24:14 -0700 [thread overview]
Message-ID: <54C0F9FE.6020208@mlbassoc.com> (raw)
In-Reply-To: <CAOMZO5DU7DYHhOD2jAjycU0f-b774OUKqUT4GEinYWPyxi_fXA@mail.gmail.com>
On 2015-01-21 17:00, Fabio Estevam wrote:
> Hi Nikolay,
>
> On Wed, Jan 21, 2015 at 9:55 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>
>> Hehe, I'm not sure that you cleared the bit actually :). I think that
>> with mask 0 you're not writing to the I2C reg at all - you can check
>> the return value of snd_soc_update_bits(), should be 0 (no error, no
>> value changed). But would be great if you can also monitor the I2C bus
>> traffic to confirm whether you really write or not to this register.
>>
>> Can you try to change only the last argument and hear whether it makes
>> a difference, like this:
>>
>> snd_soc_update_bits(codec, SGTL5000_CHIP_REF_CTRL, 1, 1);
>> snd_soc_update_bits(codec, SGTL5000_CHIP_REF_CTRL, 1, 0);
>
> My tests show the following:
>
> - With SMALL_POP 0 (no click)
> - With SMALL_POP 1 (click)
>
> Yes, this sounds strange. With my patch applied we end up with
> SMALL_POP 0 (default value) and I don't hear the click on mx28evk nor
> mx53qsb.
Are you using headphone or line-out?
My i.MX6 boards all suffer from this annoying pop - it would be great
to get to the bottom of this.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-01-22 13:24 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
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 [this message]
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=54C0F9FE.6020208@mlbassoc.com \
--to=gary@mlbassoc.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.