From: <zhangyi@everest-semi.com>
To: <krzk@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <broonie@kernel.org>,
<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<krzk+dt@kernel.org>, <robh@kernel.org>, <tiwai@suse.com>,
<zhangyi@everest-semi.com>
Subject: Re: [PATCH 7/7] ASoC: dt-bindings: ES8389: Add members about HPF and clock
Date: Tue, 9 Jun 2026 19:46:05 +0800 [thread overview]
Message-ID: <05a401dcf805$8ecda900$ac68fb00$@everest-semi.com> (raw)
> Please organize the patch documenting the ABI (DT bindings)
> before the patch using that ABI.
> See also:
https://elixir.bootlin.com/linux/v6.14-rc6/source/Documentation/devicetree/b
indings/submitting-patches.rst#L46
Thanks for the reminder
> > + everest,mclk-from-sclk:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + description:
> > + Indicates that SCLK is used as the internal clock.
>
> And what happens with mclk in such case? Is it still wired?
Yes, setting mclk-from-sclk does not affect the MCLK connection.
> > +
> > + everest,hpfl:
> > + $ref: /schemas/types.yaml#/definitions/uint8
> > + description:
> > + the HPF value of ADCL.
>
> Is HPF value in dB? If so, use proper unit suffix and proper units.
No, the values here correspond to the values in the registers.
The value is not in dB
> > vddd-supply = <&vdd3v3>;
> > vdda-supply = <&vdd3v3>;
> > + everest,hpfl = [0a];
>
> <0xa>? What did you want to say here?
I just wanted to give an example to show how to set the values of
everest,hpfl to 0x0a.
next reply other threads:[~2026-06-10 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 11:46 zhangyi [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-10 9:12 [PATCH 7/7] ASoC: dt-bindings: ES8389: Add members about HPF and clock zhangyi
[not found] <20260609071732.20939-1-zhangyi@everest-semi.com>
[not found] ` <20260609071732.20939-8-zhangyi@everest-semi.com>
2026-06-10 8:53 ` Krzysztof Kozlowski
[not found] <20260609030623.17404-1-zhangyi@everest-semi.com>
[not found] ` <20260609030623.17404-8-zhangyi@everest-semi.com>
2026-06-09 7:33 ` Krzysztof Kozlowski
2026-06-10 9:58 ` Zhang Yi
2026-06-13 7:37 ` Krzysztof Kozlowski
[not found] ` <20260615060744.18775-1-zhangyi@everest-semi.com>
2026-06-15 9:57 ` Krzysztof Kozlowski
[not found] ` <20260615101423.19781-1-zhangyi@everest-semi.com>
2026-06-15 10:58 ` Krzysztof Kozlowski
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='05a401dcf805$8ecda900$ac68fb00$@everest-semi.com' \
--to=zhangyi@everest-semi.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=robh@kernel.org \
--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