diff for duplicates of <20140924192945.GC1004@ilina-mac.local> diff --git a/a/1.txt b/N1/1.txt index eb77c06..d830771 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -66,7 +66,7 @@ On Wed, Sep 24 2014 at 11:53 -0600, Kumar Gala wrote: >>>> +- qcom,cpu: phandle for the CPU that the SPM block is attached to. >>>> + This field is required on only for SPMs that control the CPU. >>> ->>> Let’s make this just cpu-handle instead of qcom,cpu. The concept of a handle to a cpu is pretty generic. +>>> Let?s make this just cpu-handle instead of qcom,cpu. The concept of a handle to a cpu is pretty generic. >>> >> Okay. Will look into it. >> You mean just the property name, right? @@ -94,7 +94,7 @@ It is, in this case. But its not something you deviate from the spec. >>>> +- 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? +>>> 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. @@ -102,7 +102,7 @@ It is, in this case. But its not something you deviate from the spec. >> 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. +>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 @@ -133,19 +133,19 @@ with it. >>>> + >>>> +- qcom,saw2-spm-cmd-wfi: The WFI command sequence >>> ->>> probably add something like: “array of bytes …” (want to convey the data type somehow, is there a max length?) +>>> probably add something like: ?array of bytes ?? (want to convey the data type somehow, is there a max length?) >>> >> Okay. >> >>>> +- qcom,saw2-spm-cmd-spc: The Standalone PC command sequence >>> ->>> probably add something like: “array of bytes …” (want to convey the data type somehow, is there a max length?) +>>> probably add something like: ?array of bytes ?? (want to convey the data type somehow, is there a max length?) >>> >> Okay. >> >>>> + >>>> +Example: ->>>> + spm@f9089000 { +>>>> + spm at f9089000 { >>>> + compatible = "qcom,spm-v2.1"; >>>> + #address-cells = <1>; >>>> + #size-cells = <1>; @@ -169,7 +169,7 @@ with it. >>> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in ->> the body of a message to majordomo@vger.kernel.org +>> the body of a message to majordomo at vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > >-- diff --git a/a/content_digest b/N1/content_digest index f3ae068..14425a1 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,18 +3,10 @@ "ref\0F743E5F0-28C1-4A9D-A27D-73EA70A01B46@codeaurora.org\0" "ref\020140924172151.GD422@ilina-mac\0" "ref\04BFC9B4E-A3D0-422E-9B55-0DB9F4B04EE9@codeaurora.org\0" - "From\0Lina Iyer <lina.iyer@linaro.org>\0" - "Subject\0Re: [PATCH v6 1/5] qcom: spm: Add Subsystem Power Manager driver\0" + "From\0lina.iyer@linaro.org (Lina Iyer)\0" + "Subject\0[PATCH v6 1/5] qcom: spm: Add Subsystem Power Manager driver\0" "Date\0Wed, 24 Sep 2014 13:29:45 -0600\0" - "To\0Kumar Gala <galak@codeaurora.org>\0" - "Cc\0sboyd@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\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Wed, Sep 24 2014 at 11:53 -0600, Kumar Gala wrote:\n" @@ -85,7 +77,7 @@ ">>>> +- qcom,cpu: phandle for the CPU that the SPM block is attached to.\n" ">>>> +\tThis field is required on only for SPMs that control the CPU.\n" ">>>\n" - ">>> Let\342\200\231s make this just cpu-handle instead of qcom,cpu. The concept of a handle to a cpu is pretty generic.\n" + ">>> Let?s make this just cpu-handle instead of qcom,cpu. The concept of a handle to a cpu is pretty generic.\n" ">>>\n" ">> Okay. Will look into it.\n" ">> You mean just the property name, right?\n" @@ -113,7 +105,7 @@ ">>>> +- qcom,saw2-delays: The SPM delay values that SPM sequences would refer to.\n" ">>>> +\tThe register for this property is MSM_SPM_REG_SAW2_SPM_DLY.\n" ">>>\n" - ">>> Didn\342\200\231t Stephen asked about splitting this up? Or at least treating it as an array of 3 values?\n" + ">>> Didn?t Stephen asked about splitting this up? Or at least treating it as an array of 3 values?\n" ">>>\n" ">> Yes he did. My response was similar to the clk-div values, its not\n" ">> something you can change without hardware spec documentation.\n" @@ -121,7 +113,7 @@ ">> register. Splitting it up, doesnt help understanding/configuring the SPM\n" ">> any better, so didnt change it.\n" ">\n" - ">Hmm, will this value change from SPM to SPM on the same SoC? I\342\200\231m 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.\n" + ">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.\n" ">\n" "Ah. Tough proposition! The SPM sequence is a bunch of random register\n" "values, which is not open to interpretation without the programming\n" @@ -152,19 +144,19 @@ ">>>> +\n" ">>>> +- qcom,saw2-spm-cmd-wfi: The WFI command sequence\n" ">>>\n" - ">>> probably add something like: \342\200\234array of bytes \342\200\246\342\200\235 (want to convey the data type somehow, is there a max length?)\n" + ">>> probably add something like: ?array of bytes ?? (want to convey the data type somehow, is there a max length?)\n" ">>>\n" ">> Okay.\n" ">>\n" ">>>> +- qcom,saw2-spm-cmd-spc: The Standalone PC command sequence\n" ">>>\n" - ">>> probably add something like: \342\200\234array of bytes \342\200\246\342\200\235 (want to convey the data type somehow, is there a max length?)\n" + ">>> probably add something like: ?array of bytes ?? (want to convey the data type somehow, is there a max length?)\n" ">>>\n" ">> Okay.\n" ">>\n" ">>>> +\n" ">>>> +Example:\n" - ">>>> +\tspm@f9089000 {\n" + ">>>> +\tspm at f9089000 {\n" ">>>> +\t\tcompatible = \"qcom,spm-v2.1\";\n" ">>>> +\t\t#address-cells = <1>;\n" ">>>> +\t\t#size-cells = <1>;\n" @@ -188,7 +180,7 @@ ">>>\n" ">> --\n" ">> To unsubscribe from this list: send the line \"unsubscribe linux-arm-msm\" in\n" - ">> the body of a message to majordomo@vger.kernel.org\n" + ">> the body of a message to majordomo at vger.kernel.org\n" ">> More majordomo info at http://vger.kernel.org/majordomo-info.html\n" ">\n" ">-- \n" @@ -196,4 +188,4 @@ ">Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation\n" > -6a4583152374ffca37827fec783f03aa6cf34dc232358f3e665b77c20a9f607e +fea01820142ad9b5ec506fde403221a779a767b5d31cd75132b8a6911229fd9b
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.