From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: EXYNOS: Add default latency values for Device and Power Domain
Date: Mon, 11 Nov 2013 15:14:31 +0100 [thread overview]
Message-ID: <1904642.oaMlk6atuQ@flatron> (raw)
In-Reply-To: <CAPmaG0t++EtdGmVg_JOZt-MU1Su=BDAe7L-tv-un3qkQRkebfg@mail.gmail.com>
Hi Prasanna,
On Monday 11 of November 2013 10:19:40 Prasanna Kumar wrote:
> On Mon, Nov 11, 2013 at 8:52 AM, Sachin Kamat <sachin.kamat@linaro.org>
> wrote:
> >
> > Hi Tomasz,
> >
> > Thanks for reviewing.
> >
> > On 10 November 2013 22:25, Tomasz Figa <tomasz.figa@gmail.com> wrote:
> > > Hi Sachin, Prasanna,
> > >
> > > [CCing Rafael and respective mailing lists]
> > >
> > > Please see my comments inline. Also please always remember to add all
> > > appropriate recipients on CC list. More reviewers means higher chance of
> > > spotting (and so eliminating) potential issues.
> >
> > Indeed. Thanks for adding. get_maintainers somehow did not list PM
> > related folks.
> > So missed this.
> >
> > >
> > > On Friday 08 of November 2013 11:57:05 Sachin Kamat wrote:
> > >> From: Prasanna Kumar <prasanna.ps@samsung.com>
> > >>
> > >> Power domain and device timing data are intialized with default
> > >> values to avoid dump of warnings from various power domains
> > >> during power gating.
> > >>
> > >> Signed-off-by: Prasanna Kumar <prasanna.ps@samsung.com>
> > >> Signed-off-by: Prathyush K <prathyush.k@samsung.com>
> > >> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> > >> ---
> > >> arch/arm/mach-exynos/pm_domains.c | 15 ++++++++++++++-
> > >> 1 file changed, 14 insertions(+), 1 deletion(-)
> > >>
> > >> diff --git a/arch/arm/mach-exynos/pm_domains.c
> > >> b/arch/arm/mach-exynos/pm_domains.c
> > >> index 84e0483a0500..9bbb4ac23980 100644
> > >> --- a/arch/arm/mach-exynos/pm_domains.c
> > >> +++ b/arch/arm/mach-exynos/pm_domains.c
> > >> @@ -25,6 +25,10 @@
> > >> #include <mach/regs-pmu.h>
> > >> #include <plat/devs.h>
> > >>
> > >> +#define DEFAULT_DEV_LATENCY_NS 1000000UL
> > >> +#define DEFAULT_PD_PWRON_LATENCY_NS 10000000UL
> > >> +#define DEFAULT_PD_PWROFF_LATENCY_NS 10000000UL
> > >
> > > Is there any rationale behind choosing these particular values?
> >
> > IMO, these values were obtained more from experimentation. Prasanna,
> > please comment.
> As Sachin mentioned, the values are obtained from experimentation to avoid
> latency warning messages. These values can be changed when the
> information becomes available from the specs.
> As of now , this seems to be good set of values.
Do you have any measurements that confirm that there is no regression
in power consumption (e.g. caused by unnecessarily delayed runtime PM
operations) after applying this patch?
Best regards,
Tomasz
next prev parent reply other threads:[~2013-11-11 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1383892025-14759-1-git-send-email-sachin.kamat@linaro.org>
2013-11-10 16:55 ` [PATCH 1/1] ARM: EXYNOS: Add default latency values for Device and Power Domain Tomasz Figa
2013-11-11 3:22 ` Sachin Kamat
2013-11-11 4:49 ` Prasanna Kumar
2013-11-11 14:14 ` Tomasz Figa [this message]
2013-11-11 14:11 ` Yadwinder Singh Brar
2013-11-11 14:15 ` Tomasz Figa
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=1904642.oaMlk6atuQ@flatron \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).