From: Rob Herring <robh@kernel.org>
To: Carlos Iglesias <carlos.iglesias@emutex.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"lars@metafoo.de" <lars@metafoo.de>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Dan O'Donovan <dan.odonovan@emutex.com>
Subject: Re: [PATCH 1/2] dt-bindings: iio: pressure: Add support for Honeywell HSC SPI sensors
Date: Tue, 6 Nov 2018 15:29:40 -0600 [thread overview]
Message-ID: <20181106212940.GA13434@bogus> (raw)
In-Reply-To: <20181026181406.14545-2-carlos.iglesias@emutex.com>
On Fri, Oct 26, 2018 at 06:14:36PM +0000, Carlos Iglesias wrote:
> Add device tree bindings for the HSC pressure sensors.
>
> Signed-off-by: Carlos Iglesias <carlos.iglesias@emutex.com>
> ---
> .../bindings/iio/pressure/hsc_spi.txt | 85 +++++++++++++++++++
> 1 file changed, 85 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/pressure/hsc_spi.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/pressure/hsc_spi.txt b/Documentation/devicetree/bindings/iio/pressure/hsc_spi.txt
> new file mode 100644
> index 000000000000..2302d6eef7c7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/pressure/hsc_spi.txt
> @@ -0,0 +1,85 @@
> +Honeywell HSC Series of Pressure Sensors
> +
> +Pressure sensors from Honeywell with analog, I2C and SPI interfaces
But you named the file with 'spi'. You expect
> +
> +Required properties:
> +- compatible: selects the sensor model; must be one of the following
> + "honeywell,hsc001baa"
> + "honeywell,hsc001bab"
> + "honeywell,hsc001bac"
> + "honeywell,hsc001baf"
I normally tell people to imply things from compatible strings, but this
may be a good case where some properties make sense. The last letter
appears to be 'transfer function'. Maybe even the pressure range should
be a property. I think it depends if there's any other s/w visible
differences.
Plus this list doesn't even include the differential or gage parts and
those lists are longer.
> + "honeywell,hsc1_6baa"
> + "honeywell,hsc1_6bab"
> + "honeywell,hsc1_6bac"
> + "honeywell,hsc1_6baf"
> + "honeywell,hsc2_5baa"
> + "honeywell,hsc2_5bab"
> + "honeywell,hsc2_5bac"
> + "honeywell,hsc2_5baf"
> + "honeywell,hsc004baa"
> + "honeywell,hsc004bab"
> + "honeywell,hsc004bac"
> + "honeywell,hsc004baf"
> + "honeywell,hsc006baa"
> + "honeywell,hsc006bab"
> + "honeywell,hsc006bac"
> + "honeywell,hsc006baf"
> + "honeywell,hsc010baa"
> + "honeywell,hsc010bab"
> + "honeywell,hsc010bac"
> + "honeywell,hsc010baf"
> + "honeywell,hsc100kaa"
> + "honeywell,hsc100kab"
> + "honeywell,hsc100kac"
> + "honeywell,hsc100kaf"
> + "honeywell,hsc160kaa"
> + "honeywell,hsc160kab"
> + "honeywell,hsc160kac"
> + "honeywell,hsc160kaf"
> + "honeywell,hsc250kaa"
> + "honeywell,hsc250kab"
> + "honeywell,hsc250kac"
> + "honeywell,hsc250kaf"
> + "honeywell,hsc400kaa"
> + "honeywell,hsc400kab"
> + "honeywell,hsc400kac"
> + "honeywell,hsc400kaf"
> + "honeywell,hsc600kaa"
> + "honeywell,hsc600kab"
> + "honeywell,hsc600kac"
> + "honeywell,hsc600kaf"
> + "honeywell,hsc001gaa"
> + "honeywell,hsc001gab"
> + "honeywell,hsc001gac"
> + "honeywell,hsc001gaf"
> + "honeywell,hsc015paa"
> + "honeywell,hsc015pab"
> + "honeywell,hsc015pac"
> + "honeywell,hsc015paf"
> + "honeywell,hsc030paa"
> + "honeywell,hsc030pab"
> + "honeywell,hsc030pac"
> + "honeywell,hsc030paf"
> + "honeywell,hsc060paa"
> + "honeywell,hsc060pab"
> + "honeywell,hsc060pac"
> + "honeywell,hsc060paf"
> + "honeywell,hsc100paa"
> + "honeywell,hsc100pab"
> + "honeywell,hsc100pac"
> + "honeywell,hsc100paf"
> + "honeywell,hsc150paa"
> + "honeywell,hsc150pab"
> + "honeywell,hsc150pac"
> + "honeywell,hsc150paf"
> +- reg: the SPI chip select number used by the sensor.
> +- spi-max-frequency: maximum clock frequency (Hz) used for the SPI bus.
> + The maximum value supported by the sensors is 400000.
> +
> +Example:
> +
> + hsc_spi0: hsc@0 {
pressure-sensor@0
> + compatible = "honeywell,hsc010baa";
> + reg = <0>;
> + spi-max-frequency = <400000>;
> + };
> --
> 2.19.1
>
next prev parent reply other threads:[~2018-11-07 6:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 18:14 [PATCH 0/2] iio: pressure: Add support for Honeywell HSC SPI sensors Carlos Iglesias
2018-10-26 18:14 ` Carlos Iglesias
2018-10-26 18:14 ` [PATCH 1/2] dt-bindings: " Carlos Iglesias
2018-10-26 18:14 ` Carlos Iglesias
2018-10-28 17:38 ` Jonathan Cameron
2018-10-30 15:56 ` Carlos Iglesias
2018-11-03 10:36 ` Jonathan Cameron
2018-11-06 21:29 ` Rob Herring [this message]
2018-10-26 18:14 ` [PATCH 2/2] " Carlos Iglesias
2018-10-26 18:14 ` Carlos Iglesias
2018-10-28 18:44 ` 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=20181106212940.GA13434@bogus \
--to=robh@kernel.org \
--cc=carlos.iglesias@emutex.com \
--cc=dan.odonovan@emutex.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@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=pmeerw@pmeerw.net \
/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.