From: Lina Iyer <lina.iyer@linaro.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: sboyd@codeaurora.org, daniel.lezcano@linaro.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, khilman@linaro.org,
msivasub@codeaurora.org, lorenzo.pieralisi@arm.com,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v6 1/5] qcom: spm: Add Subsystem Power Manager driver
Date: Fri, 26 Sep 2014 08:45:42 -0600 [thread overview]
Message-ID: <20140926144542.GA390@ilina-mac.local> (raw)
In-Reply-To: <20140924192945.GC1004@ilina-mac.local>
On Wed, Sep 24 2014 at 13:30 -0600, Lina Iyer wrote:
>On Wed, Sep 24 2014 at 11:53 -0600, Kumar Gala wrote:
>>
>>On Sep 24, 2014, at 12:21 PM, Lina Iyer <lina.iyer@linaro.org> wrote:
>>
>>>On Wed, Sep 24 2014 at 10:33 -0600, Kumar Gala wrote:
>>>>
>>>>On Sep 23, 2014, at 6:51 PM, Lina Iyer <lina.iyer@linaro.org> wrote:
>>>>
>>>>+- qcom,saw2-delays: The SPM delay values that SPM sequences would refer to.
>>>>>+ The register for this property is MSM_SPM_REG_SAW2_SPM_DLY.
>>>>
>>>>Didn’t Stephen asked about splitting this up? Or at least treating it as an array of 3 values?
>>>>
>>>Yes he did. My response was similar to the clk-div values, its not
>>>something you can change without hardware spec documentation.
>>>And I need to mix the three values up, anyways before I write to the
>>>register. Splitting it up, doesnt help understanding/configuring the SPM
>>>any better, so didnt change it.
>>
>>Hmm, will this value change from SPM to SPM on the same SoC? I’m not a fan of allowing random register values to get poked into the HW from DT. While this one case might end up being acceptable, its a terrible practice and not something I want use in the habit of doing.
>>
>Ah. Tough proposition! The SPM sequence is a bunch of random register
>values, which is not open to interpretation without the programming
>guides. I am not sure how I can use DT for saving all the register data
>then.
>
>I agree its nice to have nice readable parameters in the DT, but, isnt
>the purpose of the DT, the hardware configuration? In an alternate way
>to do this, I could put all these register writes into the driver itself
>for each SoC. Ugly as it may be, it would solve the problem. However,
>the device node then just has the compatible string in it and may be
>some configurable elements. I fail to see the big picture of the use of
>DT in such a case.
>
>FWIW, I do understand your stance with DT, and for the most part agree
>with it.
>
Based on our offline discussion, I will make the changes to move these
proprietary register values into the driver. I will submit a patch with
the changes soon.
Thanks,
Lina.
WARNING: multiple messages have this Message-ID (diff)
From: lina.iyer@linaro.org (Lina Iyer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/5] qcom: spm: Add Subsystem Power Manager driver
Date: Fri, 26 Sep 2014 08:45:42 -0600 [thread overview]
Message-ID: <20140926144542.GA390@ilina-mac.local> (raw)
In-Reply-To: <20140924192945.GC1004@ilina-mac.local>
On Wed, Sep 24 2014 at 13:30 -0600, Lina Iyer wrote:
>On Wed, Sep 24 2014 at 11:53 -0600, Kumar Gala wrote:
>>
>>On Sep 24, 2014, at 12:21 PM, Lina Iyer <lina.iyer@linaro.org> wrote:
>>
>>>On Wed, Sep 24 2014 at 10:33 -0600, Kumar Gala wrote:
>>>>
>>>>On Sep 23, 2014, at 6:51 PM, Lina Iyer <lina.iyer@linaro.org> wrote:
>>>>
>>>>+- qcom,saw2-delays: The SPM delay values that SPM sequences would refer to.
>>>>>+ The register for this property is MSM_SPM_REG_SAW2_SPM_DLY.
>>>>
>>>>Didn?t Stephen asked about splitting this up? Or at least treating it as an array of 3 values?
>>>>
>>>Yes he did. My response was similar to the clk-div values, its not
>>>something you can change without hardware spec documentation.
>>>And I need to mix the three values up, anyways before I write to the
>>>register. Splitting it up, doesnt help understanding/configuring the SPM
>>>any better, so didnt change it.
>>
>>Hmm, will this value change from SPM to SPM on the same SoC? I?m not a fan of allowing random register values to get poked into the HW from DT. While this one case might end up being acceptable, its a terrible practice and not something I want use in the habit of doing.
>>
>Ah. Tough proposition! The SPM sequence is a bunch of random register
>values, which is not open to interpretation without the programming
>guides. I am not sure how I can use DT for saving all the register data
>then.
>
>I agree its nice to have nice readable parameters in the DT, but, isnt
>the purpose of the DT, the hardware configuration? In an alternate way
>to do this, I could put all these register writes into the driver itself
>for each SoC. Ugly as it may be, it would solve the problem. However,
>the device node then just has the compatible string in it and may be
>some configurable elements. I fail to see the big picture of the use of
>DT in such a case.
>
>FWIW, I do understand your stance with DT, and for the most part agree
>with it.
>
Based on our offline discussion, I will make the changes to move these
proprietary register values into the driver. I will submit a patch with
the changes soon.
Thanks,
Lina.
next prev parent reply other threads:[~2014-09-26 14:45 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 23:51 [PATCH v6 0/5] QCOM 8074 cpuidle driver Lina Iyer
2014-09-23 23:51 ` Lina Iyer
2014-09-23 23:51 ` [PATCH v6 1/5] qcom: spm: Add Subsystem Power Manager driver Lina Iyer
2014-09-23 23:51 ` Lina Iyer
2014-09-24 1:58 ` Lina Iyer
2014-09-24 1:58 ` Lina Iyer
2014-09-24 16:33 ` Kumar Gala
2014-09-24 16:33 ` Kumar Gala
2014-09-24 17:21 ` Lina Iyer
2014-09-24 17:21 ` Lina Iyer
2014-09-24 17:53 ` Kumar Gala
2014-09-24 17:53 ` Kumar Gala
2014-09-24 19:29 ` Lina Iyer
2014-09-24 19:29 ` Lina Iyer
2014-09-26 14:45 ` Lina Iyer [this message]
2014-09-26 14:45 ` Lina Iyer
2014-09-26 14:53 ` Kumar Gala
2014-09-26 14:53 ` Kumar Gala
2014-09-26 15:07 ` Lina Iyer
2014-09-26 15:07 ` Lina Iyer
2014-09-24 17:43 ` Josh Cartwright
2014-09-24 17:43 ` Josh Cartwright
2014-09-24 19:01 ` Lina Iyer
2014-09-24 19:01 ` Lina Iyer
2014-09-24 18:07 ` Kumar Gala
2014-09-24 18:07 ` Kumar Gala
2014-09-24 18:47 ` Lina Iyer
2014-09-24 18:47 ` Lina Iyer
2014-09-26 19:04 ` Kevin Hilman
2014-09-26 19:04 ` Kevin Hilman
2014-09-26 19:12 ` Lina Iyer
2014-09-26 19:12 ` Lina Iyer
2014-09-26 19:30 ` Kevin Hilman
2014-09-26 19:30 ` Kevin Hilman
2014-09-26 16:59 ` Kevin Hilman
2014-09-26 16:59 ` Kevin Hilman
2014-09-26 17:19 ` Lina Iyer
2014-09-26 17:19 ` Lina Iyer
2014-09-23 23:51 ` [PATCH v6 2/5] arm: dts: qcom: Add SPM device bindings for 8974 Lina Iyer
2014-09-23 23:51 ` Lina Iyer
2014-09-24 6:18 ` Pramod Gurav
2014-09-24 6:18 ` Pramod Gurav
2014-09-24 13:49 ` Lina Iyer
2014-09-24 13:49 ` Lina Iyer
2014-09-24 14:03 ` Kumar Gala
2014-09-24 14:03 ` Kumar Gala
2014-09-24 14:13 ` Lina Iyer
2014-09-24 14:13 ` Lina Iyer
2014-09-24 17:21 ` Stephen Boyd
2014-09-24 17:21 ` Stephen Boyd
2014-09-24 17:23 ` Lina Iyer
2014-09-24 17:23 ` Lina Iyer
2014-09-24 21:46 ` Stephen Boyd
2014-09-24 21:46 ` Stephen Boyd
2014-09-23 23:51 ` [PATCH v6 3/5] qcom: msm-pm: Add cpu low power mode functions Lina Iyer
2014-09-23 23:51 ` Lina Iyer
2014-09-23 23:51 ` [PATCH v6 4/5] qcom: cpuidle: Add cpuidle driver for QCOM cpus Lina Iyer
2014-09-23 23:51 ` Lina Iyer
2014-09-23 23:51 ` [PATCH v6 5/5] arm: dts: qcom: Add idle states device nodes for 8974 Lina Iyer
2014-09-23 23:51 ` 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=20140926144542.GA390@ilina-mac.local \
--to=lina.iyer@linaro.org \
--cc=daniel.lezcano@linaro.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 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.