linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	linux-iio@vger.kernel.org
Cc: devicetree@vger.kernel.org
Subject: Re: [PATCH] iio: mcp3422: Add DT binding documentation
Date: Mon, 09 Mar 2015 11:04:45 +0000	[thread overview]
Message-ID: <54FD7E4D.20403@kernel.org> (raw)
In-Reply-To: <1425821843-29185-1-git-send-email-angelo.compagnucci@gmail.com>

On 08/03/15 13:37, Angelo Compagnucci wrote:
> Adding binding documentation for ADC MCP3422.
> 
> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
Applied to the togreg branch of iio.git

Thanks,

> ---
>  Documentation/devicetree/bindings/iio/adc/mcp3422.txt | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/adc/mcp3422.txt
> 
> diff --git a/Documentation/devicetree/bindings/iio/adc/mcp3422.txt b/Documentation/devicetree/bindings/iio/adc/mcp3422.txt
> new file mode 100644
> index 0000000..333139c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/mcp3422.txt
> @@ -0,0 +1,17 @@
> +* Microchip mcp3422/3/4/6/7/8 chip family (ADC)
> +
> +Required properties:
> + - compatible: Should be
> +	"microchip,mcp3422" or
> +	"microchip,mcp3423" or
> +	"microchip,mcp3424" or
> +	"microchip,mcp3426" or
> +	"microchip,mcp3427" or
> +	"microchip,mcp3428"
> + - reg: I2C address for the device
> +
> +Example:
> +adc@0 {
> +	compatible = "microchip,mcp3424";
> +	reg = <0x68>;
> +};
> 


  reply	other threads:[~2015-03-09 11:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 13:37 [PATCH] iio: mcp3422: Add DT binding documentation Angelo Compagnucci
2015-03-09 11:04 ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-16 11:21 Angelo Compagnucci
2015-03-08 12:35 ` Jonathan Cameron
2014-12-17 18:11 Angelo Compagnucci
2014-12-26 11:58 ` 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=54FD7E4D.20403@kernel.org \
    --to=jic23@kernel.org \
    --cc=angelo.compagnucci@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-iio@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).