Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Cc: srini@kernel.org, krzk+dt@kernel.org,
	linux-sound@vger.kernel.org,  broonie@kernel.org, perex@perex.cz,
	devicetree@vger.kernel.org,  tiwai@suse.com,
	alexey.klimov@linaro.org, conor+dt@kernel.org,
	 linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] ASoC: dt-bindings: qcom,lpass-rx-macro: Add sm6115 LPASS RX
Date: Wed, 29 Oct 2025 14:34:17 -0500	[thread overview]
Message-ID: <176176645546.2481487.18047032469966565976.robh@kernel.org> (raw)
In-Reply-To: <20251029160101.423209-4-srinivas.kandagatla@oss.qualcomm.com>


On Wed, 29 Oct 2025 16:01:00 +0000, Srinivas Kandagatla wrote:
> Add bindings for Qualcomm SM6115 SoC Low Power Audio SubSystem (LPASS)
> RX macro codec, which looks like compatible with SM8450.
> 
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
> ---
>  .../devicetree/bindings/sound/qcom,lpass-rx-macro.yaml        | 4 ++++
>  1 file changed, 4 insertions(+)
> 

My bot found errors running 'make dt_binding_check' on your patch:

yamllint warnings/errors:
./Documentation/devicetree/bindings/sound/qcom,lpass-rx-macro.yaml:30:13: [warning] wrong indentation: expected 14 but found 12 (indentation)

dtschema/dtc warnings/errors:

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20251029160101.423209-4-srinivas.kandagatla@oss.qualcomm.com

The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.

If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:

pip3 install dtschema --upgrade

Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.


  reply	other threads:[~2025-10-29 19:34 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) [this message]
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
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=176176645546.2481487.18047032469966565976.robh@kernel.org \
    --to=robh@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=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