From: sashiko-bot@kernel.org
To: "Mohammad Rafi Shaik" <mohammad.rafi.shaik@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 1/3] ASoC: dt-bindings: qcom,q6apm-lpass-dais: Document DAI subnode
Date: Mon, 06 Jul 2026 13:30:51 +0000 [thread overview]
Message-ID: <20260706133051.983801F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706132009.1496321-2-mohammad.rafi.shaik@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The device tree example uses an incorrect unit address `dai@16` for `reg = <PRIMARY_MI2S_RX>`, which will cause a `unit_address_vs_reg` compiler warning.
--
commit 34242d1a4dde8cbcb03c8b665b181f4cb4658671
Author: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
ASoC: dt-bindings: qcom,q6apm-lpass-dais: Document DAI subnode
This commit extends the qcom,q6apm-lpass-dais device tree binding to
explicitly describe Digital Audio Interface (DAI) child nodes. It adds
#address-cells, #size-cells, and a dai@<id> pattern to document per-DAI
properties like the interface ID and associated clocks. This enables clock
line enablement from the platform side for codecs hardware wired to the SoC.
> diff --git a/Documentation/devicetree/bindings/sound/qcom,q6apm-lpass-dais.yaml b/Documentation/devicetree/bindings/sound/qcom,q6apm-lpass-dais.yaml
> index 2fb95544db8b5..42d05334bd391 100644
> --- a/Documentation/devicetree/bindings/sound/qcom,q6apm-lpass-dais.yaml
> +++ b/Documentation/devicetree/bindings/sound/qcom,q6apm-lpass-dais.yaml
[ ... ]
> @@ -29,7 +70,22 @@ unevaluatedProperties: false
>
> examples:
> - |
> + #include <dt-bindings/sound/qcom,q6afe.h>
> +
> dais {
> compatible = "qcom,q6apm-lpass-dais";
> #sound-dai-cells = <1>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + dai@16 {
> + reg = <PRIMARY_MI2S_RX>;
[Severity: Low]
Does this node name result in a unit_address_vs_reg warning during
make dt_binding_check?
Since PRIMARY_MI2S_RX evaluates to 16 in decimal (0x10 in hex) and unit
addresses in Device Tree node names are expected to be hexadecimal, should
this be named dai@10 instead of dai@16?
> + clocks = <&q6prmcc LPASS_CLK_ID_MCLK_1
> + LPASS_CLK_ATTRIBUTE_COUPLE_NO>,
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260706132009.1496321-1-mohammad.rafi.shaik@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-06 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 13:20 [PATCH v3 0/3] ASoC: qcom: qdsp6: Add MI2S clock control Mohammad Rafi Shaik
2026-07-06 13:20 ` [PATCH v3 1/3] ASoC: dt-bindings: qcom,q6apm-lpass-dais: Document DAI subnode Mohammad Rafi Shaik
2026-07-06 13:30 ` sashiko-bot [this message]
2026-07-06 13:20 ` [PATCH v3 2/3] ASoC: qcom: q6apm-lpass-dais: Add MI2S clock control Mohammad Rafi Shaik
2026-07-06 13:33 ` sashiko-bot
2026-07-06 18:18 ` Mark Brown
2026-07-06 13:20 ` [PATCH v3 3/3] ASoC: qcom: sc8280xp: ASoC: qcom: sc8280xp: enhance machine driver for board-specific config Mohammad Rafi Shaik
2026-07-06 13:34 ` sashiko-bot
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=20260706133051.983801F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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