From: Naina Mehta <quic_nainmeht@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <andersson@kernel.org>,
<mathieu.poirier@linaro.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<konrad.dybcio@linaro.org>, <manivannan.sadhasivam@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] dt-bindings: remoteproc: qcom,sm8550-pas: document the SDX75 PAS
Date: Fri, 7 Jun 2024 12:36:41 +0530 [thread overview]
Message-ID: <6176567c-dbfd-b752-1e17-d0a5eb8f1379@quicinc.com> (raw)
In-Reply-To: <4ed45f6d-fcc7-45d7-8df0-5470f7f75d0e@kernel.org>
On 6/6/2024 8:19 PM, Krzysztof Kozlowski wrote:
> On 06/06/2024 16:38, Naina Mehta wrote:
>> Document the MPSS Peripheral Authentication Service on SDX75 platform.
>>
>> Signed-off-by: Naina Mehta <quic_nainmeht@quicinc.com>
>> ---
>> .../devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
>> index 73fda7565cd1..02e15b1f78ab 100644
>> --- a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
>> +++ b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
>> @@ -16,6 +16,7 @@ description:
>> properties:
>> compatible:
>> enum:
>> + - qcom,sdx75-mpss-pas
>> - qcom,sm8550-adsp-pas
>> - qcom,sm8550-cdsp-pas
>> - qcom,sm8550-mpss-pas
>
> Missing updates to allOf constraints. Are you sure this is the binding
> for SDX75?
SDX75 diverged from SDX55 due to introduction of separate DTB firmware
binary and addition of DSM and Qlink logging memory regions. Considering
these additions, SM8550 PAS bindings seem closest.
Thanks for catching updates required for allOf constraints. I will add
sdx75 compatible in-line with qcom,sm8650-mpss-pas.
Please let me know if you recommend creating new bindings for SDX75.
Regards,
Naina
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-06-07 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 14:38 [PATCH 0/5] Add MPSS remoteproc support for SDX75 Naina Mehta
2024-06-06 14:38 ` [PATCH 1/5] dt-bindings: remoteproc: qcom,sm8550-pas: document the SDX75 PAS Naina Mehta
2024-06-06 14:49 ` Krzysztof Kozlowski
2024-06-07 7:06 ` Naina Mehta [this message]
2024-06-06 14:38 ` [PATCH 2/5] remoteproc: qcom: pas: Add SDX75 remoteproc support Naina Mehta
2024-06-06 14:38 ` [PATCH 3/5] arm64: dts: qcom: sdx75: add missing qlink_logging reserved memory for mpss Naina Mehta
2024-06-06 14:50 ` Krzysztof Kozlowski
2024-06-07 6:51 ` Naina Mehta
2024-06-06 14:38 ` [PATCH 4/5] arm64: dts: qcom: sdx75: Add remoteproc node Naina Mehta
2024-06-06 14:38 ` [PATCH 5/5] arm64: dts: qcom: sdx75-idp: enable MPSS " Naina Mehta
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=6176567c-dbfd-b752-1e17-d0a5eb8f1379@quicinc.com \
--to=quic_nainmeht@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.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=manivannan.sadhasivam@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@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