Linux IIO development
 help / color / mirror / Atom feed
From: Kory Maincent <kory.maincent@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>,
	Michael Welling <mwelling@ieee.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: thomas.petazzoni@bootlin.com,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Nuno Sá" <nuno.sa@analog.com>
Subject: [PATCH 2/2] dt-bindings: iio: dac: mcp4922: expand for mcp4921 support
Date: Fri, 24 Jun 2022 11:56:18 +0200	[thread overview]
Message-ID: <20220624095619.1415614-2-kory.maincent@bootlin.com> (raw)
In-Reply-To: <20220624095619.1415614-1-kory.maincent@bootlin.com>

Add device tree bindings for the MCP4921 DAC.

Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
 Documentation/devicetree/bindings/iio/dac/microchip,mcp4922.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/iio/dac/microchip,mcp4922.yaml b/Documentation/devicetree/bindings/iio/dac/microchip,mcp4922.yaml
index 12a14b3f36cb..4c430abcdbf9 100644
--- a/Documentation/devicetree/bindings/iio/dac/microchip,mcp4922.yaml
+++ b/Documentation/devicetree/bindings/iio/dac/microchip,mcp4922.yaml
@@ -15,6 +15,7 @@ properties:
     enum:
       - microchip,mcp4902
       - microchip,mcp4912
+      - microchip,mcp4921
       - microchip,mcp4922
 
   reg:
-- 
2.25.1


  reply	other threads:[~2022-06-24  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  9:56 [PATCH 1/2] iio: dac: mcp4922: add support to mcp4921 Kory Maincent
2022-06-24  9:56 ` Kory Maincent [this message]
2022-06-24 11:40   ` [PATCH 2/2] dt-bindings: iio: dac: mcp4922: expand for mcp4921 support Krzysztof Kozlowski
2022-06-24 17:59 ` [PATCH 1/2] iio: dac: mcp4922: add support to mcp4921 Miquel Raynal
2022-06-25 11:15 ` 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=20220624095619.1415614-2-kory.maincent@bootlin.com \
    --to=kory.maincent@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwelling@ieee.org \
    --cc=nuno.sa@analog.com \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@bootlin.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