mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Eric Nelson <eric@nelint.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH] ASoC: sgtl5000: only check VDDD-supply, not revision
Date: Fri, 3 Jun 2016 17:52:02 +0200	[thread overview]
Message-ID: <20160603155202.GA854@archie.localdomain> (raw)
In-Reply-To: <20160602165651.GP2282@sirena.org.uk>

On Thu, Jun 02, 2016 at 05:56:51PM +0100, Mark Brown wrote:
> On Thu, Jun 02, 2016 at 12:48:15PM -0300, Fabio Estevam wrote:
> 
> > Sometime ago you were looking at this. What do you think about this patch?
> 
> I'm rather concerned that the patches came from people working closely
> with Freescale already - are we *sure* that Freescale/NXP's public
> errata are accurate?

This was confirmed by Freescale/NXP employees, the errata and the
datasheet. First in the errata from 2012 and also in the second revision
of the errata in 2013 and the latest datasheet from 2013.
http://cache.freescale.com/files/analog/doc/errata/SGTL5000ER.pdf
https://community.nxp.com/thread/352718#comment-506518
The latest datasheet from 2013 states: "An external VDDD is required for
new designs"

So, the SGTL5000 rev 0x11 obviously can be used with external VDDD, this
is what Freescale is recommending since 2012 and what people are doing.

The revision check was introduced in the first commit in 2011, so this
was probably a mistake and was never corrected because it still works,
but it shows a misleading message at boot and enables the internal LDO,
which is not used. It's also confusing for everyone who reads the code.

Checking if there is a VDDD-supply regulator should be sufficient.

Thanks,
Clemens

  reply	other threads:[~2016-06-03 15:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 12:47 Clemens Gruber
2016-06-02 15:48 ` Fabio Estevam
2016-06-02 16:56   ` Mark Brown
2016-06-03 15:52     ` Clemens Gruber [this message]
2016-06-03 16:23   ` Eric Nelson
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=20160603155202.GA854@archie.localdomain \
    --to=clemens.gruber@pqgruber.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=eric@nelint.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

all inboxes | Powered by JetHome®