From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Dave Jones <davej@redhat.com>, Kukjin Kim <kgene.kim@samsung.com>,
cpufreq@vger.kernel.org
Subject: Re: [PATCH 2/2] s3c64xx: Add VDDINT voltage scaling
Date: Mon, 5 Dec 2011 19:50:59 +0000 [thread overview]
Message-ID: <20111205195059.GI7467@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1968469.lEDYUZcgoo@flatron>
On Mon, Dec 05, 2011 at 08:45:47PM +0100, Tomasz Figa wrote:
> On Monday 05 of December 2011 19:25:06 Mark Brown wrote:
> > 133MHz and VDDINT at 1.05V. And driver code showing some variation from
> > the power design guide :/
> I think that people from Samsung should be able to say something a bit more
> precise on this. Am I right?
Here's hoping :)
> > If it's a question of regulator quality the board should just be adding
> > an offset in the constraints without the SoC drivers having to worry
> > their pretty little heads about it. Like I say it's not an unknown
> Right, there is a field for regulator offset in regulation_constraints
> struct indeed. Somehow I missed it, sorry.
It's possible you first looked at this with a kernel that didn't have
that feature - I added it sometime this year.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] [CPUFREQ] s3c64xx: Add VDDINT voltage scaling
Date: Mon, 5 Dec 2011 19:50:59 +0000 [thread overview]
Message-ID: <20111205195059.GI7467@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1968469.lEDYUZcgoo@flatron>
On Mon, Dec 05, 2011 at 08:45:47PM +0100, Tomasz Figa wrote:
> On Monday 05 of December 2011 19:25:06 Mark Brown wrote:
> > 133MHz and VDDINT at 1.05V. And driver code showing some variation from
> > the power design guide :/
> I think that people from Samsung should be able to say something a bit more
> precise on this. Am I right?
Here's hoping :)
> > If it's a question of regulator quality the board should just be adding
> > an offset in the constraints without the SoC drivers having to worry
> > their pretty little heads about it. Like I say it's not an unknown
> Right, there is a field for regulator offset in regulation_constraints
> struct indeed. Somehow I missed it, sorry.
It's possible you first looked at this with a kernel that didn't have
that feature - I added it sometime this year.
next prev parent reply other threads:[~2011-12-05 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 18:22 [PATCH 1/2] s3c64xx: Use pr_fmt() for consistent log messages Mark Brown
2011-12-05 18:22 ` [PATCH 1/2] [CPUFREQ] " Mark Brown
2011-12-05 18:22 ` [PATCH 2/2] s3c64xx: Add VDDINT voltage scaling Mark Brown
2011-12-05 18:22 ` [PATCH 2/2] [CPUFREQ] " Mark Brown
2011-12-05 18:45 ` [PATCH 2/2] " Tomasz Figa
2011-12-05 18:45 ` [PATCH 2/2] [CPUFREQ] " Tomasz Figa
2011-12-05 18:57 ` [PATCH 2/2] " Mark Brown
2011-12-05 18:57 ` [PATCH 2/2] [CPUFREQ] " Mark Brown
2011-12-05 19:11 ` [PATCH 2/2] " Tomasz Figa
2011-12-05 19:11 ` [PATCH 2/2] [CPUFREQ] " Tomasz Figa
2011-12-05 19:25 ` [PATCH 2/2] " Mark Brown
2011-12-05 19:25 ` [PATCH 2/2] [CPUFREQ] " Mark Brown
2011-12-05 19:45 ` [PATCH 2/2] " Tomasz Figa
2011-12-05 19:45 ` [PATCH 2/2] [CPUFREQ] " Tomasz Figa
2011-12-05 19:50 ` Mark Brown [this message]
2011-12-05 19:50 ` Mark Brown
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=20111205195059.GI7467@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=tomasz.figa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.