linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/5] Documentation: add DT bindings for ARM SCPI sensors
Date: Mon, 14 Sep 2015 18:18:12 +0100	[thread overview]
Message-ID: <1442251092.2850.53.camel@linaro.org> (raw)
In-Reply-To: <9hhk2rtdq1f.fsf@e105922-lin.cambridge.arm.com>

On Mon, 2015-09-14 at 15:38 +0100, Punit Agrawal wrote:
> Mark Rutland <mark.rutland@arm.com> writes:
> 
> >> >> +Sensor bindings for the sensors based on SCPI Message Protocol
> >> >> +--------------------------------------------------------------
> >> >> +SCPI provides an API to access the various sensors on the SoC.
> >> >> +
> >> >> +Required properties:
> >> >> +- compatible : should be "arm,scpi-sensors".
> >> >> +- #thermal-sensor-cells: should be set to 1. This property follows the
> >> >> +			 thermal device tree bindings[2].
> >> >
> >> > You need to specify what the valid values for this cell are.
> >> 
> >> The enumeration depends on the number of sensors exported by SCP
> >> firmware - which is platform dependent. I could add add something like
> >> if you think that is helpful -
> >> 
> >> "Valid cell value is a number between 0..n-1, where n is the number
> >> of sensors exported by SCP firmware."
> >
> > Can the FW identifer space have holes? Or are they always contiguous?
> 
> The way the SCP interface is defined, the sensor identifiers are
> contiguous,

Is there any documentation other than DUI0922A? [1] From what I can seen
that just says it's a 16-bit value and doesn't put any particular
constraints on its value.

[1] http://community.arm.com/servlet/JiveServlet/download/8401-40-18262/DUI0922A_scp_message_interface.pdf

-- 
Tixy

  parent reply	other threads:[~2015-09-14 17:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 13:00 [PATCH v3 0/5] SCPI Sensor support Punit Agrawal
2015-09-14 13:00 ` [PATCH v3 1/5] Documentation: add DT bindings for ARM SCPI sensors Punit Agrawal
2015-09-14 13:14   ` Mark Rutland
2015-09-14 13:34     ` Punit Agrawal
2015-09-14 13:49       ` Mark Rutland
2015-09-14 14:38         ` Punit Agrawal
2015-09-14 14:43           ` Mark Rutland
2015-09-14 15:01             ` Punit Agrawal
2015-09-14 15:15               ` Mark Rutland
2015-09-14 16:03                 ` Punit Agrawal
2015-09-14 17:18           ` Jon Medhurst (Tixy) [this message]
2015-09-15  9:37             ` Punit Agrawal
2015-09-15 10:46               ` Jon Medhurst (Tixy)
2015-09-15 11:03                 ` Mark Rutland
2015-09-15 11:37                   ` Jon Medhurst (Tixy)
2015-09-15 16:04                 ` Punit Agrawal
2015-09-15 16:31                   ` Jon Medhurst (Tixy)
2015-09-14 13:00 ` [PATCH v3 2/5] firmware: arm_scpi: Extend to support sensors Punit Agrawal
2015-09-14 13:00 ` [PATCH v3 3/5] hwmon: Support sensors exported via ARM SCP interface Punit Agrawal
2015-09-14 13:00 ` [Patch v3 4/5] hwmon: Support registration of thermal zones for SCP temperature sensors Punit Agrawal
2015-09-14 13:19   ` Punit Agrawal
2015-09-14 13:00 ` [PATCH v3 4/5] hwmon: Support thermal zones registration " Punit Agrawal
2015-09-14 13:00 ` [PATCH v3 5/5] arm64: dts: Add sensor node to Juno dt Punit Agrawal

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=1442251092.2850.53.camel@linaro.org \
    --to=tixy@linaro.org \
    --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).