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 4F80F2B2DA; Mon, 12 Aug 2024 07:07:43 +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=1723446465; cv=none; b=fnJtNu5A7I40GLHFHMlZjgqTC3+ioml2Tx/jOc+WV2TcwFUjItzzTnsyro+2NodFyr5fXxYBW/yBX64DXPlgZdoKFkmWWGbrc0XDYaYMyIoorOygsBarhdLPhKMIdsegRqZfh6r8KuAFDx7I2duaI74V3NeRQe2fZc2AeeJeLKU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723446465; c=relaxed/simple; bh=OPMxeCjSxConl2mV+2ZWjQ6yXB/w5kj8tK2E+9Iuv/k=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=aTbXQJE9Q4vJooUMERxHBzIG/mlZgULmWYQFDVl2fw9gy/xzvhZcf2+kxh7BFULNJyl5VvquoWzBeI6rDvgua4HzCzHSSe0tDDaRrmRpudaUkdvNFaXUwPQnvE2EaxNIfyEHD0ZVe5565LOeg9vQbK3CoB3qP+net0WVAVHrZbE= 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=l/vYqaAC; 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="l/vYqaAC" Received: from pps.filterd (m0279862.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 47C2Zer3009744; Mon, 12 Aug 2024 07:07:40 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= uv+sV1CCcOdAKae2mYrI+fII8z5EIZR9snnHzC721as=; b=l/vYqaACKRj8FoqH lBwkk++hbDPMRCYpLoMhAA1VpWZwdiHPf16WPW5IPCpA6lNnjXzL07nG0EH/JFLS sRn/P30TqHNbEKwZFh3KLrCTfvmq2jb1gjtNg68/sIExcU0kIGZ8jsv0yp3KYGDd 834VshBLoLmZspDjV0MOBGoe2TO6DtTdLaa4EWEMOuQwfYS5DcqeXT9r4Do8O89Q JlRpw1zv1YgzAvBWVlFqIiOPYyUfMDYN0yVtiPbK/iNZUnjbsEB82rTw+Iw/Pnt/ 9aBn9Ml9Cjtaw+LO8hka8YN7/YSCGw5Xy8+pLT6nwXyaa+pxHIot7UH50cMjt3EC He6KQg== Received: from nalasppmta03.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 40x167u5r7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Aug 2024 07:07:40 +0000 (GMT) Received: from nalasex01b.na.qualcomm.com (nalasex01b.na.qualcomm.com [10.47.209.197]) by NALASPPMTA03.qualcomm.com (8.18.1.2/8.18.1.2) with ESMTPS id 47C77dkA005839 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Aug 2024 07:07:39 GMT Received: from [10.233.17.145] (10.80.80.8) by nalasex01b.na.qualcomm.com (10.47.209.197) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.9; Mon, 12 Aug 2024 00:07:24 -0700 Message-ID: <72b2d710-a7cb-45cf-9dad-e9fbd876697b@quicinc.com> Date: Mon, 12 Aug 2024 15:07:22 +0800 Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 4/4] arm64: dts: qcom: sa8775p-ride: Add QCS9100 compatible To: Krzysztof Kozlowski , Tengfei Fan , Bjorn Andersson , "Konrad Dybcio" , Rob Herring , "Krzysztof Kozlowski" , Conor Dooley CC: , , , References: <20240806-add_qcs9100_soc_id-v1-0-04d14081f304@quicinc.com> <20240806-add_qcs9100_soc_id-v1-4-04d14081f304@quicinc.com> <90eae361-7d5d-440f-a85d-dfd81b384fe7@kernel.org> <4a350e94-3c95-48e1-9ea8-ced483c1aa45@quicinc.com> <14ec06bd-0c27-4930-8bce-d3f5b68067ed@kernel.org> <9323127a-e6b5-4835-afa0-4ce0086fd9d1@kernel.org> <0d1c44b9-3d5f-4d93-af64-1756e52f4fe3@quicinc.com> <47c966c7-8736-44a2-8ec7-4d7989efa9cd@kernel.org> From: Tingwei Zhang In-Reply-To: <47c966c7-8736-44a2-8ec7-4d7989efa9cd@kernel.org> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nalasex01b.na.qualcomm.com (10.47.209.197) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: n9bsPKjsUerjrBkIQEdLd23g-DkCfKnL X-Proofpoint-ORIG-GUID: n9bsPKjsUerjrBkIQEdLd23g-DkCfKnL 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-08-11_25,2024-08-07_01,2024-05-17_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 bulkscore=0 clxscore=1015 suspectscore=0 mlxlogscore=735 impostorscore=0 malwarescore=0 spamscore=0 mlxscore=0 priorityscore=1501 phishscore=0 adultscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2407110000 definitions=main-2408120053 在 8/12/2024 2:15 PM, Krzysztof Kozlowski 写道: > On 12/08/2024 04:16, Tingwei Zhang wrote: >> On 8/8/2024 7:05 PM, Krzysztof Kozlowski wrote: >>> On 07/08/2024 13:04, Tingwei Zhang wrote: >>>> On 8/7/2024 5:35 PM, Krzysztof Kozlowski wrote: >>>>> On 07/08/2024 11:17, Tengfei Fan wrote: >>>>>> >>>>>> >>>>>> On 8/7/2024 3:28 PM, Krzysztof Kozlowski wrote: >>>>>>> On 06/08/2024 06:19, Tengfei Fan wrote: >>>>>>>> Add QCS9100 compatible in sa8775p ride and sa8775p ride r3 board DTS. >>>>>>>> QCS9100 references SA8775p, they share the same SoC DTSI and board DTS. >>>>>>>> >>>>>>> >>>>>>> I don't understand this. You claim here that QCS9100 references SA8775p >>>>>>> but your diff says other way: SA8775p references QCS9100. >>>>>>> >>>>>>> Sorry, that's confusing. >>>>>>> >>>>>>> Best regards, >>>>>>> Krzysztof >>>>>>> >>>>>> >>>>>> I will update the compatible as follows to indicate that QCS9100 >>>>>> references SA8775p. >>>>>> >>>>>> compatible = "qcom,sa8775p-ride", "qcom,qcs9100", "qcom,sa8775p"; >>>>> >>>>> Is this still correct, though? sa8775p won't come with qcs9100 SoC. >>>> We have a new board. Hardware is same as sa877p-ride except sa8775p is >>>> replaced with qcs9100. We add qcs9100 SoC compatible to sa8775p-ride >>> >>> Does "new board" mean that "old board" disappears? No users to care >>> about it? Or just the existing board is being changed (like new revision)? >> >> We will support both boards. Sa8775p-ride board with sa8775p chipset and >> sa8775p-ride board with qcs9100 chipset. Both of them can be used for >> development. > > Patch does something else then - changes compatibles for the existing > (old) board. Can you educate us the right way to add the qcs9100 SoC support in sa8775p-ride board? We don't want to duplicate whole device tree file since all the hardwares are same except the SoC, so we add qcs9100 SoC compatible to sa8775p-ride board and still keep sa8775p SoC compatible. > > Best regards, > Krzysztof > -- Thanks, Tingwei