From: Jai Luthra <j-luthra@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: sound: tlv320aic3x: Convert to dtschema
Date: Wed, 3 Aug 2022 10:11:27 -0500 [thread overview]
Message-ID: <20220803151127.23tmkvobrh5so46v@uda0497096> (raw)
In-Reply-To: <7effc23b-b61a-9887-3875-d102b8fa270e@linaro.org>
Hi Krzysztof,
Thanks for the review.
On 08:29-20220803, Krzysztof Kozlowski wrote:
> On 02/08/2022 23:48, Jai Luthra wrote:
> > Convert bindings for TI's TLV320AIC3x audio codecs to dtschema.
> >
> > Signed-off-by: Jai Luthra <j-luthra@ti.com>
> > ---
>
>
> Thank you for your patch. There is something to discuss/improve.
>
> > diff --git a/Documentation/devicetree/bindings/sound/tlv320aic3x.yaml b/Documentation/devicetree/bindings/sound/tlv320aic3x.yaml
> > new file mode 100644
> > index 000000000000..6efb1d459543
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/sound/tlv320aic3x.yaml
> > @@ -0,0 +1,145 @@
> > +# SPDX-License-Identifier: GPL-2.0
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/sound/tlv320aic3x.yaml#
>
> Filename with vendor prefix, so ti,tlv320aic3x.yaml
>
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Texas Instruments TLV320AIC3x Codec Device Tree Bindings
>
> s/Device Tree Bindings//
>
> > +
> > +maintainers:
> > + - Jai Luthra <j-luthra@ti.com>
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - ti,tlv320aic3x
> > + - ti,tlv320aic33
> > + - ti,tlv320aic3007
> > + - ti,tlv320aic3106
> > + - ti,tlv320aic3104
> > +
> > + reg:
> > + maxItems: 1
> > + description: i2c slave address
>
> Skip description.
>
> > +
> > + reset-gpios:
> > + maxItems: 1
> > + description:
> > + GPIO specification for the active low RESET input.
> > +
> > + ai3x-gpio-func:
> > + description: AIC3X_GPIO1 & AIC3X_GPIO2 Functionality
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + minItems: 3
>
> uint32-array. Old bindings say about two items only. Mention any changes
> to binding in cover letter.
My bad, that should still be 2 items.
>
> > + maxItems: 3
> > +
>
> You lost gpio-reset property. Also not explained in commit msg.
>
> > + ai3x-micbias-vg:
> > + description: MicBias required voltage. If node is omitted then MicBias is powered down.
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + oneOf:
> > + - const: 1
> > + description: MICBIAS output is powered to 2.0V.
> > + - const: 2
> > + description: MICBIAS output is powered to 2.5V.
> > + - const: 3
> > + description: MICBIAS output is connected to AVDD.
> > +
> > + ai3x-ocmv:
> > + description: Output Common-Mode Voltage selection.
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + oneOf:
> > + - const: 0
> > + description: 1.35V
> > + - const: 1
> > + description: 1.5V
> > + - const: 2
> > + description: 1.65V
> > + - const: 3
> > + description: 1.8V
> > +
> > + AVDD-supply:
> > + description: Analog DAC voltage.
>
> New properties?
>
These regulator properties were mentioned in the txt as well.
> > +
> > + IOVDD-supply:
> > + description: I/O voltage.
> > +
> > + DRVDD-supply:
> > + description: ADC analog and output driver voltage.
> > +
> > + DVDD-supply:
> > + description: Digital core voltage.
> > +
> > + '#sound-dai-cells':
> > + const: 0
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +#The pins can be used in referring sound node's audio-routing property.
> > +
> > +#CODEC output pins:
> > + # LLOUT
> > + # RLOUT
> > + # MONO_LOUT
> > + # HPLOUT
> > + # HPROUT
> > + # HPLCOM
> > + # HPRCOM
> > +
> > +#CODEC input pins for TLV320AIC3104:
> > + # MIC2L
> > + # MIC2R
> > + # LINE1L
> > + # LINE1R
> > +
> > +#CODEC input pins for other compatible codecs:
> > + # MIC3L
> > + # MIC3R
> > + # LINE1L
> > + # LINE2L
> > + # LINE1R
> > + # LINE2R
>
> All this goes to top level description.
>
>
> Best regards,
> Krzysztof
Fixed rest of the comments in v2.
Thanks,
Jai
prev parent reply other threads:[~2022-08-03 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 21:48 Jai Luthra
2022-08-02 22:38 ` Rob Herring
2022-08-03 6:29 ` Krzysztof Kozlowski
2022-08-03 15:11 ` Jai Luthra [this message]
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=20220803151127.23tmkvobrh5so46v@uda0497096 \
--to=j-luthra@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®