linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
	Carlo Caione <carlo@caione.org>,
	devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 3/4] Documentation: bindings: Add missing Amlogic SCPI sensor bindings
Date: Thu, 8 Nov 2018 16:04:57 +0000	[thread overview]
Message-ID: <20181108160457.GA10953@e107155-lin> (raw)
In-Reply-To: <20181108135352.8459-4-jbrunet@baylibre.com>

On Thu, Nov 08, 2018 at 02:53:51PM +0100, Jerome Brunet wrote:
> amlogic,meson-gxbb-scpi-sensors is both the driver and DT but is not
> documented. Just add it to amlogic's scpi documentation
> 
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
>  Documentation/devicetree/bindings/arm/amlogic,scpi.txt | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/amlogic,scpi.txt b/Documentation/devicetree/bindings/arm/amlogic,scpi.txt
> index 7b9a861e9306..5ab59da052df 100644
> --- a/Documentation/devicetree/bindings/arm/amlogic,scpi.txt
> +++ b/Documentation/devicetree/bindings/arm/amlogic,scpi.txt
> @@ -17,4 +17,11 @@ Required sub-node properties:
>  - compatible : should be "amlogic,meson-gxbb-scp-shmem" for SRAM based shared
>  		memory on Amlogic GXBB SoC.
>  
> +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 "amlogic,meson-gxbb-scpi-sensors".
> +

Not sure if it's worth mentioning the reason for being able to identify
amlogic,meson-gxbb sensors from generic scpi ones. IIRC it was for the
unit values of these sensors are different ? But I will leave that to
DT or platform maintainers' taste.

--
Regards,
Sudeep

  reply	other threads:[~2018-11-08 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 13:53 [PATCH 0/4] arm64: dts: meson-axg: enable SCPI Jerome Brunet
2018-11-08 13:53 ` [PATCH 1/4] arm64: dts: meson-axg: fix mailbox address Jerome Brunet
2018-11-09  9:37   ` Neil Armstrong
2018-11-08 13:53 ` [PATCH 2/4] arm64: dts: meson-axg: correct sram shared mem unit-address Jerome Brunet
2018-11-09  9:38   ` Neil Armstrong
2018-11-08 13:53 ` [PATCH 3/4] Documentation: bindings: Add missing Amlogic SCPI sensor bindings Jerome Brunet
2018-11-08 16:04   ` Sudeep Holla [this message]
2018-11-08 16:29     ` jbrunet
2018-11-17 16:21   ` Rob Herring
2018-11-08 13:53 ` [PATCH 4/4] arm64: dts: meson-axg: enable SCPI Jerome Brunet
2018-11-09  9:39   ` Neil Armstrong
2018-11-15 20:07 ` [PATCH 0/4] " Kevin Hilman

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=20181108160457.GA10953@e107155-lin \
    --to=sudeep.holla@arm.com \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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).