From: Luca Weiss <luca@z3ntu.xyz>
To: linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Luca Weiss <luca@z3ntu.xyz>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/5] ARM: dts: qcom: apq8026-asus-sparrow: Enable ADSP
Date: Sat, 23 Apr 2022 17:50:58 +0200 [thread overview]
Message-ID: <20220423155059.660387-4-luca@z3ntu.xyz> (raw)
In-Reply-To: <20220423155059.660387-1-luca@z3ntu.xyz>
The customized reserved memory for ADSP is already configured, so we
just need to enable the node.
Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
---
arch/arm/boot/dts/qcom-apq8026-asus-sparrow.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-apq8026-asus-sparrow.dts b/arch/arm/boot/dts/qcom-apq8026-asus-sparrow.dts
index 818c1a201227..215613c65250 100644
--- a/arch/arm/boot/dts/qcom-apq8026-asus-sparrow.dts
+++ b/arch/arm/boot/dts/qcom-apq8026-asus-sparrow.dts
@@ -59,6 +59,10 @@ vreg_wlan: wlan-regulator {
};
};
+&adsp {
+ status = "okay";
+};
+
&blsp1_uart1 {
status = "okay";
--
2.36.0
next prev parent reply other threads:[~2022-04-23 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 15:50 [PATCH 1/5] dt-bindings: remoteproc: qcom: pas: Add MSM8226 adsp Luca Weiss
2022-04-23 15:50 ` [PATCH 2/5] remoteproc: qcom: pas: Add MSM8226 ADSP support Luca Weiss
2022-04-23 15:50 ` [PATCH 3/5] ARM: dts: qcom: msm8226: Add ADSP node Luca Weiss
2022-07-19 18:21 ` Luca Weiss
2022-04-23 15:50 ` Luca Weiss [this message]
2022-04-23 15:50 ` [PATCH 5/5] ARM: dts: qcom: apq8026-lg-lenok: Enable ADSP Luca Weiss
2022-04-23 19:56 ` [PATCH 1/5] dt-bindings: remoteproc: qcom: pas: Add MSM8226 adsp Krzysztof Kozlowski
2022-09-15 18:46 ` (subset) " Bjorn Andersson
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=20220423155059.660387-4-luca@z3ntu.xyz \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).