public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>,
	agross@kernel.org, andersson@kernel.org, lgirdwood@gmail.com,
	broonie@kernel.org, robh+dt@kernel.org, quic_plai@quicinc.com,
	bgoswami@quicinc.com, perex@perex.cz, tiwai@suse.com,
	srinivas.kandagatla@linaro.org, quic_rohkumar@quicinc.com,
	linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, swboyd@chromium.org,
	judyhsiao@chromium.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] ASoC: google: dt-bindings: sc7280: Add #sound-dai-cells property
Date: Thu, 19 Jan 2023 13:17:12 +0100	[thread overview]
Message-ID: <452b332a-d796-119c-e80a-e68914f46702@kernel.org> (raw)
In-Reply-To: <1674108674-8392-4-git-send-email-quic_srivasam@quicinc.com>

On 19/01/2023 07:11, Srinivasa Rao Mandadapu wrote:
> Update sc7280 machine driver bindings with #sound-dai-cells property.
> This is to fix dtbs_check errors.
> 
> Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
> Tested-by: Ratna Deepthi Kudaravalli <quic_rkudarv@quicinc.com>
> ---
>  Documentation/devicetree/bindings/sound/google,sc7280-herobrine.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/sound/google,sc7280-herobrine.yaml b/Documentation/devicetree/bindings/sound/google,sc7280-herobrine.yaml
> index ccf1b1d..be5c60a 100644
> --- a/Documentation/devicetree/bindings/sound/google,sc7280-herobrine.yaml
> +++ b/Documentation/devicetree/bindings/sound/google,sc7280-herobrine.yaml
> @@ -35,6 +35,9 @@ properties:
>    "#size-cells":
>      const: 0
>  
> +  "#sound-dai-cells":
> +    const: 0

That's not correct property for the sound card. Does the sound card
exposes DAIs? Who uses these?

> +
>  patternProperties:
>    "^dai-link@[0-9a-f]$":
>      description:

Best regards,
Krzysztof


      reply	other threads:[~2023-01-19 12:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19  6:11 [PATCH 0/3] Update lpass dt-bindings Srinivasa Rao Mandadapu
2023-01-19  6:11 ` [PATCH 1/3] ASoC: qcom: dt-bindings: lpass-va-macro: Update clock name Srinivasa Rao Mandadapu
2023-01-19 12:08   ` Krzysztof Kozlowski
2023-01-19 13:02   ` Rob Herring
2023-01-19  6:11 ` [PATCH 2/3] ASoC: google: dt-bindings: sc7280: Add platform property Srinivasa Rao Mandadapu
2023-01-19 12:13   ` Krzysztof Kozlowski
2023-01-20  7:36     ` Srinivasa Rao Mandadapu
2023-01-20  8:39       ` Krzysztof Kozlowski
2023-01-19  6:11 ` [PATCH 3/3] ASoC: google: dt-bindings: sc7280: Add #sound-dai-cells property Srinivasa Rao Mandadapu
2023-01-19 12:17   ` Krzysztof Kozlowski [this message]

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=452b332a-d796-119c-e80a-e68914f46702@kernel.org \
    --to=krzk@kernel.org \
    --cc=agross@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=andersson@kernel.org \
    --cc=bgoswami@quicinc.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=judyhsiao@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=quic_plai@quicinc.com \
    --cc=quic_rohkumar@quicinc.com \
    --cc=quic_srivasam@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=swboyd@chromium.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