From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <matt.ranostay@konsulko.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: chemical: add CO2 EZO module documentation
Date: Sat, 16 May 2020 17:56:02 +0100 [thread overview]
Message-ID: <20200516175602.12473d0f@archlinux> (raw)
In-Reply-To: <20200511023214.14704-2-matt.ranostay@konsulko.com>
On Mon, 11 May 2020 05:32:13 +0300
Matt Ranostay <matt.ranostay@konsulko.com> wrote:
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
This crossed with the RTD driver, so applied with fuzz to the togreg
branch of iio.git and pushed out as testing for the autobuilders to play
with it. As ever if a DT maintainer wants to comment there is still
time to add tags (though in this case it is trivial enough I'd not waste
your time reading it!)
Jonathan
> ---
> .../devicetree/bindings/iio/chemical/atlas,sensor.yaml | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/chemical/atlas,sensor.yaml b/Documentation/devicetree/bindings/iio/chemical/atlas,sensor.yaml
> index edcd2904d50e..0d109e1b34ee 100644
> --- a/Documentation/devicetree/bindings/iio/chemical/atlas,sensor.yaml
> +++ b/Documentation/devicetree/bindings/iio/chemical/atlas,sensor.yaml
> @@ -4,19 +4,20 @@
> $id: http://devicetree.org/schemas/iio/chemical/atlas,sensor.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: Atlas Scientific OEM sensors
> +title: Atlas Scientific OEM + EZO sensors
>
> maintainers:
> - Matt Ranostay <matt.ranostay@konsulko.com>
>
> description: |
> - Atlas Scientific OEM sensors connected via I2C
> + Atlas Scientific OEM + EZO sensors connected via I2C
>
> Datasheets:
> http://www.atlas-scientific.com/_files/_datasheets/_oem/DO_oem_datasheet.pdf
> http://www.atlas-scientific.com/_files/_datasheets/_oem/EC_oem_datasheet.pdf
> http://www.atlas-scientific.com/_files/_datasheets/_oem/ORP_oem_datasheet.pdf
> http://www.atlas-scientific.com/_files/_datasheets/_oem/pH_oem_datasheet.pdf
> + http://www.atlas-scientific.com/_files/_datasheets/_probe/EZO_CO2_Datasheet.pdf
>
> properties:
> compatible:
> @@ -25,6 +26,7 @@ properties:
> - atlas,ec-sm
> - atlas,orp-sm
> - atlas,ph-sm
> + - atlas,co2-ezo
>
> reg:
> maxItems: 1
prev parent reply other threads:[~2020-05-16 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200511023214.14704-1-matt.ranostay@konsulko.com>
2020-05-11 2:32 ` [PATCH v2 1/2] dt-bindings: iio: chemical: add CO2 EZO module documentation Matt Ranostay
2020-05-16 16:56 ` Jonathan Cameron [this message]
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=20200516175602.12473d0f@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=matt.ranostay@konsulko.com \
/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).