From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 77C1929CF0; Thu, 11 Jul 2024 10:47:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720694830; cv=none; b=cTdQ12qK2sttIrM3QJlKDHwZmkRcyx7iUh6tWm5E845VEx5Kh5kl+y4s+PnSJkJI+NCKVD3ldHYNSccVSUM8aVH88zyovDWkHWmQfzirddRDmxdeUL8sTnkqDPeYT19gFzOgPDctJHKUtB0LWhC0/EwFGvedkgkbuIHg0tUUhxs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720694830; c=relaxed/simple; bh=f1ovXvPk52+ctLuYR1CD6jYCIGjkmFOkye8IjwVvGxQ=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=bo0KdGfRi+/V7EaSMg8n0o4TM0ShC8sOIQERtgSTdafHW63m8cHeLdtagq7a5wgpG/Hw5JAaiYOm8Dn57C8H+hrvDIMQYNCew7WbGnC6Jp3xpFro7gdd1dGmSrQzKevsFfzp755O5lsCroTflP7jWYKHUmT4h/9co36VnYRpnuY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=quicinc.com; spf=pass smtp.mailfrom=quicinc.com; dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com header.b=j+CuF7av; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=quicinc.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=quicinc.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com header.b="j+CuF7av" Received: from pps.filterd (m0279863.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 46B4mu5g008802; Thu, 11 Jul 2024 10:47:02 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= HMgmTT5lVtF+KlTpkcTEciTG+//l2SalS78yhnkfc6E=; b=j+CuF7avC2dM5Ous ngjYfGiD2Z1RlS1UEPXvntSmWWKPyj4SdAGJBGfPyvnI+erFytvYUfFg1OtA6/cD FgUUUEebmM0bPQ/LEXROnvq9mYsnTU7TeyQtVANqZCBJCOKGq1VlIusdnLVLGUDu pkFW7oGYuxCzqXepSsrpvT18VEL3FPy6gQqkfU5p3SzM6yV49qkhWXZu3WvubA/Q sCPtkoK4AuMERhbpdP1rI6qPfQqlkY0ZuPn9ZaclDRMdux3qQLitwYPbvv326tAO Y5Nzy1zgsYYS+wocs8jY67cNe8zn7LKLZxE7WOiTQ5m0+p4Ok55HZAGjZv43oAT5 z8qwgg== Received: from nasanppmta05.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 406x51c8x5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Jul 2024 10:47:01 +0000 (GMT) Received: from nasanex01a.na.qualcomm.com (nasanex01a.na.qualcomm.com [10.52.223.231]) by NASANPPMTA05.qualcomm.com (8.17.1.19/8.17.1.19) with ESMTPS id 46BAl1O3019021 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Jul 2024 10:47:01 GMT Received: from [10.239.132.150] (10.80.80.8) by nasanex01a.na.qualcomm.com (10.52.223.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.9; Thu, 11 Jul 2024 03:46:55 -0700 Message-ID: Date: Thu, 11 Jul 2024 18:46:52 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2] dt-bindings: soc: qcom,aoss-qmp: Document the QCS9100 AOSS channel To: Chris Lew , Tengfei Fan , Bjorn Andersson , Konrad Dybcio , Rob Herring , "Krzysztof Kozlowski" , Conor Dooley CC: , , , References: <20240709-document_qcs9100_aoss_qmp_compatible-v2-1-6c7f35bc9ec3@quicinc.com> <24302005-d9a5-400e-a28c-40276a3f7250@quicinc.com> Content-Language: en-US From: "Aiqun Yu (Maria)" In-Reply-To: <24302005-d9a5-400e-a28c-40276a3f7250@quicinc.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nasanex01a.na.qualcomm.com (10.52.223.231) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: qZhCkWpSRu7vt9ewYO5Fr8X0oYyaqyRR X-Proofpoint-ORIG-GUID: qZhCkWpSRu7vt9ewYO5Fr8X0oYyaqyRR X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-07-11_06,2024-07-11_01,2024-05-17_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 adultscore=0 suspectscore=0 impostorscore=0 mlxlogscore=999 mlxscore=0 bulkscore=0 priorityscore=1501 malwarescore=0 lowpriorityscore=0 phishscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2406140001 definitions=main-2407110076 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 >> --- >> 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