linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: icenowy@aosc.io (Icenowy Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: About the thermal sensor driver on H3/A64/H5
Date: Wed, 29 Mar 2017 00:40:09 +0800	[thread overview]
Message-ID: <20170329004009.2aa6b7a9@x220i> (raw)

Hi everyone,
I'm trying to do a mainlinable thermal driver for H3/A64/H5 SoCs;
however, I found some problem:

Maxime have told me to reuse the code for A10/A13/A31/A33 thermal
driver -- I tried, and it works on H3.

However, as it is an IIO driver, some failure occured on H5 -- the
temperature sensor is not linear on H5: it has a different formula
when it's higher than 70 Celsius degree.

In addition, a lot of code for A33 is in fact rewrite for H3, due to
totally changed register map. But H3/A64/H5 become a new group with
nearly identical register map.

Is it still worth to implement it with the IIO driver? Or should we
start a new thermal sensor-based driver? (For both I have already
local tested code at least for H3)

Thanks,
Icenowy

             reply	other threads:[~2017-03-28 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 16:40 Icenowy Zheng [this message]
2017-03-28 19:14 ` [linux-sunxi] About the thermal sensor driver on H3/A64/H5 Vincent Legoll

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=20170329004009.2aa6b7a9@x220i \
    --to=icenowy@aosc.io \
    --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).