From: Rob Herring <robh@kernel.org>
To: Zhu Ning <zhuning0077@gmail.com>
Cc: alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com, tiwai@suse.com,
broonie@kernel.org, devicetree@vger.kernel.org,
ckeepax@opensource.cirrus.com,
David Yang <yangxiaohua@everest-semi.com>,
Zhu Ning <zhuning@everest-semi.com>
Subject: Re: [PATCH v3 2/2] ASoC: dt-bindings: Add Everest ES8326 audio CODEC
Date: Wed, 27 Jul 2022 09:22:03 -0600 [thread overview]
Message-ID: <20220727152203.GA2681685-robh@kernel.org> (raw)
In-Reply-To: <20220726131747.127992-2-zhuning0077@gmail.com>
On Tue, Jul 26, 2022 at 09:17:47PM +0800, Zhu Ning wrote:
> Add device tree binding documentation for Everest ES8326
>
> Signed-off-by: David Yang <yangxiaohua@everest-semi.com>
> Signed-off-by: Zhu Ning <zhuning@everest-semi.com>
> ---
> .../bindings/sound/everest,es8326.yaml | 84 +++++++++++++++++++
> 1 file changed, 84 insertions(+)
> create mode 100755 Documentation/devicetree/bindings/sound/everest,es8326.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/everest,es8326.yaml b/Documentation/devicetree/bindings/sound/everest,es8326.yaml
> new file mode 100755
> index 000000000000..f6aa3c03d456
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/everest,es8326.yaml
> @@ -0,0 +1,84 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/everest,es8326.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Everest ES8326 audio CODEC
> +
> +maintainers:
> + - David Yang <yangxiaohua@everest-semi.com>
> +
> +properties:
> + compatible:
> + const: everest,es8326
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: clock for master clock (MCLK)
> +
> + clock-names:
> + items:
> + - const: mclk
> +
> + "#sound-dai-cells":
> + const: 0
> +
> + everest,jack-pol:
> + description:
> + just the value of reg 57. Bit(3) decides whether the jack polarity is inverted.
> + Bit(2) decides whether the bottom on the headset is inverted.
s/bottom/button/?
> + Bit(1)/(0) decides the mic properity to be OMTP/CTIA or auto.
> + $ref: /schemas/types.yaml#/definitions/uint8-array
Array or...
> + minimum: 0
> + maximum: 0x0f
> + default: 0x0f
Scalar?
> +
> + everest,mic1-src:
> + description:
> + the value of reg 2A when headset plugged.
> + $ref: /schemas/types.yaml#/definitions/uint8-array
> + minimum: 0x00
> + maximum: 0x77
> + default: 0x22
> +
> + everest,mic2-src:
> + description:
> + the value of reg 2A when headset unplugged.
> + $ref: /schemas/types.yaml#/definitions/uint8-array
> + minimum: 0x00
> + maximum: 0x77
> + default: 0x44
> +
> + everest,jack-detect-inverted:
> + description:
> + Defined to invert the jack detection.
What's the difference with this and bit 3 of everest,jack-pol?
We already have numerous vendor properties for jack detect. Can we come
up with something common?
The problem with 'inverted' is it assumes you know the non-inverted
state. Better to just state high or low.
> + $ref: /schemas/types.yaml#/definitions/flag
> +
> +required:
> + - compatible
> + - reg
> + - "#sound-dai-cells"
> +
> +
Extra blank line.
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c0 {
i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + es8326: codec@19 {
> + compatible = "everest,es8326";
> + reg = <0x19>;
> + clocks = <&clks 10>;
> + clock-names = "mclk";
> + #sound-dai-cells = <0>;
> + everest,mic1-src = [22];
> + everest,mic2-src = [44];
> + everest,jack-pol = [0e];
> + };
> + };
> --
> 2.36.1
>
>
next prev parent reply other threads:[~2022-07-27 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 13:17 [PATCH v3 1/2] ASoC: codecs: add support for ES8326 Zhu Ning
2022-07-26 13:17 ` [PATCH v3 2/2] ASoC: dt-bindings: Add Everest ES8326 audio CODEC Zhu Ning
2022-07-27 15:22 ` Rob Herring [this message]
2022-07-26 13:43 ` [PATCH v3 1/2] ASoC: codecs: add support for ES8326 Mark Brown
2022-07-26 14:06 ` Pierre-Louis Bossart
2022-07-26 14:56 ` Mark Brown
2022-07-26 15:06 ` Pierre-Louis Bossart
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=20220727152203.GA2681685-robh@kernel.org \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yangxiaohua@everest-semi.com \
--cc=zhuning0077@gmail.com \
--cc=zhuning@everest-semi.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).