diff for duplicates of <20180702204611.GZ129942@google.com> diff --git a/a/1.txt b/N1/1.txt index 6556e11..647352f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,10 +3,10 @@ On Mon, Jul 02, 2018 at 12:53:44PM -0700, Doug Anderson wrote: > > On Mon, Jul 2, 2018 at 11:10 AM, Matthias Kaehlcke <mka@chromium.org> wrote: > > The thermal zone uses spmi-temp-alarm as sensor. If the sensor is -> > configured without an IIO input it always reports 37°C for temperatures -> > below the first hardware trip point at 105°C. This hardware trip point +> > configured without an IIO input it always reports 37?C for temperatures +> > below the first hardware trip point at 105?C. This hardware trip point > > is configured as critical trip point, to initiate a system shutdown -> > before the temperature reaches the next hardware trip point at 125°C, +> > before the temperature reaches the next hardware trip point at 125?C, > > where the PMIC performs a partial shutdown. > > > > The temperature of the critical trip point can be raised after adding @@ -18,7 +18,7 @@ On Mon, Jul 02, 2018 at 12:53:44PM -0700, Doug Anderson wrote: > > Changes in v2: > > - defined 'thermal-zones' node in pm8998.dtsi instead of using a label > > to refer to it -> > - use 105°C hardware trip point as critical trip point +> > - use 105?C hardware trip point as critical trip point > > I'm not sure this was right. I guess you're trying to avoid > Temperature Stage 2? @@ -44,7 +44,7 @@ Indeed > better chance of succeeding without getting to stage 3. That was my starting point, however in my tests the system reset -several times when the temperature got close to 125°C, not allowing +several times when the temperature got close to 125?C, not allowing for a proper shutdown. Apparently the partial shutdown of the PMIC can result in a full reset at least on some systems. @@ -86,7 +86,7 @@ Exactly, once we have more granularity we could add (an)other trip point(s). > > +#include <dt-bindings/thermal/thermal.h> > > > > &spmi_bus { -> > pm8998_lsid0: pmic@0 { +> > pm8998_lsid0: pmic at 0 { > > @@ -60,3 +61,27 @@ > > #size-cells = <0>; > > }; diff --git a/a/content_digest b/N1/content_digest index 93c3b71..e41f4c4 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,22 +1,10 @@ "ref\020180702181005.18247-1-mka@chromium.org\0" "ref\020180702181005.18247-2-mka@chromium.org\0" "ref\0CAD=FV=WH8q-3Rt89Get0N357+hWmKiEsruaKtWzo_JoE6gd_3g@mail.gmail.com\0" - "From\0Matthias Kaehlcke <mka@chromium.org>\0" - "Subject\0Re: [PATCH v2 2/2] arm64: dts: qcom: pm8998: Add pm8998 thermal zone\0" + "From\0mka@chromium.org (Matthias Kaehlcke)\0" + "Subject\0[PATCH v2 2/2] arm64: dts: qcom: pm8998: Add pm8998 thermal zone\0" "Date\0Mon, 2 Jul 2018 13:46:11 -0700\0" - "To\0Doug Anderson <dianders@chromium.org>\0" - "Cc\0Andy Gross <andy.gross@linaro.org>" - David Brown <david.brown@linaro.org> - Rob Herring <robh+dt@kernel.org> - Mark Rutland <mark.rutland@arm.com> - Catalin Marinas <catalin.marinas@arm.com> - Will Deacon <will.deacon@arm.com> - open list:ARM/QUALCOMM SUPPORT <linux-soc@vger.kernel.org> - linux-arm-msm <linux-arm-msm@vger.kernel.org> - Linux ARM <linux-arm-kernel@lists.infradead.org> - LKML <linux-kernel@vger.kernel.org> - David Collins <collinsd@codeaurora.org> - " Stephen Boyd <sboyd@kernel.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Mon, Jul 02, 2018 at 12:53:44PM -0700, Doug Anderson wrote:\n" @@ -24,10 +12,10 @@ "> \n" "> On Mon, Jul 2, 2018 at 11:10 AM, Matthias Kaehlcke <mka@chromium.org> wrote:\n" "> > The thermal zone uses spmi-temp-alarm as sensor. If the sensor is\n" - "> > configured without an IIO input it always reports 37\302\260C for temperatures\n" - "> > below the first hardware trip point at 105\302\260C. This hardware trip point\n" + "> > configured without an IIO input it always reports 37?C for temperatures\n" + "> > below the first hardware trip point at 105?C. This hardware trip point\n" "> > is configured as critical trip point, to initiate a system shutdown\n" - "> > before the temperature reaches the next hardware trip point at 125\302\260C,\n" + "> > before the temperature reaches the next hardware trip point at 125?C,\n" "> > where the PMIC performs a partial shutdown.\n" "> >\n" "> > The temperature of the critical trip point can be raised after adding\n" @@ -39,7 +27,7 @@ "> > Changes in v2:\n" "> > - defined 'thermal-zones' node in pm8998.dtsi instead of using a label\n" "> > to refer to it\n" - "> > - use 105\302\260C hardware trip point as critical trip point\n" + "> > - use 105?C hardware trip point as critical trip point\n" "> \n" "> I'm not sure this was right. I guess you're trying to avoid\n" "> Temperature Stage 2?\n" @@ -65,7 +53,7 @@ "> better chance of succeeding without getting to stage 3.\n" "\n" "That was my starting point, however in my tests the system reset\n" - "several times when the temperature got close to 125\302\260C, not allowing\n" + "several times when the temperature got close to 125?C, not allowing\n" "for a proper shutdown. Apparently the partial shutdown of the PMIC can\n" "result in a full reset at least on some systems.\n" "\n" @@ -107,7 +95,7 @@ "> > +#include <dt-bindings/thermal/thermal.h>\n" "> >\n" "> > &spmi_bus {\n" - "> > pm8998_lsid0: pmic@0 {\n" + "> > pm8998_lsid0: pmic at 0 {\n" "> > @@ -60,3 +61,27 @@\n" "> > #size-cells = <0>;\n" "> > };\n" @@ -143,4 +131,4 @@ "\n" Ok, thanks, will do in v3 -cdb832dbb8694685848920108a05e78d169f21778eca0b53afa9e3bb918ad8b6 +63dcbb00deda9a1e315f8016e7ccc889273ad189c20376e03c2aa4245fab28b2
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.