From: "Yi Zhang" <yizhanghust@163.com>
To: "Mark Brown" <broonie@kernel.org>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
yizhang@marvell.com, zhenzh@marvell.com, zhouqiao@marvell.com
Subject: Re:Re: [Question] should we export set_suspend_voltage()?
Date: Mon, 9 Feb 2015 15:37:16 +0800 (CST) [thread overview]
Message-ID: <1025bdeb.93e8.14b6d455a4f.Coremail.yizhanghust@163.com> (raw)
In-Reply-To: <20150206221058.GC31311@finisterre.sirena.org.uk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1165 bytes --]
At 2015-02-07 06:10:58, "Mark Brown" <broonie@kernel.org> wrote:
>On Fri, Feb 06, 2015 at 10:57:49AM +0800, Yi Zhang wrote:
>
>Please fix your mailer to word wrap within paragraphs, your mail is very
>difficult to read and reply to.
>
Thanks Mark for pointing this out;
>> do you think it's good to export the set_suspend_voltage()? to make it
>> controllable by the regulator itself? another method in my opinion is
>> add a set of virtual-regulator for this usage?
>
>> could you please share your advice?
>
>There's been some discussion of this in the context of some Qualcomm
>systems recently, search the archives for discussions especially with
>Bjorn Andersson recently. The basic idea was to mirror the existing
>APIs but with an additional mode argument (and permisions) to allow
>consumers to manipulate states other than the default state.
Thanks, I searched http://article.gmane.org/gmane.linux.ports.arm.msm/10606
if possible, could you please add me in that loop? thanks very much;
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2015-02-09 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 2:57 Yi Zhang
2015-02-06 22:10 ` Mark Brown
2015-02-09 7:37 ` Yi Zhang [this message]
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=1025bdeb.93e8.14b6d455a4f.Coremail.yizhanghust@163.com \
--to=yizhanghust@163.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yizhang@marvell.com \
--cc=zhenzh@marvell.com \
--cc=zhouqiao@marvell.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®