From: Mark Brown <broonie@kernel.org>
To: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
lgirdwood@gmail.com, devicetree@vger.kernel.org,
robh+dt@kernel.org, grant.likely@linaro.org,
Robin Gong <b38343@freescale.com>
Subject: Re: PFUZE100 regulator not going off when PWRON is 0
Date: Wed, 3 Sep 2014 13:52:48 +0100 [thread overview]
Message-ID: <20140903125248.GK29327@sirena.org.uk> (raw)
In-Reply-To: <CAL8zT=hNnRU3gbprVXOMt6FC9veRvQKRmS9gSeCm5-DNfGv-xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Wed, Sep 03, 2014 at 11:44:22AM +0200, Jean-Michel Hautbois wrote:
> I have a custom i.MX6 based board, but PMIC part is exactly the same
> as the Freescale SabreSD board.
> I have a reset button, which makes the PWRON signal on PFUZE100 go from 1 to 0.
> I thought this would reset the chip, and thus all voltages would go to
> 0, but this is not the case. It seems that SWxOMODE registers are
> involved in this process, accorgind to the datasheet, but I don't
> think this is implemented right now.
>
> I also removed regulator-always-on for my SW2 pin in order to get it
> off, but this has no effect.
You should really contact someone who worked on the driver or Freescale
about this - I don't think anyone on the CC list knows anything about
the part. In general if you're asking about a specific driver this is a
good approach. I've CCed Robin Gong who was the original author.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-03 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 9:44 PFUZE100 regulator not going off when PWRON is 0 Jean-Michel Hautbois
2014-09-03 12:52 ` Mark Brown [this message]
2014-09-09 2:41 ` Robin Gong
2014-09-09 20:59 ` Jean-Michel Hautbois
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=20140903125248.GK29327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=b38343@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=jean-michel.hautbois@vodalys.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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