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 12857189F54; Wed, 10 Jul 2024 16:45:38 +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=1720629940; cv=none; b=BRNu3LobG2ux4nms1DOJWJPZW+rn7erPEn9a5+06V/hPjjNzMo77onlkmS2D98xk/sZz4sLJ89xVpLsm2++ZMlLGHIsuM5qlIsT13jEUY9fewbIJ0dWzOMqDxObLK3itKQKl+iZLEvwFXEcLnylmTPlB9h6Xw2raHEJ14MJizc0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720629940; c=relaxed/simple; bh=ikUW+vPhF/kzlKZiQwKW5Ysxf41ejHqycbCX6ngMcMg=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=o0PzR22tUqNrFD1n1EqfxnPwGU/KsNDtULIcM1Xsqt6eYX2G+gwkjOnHwg6kaE0aptEHlJvT74sj+SXIESyhx+CZ7Vj4AkDQ9KvituqisSwM6aaTwIVnKId469+ghpZvUNYSzRW36vc2GY6PCfFcf5iAs2cFFwfKhTuG/CVjy6E= 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=YxFQKRIX; 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="YxFQKRIX" Received: from pps.filterd (m0279864.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 46A9avof016973; Wed, 10 Jul 2024 16:45:32 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= G6LwVwxoe1zXgroiWAGG01bsemNaFzH2jQrDan8X8XU=; b=YxFQKRIXKp1iLhGp 13xWuMZ2xCXHenujZi3TleVUCjn2p3x6godAVHghdvT6JLFvKZwSz5fLBwp8Qhp4 Wq5LGos1zikBDsGBjeFWrus5tbGkdIY4QRXtinVvTopbDZtHLLagMS/TNdytn60P Z5LgzOAeuGPbzAPsObnL07mOtgqtqHNognAMMONPjgtoiHfOkeIX40jb3Qa7aKh5 LY4yall+q/fPdcGw4vxVXDWTi6q4GXU4ej7Su0phbrNqgvsRsv3mTpajKwAlMseb rmosSzw9E2CQS9wVQqYIISIOH/LQsMeO2xvz62KOlhsZCsshOuuWyA8hECXydmIh sgqLAA== Received: from nasanppmta05.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 406y3hhhxr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Jul 2024 16:45:32 +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 46AGjJMO006063 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Jul 2024 16:45:19 GMT Received: from [10.110.80.193] (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; Wed, 10 Jul 2024 09:45:15 -0700 Message-ID: <3b8684f0-c89d-1a76-6bc5-93ced59dc51c@quicinc.com> Date: Wed, 10 Jul 2024 09:45:14 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: [PATCH v2] dt-bindings: phy: qcom,usb-snps-femto-v2: Add bindings for QCS9100 Content-Language: en-US To: Rob Herring , Tengfei Fan CC: Vinod Koul , Kishon Vijay Abraham I , Krzysztof Kozlowski , Conor Dooley , Wesley Cheng , , , , , References: <20240709-document_qcs9100_usb_hs_phy_compatible-v2-1-c84fbbafa9d6@quicinc.com> <20240710162745.GA3212156-robh@kernel.org> From: Trilok Soni In-Reply-To: <20240710162745.GA3212156-robh@kernel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) 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-ORIG-GUID: eK17DbsDWlOOU_1KyisRLNdD1-0qkt-C X-Proofpoint-GUID: eK17DbsDWlOOU_1KyisRLNdD1-0qkt-C 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-10_12,2024-07-10_01,2024-05-17_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 bulkscore=0 spamscore=0 adultscore=0 mlxscore=0 lowpriorityscore=0 suspectscore=0 clxscore=1011 mlxlogscore=999 impostorscore=0 phishscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2406140001 definitions=main-2407100117 On 7/10/2024 9:27 AM, Rob Herring wrote: > On Tue, Jul 09, 2024 at 08:46:19PM +0800, Tengfei Fan wrote: >> Document the compatible string for USB phy found in Qualcomm QCS9100 >> SoC. >> QCS9100 is drived from SA8775p. Currently, both the QCS9100 and SA8775p >> 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-usb-hs-phy" to describe >> non-SCMI based USB phy. >> >> 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. > > I'm not convinced this is not just pointless churn. Aren't we going to > end up with 2 compatible strings for everything? SCMI should just change > the providers, but otherwise the consumers are the same. I suppose if > clocks are abstracted into power-domains (an abuse IMO) then the > bindings change. > > Why do we need to support both SCMI and not-SCMI for the same chip? IOT SKU of this SOC is using the non-SCMI solution and Auto SKU of this SOC is using the SCMI based solution due to additional safety requirements. -- ---Trilok Soni