From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] PMIC: TI: TPS65903X errata (SLIA087) code
Date: Thu, 16 Mar 2017 06:49:14 +0100 [thread overview]
Message-ID: <20170316064914.082fd912@jawa> (raw)
In-Reply-To: <115d9898-ba2e-4bbf-e766-c6e3ea06f641@ti.com>
Hi Lokesh,
> Hi Lucas,
>
> On Saturday 11 March 2017 04:10 AM, Lukasz Majewski wrote:
> > This patch adds code, which comply with TPS65903X errata pseudocode
> > described in SLIA087 - "Guide to Using the GPADC in TPS65903x and
> > TPS6591x Devices".
> >
> > It is enabled by proper Kconfig option, when TI's palmas PMIC
> > support is added.
> >
> > The TI's e2e thread with test procedure description:
> > https://e2e.ti.com/support/power_management/pmu/f/200/p/579649/2130910#2130910
>
> I could not understand the reason for why this is being done in
> U-Boot. Can you explain a it more on this?
Just as a safety matter. Doing this for GPADC PMIC in u-boot avoids
"surprises" latter on - when the high level user wants to use the GPADC
results from the first measurement that he/she does (for example at
safety critical application).
The u-boot driver (as it touches it first) is responsible to give the
TPS65903x PMIC to latter boot stage as free from any known problems
(i.e erratas).
>
> Thanks and regards,
> Lokesh
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
next prev parent reply other threads:[~2017-03-16 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 22:40 [U-Boot] [PATCH] PMIC: TI: TPS65903X errata (SLIA087) code Lukasz Majewski
2017-03-14 13:22 ` Tom Rini
2017-03-15 10:07 ` Lukasz Majewski
2017-03-15 13:35 ` Tom Rini
2017-03-15 14:23 ` Lukasz Majewski
2017-03-16 5:16 ` Lokesh Vutla
2017-03-16 5:49 ` Lukasz Majewski [this message]
2017-03-16 10:47 ` Lokesh Vutla
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=20170316064914.082fd912@jawa \
--to=lukma@denx.de \
--cc=u-boot@lists.denx.de \
/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