All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Patrick Havelange <patrick.havelange@essensium.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Matt Weber <matthew.weber@rockwellcollins.com>,
	Paresh Chaudhary <paresh.chaudhary@rockwellcollins.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/4] dt-bindings: iio/temperature: Add doc for thermocouple-type
Date: Sun, 10 Mar 2019 09:50:14 +0000	[thread overview]
Message-ID: <20190310095014.498d198c@archlinux> (raw)
In-Reply-To: <20190307103409.24174-2-patrick.havelange@essensium.com>

On Thu,  7 Mar 2019 11:34:07 +0100
Patrick Havelange <patrick.havelange@essensium.com> wrote:

> This explains the new generic property "thermocouple-type" that
> can be used with temperature sensors.
> 
> Signed-off-by: Patrick Havelange <patrick.havelange@essensium.com>
I'm happy with this, but want to allow time for Rob and other
devicetree types to have a look at it as well.

Give me a poke if this is looking unloved in a week or so.

Thanks,

Jonathan

> ---
> Changes v6
>  - Add this file
> ---
>  .../bindings/iio/temperature/temperature-bindings.txt | 11 +++++++++++
>  1 file changed, 11 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/temperature/temperature-bindings.txt
> 
> diff --git a/Documentation/devicetree/bindings/iio/temperature/temperature-bindings.txt b/Documentation/devicetree/bindings/iio/temperature/temperature-bindings.txt
> new file mode 100644
> index 000000000000..69a6441d8083
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/temperature/temperature-bindings.txt
> @@ -0,0 +1,11 @@
> +If the temperature sensor device can be configured to use some specific
> +thermocouple type, you can use the defined types provided in the file
> +"include/dt-bindings/iio/temperature/thermocouple.h".
> +
> +Optional property:
> +thermocouple-type:	The type of the thermocouple used by the device.
> +
> +For example:
> +	device {
> +		thermocouple-type = <THERMOCOUPLE_TYPE_K> ;
> +	};


  reply	other threads:[~2019-03-10  9:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 10:34 [PATCH v6 1/4] dt-bindings: iio/temperature: Add thermocouple types Patrick Havelange
2019-03-07 10:34 ` [PATCH v6 2/4] dt-bindings: iio/temperature: Add doc for thermocouple-type Patrick Havelange
2019-03-10  9:50   ` Jonathan Cameron [this message]
2019-03-11 22:26   ` Rob Herring
2019-03-07 10:34 ` [PATCH v6 3/4] iio:temperature:max31856:Add device tree bind info Patrick Havelange
2019-03-11 22:28   ` Rob Herring
2019-03-11 22:28     ` Rob Herring
2019-03-07 10:34 ` [PATCH v6 4/4] iio:temperature: Add MAX31856 thermocouple support Patrick Havelange
2019-03-10  9:51   ` Jonathan Cameron

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=20190310095014.498d198c@archlinux \
    --to=jic23@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matthew.weber@rockwellcollins.com \
    --cc=paresh.chaudhary@rockwellcollins.com \
    --cc=patrick.havelange@essensium.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.