linux-kernel - Re: PFUZE100 regulator not going off when PWRON is 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 9 Sep 2014 10:41:02 +0800
From:	Robin Gong <b38343@...escale.com>
To:	Mark Brown <broonie@...nel.org>
CC:	Jean-Michel Hautbois <jean-michel.hautbois@...alys.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	<lgirdwood@...il.com>, <devicetree@...r.kernel.org>,
	<robh+dt@...nel.org>, <grant.likely@...aro.org>
Subject: Re: PFUZE100 regulator not going off when PWRON is 0

Thanks for Mark's forward.

Hi Jean-Michel,
  Yes, SWxOMODE can be set as 1 to active sleep mode if PWRON turn-off event
occurs. And the voltage of sleep mode can be set in other register SWxOFF. But
by default, SWxOMODE is 0 which means all SW will be turned off while PWRON go
form 1 to 0. For your issue, I hope you check the hardware design, and measure
PWRON pin to see whether it has been pulled low once your push reset key.

On Wed, Sep 03, 2014 at 01:52:48PM +0100, Mark Brown wrote:
> 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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/