From: wxt@rock-chips.com (Caesar Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/1] thermal: rockchip: make temperature reporting much more accurate
Date: Thu, 22 Jan 2015 01:29:29 +0800 [thread overview]
Message-ID: <1421861370-19422-1-git-send-email-wxt@rock-chips.com> (raw)
This patch is merged on chromiumos/third_party/kernel.
https://chromium-review.googlesource.com/#/c/239190/
Tested on veyron boards.
Changes in v3:
Suggested-by Daniel Kurtz,
the check doesn't reject "code == 0xfff"
Fixed in rk_tsadcv2_code_to_temp(u32 code)
Changes in v2:
Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Caesar Wang (1):
thermal: rockchip: make temperature reporting much more accurate
drivers/thermal/rockchip_thermal.c | 32 ++++++++++++++++++++++----------
1 file changed, 22 insertions(+), 10 deletions(-)
--
1.9.1
next reply other threads:[~2015-01-21 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 17:29 Caesar Wang [this message]
2015-01-21 17:29 ` [PATCH v3] thermal: rockchip: make temperature reporting much more accurate Caesar Wang
2015-01-22 4:01 ` Daniel Kurtz
2015-01-22 4:21 ` Caesar Wang
2015-01-22 4:25 ` Daniel Kurtz
2015-01-22 4:57 ` Caesar Wang
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=1421861370-19422-1-git-send-email-wxt@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.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).