From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
martin.botka@somainline.org,
angelogioacchino.delregno@somainline.org,
marijn.suijten@somainline.org, jamipkettunen@somainline.org,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] arm64: dts: qcom: sm8250-edo: Enable ADSP/CDSP/SLPI
Date: Tue, 15 Jun 2021 21:44:32 -0500 [thread overview]
Message-ID: <YMllkBcLzrM3vdvM@builder.lan> (raw)
In-Reply-To: <20210616005843.79579-4-konrad.dybcio@somainline.org>
On Tue 15 Jun 19:58 CDT 2021, Konrad Dybcio wrote:
> Enabling the hardware thankfully comes down to a simple status = "okay".
> We assume that the firmware is provided by the Linux distribution, as it's
> signed and needs to come from the stock Android.
>
Are you okay with the default firmware paths? Or perhaps would it be
better to shove them into qcom/sm8250/sony/<some-identifier>/* to avoid
moving them later?
Regards,
Bjorn
> Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
> ---
> arch/arm64/boot/dts/qcom/sm8250-sony-xperia-edo.dtsi | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8250-sony-xperia-edo.dtsi b/arch/arm64/boot/dts/qcom/sm8250-sony-xperia-edo.dtsi
> index 0d7e3dbb12b1..82ae246694ad 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250-sony-xperia-edo.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250-sony-xperia-edo.dtsi
> @@ -118,6 +118,10 @@ ramoops@ffc00000 {
> };
> };
>
> +&adsp {
> + status = "okay";
> +};
> +
> &apps_rsc {
> pm8150-rpmh-regulators {
> compatible = "qcom,pm8150-rpmh-regulators";
> @@ -410,6 +414,10 @@ vreg_l7f_1p8: ldo7 {
> };
> };
>
> +&cdsp {
> + status = "okay";
> +};
> +
> &i2c1 {
> status = "okay";
> clock-frequency = <400000>;
> @@ -516,6 +524,10 @@ &sdhc_2 {
> no-emmc;
> };
>
> +&slpi {
> + status = "okay";
> +};
> +
> &tlmm {
> gpio-reserved-ranges = <40 4>, <52 4>;
>
> --
> 2.32.0
>
next prev parent reply other threads:[~2021-06-16 2:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 0:58 [PATCH 1/6] arm64: dts: qcom: sm8250-edo: Add hardware keys Konrad Dybcio
2021-06-16 0:58 ` [PATCH 2/6] arm64: dts: qcom: sm8250: Commonize PCIe pins Konrad Dybcio
2021-06-16 2:41 ` Bjorn Andersson
2021-06-16 0:58 ` [PATCH 3/6] arm64: dts: qcom: sm8250-edo: Enable PCIe Konrad Dybcio
2021-06-16 0:58 ` [PATCH 4/6] arm64: dts: qcom: sm8250-edo: Enable ADSP/CDSP/SLPI Konrad Dybcio
2021-06-16 2:44 ` Bjorn Andersson [this message]
2021-06-16 12:18 ` Konrad Dybcio
2021-06-16 0:58 ` [PATCH 5/6] arm64: dts: qcom: sm8250-edo: Enable GPI DMA Konrad Dybcio
2021-06-16 0:58 ` [PATCH 6/6] arm64: dts: qcom: sm8250-edo: Add Samsung touchscreen Konrad Dybcio
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=YMllkBcLzrM3vdvM@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=devicetree@vger.kernel.org \
--cc=jamipkettunen@somainline.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.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).