Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
	trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com
Subject: Re: [PATCH 2/6] dt-bindings: remoteproc: qcom,sm8550-pas: Add Kaanapali CDSP
Date: Fri, 24 Oct 2025 09:28:42 +0200	[thread overview]
Message-ID: <91288aa0-0088-4b50-8b33-661d8c0c25ae@gmail.com> (raw)
In-Reply-To: <1f98f83f-328f-47c8-84e7-2c77abb37a6a@oss.qualcomm.com>

On 24/10/2025 04:10, Jingyi Wang wrote:
>>>
>>> Hi Krzysztof,
>>>
>>> I tested with falling back to sm8650 cdsp but it will fail with:
>>> [    4.739615] qcom_q6v5_pas 26300000.remoteproc: unable to resolve shareable memory-region index 0
>>>
>>> sm8550 and kaanapali define 2 memory regions: 
>>> "memory-region = <&cdsp_mem>, <&q6_cdsp_dtb_mem>;"
>>>
>>> sm8650 and sm8750 define 3 memory regions:
>>> "memory-region = <&cdsp_mem>, <&q6_cdsp_dtb_mem>, <&global_sync_mem>;"
>>> with the driver:
>>>
>>> static const struct qcom_pas_data sm8650_cdsp_resource = {
>>>         .crash_reason_smem = 601,
>>>         .firmware_name = "cdsp.mdt",
>>>         .dtb_firmware_name = "cdsp_dtb.mdt",
>>>          <...>
>>>         .region_assign_idx = 2,
>>>         .region_assign_count = 1,
>>>         .region_assign_shared = true,
>>>         .region_assign_vmid = QCOM_SCM_VMID_CDSP,
>>> };
>>>
>>> When kaanapali fallback to sm8650 it cannot parse this region_assign_idx.
>>>
>>> So shall we still fallback to sm8550 or define a new node "kaanapali_cdsp_resource"
>>> in the driver?
>>
>> And partially the point here is that you might need the third region, no?
>> Best regards,
>> Krzysztof
> 
> On kaanapali, the global_sync_mem region is not managed by kernel, so it should
> be removed.


OK, then please mention this in the commit msg, so it is clear why this
is not compatible with previous generation.

Best regards,
Krzysztof

  reply	other threads:[~2025-10-24  7:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 23:37 [PATCH 0/6] Add initial remoteproc support for Kaanapali SoC Jingyi Wang
2025-09-24 23:37 ` [PATCH 1/6] dt-bindings: remoteproc: qcom,sm8550-pas: Add Kaanapali ADSP Jingyi Wang
2025-09-25  2:19   ` Dmitry Baryshkov
2025-09-29  6:06     ` Jingyi Wang
2025-09-29  9:39       ` Dmitry Baryshkov
2025-09-29 10:11         ` Jingyi Wang
2025-09-29 12:22           ` Dmitry Baryshkov
2025-09-30  2:12             ` Jingyi Wang
2025-09-30  2:16               ` Dmitry Baryshkov
2025-09-30  2:54                 ` Jingyi Wang
2025-09-24 23:37 ` [PATCH 2/6] dt-bindings: remoteproc: qcom,sm8550-pas: Add Kaanapali CDSP Jingyi Wang
2025-09-25  1:48   ` Krzysztof Kozłowski
2025-09-29  6:20     ` Jingyi Wang
2025-09-29  9:34       ` Dmitry Baryshkov
2025-09-29  9:41         ` Jingyi Wang
2025-09-29 10:03           ` Dmitry Baryshkov
2025-10-09 10:29             ` Krzysztof Kozlowski
2025-10-14  2:12               ` Jingyi Wang
2025-10-23  4:07               ` Jingyi Wang
2025-10-23  6:28                 ` Krzysztof Kozlowski
2025-10-24  2:10                   ` Jingyi Wang
2025-10-24  7:28                     ` Krzysztof Kozlowski [this message]
2025-10-24  7:42                       ` Jingyi Wang
2025-10-24  7:45                         ` Krzysztof Kozlowski
2025-09-24 23:37 ` [PATCH 3/6] dt-bindings: remoteproc: qcom,sm8550-pas: Add Kaanapali MPSS Jingyi Wang
2025-10-09 10:30   ` Krzysztof Kozlowski
2025-09-24 23:37 ` [PATCH 4/6] dt-bindings: remoteproc: qcom,pas: Document pas for Kaanapali SoCCP Jingyi Wang
2025-10-09 10:27   ` Krzysztof Kozlowski
2025-10-14  4:28     ` Jingyi Wang
2025-10-14  4:47       ` Krzysztof Kozlowski
2025-10-14  5:30         ` Jingyi Wang
2025-10-14 21:57           ` Krzysztof Kozlowski
2025-09-24 23:37 ` [PATCH 5/6] remoteproc: qcom: pas: Add late attach support for subsystems Jingyi Wang
2025-09-25  3:04   ` Dmitry Baryshkov
2025-09-29  6:42     ` Jingyi Wang
2025-09-29  9:35       ` Dmitry Baryshkov
2025-09-29 10:29         ` Jingyi Wang
2025-09-25  5:56   ` Zhongqiu Han
2025-09-29  6:27     ` Jingyi Wang
2025-09-24 23:37 ` [PATCH 6/6] remoteproc: qcom_q6v5_pas: Add SoCCP node on Kaanapali Jingyi Wang
2025-09-25 11:42   ` Konrad Dybcio
2025-09-29  6:27     ` Jingyi Wang

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=91288aa0-0088-4b50-8b33-661d8c0c25ae@gmail.com \
    --to=k.kozlowski.k@gmail.com \
    --cc=aiqun.yu@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=jingyi.wang@oss.qualcomm.com \
    --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=tingwei.zhang@oss.qualcomm.com \
    --cc=trilok.soni@oss.qualcomm.com \
    --cc=yijie.yang@oss.qualcomm.com \
    /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