public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Mark Brown <broonie@sirena.org.uk>,
	mike.rapoport@gmail.com, eric miao <eric.y.miao@gmail.com>
Subject: Re: da9030: ldo11 ignores disable
Date: Fri, 26 Jun 2009 10:17:10 +0000	[thread overview]
Message-ID: <4A44A026.3050207@cam.ac.uk> (raw)
In-Reply-To: <1246009446.30631.27.camel@vega.slimlogic.co.uk>

Liam Girdwood wrote:
> 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.
Don't thing that could happen here.
> 
> Another option is that your hardware config doesn't allow ldo11 to be
> disabled ?
Other than the obvious possibility that the hardware has a bug, I can't
seem to find a reason why this shouldn't work.

Thanks,

Jonathan

  reply	other threads:[~2009-06-26 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 15:39 da9030: ldo11 ignores disable Jonathan Cameron
2009-06-26  9:44 ` Liam Girdwood
2009-06-26 10:17   ` Jonathan Cameron [this message]
2009-07-03  7:46     ` Eric Miao
2009-07-14 15:17       ` Eric Miao
2009-07-14 15:34         ` Jonathan Cameron

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=4A44A026.3050207@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=broonie@sirena.org.uk \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=mike.rapoport@gmail.com \
    /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