linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lina Iyer <lina.iyer@linaro.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Kevin Hilman <khilman@linaro.org>,
	Amit Kucheria <amit.kucheria@linaro.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	David Brown <davidb@codeaurora.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Mahesh Sivasubramanian <msivasub@codeaurora.org>,
	Bryan Huntsman <bryanh@codeaurora.org>,
	Praveen Chidamabram <pchidamb@codeaurora.org>,
	Murali Nalajala <mnalajal@codeaurora.org>
Subject: Re: [RFC] [PATCH 03/13] qcom: spm: Add Subsystem Power Manager driver for QCOM chipsets
Date: Fri, 8 Aug 2014 15:53:41 -0600	[thread overview]
Message-ID: <20140808215340.GA8257@ilina-mac.local> (raw)
In-Reply-To: <593CBA21-2CB5-4BED-833D-0AE7C19171C1@codeaurora.org>

On Fri, Aug 08, 2014 at 11:16:04AM -0500, Kumar Gala wrote:
>
> On Aug 7, 2014, at 11:05 PM, Lina Iyer <lina.iyer@linaro.org> wrote:
>
  > +Required properties
> > +
> > +- compatible: "qcom,spm-v2"
> > +- reg: The physical address and the size of the SPM's memory mapped registers
> > +- qcom,cpu: phandle for the CPU that the SPM block is attached to. On targets
> > + that dont support CPU phandles the driver would support qcom,core-id.
> > + This field is required on only for SPMs that control the CPU.
> > +- qcom, core-id: This property will be deprecated once all targets start
> > + supporting CPU phandles. This field will be used to identify SPMs
> > + that control the CPU.
> > + {0..n} for cores {0..n}
>
> Why aren’t we just using cpu phandles for upstream?
Need to specify L2 index as well. I dont know, but does cpu handle
define that?
>
> > +- qcom,saw2-ver-reg: The location of the version register
>
> I
>
> > +- qcom,saw2-cfg: SAW2 configuration register
>
> What does this even mean, why is this not part of the reg property?
This is a hardware register with that name. Using the same name as the 
h/w for consistency.

>
> > +- qcom,saw2-avs-ctl: The AVS control register
>
> What does this even mean, why is this not part of the reg property?
Same.

>
> > +- qcom,saw2-avs-hysterisis: The AVS hysterisis register to delay the AVS
> > + controller requests
>
> Why do we need this?
Not all registers initialize to 0 on power on. So, its better to
initialize it. We dont use AVS currently in the chipset.
>
> > +- qcom,saw2-spm-dly: Provides the values for the SPM delay command in the SPM
> > + sequence
>
> how many values?
HW configuration value.
>
> > +- qcom,saw2-spm-ctl: The SPM control register
>
> What does this mean?  Is it the offset of the register, and if so from what base?  Also, why does this vary, this should possibly be handled by different compatible values.
The register controls the SPM. 0x1 means its ON.
>
> > +- qcom,vctl-timeout-us: The timeout value in us to wait for voltage to change
>
> us -> microseconds
>
> > + after sending the voltage command to the PMIC
>
> Have we really ever set this to any value other than 50 usec?
>
> > +- qcom,name: The name with which a SPM device is identified by the power
> > +management code.
>
> what does this even mean?
Power/idle drivers, that I am trying to split and get at, would use this
reference to match and configure the correct SPM.
>
> > +
> > +Optional properties
> > +
> > +- qcom,saw2-avs-limit: The AVS limit register
>
> same comments above (as qcom,saw2-spm-ctl)
>
> > +- qcom,saw2-avs-dly: The AVS delay register is used to specify the delay values
> > + between AVS controller requests
>
> is this a delay value, list of values, a register offset? not clear.
>
> > +- qcom,saw2-pmic-data0..7: Specify the pmic data value and the associated FTS
> > + index to send the PMIC data to
>
> what is FTS?
Fast Transient Switch of the PMIC regulator

