From: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: robh@kernel.org, srini@kernel.org, amahesh@qti.qualcomm.com,
krzk+dt@kernel.org, conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org, 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
Subject: Re: [PATCH V3 1/5] dt-bindings: remoteproc: qcom,sm8550-pas: Add Glymur ADSP
Date: Mon, 23 Feb 2026 15:06:09 +0530 [thread overview]
Message-ID: <ffecf0ae-f826-4690-8ec5-c19011f2c50b@oss.qualcomm.com> (raw)
In-Reply-To: <20260205-succinct-honest-badger-52e1b7@quoll>
On 2/5/2026 4:04 PM, Krzysztof Kozlowski wrote:
> On Thu, Jan 29, 2026 at 05:43:54AM +0530, Sibi Sankar wrote:
>> Document compatible for Qualcomm Glymur ADSP PAS which is fully
>> compatible with Qualcomm Kaanapali ADSP PAS.
>>
>> Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
>> ---
>>
>> Changes in v3:
>> - A few variants of the SoC are expected to run Linux at EL1 hence the
>> iommus properties are left optional.
>> - Link to v2: https://lore.kernel.org/all/20251029-knp-remoteproc-v2-0-6c81993b52ea@oss.qualcomm.com/
>>
>> .../devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
>> index b117c82b057b..fb6e0b4f54e8 100644
>> --- a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
>> +++ b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
>> @@ -29,6 +29,7 @@ properties:
>> - qcom,x1e80100-cdsp-pas
>> - items:
>> - enum:
>> + - qcom,glymur-adsp-pas
>> - qcom,kaanapali-adsp-pas
> There is no such hunk... I think this continues my comments from Sep/Oct
> 2025 that creating such patches, with multiple dependencies makes more
> difficult to review.
Hey Krzysztof, Thanks for taking time to review the series :) I'll give
some more context here to ensure that your comments were followed and
this is just a one-off. This patch was held off from the dependent
Kaanapali patches since it wasn't clear at that time if this SoC would
be running at EL1. Only with that confirmation and given that dependent
patch was on the list for a couple of weeks with Rbs, this series got
posted out. -Sibi
> I mark it as not applicable, please send when your dependencies hit the
> tree so I can review it in proper context.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-02-23 9:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 0:13 [PATCH V3 0/5] Enable ADSP and CDSP for Glymur SoC Sibi Sankar
2026-01-29 0:13 ` [PATCH V3 1/5] dt-bindings: remoteproc: qcom,sm8550-pas: Add Glymur ADSP Sibi Sankar
2026-02-05 10:34 ` Krzysztof Kozlowski
2026-02-23 9:36 ` Sibi Sankar [this message]
2026-01-29 0:13 ` [PATCH V3 2/5] dt-bindings: remoteproc: qcom,sm8550-pas: Add Glymur CDSP Sibi Sankar
2026-01-29 0:13 ` [PATCH V3 3/5] dt-bindings: misc: qcom,fastrpc: Add compatible for Glymur Sibi Sankar
2026-02-23 16:31 ` Bjorn Andersson
2026-02-24 5:54 ` Sibi Sankar
2026-01-29 0:13 ` [PATCH V3 4/5] arm64: dts: qcom: glymur: Add ADSP and CDSP for Glymur SoC Sibi Sankar
2026-01-30 9:54 ` Konrad Dybcio
2026-02-17 12:03 ` Abel Vesa
2026-01-29 0:13 ` [PATCH V3 5/5] arm64: dts: qcom: glymur-crd: Enable ADSP and CDSP Sibi Sankar
2026-01-30 9:55 ` Konrad Dybcio
2026-01-31 7:54 ` Dmitry Baryshkov
2026-02-02 10:16 ` Konrad Dybcio
2026-02-03 12:39 ` Dmitry Baryshkov
2026-02-23 9:09 ` Sibi Sankar
2026-02-23 17:14 ` Dmitry Baryshkov
2026-02-24 6:18 ` Sibi Sankar
2026-02-24 6:30 ` Dmitry Baryshkov
2026-02-24 9:38 ` Sibi Sankar
2026-02-17 12:02 ` Abel Vesa
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=ffecf0ae-f826-4690-8ec5-c19011f2c50b@oss.qualcomm.com \
--to=sibi.sankar@oss.qualcomm.com \
--cc=amahesh@qti.qualcomm.com \
--cc=andersson@kernel.org \
--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=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--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