From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Emmanuel Vadot <manu@freebsd.org>
Subject: Re: [PATCH 1/7] dt-bindings: Add DT bindings documentation for Allwinner Thermal Sensor Controller
Date: Sat, 25 Aug 2018 13:07:40 +0200 (CEST) [thread overview]
Message-ID: <66249ae2a698cdc7@bloch.sibelius.xs4all.nl> (raw)
Hi Emmanuel,
I think the following bit in your proposed binding is wrong:
+- #thermal-sensor-cells : Depend on the SoC
+ For H3 should be 0
+ For H5 should be 1
+ For A64 should be 2
+ See ./thermal.txt for a description.
I think what you're trying to say here is that H3 has a single sensor
and that H5 and A64 have more sensors. But even though the number of
sensors is different for H5 and A64 (two for H3, three for A64) you
need only a single cell to describe which sensor to read. So
#thermal-sensors-cells should be 1 for both H5 and A64.
As far as I can see this proposed binding is compatible with the
OpenBSD's sxitemp(4) driver. That driver also supports the R40 with
"allwinner,sun8i-r40-ths" as the compatible string. The R40 has two
sensors so #thermal-sensor-cells should be 1 for this SoC as well.
Cheers,
Mark
next reply other threads:[~2018-08-25 14:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 11:07 Mark Kettenis [this message]
2018-08-25 15:42 ` [PATCH 1/7] dt-bindings: Add DT bindings documentation for Allwinner Thermal Sensor Controller Emmanuel Vadot
2018-08-25 15:49 ` Emmanuel Vadot
-- strict thread matches above, loose matches on Subject: below --
2018-08-04 7:03 Emmanuel Vadot
2018-08-14 19:20 ` Rob Herring
2018-08-20 11:17 ` Maxime Ripard
2018-08-20 13:41 ` Rob Herring
2018-08-20 13:57 ` Emmanuel Vadot
2018-08-20 14:07 ` Maxime Ripard
2018-08-20 14:27 ` Emmanuel Vadot
2018-08-24 14:58 ` Maxime Ripard
2018-08-24 19:59 ` Emmanuel Vadot
2018-08-24 23:03 ` Eduardo Valentin
2018-08-25 15:43 ` Emmanuel Vadot
2018-08-29 12:38 ` Maxime Ripard
2018-08-29 13:31 ` Maxime Ripard
2018-08-20 18:47 ` Rob Herring
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=66249ae2a698cdc7@bloch.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=manu@freebsd.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).