From: Axel Haslam <ahaslam@baylibre.com>
To: Lina Iyer <lina.iyer@linaro.org>
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
"Kevin Hilman" <khilman@linaro.org>,
"Krzysztof Kozłowski" <k.kozlowski.k@gmail.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Benoit Cousson" <bcousson@baylibre.com>,
"Linux PM list" <linux-pm@vger.kernel.org>,
"Axel Haslam" <ahaslam+renesas@baylibre.com>
Subject: Re: [PATCH v7 1/5] PM / Domains: prepare for multiple states
Date: Tue, 12 May 2015 18:26:35 +0200 [thread overview]
Message-ID: <CAKXjFTNYDoU0b==wgNwX8KRx5gtnzHYn_ET66=oTdHE7SabKXQ@mail.gmail.com> (raw)
In-Reply-To: <20150512153702.GL16124@linaro.org>
Hi Lina,
On Tue, May 12, 2015 at 5:37 PM, Lina Iyer <lina.iyer@linaro.org> wrote:
> On Thu, Apr 30 2015 at 04:57 -0600, ahaslam@baylibre.com wrote:
>>
>> From: Axel Haslam <ahaslam+renesas@baylibre.com>
>>
>> prepare generic power domain init function parameters
>> to accept a pointer to the states structure that describes
>> the possible states that a power domain can enter.
>>
>> There is no functional change, as support for multiple
>> domains will be added in subsequent patches.
>>
>> Signed-off-by: Axel Haslam <ahaslam+renesas@baylibre.com>
>
>
> [...]
>
>> diff --git a/include/linux/pm_domain.h b/include/linux/pm_domain.h
>> index 681ccb0..6b4802e 100644
>> --- a/include/linux/pm_domain.h
>> +++ b/include/linux/pm_domain.h
>> @@ -46,6 +46,12 @@ struct gpd_cpuidle_data {
>> struct cpuidle_state *idle_state;
>> };
>>
>> +struct genpd_power_state {
>> + char *name;
>> + s64 power_off_latency_ns;
>> + s64 power_on_latency_ns;
>> +};
>> +
>
>
> I know you carried this over from the existing code, but any reason why
> this should be signed?
>
correct, i just carried this values over as they were originally.
i suppose they can be changed to u64.
maybe a separate cleanup patch, as it would make sense to change
some other s64's in domain.c, like "s64 elapsed_ns;"
> -- Lina
next prev parent reply other threads:[~2015-05-12 16:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 10:55 [PATCH v7 0/5] genpd multiple states v7 ahaslam
2015-04-30 10:55 ` [PATCH v7 1/5] PM / Domains: prepare for multiple states ahaslam
2015-04-30 15:29 ` Lina Iyer
2015-04-30 16:06 ` Axel Haslam
2015-05-01 16:31 ` Lina Iyer
2015-05-01 18:58 ` Geert Uytterhoeven
2015-05-08 0:36 ` Krzysztof Kozlowski
2015-05-11 8:23 ` Axel Haslam
2015-05-12 15:37 ` Lina Iyer
2015-05-12 16:26 ` Axel Haslam [this message]
2015-04-30 10:55 ` [PATCH v7 2/5] PM / Domains: core changes " ahaslam
2015-05-07 15:53 ` Lina Iyer
2015-05-08 20:53 ` Kevin Hilman
2015-05-08 22:31 ` Lina Iyer
2015-05-11 15:53 ` Axel Haslam
2015-05-11 16:50 ` Lina Iyer
2015-05-12 11:58 ` Axel Haslam
2015-05-12 15:29 ` Lina Iyer
2015-04-30 10:55 ` [PATCH v7 3/5] PM / Domains: make governor select deepest state ahaslam
2015-04-30 10:55 ` [PATCH v7 4/5] ARM: imx6: pm: declare pm domain latency on power_state struct ahaslam
2015-04-30 10:55 ` [PATCH v7 5/5] PM / Domains: remove old power on/off latencies ahaslam
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='CAKXjFTNYDoU0b==wgNwX8KRx5gtnzHYn_ET66=oTdHE7SabKXQ@mail.gmail.com' \
--to=ahaslam@baylibre.com \
--cc=ahaslam+renesas@baylibre.com \
--cc=bcousson@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=k.kozlowski.k@gmail.com \
--cc=khilman@linaro.org \
--cc=lina.iyer@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.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).