Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhang Yi <zhangyi@everest-semi.com>
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
Subject: Re: [PATCH 7/7] ASoC: dt-bindings: ES8389: Add members about HPF and clock
Date: Mon, 15 Jun 2026 11:57:13 +0200	[thread overview]
Message-ID: <241d0fab-26ea-4c06-9928-e256f2cc5d1c@kernel.org> (raw)
In-Reply-To: <20260615060744.18775-1-zhangyi@everest-semi.com>

On 15/06/2026 08:07, Zhang Yi wrote:
>>>>> +    $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.
>>
>> I am asking about wiring of the device. If MCLK is used from SCLK, but
>> SCLK is used as the internal clock, then how can you still have MCLK
>> connected?
> 
> If MCLK is derived from SCLK, whether the 'MCLK' pin on the device is
> connected or not has no effect on operation.

If MCLK is connected, why would you derive it from SCLK? That's the
point - your clocks property already might be telling everything needed
here.

> 
>>>>> +
>>>>> +  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
>>
>> What are the meanings of the register values?
> 
> The value of everest,hpfl is equal to the value of the corresponding register,
> not the cutoff frequency of the HPF.

You keep avoiding answers.

I don't want you to encode standard units as register values.


Best regards,
Krzysztof

  reply	other threads:[~2026-06-15  9:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09  3:06 [PATCH 0/7] ASoC: codecs: ES8389: Modify the ES8389 driver Zhang Yi
2026-06-09  3:06 ` [PATCH 1/7] ASoC: codecs: ES8389: Modify volatile_register Zhang Yi
2026-06-09  3:17   ` sashiko-bot
2026-06-09  3:06 ` [PATCH 2/7] ASoC: codecs: ES8389: Fix the issue about mclk_src Zhang Yi
2026-06-09  3:20   ` sashiko-bot
2026-06-09  7:34   ` Krzysztof Kozlowski
2026-06-10 10:06     ` Zhang Yi
2026-06-13  7:33       ` Krzysztof Kozlowski
2026-06-15  6:06         ` Zhang Yi
2026-06-09  3:06 ` [PATCH 3/7] ASoC: codecs: ES8389: Modify the clock table Zhang Yi
2026-06-09  3:19   ` sashiko-bot
2026-06-09  3:06 ` [PATCH 4/7] ASoC: codecs: ES8389: Modify the initial configuration Zhang Yi
2026-06-09  3:13   ` sashiko-bot
2026-06-09  3:06 ` [PATCH 5/7] ASoC: codecs: ES8389: Add private members related to HPF Zhang Yi
2026-06-09  3:06 ` [PATCH 6/7] ASoC: codecs: ES8389: Add INPUTL MUX and INPUTR MUX Zhang Yi
2026-06-09  3:21   ` sashiko-bot
2026-06-09  3:06 ` [PATCH 7/7] ASoC: dt-bindings: ES8389: Add members about HPF and clock Zhang Yi
2026-06-09  7:33   ` Krzysztof Kozlowski
2026-06-10  9:58     ` Zhang Yi
2026-06-13  7:37       ` Krzysztof Kozlowski
2026-06-15  6:07         ` Zhang Yi
2026-06-15  9:57           ` Krzysztof Kozlowski [this message]
2026-06-15 10:14             ` Zhang Yi
2026-06-15 10:58               ` Krzysztof Kozlowski
  -- strict thread matches above, loose matches on Subject: below --
2026-06-09  7:17 [PATCH 0/7] ASoC: codecs: ES8389: Modify the ES8389 driver Zhang Yi
2026-06-09  7:17 ` [PATCH 7/7] ASoC: dt-bindings: ES8389: Add members about HPF and clock Zhang Yi
2026-06-10  8:53   ` Krzysztof Kozlowski
2026-06-10  9:12 zhangyi

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=241d0fab-26ea-4c06-9928-e256f2cc5d1c@kernel.org \
    --to=krzk@kernel.org \
    --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=robh@kernel.org \
    --cc=tiwai@suse.com \
    --cc=zhangyi@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