From: Mark Brown <broonie@kernel.org>
To: derek.fang@realtek.com
Cc: oder_chiou@realtek.com, jack.yu@realtek.com,
alsa-devel@alsa-project.org, lars@metafoo.de,
lgirdwood@gmail.com, albertchen@realtek.com,
shumingf@realtek.com, flove@realtek.com
Subject: Re: [PATCH 2/2] ASoC: dt-bindings: rt5682s: add bindings for rt5682s
Date: Thu, 26 Aug 2021 12:34:41 +0100 [thread overview]
Message-ID: <20210826113441.GA4148@sirena.org.uk> (raw)
In-Reply-To: <20210826080938.14872-2-derek.fang@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Thu, Aug 26, 2021 at 04:09:38PM +0800, derek.fang@realtek.com wrote:
> + realtek,dmic1-data-pin:
> + enum:
> + - 0 # dmic1 is not used
> + - 1 # using GPIO2 pin as dmic1 data pin
> + - 2 # using GPIO5 pin as dmic1 data pin
> +
> + realtek,dmic1-clk-pin:
> + enum:
> + - 0 #using GPIO1 pin as dmic1 clock pin
> + - 1 #using GPIO3 pin as dmic1 clock pin
It works but it's a bit weird that there's no unused option on the clock
- I'd expect this to be symmetric.
> + realtek,jd-src:
> + enum:
> + - 0 # No JD is used
> + - 1 # using JD1 as JD source
Are there other possible JD sources which are not supported yet?
> + realtek,dmic-delay-ms:
> + description: |
> + Set the delay time (ms) for the requirement of the particular DMIC.
Startup delay or some other delay?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-26 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 8:09 [PATCH 1/2] ASoC: rt5682s: Add driver for ALC5682I-VS codec derek.fang
2021-08-26 8:09 ` [PATCH 2/2] ASoC: dt-bindings: rt5682s: add bindings for rt5682s derek.fang
2021-08-26 11:34 ` Mark Brown [this message]
2021-08-26 12:14 ` [PATCH 1/2] ASoC: rt5682s: Add driver for ALC5682I-VS codec Mark Brown
[not found] ` <e2ad57c54ea0422d8083bbf2b116563c@realtek.com>
2021-09-03 12:30 ` Mark Brown
2021-08-26 16:57 ` kernel test robot
2021-08-26 21:25 ` kernel test robot
2021-08-31 10:56 ` Bard liao
2021-08-31 12:37 ` Derek [方德義]
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=20210826113441.GA4148@sirena.org.uk \
--to=broonie@kernel.org \
--cc=albertchen@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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