From: Krzysztof Kozlowski <krzk@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Cc: robh@kernel.org, broonie@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org, perex@perex.cz,
tiwai@suse.com, srini@kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
alexey.klimov@linaro.org
Subject: Re: [PATCH 4/4] ASoC: dt-bindings: qcom,lpass-va-macro: Add sm6115 LPASS VA
Date: Thu, 30 Oct 2025 07:30:06 +0100 [thread overview]
Message-ID: <20251030-flat-elated-pony-de74ab@kuoka> (raw)
In-Reply-To: <20251029160101.423209-5-srinivas.kandagatla@oss.qualcomm.com>
On Wed, Oct 29, 2025 at 04:01:01PM +0000, Srinivas Kandagatla wrote:
> Add bindings for Qualcomm SM6115 SoC Low Power Audio SubSystem (LPASS)
> VA macro codec, which looks like compatible with SM8450, however one of
> the clocks macro is available in this SoC. So updated the bindings to
is or is not? Which clock?
> allow min-clocks to be 3 to be able to use SM8450 compatible for
> SM6115.
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
> ---
> .../devicetree/bindings/sound/qcom,lpass-va-macro.yaml | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/sound/qcom,lpass-va-macro.yaml b/Documentation/devicetree/bindings/sound/qcom,lpass-va-macro.yaml
> index 5b450f227b70..1ac3392776ca 100644
> --- a/Documentation/devicetree/bindings/sound/qcom,lpass-va-macro.yaml
> +++ b/Documentation/devicetree/bindings/sound/qcom,lpass-va-macro.yaml
> @@ -26,6 +26,10 @@ properties:
> - qcom,sm8750-lpass-va-macro
> - qcom,x1e80100-lpass-va-macro
> - const: qcom,sm8550-lpass-va-macro
> + - items:
> + - enum:
> + - qcom,sm6115-lpass-va-macro
> + - const: qcom,sm8450-lpass-va-macro
>
> reg:
> maxItems: 1
> @@ -44,9 +48,9 @@ properties:
> minItems: 1
> items:
> - const: mclk
> - - const: macro
No, that's ABI break and I know existing code works fine, so there
cannot be justification for exception here.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-30 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 16:00 [PATCH 0/4] ASoC: codecs: lpass-macro: complete sm6115 support Srinivas Kandagatla
2025-10-29 16:00 ` [PATCH 1/4] ASoC: codecs: lpass-tx-macro: fix SM6115 support Srinivas Kandagatla
2025-10-30 9:06 ` Konrad Dybcio
2025-10-30 9:42 ` Srinivas Kandagatla
2025-10-29 16:00 ` [PATCH 2/4] ASoC: dt-bindings: qcom,lpass-tx-macro: Add sm6115 LPASS TX Srinivas Kandagatla
2025-10-30 18:11 ` Rob Herring
2025-10-30 21:46 ` Srinivas Kandagatla
2025-10-29 16:01 ` [PATCH 3/4] ASoC: dt-bindings: qcom,lpass-rx-macro: Add sm6115 LPASS RX Srinivas Kandagatla
2025-10-29 19:34 ` Rob Herring (Arm)
2025-10-29 16:01 ` [PATCH 4/4] ASoC: dt-bindings: qcom,lpass-va-macro: Add sm6115 LPASS VA Srinivas Kandagatla
2025-10-29 19:34 ` Rob Herring (Arm)
2025-10-30 6:30 ` Krzysztof Kozlowski [this message]
2025-10-30 8:55 ` Srinivas Kandagatla
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=20251030-flat-elated-pony-de74ab@kuoka \
--to=krzk@kernel.org \
--cc=alexey.klimov@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.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