From: Bjorn Andersson <andersson@kernel.org>
To: robh@kernel.org, srini@kernel.org, amahesh@qti.qualcomm.com,
krzk+dt@kernel.org, conor+dt@kernel.org, konradybcio@kernel.org,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>
Cc: mathieu.poirier@linaro.org, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
mani@kernel.org
Subject: Re: (subset) [PATCH V5 0/5] Enable ADSP and CDSP for Glymur SoC
Date: Tue, 12 May 2026 15:23:12 -0500 [thread overview]
Message-ID: <177861739391.1242344.793126639808307051.b4-ty@kernel.org> (raw)
In-Reply-To: <20260313120814.1312410-1-sibi.sankar@oss.qualcomm.com>
On Fri, 13 Mar 2026 17:38:09 +0530, Sibi Sankar wrote:
> Qualcomm Glymur SoC variants predominantly boot Linux at EL2. This means
> that the firmware streams of the remote processors are managed in kernel
> and not in Gunyah hypervisor. Given that the Peripheral Image Loader for
> Qualcomm SoCs now support running Linux Host at EL2 [1], this series
> documents and enables ADSP and CDSP on Qualcomm Glymur SoCs with its
> fastrpc nodes. A few variants of the SoC are expected to run Linux at EL1
> hence the iommus properties are left optional.
>
> [...]
Applied, thanks!
[4/5] arm64: dts: qcom: glymur: Add ADSP and CDSP for Glymur SoC
commit: cd1d174c75f70fb0d7204802551aeaeb84689b59
[5/5] arm64: dts: qcom: glymur-crd: Enable ADSP and CDSP
commit: 377665c6078d1aa18d29d56a39d70ed8185cd2d1
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
parent reply other threads:[~2026-05-12 20:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260313120814.1312410-1-sibi.sankar@oss.qualcomm.com>]
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=177861739391.1242344.793126639808307051.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=amahesh@qti.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.com \
--cc=srini@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