All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jorge Ramirez-Ortiz, Foundries <jorge@foundries.io>
To: u-boot@lists.denx.de
Subject: question: mx7ulp - LDO_ENABLED_MODE
Date: Thu, 16 Jan 2020 21:30:00 +0100	[thread overview]
Message-ID: <20200116203000.GA21781@trex> (raw)

Hi Fabio,

I am trying to enable LDO in an imx7ulp based board but somehow the
board locks up as soon I  write to PMC1_RUN (using the init_ldo_mode
sequence).

I think it is interesting that bit PMC0_CTRL_PMC1ON is already set so
I am wondering if you think it is possible - in your experience- that
ROM might have already configured LDO? or was this also the case -
this bit already set- when you tested the feature?

I also noticed that if I dont execute the init_ldo_mode sequence and
just check for the LODEN bit [see snipet below], this is already set
which too seems strange.

any suggestions or thoughts?

thanks in advance!

Jorge


#define PMC0_BASE_ADDR		0x410a1000
#define PMC0_CTRL		0x28
#define PMC0_CTRL_LDOEN		BIT(31)

static bool ldo_mode_is_enabled(void)
{
	unsigned int reg;

	reg = readl(PMC0_BASE_ADDR + PMC0_CTRL);
	if (reg & PMC0_CTRL_LDOEN)
		return true;
	else
		return false;
}

             reply	other threads:[~2020-01-16 20:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 20:30 Jorge [this message]
2020-01-16 21:33 ` question: mx7ulp - LDO_ENABLED_MODE Fabio Estevam
2020-01-16 21:51   ` Fabio Estevam
2020-01-16 22:04     ` Fabio Estevam
2020-01-16 22:24       ` Jorge
2020-01-16 22:38         ` Fabio Estevam
2020-01-17  9:24           ` Jorge
2020-01-16 22:01   ` Jorge
2020-01-17 13:26 ` Fabio Estevam
2020-01-17 14:26   ` Jorge
2020-01-17 16:51   ` Jorge
2020-01-17 17:18     ` Fabio Estevam
2020-01-17 18:40       ` Jorge
2020-01-17 18:53         ` Fabio Estevam
2020-01-17 19:02           ` Jorge

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=20200116203000.GA21781@trex \
    --to=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 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.