The saw2 binding describes the SPM/AVS wrapper hardware used to control the regulator supplying voltage to the Krait CPUs. Cc: <devicetree@xxxxxxxxxxxxxxx> Signed-off-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> --- When a SAW is for a CPU it is put behind the CPU alias region similar to the ACC and timers. I haven't documented that here because I'm not using it right now. I'm also thinking perhaps l2-saw2 is not important (technically its the same hardware block as a CPU's saw). Instead I should point to this node via the l2-cache node via some *-supply property. Thoughts? .../devicetree/bindings/arm/msm/qcom,saw2.txt | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,saw2.txt diff --git a/Documentation/devicetree/bindings/arm/msm/qcom,saw2.txt b/Documentation/devicetree/bindings/arm/msm/qcom,saw2.txt new file mode 100644 index 0000000..6360db2 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/msm/qcom,saw2.txt @@ -0,0 +1,23 @@ +* SPM AVS Wrapper 2 (SAW2) + +The SAW2 is a wrapper around the Subsystem Power Manager (SPM) and the +Adaptive Voltage Scaling (AVS) hardware. The SPM is programmable +micro-controller that transitions a piece of hardware (like a processor) into +and out of low power modes via a direct connection to the PMIC. It can also +be wired up to interact with other processors in the system, notifying them +when a low power state is entered or exited. + +Required Properties: + +- compatible : Shall contain "qcom,saw2". + A more specific property can be specified as follows: + "qcom,l2-saw2" +- reg: Specifies the base address and size of the register region. + +Example: + + regulator@f9012000 { + compatible = "qcom,l2-saw2", "qcom,saw2"; + reg = <0xf9012000 0x1000>; + }; + -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html