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,
tiwai@suse.com, 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
Subject: Re: [PATCH v2 1/2] ASoC: dt-bindings: nuvoton,nau8360: Add NAU83G60
Date: Wed, 20 May 2026 11:22:52 +0800 [thread overview]
Message-ID: <204dd64c-414e-6f6a-e992-c1fdb1b398ce@gmail.com> (raw)
In-Reply-To: <20260518-heavy-bear-of-camouflage-d7c89d@quoll>
On 5/18/26 20:02, Krzysztof Kozlowski wrote:
> On Mon, May 18, 2026 at 10:47:03AM +0800, Neo Chang wrote:
>> Add device tree bindings documentation for the Nuvoton NAU83G60
>> audio amplifier.
>>
>> Signed-off-by: Neo Chang <YLCHANG2@nuvoton.com>
>> ---
>> Changes in v2:
>> - Dropped the word "driver" from the description.
>> - Removed runtime/software configuration properties:
>> nuvoton,low-latency, nuvoton,anc-enable, nuvoton,aec-enable,
>> nuvoton,vbat-microvolt, and nuvoton,tdm-channel-length.
>> - Added missing "nuvoton,dac-cur-enable" property for static speaker impedance matching.
>> - Removed unnecessary '|' formatting from single-line descriptions.
>> - Fixed typo in firmware-name property.
> You didn't really...
>
> git grep firmware-name
Sorry for the oversight. I missed it in the final v2 patch. I will fix
it in v3.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-05-20 3:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 2:47 [PATCH v2 0/2] ASoC: codecs: Add Nuvoton NAU83G60 audio codec driver Neo Chang
2026-05-18 2:47 ` [PATCH v2 1/2] ASoC: dt-bindings: nuvoton,nau8360: Add NAU83G60 Neo Chang
2026-05-18 2:53 ` sashiko-bot
2026-05-18 4:36 ` Rob Herring (Arm)
2026-05-18 12:02 ` Krzysztof Kozlowski
2026-05-20 3:22 ` YLCHANG2 [this message]
2026-05-18 2:47 ` [PATCH v2 2/2] ASoC: codecs: nau8360: Add support for NAU83G60 amplifier Neo Chang
2026-05-18 3:23 ` sashiko-bot
2026-05-18 11:35 ` Mark Brown
2026-05-20 3:22 ` YLCHANG2
[not found] ` <ddacfe50-072d-66fd-c760-c898bdab52f4@gmail.com>
2026-05-21 15:35 ` Mark Brown
2026-05-22 2:18 ` 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=204dd64c-414e-6f6a-e992-c1fdb1b398ce@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=perex@perex.cz \
--cc=robh@kernel.org \
--cc=sjlin0@nuvoton.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox