From: YLCHANG2 <neo.chang70@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, Neo Chang <YLCHANG2@nuvoton.com>
Cc: broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
robh@kernel.org, krzk+dt@kernel.org, linux-sound@vger.kernel.org,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
kchsu0@nuvoton.com, sjlin0@nuvoton.com, lkp@intel.com
Subject: Re: [PATCH v2 1/2] ASoC: dt-bindings: nuvoton,nau8310: Add NAU83G10
Date: Tue, 17 Nov 2026 11:38:15 +0800 [thread overview]
Message-ID: <63472ed5-1bc5-4acb-97ba-55749ec93c2a@gmail.com> (raw)
In-Reply-To: <20261109-grateful-white-meerkat-090edc@quoll>
On 11/9/26 21:11, Krzysztof Kozlowski wrote:
> On Mon, Nov 09, 2026 at 01:12:50PM +0800, Neo Chang wrote:
>> + nuvoton,sar-voltage:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description:
>> + SAR Gain Tracking Selection.
>> + enum:
>> + - 0 # VDDA
>> + - 1 # VDDA * 1.0
>> + - 2 # VDDA * 1.1
>> + - 3 # VDDA * 1.2
>> + - 4 # VDDA * 1.3
>> + - 5 # VDDA * 1.4
>> + - 6 # VDDA * 1.54
>> + - 7 # VDDA * 3.12
>> + default: 0
>> +
>> + nuvoton,sar-compare-time:
> Use proper unit suffix from property-units in dtschema.
>
> Also, Sashiko feedback needs to be addressed.
Got it. I will update the property name with the proper unit suffix and
address Sashiko's feedback in the next version.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-11-17 3:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 5:12 [PATCH v2 0/2] ASoC: codecs: nau8310: Add NAU83G10 amplifier Neo Chang
2026-11-09 5:12 ` [PATCH v2 1/2] ASoC: dt-bindings: nuvoton,nau8310: Add NAU83G10 Neo Chang
2026-11-09 5:23 ` sashiko-bot
2026-11-09 13:11 ` Krzysztof Kozlowski
2026-11-17 3:38 ` YLCHANG2 [this message]
2026-11-09 5:12 ` [PATCH v2 2/2] ASoC: codecs: nau8310: Add support for NAU83G10 amplifier Neo Chang
2026-11-09 5:44 ` sashiko-bot
2026-11-09 13:15 ` Krzysztof Kozlowski
2026-11-17 3:38 ` YLCHANG2
2026-11-09 19:48 ` Mark Brown
2026-11-17 3:39 ` YLCHANG2
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=63472ed5-1bc5-4acb-97ba-55749ec93c2a@gmail.com \
--to=neo.chang70@gmail.com \
--cc=YLCHANG2@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kchsu0@nuvoton.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=sjlin0@nuvoton.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