From: Amit Kucheria <amit.kucheria@linaro.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Konrad Dybcio <konradybcio@gmail.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 2/2] thermal: qcom: tsens-v0_1: Add support for MSM8939
Date: Mon, 27 Jul 2020 12:06:54 +0530 [thread overview]
Message-ID: <CAHLCerPEPEOkkBd8MZq8T99eS7nE2pMio6ojnMn7bc54ian-3A@mail.gmail.com> (raw)
In-Reply-To: <CAHLCerMyEsvuhNPnwDow5JYVAbem0Rzs+5-uzKZNeFt+3rYHQg@mail.gmail.com>
On Mon, Jul 27, 2020 at 11:56 AM Amit Kucheria <amit.kucheria@linaro.org> wrote:
>
> On Tue, Jun 30, 2020 at 1:09 AM Shawn Guo <shawn.guo@linaro.org> wrote:
> >
> > The TSENS integrated on MSM8939 is a v0_1 device with 10 sensors.
> > Different from its predecessor MSM8916, where 'calib_sel' bits sit in
> > separate qfprom word, MSM8939 has 'cailb' and 'calib_sel' bits mixed and
> > spread on discrete offsets. That's why all qfprom bits are read as one
> > go and later mapped to calibration data for MSM8939.
> >
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
>
> Acked-by: Amit Kucheria <amit.kucheria@linaro.org>
Shawn,
Have you not sent the change to the tsens.yaml and 8939 DT yet or did
I miss them?
Regards,
Amit
next prev parent reply other threads:[~2020-07-27 6:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 14:49 [PATCH 0/2] Add msm8939 tsens support Shawn Guo
2020-06-29 14:49 ` [PATCH 1/2] dt-bindings: tsens: qcom: Document MSM8939 compatible Shawn Guo
2020-06-29 14:49 ` [PATCH 2/2] thermal: qcom: tsens-v0_1: Add support for MSM8939 Shawn Guo
2020-07-27 6:26 ` Amit Kucheria
2020-07-27 6:36 ` Amit Kucheria [this message]
2020-07-27 8:33 ` Shawn Guo
2020-07-27 9:15 ` Amit Kucheria
2020-07-21 13:29 ` [PATCH 0/2] Add msm8939 tsens support Daniel Lezcano
2020-07-25 12:25 ` Konrad Dybcio
2020-07-27 8:34 ` Daniel Lezcano
2020-07-27 8:44 ` Daniel Lezcano
2020-07-27 8:48 ` Shawn Guo
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=CAHLCerPEPEOkkBd8MZq8T99eS7nE2pMio6ojnMn7bc54ian-3A@mail.gmail.com \
--to=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=konradybcio@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shawn.guo@linaro.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).