From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] PMIC initialization
Date: Sun, 17 Feb 2019 23:54:57 +0100 [thread overview]
Message-ID: <20190217235457.682289bd@jawa> (raw)
In-Reply-To: <AM6P191MB04726736E3FCFB1408DFA10893640@AM6P191MB0472.EURP191.PROD.OUTLOOK.COM>
Hi Jeroen van der Laan,
> Hi there,
>
> I'm working on a board that is based on a i.Mx6soloX it has a
> PFUZE3000 PMIC the u-boot version we're using is 2016-03. The PMIC is
> by default configured with a voltage for our DRAM that is too low.
> We've discovered that this is an issue with some boards some of the
> time. The voltage is just below the bare minimum so I think the board
> has no big issue most of the time.
>
> I want to adjust the voltage in u-boot in time for the board bring
> up. I'm afraid that a lot of issues will disappear but our tests will
> not cover if the initialization is too late. I want to be absolutely
> certain that it happens on time before the memory initialization.
>
> what is the place to do this?
> Should I use an SPL bootloader?
You shall do it just before the DRAM init (and of course wait for some
time so the voltage can stabilize).
You don't need to use the PMIC DM/framework, just communicate with I2C
and change the values of registers of pfuze.
> Is power_init_board soon enough, or does code in this place require
> RAM? Are there any other options?
I think that board_early_init is a good place for this, but u-boot
2016.03 differs considerably from what we have now as massive DM/DTS
conversion is going on.
>
> Best regards,
> Jeroen van der Laan
>
>
> [ICT zorgt voor mensen]<https://www.zorg-en-ict.nl/default.aspx>
>
>
> Dit e-mailbericht is uitsluitend bestemd voor de geadresseerde. Als
> dit bericht niet voor u bestemd is, wordt u vriendelijk verzocht dit
> aan de afzender te melden. Van Breda BV staat door de elektronische
> verzending van dit bericht niet in voor de juiste en volledige
> overbrenging van de inhoud, noch voor tijdige ontvangst daarvan. Voor
> informatie over Van Breda BV raadpleegt u
> www.vanbreda.nl<http://www.vanbreda.nl>.
>
> This e-mail is intended for the addressee's eyes only. If you are not
> the intended recipient, you are hereby kindly requested to inform the
> sender of this. In view of the electronic nature of this
> communication, Van Breda BV is neither liable for the proper and
> complete transmission of the information contained therein nor for
> any delay in its receipt. For information about Van Breda BV, please
> visit www.vanbreda.nl<http://www.vanbreda.nl>.
> _______________________________________________ U-Boot mailing list
> U-Boot at lists.denx.de https://lists.denx.de/listinfo/u-boot
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-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190217/a37f1d3b/attachment.sig>
prev parent reply other threads:[~2019-02-17 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 10:37 [U-Boot] PMIC initialization Jeroen van der Laan
2019-02-17 22:54 ` Lukasz Majewski [this message]
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=20190217235457.682289bd@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