From: Krzysztof Kozlowski <krzk@kernel.org>
To: Richard Acayan <mailingradian@gmail.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 04/11] dt-bindings: remoteproc: qcom: adsp: Add SDM670 ADSP compatible
Date: Sun, 27 Sep 2026 20:10:40 +0200 [thread overview]
Message-ID: <20260927-antique-honored-quail-ddbdba@quoll> (raw)
In-Reply-To: <20260922015801.32373-5-mailingradian@gmail.com>
On Mon, Sep 21, 2026 at 09:57:54PM -0400, Richard Acayan wrote:
> Add the compatible for the Audio DSP on SDM670.
>
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
You need to update constraints.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-27 18:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 1:57 [PATCH 00/11] ADSP for SDM670 and sound on Google Pixel 3a Richard Acayan
2026-09-22 1:57 ` [PATCH 01/11] dt-bindings: soc: qcom,smp2p: add sleepstate support Richard Acayan
2026-09-27 18:08 ` Krzysztof Kozlowski
2026-09-22 1:57 ` [PATCH 02/11] dt-bindings: mailbox: qcom: Add SDM670 APCS compatible Richard Acayan
2026-09-27 18:09 ` Krzysztof Kozlowski
2026-09-22 1:57 ` [PATCH 03/11] dt-bindings: soc: qcom: aoss: Add compatible for SDM670 Richard Acayan
2026-09-27 18:10 ` Krzysztof Kozlowski
2026-09-22 1:57 ` [PATCH 04/11] dt-bindings: remoteproc: qcom: adsp: Add SDM670 ADSP compatible Richard Acayan
2026-09-27 18:10 ` Krzysztof Kozlowski [this message]
2026-09-22 1:57 ` [PATCH 05/11] remoteproc: qcom: pas: Add SDM670 ADSP support Richard Acayan
2026-09-22 10:44 ` Konrad Dybcio
2026-09-28 14:55 ` Richard Acayan
2026-09-22 1:57 ` [PATCH 06/11] arm64: dts: qcom: sdm670: add adsp Richard Acayan
2026-09-22 2:08 ` sashiko-bot
2026-10-01 8:38 ` Konrad Dybcio
2026-09-22 1:57 ` [PATCH 07/11] arm64: dts: qcom: sdm670-google: enable adsp Richard Acayan
2026-10-01 8:38 ` Konrad Dybcio
2026-09-22 1:57 ` [PATCH 08/11] arm64: dts: qcom: sdm670-google: add sound card Richard Acayan
2026-09-22 1:57 ` [PATCH 09/11] arm64: dts: qcom: pm660l: add analog audio codec Richard Acayan
2026-09-22 2:05 ` sashiko-bot
2026-09-22 1:58 ` [PATCH 10/11] arm64: dts: qcom: sdm670: add digital " Richard Acayan
2026-10-01 8:39 ` Konrad Dybcio
2026-09-22 1:58 ` [PATCH 11/11] arm64: dts: qcom: sdm670-google: configure analog and digital codecs Richard Acayan
2026-09-22 2:11 ` sashiko-bot
2026-09-22 10:47 ` Konrad Dybcio
2026-09-25 17:48 ` Richard Acayan
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=20260927-antique-honored-quail-ddbdba@quoll \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
/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