>
> > +- qcom,vctl-port: The PVC (PMIC Virtual Channel) port used for changing
> > + voltage
> > +- qcom,phase-port: The PVC port used for changing the number of phases
> > +- qcom,pfm-port: The PVC port used for enabling PWM/PFM modes
> > +- qcom,saw2-spm-cmd-wfi: The WFI command sequence
> > +- qcom,saw2-spm-cmd-ret: The Retention command sequence
> > +- qcom,saw2-spm-cmd-spc: The Standalone PC command sequence
> > +- qcom,saw2-spm-cmd-pc-no-rpm: The Power Collapse command sequence where APPS
> > + proc won't inform the RPM.
> > +- qcom,saw2-spm-cmd-pc: The Power Collapse command sequence
> > +- qcom,saw2-spm-cmd-gdhs: L2 GDHS command sequence
>
> GDHS?
Globally Distributed Head Switch. Even though it doesnt match the state 
correctly, it has been a convention (internally) to use GDHS
to indicate that the L2 memory would be retained while the control logic
would be powered down as opposed to retention where both the memory and 
the control logic would be on.
>
> > +- qcom,cpu-vctl-mask: Mask of cpus, whose voltage the spm device can control.
> > + Depricated: Replaced with cpu-vctl-list when cpu phandles are available.
>
> if deprecated, remove it.
Will evaluate the need of this for 8064 and remove this.

- Lina 

  reply	other threads:[~2014-08-08 21:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  4:05 [RFC] [PATCH 00/13] QCOM: 8074 CPUIDLE driver Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 01/13] msm: scm: Move scm-boot files to drivers/soc and include/soc Lina Iyer
2014-08-08  7:42   ` Pramod Gurav
2014-08-08 14:39     ` Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 02/13] msm: scm: Add SCM warmboot flags for quad core targets Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 03/13] qcom: spm: Add Subsystem Power Manager driver for QCOM chipsets Lina Iyer
2014-08-08  9:18   ` Pramod Gurav
2014-08-08 10:07     ` Pramod Gurav
2014-08-08 14:31       ` Lina Iyer
2014-08-08 16:16   ` Kumar Gala
2014-08-08 21:53     ` Lina Iyer [this message]
2014-08-11 19:54       ` Kumar Gala
2014-08-11 20:40         ` Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 04/13] arm: dts: qcom: Add SPM device bindings for 8974 Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 05/13] qcom: msm-pm: Add cpu low power mode functions Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 06/13] qcom: msm-pm: Add support for hotplug and secondary startup Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 07/13] qcom: sleep-status: Add ability to recognize cpu power down state Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 08/13] arm: dts: qcom: Add device binding for sleep status Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 09/13] soc: qcom: Add QCOM Power management config Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 10/13] qcom: platsmp: Enable deeper idle states for hotplug Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 11/13] qcom: cpuidle: Add cpuidle driver for QCOM cpus Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 12/13] qcom: cpuidle: Add cpuidle device nodes for 8974 chipset Lina Iyer
2014-08-08  4:05 ` [RFC] [PATCH 13/13] qcom: cpuidle: Config option to enable QCOM cpuidle driver Lina Iyer
  -- strict thread matches above, loose matches on Subject: below --
2014-08-08  4:00 [RFC] [PATCH 00/13] QCOM: 8087 CPUIDLE driver Lina Iyer
2014-08-08  4:00 ` [RFC] [PATCH 03/13] qcom: spm: Add Subsystem Power Manager driver for QCOM chipsets 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=20140808215340.GA8257@ilina-mac.local \
    --to=lina.iyer@linaro.org \
    --cc=amit.kucheria@linaro.org \
    --cc=bryanh@codeaurora.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=davidb@codeaurora.org \
    --cc=galak@codeaurora.org \
    --cc=khilman@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mnalajal@codeaurora.org \
    --cc=msivasub@codeaurora.org \
    --cc=pchidamb@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).