From: Eric Nelson <eric@nelint.com>
To: Fabio Estevam <festevam@gmail.com>,
Clemens Gruber <clemens.gruber@pqgruber.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: sgtl5000: only check VDDD-supply, not revision
Date: Fri, 3 Jun 2016 18:23:18 +0200 [thread overview]
Message-ID: <5751AEF6.40200@nelint.com> (raw)
In-Reply-To: <CAOMZO5B20n7Tu3r+BsU2R5BbYj41tf7qBsMLRWxChdWMkHxLNQ@mail.gmail.com>
Hi Fabio,
On 06/02/2016 05:48 PM, Fabio Estevam wrote:
> Hi Clemens,
>
> On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber
> <clemens.gruber@pqgruber.com> wrote:
>> Instead of checking the SGTL5000 chip revision, we should only check if
>> the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
>> if the regulator is missing.
>> Otherwise, the user reads in the kernel log that the internal LDO is
>> used, even though he did follow the NXP recommendation to use external
>> VDDD and also specified VDDD-supply in the devicetree.
>>
>> Also remove the comment, which incorrectly states that external VDDD is
>> only supported for SGTL5000 chip revisions < 0x11.
>> Official NXP documentation recommends using external VDDD and not the
>> internal LDO due to the SGTL5000 erratum ER1. This also applies to
>> revisions >= 0x11.
>>
>> Tested on an i.MX6Q board with SGTL5000 rev 0x11 and external VDDD.
>
> Patch looks good to me.
>
> Eric,
>
> Sometime ago you were looking at this. What do you think about this patch?
>
Sorry. I'm traveling and haven't had a chance to review this, but it's
on my to-do.
next prev parent reply other threads:[~2016-06-03 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 12:47 [PATCH] ASoC: sgtl5000: only check VDDD-supply, not revision Clemens Gruber
2016-06-02 15:48 ` Fabio Estevam
2016-06-02 16:56 ` Mark Brown
2016-06-03 15:52 ` Clemens Gruber
2016-06-03 16:23 ` Eric Nelson [this message]
2016-06-04 5:18 ` Eric Nelson
2016-06-04 9:03 ` Clemens Gruber
[not found] ` <20160604171525.GA29266@archie.localdomain>
2016-06-05 23:16 ` [alsa-devel] " Clemens Gruber
2016-06-06 1:22 ` Fabio Estevam
2016-06-06 16:45 ` Clemens Gruber
2016-06-06 17:10 ` Fabio Estevam
2016-06-06 17:55 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2016-05-31 19:11 Clemens Gruber
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=5751AEF6.40200@nelint.com \
--to=eric@nelint.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=clemens.gruber@pqgruber.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox