mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>
Subject: [Q] regulators: 3-current-regulated supply
Date: Thu, 15 Nov 2012 08:15:15 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.1211150749290.684@axis700.grange> (raw)

Hi

I'm trying to implement a regulator driver for a PMIC [1], and so far I 
don't see how it can be mapped to the present regulator API. Most its 
parts are pretty simple - DCDC step-down, LDO. The first step-up DCDC 
isn't a problem either. It's the second step-up supply, that I'm having a 
problem with. It's output voltage can be regulated by using either a 
voltage feedback or the three current feedbacks. In the current feedback 
mode one has a choice between a manual mode, in which case you just choose 
one of the feedbacks and everything is simple again, or in automatic mode. 
In the automatic mode one can use any subset of the 3 feedbacks. Then the 
PMIC "automatically selects the highest string" (any idea what that means 
anyone?) In any case, that means, that the chip uses some algorithm to 
pick up one of the feedbacks dynamically at run-time, depending on the 
current loads. So, question #1: what should I return from 
.get_current_limit()? I don't think there is a way to find out, which 
current limit is currently being used or how much consumers consume. #2: 
how do I set those 3 limits, resp., what do I do in .set_current_limit()? 
Looks like an API extension is needed...

Thanks
Guennadi

[1] http://www.ams.com/eng/content/download/278923/1044357/AS3711_Datasheet_v1_20.pdf
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

             reply	other threads:[~2012-11-15  7:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15  7:15 Guennadi Liakhovetski [this message]
2012-11-15  7:18 ` Mark Brown
2012-11-15 10:10   ` Guennadi Liakhovetski

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=Pine.LNX.4.64.1211150749290.684@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.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

all inboxes | Powered by JetHome®