linux-kernel - Re: da9030: ldo11 ignores disable

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]

Message-Id: <1246009446.30631.27.camel@vega.slimlogic.co.uk>
Date:	Fri, 26 Jun 2009 10:44:05 +0100
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Mark Brown <broonie@...ena.org.uk>, mike.rapoport@...il.com,
	eric miao <eric.y.miao@...il.com>
Subject: Re: da9030: ldo11 ignores disable

On Thu, 2009-06-25 at 15:39 +0000, Jonathan Cameron wrote:
> Hi All,
> 
> Whilst testing a regulator machine config I've run into a weird issue.
> 
> The preliminary data sheet I have suggests that there are two enable
> registers
> for ldo11 but neither rctl22 or rctl11 seems to have any effect (on
> their own
> or both cleared together). I can change the voltage just fine, but not
> actually turn it off.
> 
> Anyone come across this problem or have any idea what is going on?

I've come across something similar in the past with two enable bits
causing I2C register cache coherency issues. The cache bits became out
of sync with reality and stopped some I2C writes happening.

Another option is that your hardware config doesn't allow ldo11 to be
disabled ?

HTH

Liam

--
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/