From: sudeep.holla@arm.com (Sudeep Holla)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 1/2] Documentation: bindings: Introduce scpi,sensors-scale
Date: Wed, 15 Mar 2017 18:20:33 +0000 [thread overview]
Message-ID: <57ff035a-b462-6f5d-0100-051e99e9a2b6@arm.com> (raw)
In-Reply-To: <20170309101759.18081-2-carlo@caione.org>
On 09/03/17 10:17, Carlo Caione wrote:
> From: Carlo Caione <carlo@endlessm.com>
>
> Document the new property `scpi,sensors-scale` used by the hwmon-scpi
> driver to convert the sensor readings to the correct / expected scale.
>
I am fine with DT bindings if DT maintainers agree with having one but I
would like to add couple of points to get their feedback:
1. ARM recognized the drawbacks of SCPI which started informally with
ARM Ltd platforms and got adopted by few vendors. It's now being
worked on and a much better and scalable replacement protocol is
being discussed with vendors now. So future enhancement to this SCPI
protocol is unlikely.
2. AmLogic has diverted from base protocol in many ways and most of them
are handled with just compatible so far without any need for
additional bindings. Can we avoid it ?
So based on these, I prefer not to add more bindings to handle such
deviations but make it just AmLogic specific.
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-03-15 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 10:17 [PATCH v3 0/2] scpi-sensors: Fix SCP sensor readings scale Carlo Caione
2017-03-09 10:17 ` [PATCH v3 1/2] Documentation: bindings: Introduce scpi,sensors-scale Carlo Caione
2017-03-15 18:20 ` Sudeep Holla [this message]
2017-03-15 19:30 ` Guenter Roeck
2017-03-15 20:36 ` Rob Herring
2017-03-15 20:56 ` [PATCH v3 1/2] Documentation: bindings: Introduce scpi, sensors-scale Martin Blumenstingl
2017-03-15 22:40 ` [PATCH v3 1/2] Documentation: bindings: Introduce scpi,sensors-scale Guenter Roeck
2017-03-09 10:17 ` [PATCH v3 2/2] hwmon: (scpi) Fix the scale of SCP sensor readings Carlo Caione
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=57ff035a-b462-6f5d-0100-051e99e9a2b6@arm.com \
--to=sudeep.holla@arm.com \
--cc=linus-amlogic@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
all inboxes | Powered by JetHome®