From: Lina Iyer <lina.iyer@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: daniel.lezcano@linaro.org, khilman@linaro.org,
galak@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
lorenzo.pieralisi@arm.com, msivasub@codeaurora.org,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [RFC PATCH v15 02/11] ARM: qcom: Add Subsystem Power Manager (SPM) driver
Date: Mon, 16 Mar 2015 16:51:27 -0600 [thread overview]
Message-ID: <20150316225127.GC501@linaro.org> (raw)
In-Reply-To: <5507506B.6060201@codeaurora.org>
On Mon, Mar 16 2015 at 15:51 -0600, Stephen Boyd wrote:
>On 03/09/15 08:16, Lina Iyer wrote:
>> +
>> +static int qcom_idle_enter(int cpu, unsigned long index)
>> +{
>> + if (!per_cpu(qcom_idle_ops, cpu)[index])
>> + return -EOPNOTSUPP;
>
>Is this case still happening?
>
I think, I can remove it safely now.
>> +
>> + return per_cpu(qcom_idle_ops, cpu)[index](cpu);
>> +}
>> +
>> +const struct of_device_id qcom_idle_state_match[] __initconst = {
>
>static?
>
Ok
>> + { .compatible = "qcom,idle-state-stby", .data = qcom_cpu_standby },
>> + { .compatible = "qcom,idle-state-spc", .data = qcom_cpu_spc },
>> + { },
>> +};
>> +
>> +static int __init qcom_cpuidle_init(struct device_node *cpu_node, int cpu)
>> +{
>> + const struct of_device_id *match_id;
>> + struct device_node *state_node;
>> + int i;
>> + int state_count = 0;
>> + idle_fn idle_fns[CPUIDLE_STATE_MAX];
>> + idle_fn *fns;
>> + cpumask_t mask;
>> + bool use_scm_power_down = false;
>> +
>> + for (i = 0; ; i++) {
>> + state_node = of_parse_phandle(cpu_node, "cpu-idle-states", i);
>> + if (!state_node)
>> + break;
>> +
>> + if (!of_device_is_available(state_node))
>> + continue;
>> +
>> + if (i == CPUIDLE_STATE_MAX) {
>> + pr_warn("%s: cpuidle states reached max possible\n",
>> + __func__);
>> + break;
>> + }
>> +
>> + match_id = of_match_node(qcom_idle_state_match, state_node);
>> + if (!match_id)
>> + return -ENODEV;
>> +
>> + idle_fns[state_count] = match_id->data;
>> +
>> + /* Check if any of the states allow power down */
>> + if (match_id->data == qcom_cpu_spc)
>> + use_scm_power_down = true;
>> +
>> + state_count++;
>> + }
>> +
>> + if (!state_count) {
>> + pr_warn("No idle ops founds for cpu %d\n", cpu);
>
>Maybe pr_debug? It's not the end of the world that we don't have cpuidle.
>
Sure.
>> + return -ENODEV;
>> + }
>> +
>> + fns = kcalloc(state_count, sizeof(*fns), GFP_KERNEL);
>> + if (!fns)
>> + return -ENOMEM;
>> +
>> + for (i = 0; i < state_count; i++)
>> + fns[i] = idle_fns[i];
>> +
>> + if (use_scm_power_down) {
>> + /* We have atlease one power down mode */
>
>s/atlease/at least/
>
Thanks!
>> + cpumask_clear(&mask);
>> + cpumask_set_cpu(cpu, &mask);
>> + qcom_scm_set_warm_boot_addr(cpu_resume, &mask);
>> + }
>> +
>> + per_cpu(qcom_idle_ops, cpu) = fns;
>> +
>> + /*
>> + * Condition: cpuidle_driver_register() needs to happen before
>> + * cpuidle_register_device().
>> + * Check if the SPM probe has happened -
>> + * - If SPM probed successfully before arm_idle_init(), then defer
>> + * the registration of cpuidle_device back to arm_idle_init()
>> + * - If the SPM probe happens in the future, then let the SPM probe
>> + * register the cpuidle device, return -ENOSYS.
>> + */
>> + return per_cpu(cpu_spm_drv, cpu) ? 0 : -ENOSYS;
>> +}
>> +
>> +struct cpuidle_ops qcom_kpss_v1_cpuidle_ops __initdata = {
>> + .name = "qcom,kpss-acc-v1",
>> + .suspend = qcom_idle_enter,
>> + .init = qcom_cpuidle_init,
>> +};
>> +
>> +struct cpuidle_ops qcom_kpss_v2_cpuidle_ops __initdata = {
>> + .name = "qcom,kpss-acc-v2",
>> + .suspend = qcom_idle_enter,
>> + .init = qcom_cpuidle_init,
>> +};
>> +
>>
>
>This just looks weird because of the macro magic in Daniel's series. Any
>reason we can't use the linker instead of doing preprocessor magic so
>that it looks like these structures are actually used?
>
Hmm.. Will wait on Daniel's response to your other mail.
>--
>Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>a Linux Foundation Collaborative Project
>
next prev parent reply other threads:[~2015-03-16 22:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 15:16 [RFC PATCH v15 00/11] ARM: qcom: cpuidle support for 8064, 8074, 8084 Lina Iyer
2015-03-09 15:16 ` [RFC PATCH v15 01/11] ARM: cpuidle: Register per cpuidle device Lina Iyer
2015-03-09 21:29 ` Andy Gross
2015-03-09 21:40 ` Lina Iyer
2015-03-09 22:04 ` Andy Gross
2015-03-10 10:37 ` Russell King - ARM Linux
2015-03-10 14:57 ` Lina Iyer
2015-03-09 15:16 ` [RFC PATCH v15 02/11] ARM: qcom: Add Subsystem Power Manager (SPM) driver Lina Iyer
2015-03-10 17:26 ` Kumar Gala
2015-03-10 18:51 ` Lina Iyer
2015-03-12 22:50 ` Lina Iyer
2015-03-16 21:51 ` Stephen Boyd
2015-03-16 22:51 ` Lina Iyer [this message]
[not found] ` <1425914206-22295-1-git-send-email-lina.iyer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-03-09 15:16 ` [PATCH v15 03/11] ARM: cpuidle: qcom: Add documentation for qcom cpuidle states Lina Iyer
2015-03-09 15:16 ` [PATCH v15 06/11] ARM: dts: qcom: Add power-controller device node for 8084 Krait CPUs Lina Iyer
2015-03-09 15:16 ` [PATCH v15 09/11] ARM: dts: qcom: Add idle states device nodes for 8084 Lina Iyer
2015-03-09 15:16 ` [RFC PATCH v15 04/11] ARM: cpuidle: Register cpuidle_ops for QCOM cpus Lina Iyer
2015-03-11 18:16 ` Stephen Boyd
2015-03-12 12:34 ` Daniel Lezcano
2015-03-12 15:06 ` Lina Iyer
2015-03-13 9:57 ` Daniel Lezcano
2015-03-09 15:16 ` [PATCH v15 05/11] ARM: dts: qcom: Add power-controller device node for 8074 Krait CPUs Lina Iyer
2015-03-09 15:16 ` [PATCH v15 07/11] ARM: dts: qcom: Update power-controller device node for 8064 " Lina Iyer
2015-03-09 15:16 ` [PATCH v15 08/11] ARM: dts: qcom: Add idle states device nodes for 8074 Lina Iyer
2015-03-09 15:16 ` [PATCH v15 10/11] ARM: dts: qcom: Add idle state device nodes for 8064 Lina Iyer
2015-03-09 15:16 ` [PATCH v15 11/11] ARM: qcom: Update defconfig Lina Iyer
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=20150316225127.GC501@linaro.org \
--to=lina.iyer@linaro.org \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=msivasub@codeaurora.org \
--cc=sboyd@codeaurora.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).