linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Lina Iyer <lina.iyer@linaro.org>
Cc: daniel.lezcano@linaro.org, khilman@linaro.org,
	sboyd@codeaurora.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
Subject: Re: [PATCH v13 03/10] qcom: spm: Add Subsystem Power Manager driver
Date: Thu, 27 Nov 2014 10:44:23 +0200	[thread overview]
Message-ID: <1417077863.10282.3.camel@mm-sol.com> (raw)
In-Reply-To: <1417065854-37745-4-git-send-email-lina.iyer@linaro.org>


Hi, 

On Wed, 2014-11-26 at 22:24 -0700, Lina Iyer wrote:
> 

>  - compatible:
> @@ -14,10 +23,13 @@ PROPERTIES
>         Value type: <string>
>         Definition: shall contain "qcom,saw2". A more specific value should be
>                                                 one of:

Which driver is supposed to handle this property?

> -                               "qcom,saw2-v1"
> -                               "qcom,saw2-v1.1"
> -                               "qcom,saw2-v2"
> -                               "qcom,saw2-v2.1"
> +                       "qcom,saw2-v1"
> +                       "qcom,saw2-v1.1"
> +                       "qcom,saw2-v2"
> +                       "qcom,saw2-v2.1"

Doesn't seems to be used or supported?

> +                       "qcom,apq8064-saw2-v1.1-cpu"
> +                       "qcom,msm8974-saw2-v2.1-cpu"
> +                       "qcom,apq8084-saw2-v2.1-cpu"
> 

<snip>

> -       regulator@2099000 {
> +       power-controller@2099000 {
>                 compatible = "qcom,saw2";
>                 reg = <0x02099000 0x1000>, <0x02009000 0x1000>;
> +               regulator;
> 

<snip>

> +static const struct of_device_id spm_match_table[] = {
> +       { .compatible = "qcom,msm8974-saw2-v2.1-cpu",
> +                       .data = &spm_reg_8974_8084_cpu },
> +       { .compatible = "qcom,apq8084-saw2-v2.1-cpu",
> +                       .data = &spm_reg_8974_8084_cpu },
> +       { .compatible = "qcom,apq8064-saw2-v1.1-cpu",
> +                       .data = &spm_reg_8064_cpu },
> +       { },
> +};
> +

Regards,
Ivan

  reply	other threads:[~2014-11-27  8:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  5:24 [PATCH v13 00/10] cpuidle driver for QCOM SoCs: 8064, 8074, 8084 Lina Iyer
2014-11-27  5:24 ` [PATCH v13 01/10] qcom: scm: Move scm-boot files to drivers/soc/qcom/ and include/soc/qcom Lina Iyer
2014-11-27  5:24 ` [PATCH v13 02/10] qcom: scm: Add SCM warmboot support for quad core SoCs Lina Iyer
2014-11-27  5:24 ` [PATCH v13 03/10] qcom: spm: Add Subsystem Power Manager driver Lina Iyer
2014-11-27  8:44   ` Ivan T. Ivanov [this message]
2014-12-01 17:57     ` Lina Iyer
2014-11-27  8:52   ` Daniel Lezcano
2014-12-01 18:50     ` Lina Iyer
2014-12-02  9:53       ` Daniel Lezcano
2014-12-02 15:35         ` Lina Iyer
2014-12-02 15:47           ` Daniel Lezcano
2014-11-27 15:01   ` Lorenzo Pieralisi
2014-12-01 18:57     ` Lina Iyer
2014-12-02 11:10       ` Catalin Marinas
2014-12-02 15:52         ` Lina Iyer
2014-11-27  5:24 ` [PATCH v13 04/10] arm: dts: qcom: Add power-controller device node for 8074 Krait CPUs Lina Iyer
2014-11-27  5:24 ` [PATCH v13 05/10] arm: dts: qcom: Add power-controller device node for 8084 " Lina Iyer
2014-11-27  5:24 ` [PATCH v13 06/10] arm: dts: qcom: Update power-controller device node for 8064 " Lina Iyer
2014-11-27  5:24 ` [PATCH v13 07/10] qcom: cpuidle: Add cpuidle driver for QCOM cpus Lina Iyer
2014-11-27  5:24 ` [PATCH v13 08/10] arm: dts: qcom: Add idle states device nodes for 8074 Lina Iyer
2014-11-27  5:24 ` [PATCH v13 09/10] arm: dts: qcom: Add idle states device nodes for 8084 Lina Iyer
2014-11-27  5:24 ` [PATCH v13 10/10] arm: dts: qcom: Add idle state device nodes for 8064 Lina Iyer
2014-11-27  8:53 ` [PATCH v13 00/10] cpuidle driver for QCOM SoCs: 8064, 8074, 8084 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=1417077863.10282.3.camel@mm-sol.com \
    --to=iivanov@mm-sol.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=khilman@linaro.org \
    --cc=lina.iyer@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).