[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fad016b1-4079-468f-a2a6-a482c3aab66f@quicinc.com>
Date: Thu, 11 Jul 2024 18:46:52 +0800
From: "Aiqun Yu (Maria)" <quic_aiquny@...cinc.com>
To: Chris Lew <quic_clew@...cinc.com>, Tengfei Fan <quic_tengfan@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio
<konrad.dybcio@...aro.org>,
Rob Herring <robh@...nel.org>,
"Krzysztof
Kozlowski" <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
CC: <kernel@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: soc: qcom,aoss-qmp: Document the QCS9100
AOSS channel
On 7/11/2024 3:58 AM, Chris Lew wrote:
> Hi Tengfei,
>
> On 7/9/2024 7:24 AM, Tengfei Fan wrote:
>> Document the Always-On Subsystem side channel on the QCS9100 Platform.
>> QCS9100 is drived from SA8775p. Currently, both the QCS9100 and SA8775p
>
> /s/drived/derived/
>
>> platform use non-SCMI resource. In the future, the SA8775p platform will
>> move to use SCMI resources and it will have new sa8775p-related device
>> tree. Consequently, introduce "qcom,qcs9100-aoss-qmp" to describe
>> non-SCMI based AOSS channel.
>>
>
> Were there any differences between non-SCMI and SCMI based platforms
> specifically for the qcom_aoss.com driver?
Hi Chris, the non-SCMI solution and SCMI solution is different from the
clk resource etc. So for current qcom_aoss.com driver, I am expecting
the qdss clk resource feature inside this driver may have some different
design. More details is discussed via other internal emails as well.
Currently, we want to have qcs9100(non-scmi) compatible added to
differentiate sa8775p(scmi) compatible firstly to not blocking IOT and
AUTO separately. Currently it is a looping dependency for moving forward.
Feel free to let us know if you have other opinions.
>
>
>> Signed-off-by: Tengfei Fan <quic_tengfan@...cinc.com>
>> ---
>> Introduce support for the QCS9100 SoC device tree (DTSI) and the
>> QCS9100 RIDE board DTS. The QCS9100 is a variant of the SA8775p.
>> While the QCS9100 platform is still in the early design stage, the
>> QCS9100 RIDE board is identical to the SA8775p RIDE board, except it
>> mounts the QCS9100 SoC instead of the SA8775p SoC.
>>
>> The QCS9100 SoC DTSI is directly renamed from the SA8775p SoC DTSI, and
>> all the compatible strings will be updated from "SA8775p" to "QCS9100".
>> The QCS9100 device tree patches will be pushed after all the device tree
>> bindings and device driver patches are reviewed.
>>
>> The final dtsi will like:
>> https://lore.kernel.org/linux-arm-msm/20240703025850.2172008-3-quic_tengfan@quicinc.com/
>>
>> The detailed cover letter reference:
>> https://lore.kernel.org/linux-arm-msm/20240703025850.2172008-1-quic_tengfan@quicinc.com/
>> ---
>> Changes in v2:
>> - Split huge patch series into different patch series according to
>> subsytems
>> - Update patch commit message
>>
>> prevous disscussion here:
>> [1] v1:
>> https://lore.kernel.org/linux-arm-msm/20240703025850.2172008-1-quic_tengfan@quicinc.com/
>> ---
>> Documentation/devicetree/bindings/soc/qcom/qcom,aoss-qmp.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/soc/qcom/qcom,aoss-qmp.yaml
>> b/Documentation/devicetree/bindings/soc/qcom/qcom,aoss-qmp.yaml
>> index 7afdb60edb22..80e1a8b43586 100644
>> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,aoss-qmp.yaml
>> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,aoss-qmp.yaml
>> @@ -25,6 +25,7 @@ properties:
>> compatible:
>> items:
>> - enum:
>> + - qcom,qcs9100-aoss-qmp
>> - qcom,qdu1000-aoss-qmp
>> - qcom,sa8775p-aoss-qmp
>> - qcom,sc7180-aoss-qmp
>>
>> ---
>> base-commit: 0b58e108042b0ed28a71cd7edf5175999955b233
>> change-id: 20240709-document_qcs9100_aoss_qmp_compatible-a7376629ea6c
>>
>> Best regards,
--
Thx and BRs,
Aiqun(Maria) Yu
Powered by blists - more mailing lists