All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: Fabio Estevam <festevam@gmail.com>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Gary Thomas <gary@mlbassoc.com>
Subject: Re: Audio glitch with SGTL5000
Date: Thu, 22 Jan 2015 21:49:39 +0200	[thread overview]
Message-ID: <54C15453.8050100@mail.bg> (raw)
In-Reply-To: <CAOMZO5B8rE=mfqMwbG7e9UNp-kJKN7+sVavK3_K0_k4y8BS0WA@mail.gmail.com>

Hi Fabio,

On 01/22/2015 09:33 PM, Fabio Estevam wrote:
> On Thu, Jan 22, 2015 at 5:20 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>
>> As we discussed with Fabio, when you define SGTL5000_SMALL_POP as 0, the
>> following call...
>>
>> snd_soc_update_bits(codec, SGTL5000_CHIP_REF_CTRL, SGTL5000_SMALL_POP, 1);
>>
>> ...doesn't actually write to the I2C register, and leaves the default
>> behavior, which is SMALL_POP = 1. And as Fabio noted, the audible behavior
>> of this SMALL_POP bit is inverted as compared to the documentation, so
>> SMALL_POP 0 should have the click audible, and SMALL_POP 1 should make it
>> inaudible.
>>
>> For me personally the patch is misleading written this way - it looks like
>> it's writing to the register, but neither this write is actually happening
>> (you can sniff the I2C bus if you wish), and also this patch hides the issue
>> with improperly documented SMALL_POP bit.
>
> There was no intention to hide anything in that patch.

Sorry, I didn't mean that at all.

> This is off-topic here on a Yocto list though, so I suggest we move
> such discussion to the alsa-devel list which is the appropriate place.

OK, understood.

Regards,
Nikolay


  reply	other threads:[~2015-01-22 19:49 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
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 [this message]
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=54C15453.8050100@mail.bg \
    --to=picmaster@mail.bg \
    --cc=festevam@gmail.com \
    --cc=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.