All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lin Huang <hl@rock-chips.com>
To: broonie@kernel.org, arnaud.pouliquen@st.com, dgreif@chromium.org
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
	briannorris@chromium.org, linux-kernel@vger.kernel.org,
	tiwai@suse.com, mka@chromium.org, dianders@chromium.org,
	huang lin <hl@rock-chips.com>
Subject: [PATCH v2 2/2] dt-bindings: sound: add dmicen property in dmic driver
Date: Thu, 17 Aug 2017 10:24:45 +0800	[thread overview]
Message-ID: <1502936685-24414-2-git-send-email-hl@rock-chips.com> (raw)
In-Reply-To: <1502936685-24414-1-git-send-email-hl@rock-chips.com>

From: huang lin <hl@rock-chips.com>

there may use enable pin to control dmic start and stop,
so add this property in dt-bindings.

Signed-off-by: Lin Huang <hl@rock-chips.com>
---
 Documentation/devicetree/bindings/sound/dmic.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/sound/dmic.txt b/Documentation/devicetree/bindings/sound/dmic.txt
index a0c58f2..54c8ef6 100644
--- a/Documentation/devicetree/bindings/sound/dmic.txt
+++ b/Documentation/devicetree/bindings/sound/dmic.txt
@@ -5,8 +5,12 @@ This device support generic PDM digital microphone.
 Required properties:
 	- compatible: should be "dmic-codec".
 
+Optional properties:
+	- dmicen-gpios: GPIO specifier for dmic to control start and stop
+
 Example node:
 
 	dmic_codec: dmic@0 {
 		compatible = "dmic-codec";
+		dmicen-gpios = <&gpio4 3 GPIO_ACTIVE_HIGH>;
 	};
-- 
2.7.4

  reply	other threads:[~2017-08-17  2:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  2:24 [PATCH v2 1/2] ASoC: codec: use enable pin to control dmic start and stop Lin Huang
2017-08-17  2:24 ` Lin Huang [this message]
2017-09-04 10:03 ` Arnaud Pouliquen
2017-09-04 12:18   ` Mark Brown
2017-09-05  2:26   ` hl

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=1502936685-24414-2-git-send-email-hl@rock-chips.com \
    --to=hl@rock-chips.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=briannorris@chromium.org \
    --cc=broonie@kernel.org \
    --cc=dgreif@chromium.org \
    --cc=dianders@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=tiwai@suse.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 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.