From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"robherring2@gmail.com" <robherring2@gmail.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"lina.iyer@linaro.org" <lina.iyer@linaro.org>
Subject: Re: [PATCH 2/6] ARM: cpuidle: Add a cpuidle ops structure to be used for DT
Date: Tue, 17 Mar 2015 12:01:59 +0100 [thread overview]
Message-ID: <550809A7.3020600@linaro.org> (raw)
In-Reply-To: <20150316181659.GA13335@red-moon>
On 03/16/2015 07:16 PM, Lorenzo Pieralisi wrote:
> On Tue, Mar 03, 2015 at 12:29:33PM +0000, Daniel Lezcano wrote:
>> The current state of the different cpuidle drivers is the different PM
>
> Nit: "The current state of cpuidle drivers is such that different ..."
Ok.
>> operations are passed via the platform_data using the platform driver
>> paradigm.
>>
>> This approach allowed to split the low level PM code from the arch specific
>> and the generic cpuidle code.
>>
>> Unfortunately there are complains about this approach as, in the context of the
>
> Nit: s/complains/complaints
Ok.
[ ... ]
>> @@ -27,4 +27,14 @@ static inline int arm_cpuidle_simple_enter(struct cpuidle_device *dev,
>> */
>> #define ARM_CPUIDLE_WFI_STATE ARM_CPUIDLE_WFI_STATE_PWR(UINT_MAX)
>>
>> +struct cpuidle_ops {
>> + const char *name;
>> + int (*suspend)(int cpu, unsigned long arg);
>> + int (*init)(struct device_node *, int cpu);
>> +};
>> +
>> +extern int arm_cpuidle_suspend(int index);
>> +
>> +extern int arm_cpuidle_init(int cpu);
>
> idle_cpu_suspend()
> idle_cpu_init()
>
> ?
>
> I am really not fussed about the naming.
>
> To make this and x86 driver name compliant (well, function signatures
> are a bit different) we could use:
>
> arm_idle()
> arm_idle_cpu_init()
>
> even though I think the arch prefix is useless.
>
> Side note: why is the x86 driver in drivers/idle ? To have another dir :) ?
I believe it is there for historical reasons.
[ ... ]
>> +static struct cpuidle_ops cpuidle_ops[NR_CPUS];
>
> That's because you want platform cpuidle_ops to be __initdata ?
Yes.
> It should not be a big overhead on arm32 to have a number of
> structs equal to NR_CPUS, on arm64 it is the other way around
> there are few cpu_ops, but number of CPUs can be high so it
> is an array of pointers.
>
> I think it is ok to leave it as it is (or probably make cpuidle_ops
> a single struct, I expect enable-method to be common across cpus).
I prefer to keep per cpu because I am not sure of this assumption.
[ ... ]
>> + cpuidle_ops[cpu] = *ops; /* structure copy */
>
> See above.
>
>> +
>> + pr_notice("cpuidle: enable-method property '%s'"
>> + " found operations\n", ops->name);
>> +
>> + return 0;
>> +}
>> +
>> +int __init arm_cpuidle_init(int cpu)
>> +{
>> + int ret = -EOPNOTSUPP;
>
> Nit: You always assign ret, so there is no point in initializing it.
Ok, I will fix it.
Thanks for reviewing.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] ARM: cpuidle: Add a cpuidle ops structure to be used for DT
Date: Tue, 17 Mar 2015 12:01:59 +0100 [thread overview]
Message-ID: <550809A7.3020600@linaro.org> (raw)
In-Reply-To: <20150316181659.GA13335@red-moon>
On 03/16/2015 07:16 PM, Lorenzo Pieralisi wrote:
> On Tue, Mar 03, 2015 at 12:29:33PM +0000, Daniel Lezcano wrote:
>> The current state of the different cpuidle drivers is the different PM
>
> Nit: "The current state of cpuidle drivers is such that different ..."
Ok.
>> operations are passed via the platform_data using the platform driver
>> paradigm.
>>
>> This approach allowed to split the low level PM code from the arch specific
>> and the generic cpuidle code.
>>
>> Unfortunately there are complains about this approach as, in the context of the
>
> Nit: s/complains/complaints
Ok.
[ ... ]
>> @@ -27,4 +27,14 @@ static inline int arm_cpuidle_simple_enter(struct cpuidle_device *dev,
>> */
>> #define ARM_CPUIDLE_WFI_STATE ARM_CPUIDLE_WFI_STATE_PWR(UINT_MAX)
>>
>> +struct cpuidle_ops {
>> + const char *name;
>> + int (*suspend)(int cpu, unsigned long arg);
>> + int (*init)(struct device_node *, int cpu);
>> +};
>> +
>> +extern int arm_cpuidle_suspend(int index);
>> +
>> +extern int arm_cpuidle_init(int cpu);
>
> idle_cpu_suspend()
> idle_cpu_init()
>
> ?
>
> I am really not fussed about the naming.
>
> To make this and x86 driver name compliant (well, function signatures
> are a bit different) we could use:
>
> arm_idle()
> arm_idle_cpu_init()
>
> even though I think the arch prefix is useless.
>
> Side note: why is the x86 driver in drivers/idle ? To have another dir :) ?
I believe it is there for historical reasons.
[ ... ]
>> +static struct cpuidle_ops cpuidle_ops[NR_CPUS];
>
> That's because you want platform cpuidle_ops to be __initdata ?
Yes.
> It should not be a big overhead on arm32 to have a number of
> structs equal to NR_CPUS, on arm64 it is the other way around
> there are few cpu_ops, but number of CPUs can be high so it
> is an array of pointers.
>
> I think it is ok to leave it as it is (or probably make cpuidle_ops
> a single struct, I expect enable-method to be common across cpus).
I prefer to keep per cpu because I am not sure of this assumption.
[ ... ]
>> + cpuidle_ops[cpu] = *ops; /* structure copy */
>
> See above.
>
>> +
>> + pr_notice("cpuidle: enable-method property '%s'"
>> + " found operations\n", ops->name);
>> +
>> + return 0;
>> +}
>> +
>> +int __init arm_cpuidle_init(int cpu)
>> +{
>> + int ret = -EOPNOTSUPP;
>
> Nit: You always assign ret, so there is no point in initializing it.
Ok, I will fix it.
Thanks for reviewing.
-- Daniel
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-03-17 11:01 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 12:29 [PATCH 0/6] ARM: cpuidle: Unify the ARM64/ARM DT approach Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-03 12:29 ` [PATCH 1/6] ARM: cpuidle: Remove duplicate header inclusion Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-13 17:54 ` Lorenzo Pieralisi
2015-03-13 17:54 ` Lorenzo Pieralisi
2015-03-03 12:29 ` [PATCH 2/6] ARM: cpuidle: Add a cpuidle ops structure to be used for DT Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-16 18:16 ` Lorenzo Pieralisi
2015-03-16 18:16 ` Lorenzo Pieralisi
2015-03-17 11:01 ` Daniel Lezcano [this message]
2015-03-17 11:01 ` Daniel Lezcano
2015-03-16 22:08 ` Stephen Boyd
2015-03-16 22:08 ` Stephen Boyd
2015-03-17 11:29 ` Lorenzo Pieralisi
2015-03-17 11:29 ` Lorenzo Pieralisi
2015-03-18 1:14 ` Stephen Boyd
2015-03-18 1:14 ` Stephen Boyd
2015-03-18 8:13 ` Daniel Lezcano
2015-03-18 8:13 ` Daniel Lezcano
2015-03-20 17:23 ` Catalin Marinas
2015-03-20 17:23 ` Catalin Marinas
2015-03-03 12:29 ` [PATCH 3/6] ARM64: cpuidle: Replace cpu_suspend by the common ARM/ARM64 function Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-13 18:21 ` Catalin Marinas
2015-03-13 18:21 ` Catalin Marinas
2015-03-13 21:22 ` Daniel Lezcano
2015-03-13 21:22 ` Daniel Lezcano
2015-03-03 12:29 ` [PATCH 5/6] ARM64: cpuidle: Remove arm64 reference Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
[not found] ` <1425385777-14766-1-git-send-email-daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-03-03 12:29 ` [PATCH 4/6] ARM64: cpuidle: Rename cpu_init_idle to a common function name Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
[not found] ` <1425385777-14766-5-git-send-email-daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-03-13 18:22 ` Catalin Marinas
2015-03-13 18:22 ` Catalin Marinas
2015-03-13 18:22 ` Catalin Marinas
2015-03-14 11:41 ` Catalin Marinas
2015-03-14 11:41 ` Catalin Marinas
2015-03-15 16:26 ` Lorenzo Pieralisi
2015-03-15 16:26 ` Lorenzo Pieralisi
2015-03-20 16:01 ` Daniel Lezcano
2015-03-20 16:01 ` Daniel Lezcano
2015-03-20 16:01 ` Daniel Lezcano
2015-03-20 17:26 ` Catalin Marinas
2015-03-20 17:26 ` Catalin Marinas
2015-03-03 12:29 ` [PATCH 6/6] ARM: cpuidle: Enable the ARM64 driver for both ARM32/ARM64 Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-03 12:29 ` Daniel Lezcano
2015-03-12 14:25 ` [PATCH 0/6] ARM: cpuidle: Unify the ARM64/ARM DT approach Daniel Lezcano
2015-03-12 14:25 ` Daniel Lezcano
2015-03-12 14:25 ` Daniel Lezcano
2015-03-13 18:29 ` Catalin Marinas
2015-03-13 18:29 ` Catalin Marinas
2015-03-13 21:26 ` Daniel Lezcano
2015-03-13 21:26 ` Daniel Lezcano
2015-03-13 20:51 ` Rob Herring
2015-03-13 20:51 ` Rob Herring
2015-03-13 21:31 ` Daniel Lezcano
2015-03-13 21:31 ` Daniel Lezcano
2015-03-15 16:48 ` Lorenzo Pieralisi
2015-03-15 16:48 ` Lorenzo Pieralisi
2015-03-13 17:03 ` Kevin Hilman
2015-03-13 17:03 ` Kevin Hilman
2015-03-13 17:08 ` Daniel Lezcano
2015-03-13 17:08 ` Daniel Lezcano
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=550809A7.3020600@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Catalin.Marinas@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=lina.iyer@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robherring2@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.