From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DAA05C00528 for ; Thu, 3 Aug 2023 11:12:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232831AbjHCLMW (ORCPT ); Thu, 3 Aug 2023 07:12:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48584 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232519AbjHCLMF (ORCPT ); Thu, 3 Aug 2023 07:12:05 -0400 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EA68735A6; Thu, 3 Aug 2023 04:11:55 -0700 (PDT) Received: from pps.filterd (m0279873.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 373AWJFf027628; Thu, 3 Aug 2023 11:11:52 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : to : references : from : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=nIhYZQ2o7rdTlb24IfHDbwWufWVPzpCWsdj/IAyGH28=; b=R9Byoya6EIDQFWw0TKmqyMpLIKTMY5egmjyoGa1wcy4//+G7o20KLbp9ma7O7qq/1DD2 bkrBrEtENaWqFCB1D4J8G2Nr0BB9mF5BM6iTfjk9jyrCFzkozOXGR0i2T1S+myQnBQHc CqlautRyHZS4ohHoWY8uGwxs9ofMr+vGrtkbbyRpxY/fouoW5SBMVyzD2alDeGKj1NMF xYkd6h53gcYo1vcaX8Ui4g6LhOsyC4+po0g8QXLHVGaDLOgYaN3VpAWP2JO8fYldMTEU 5u5NRH6cXOMWdCXjAQjDtOv737XAS58DQoMHk54D6nPxm2MfEl0owSsf4J/KyZWB2Dvz nw== Received: from nalasppmta03.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3s87jhgepw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 03 Aug 2023 11:11:51 +0000 Received: from nalasex01c.na.qualcomm.com (nalasex01c.na.qualcomm.com [10.47.97.35]) by NALASPPMTA03.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 373BBoH7029762 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 3 Aug 2023 11:11:50 GMT Received: from [10.201.206.212] (10.80.80.8) by nalasex01c.na.qualcomm.com (10.47.97.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.30; Thu, 3 Aug 2023 04:11:47 -0700 Message-ID: <1ac4ec1d-f01e-6ddd-708d-6dec7ca4ea3d@quicinc.com> Date: Thu, 3 Aug 2023 16:41:44 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: document AL02-Cx and AL03-C2 boards based on IPQ9574 family To: Krzysztof Kozlowski , Konrad Dybcio , , , , , , , , References: <20230720084534.6461-1-quic_sridsn@quicinc.com> <20230720084534.6461-2-quic_sridsn@quicinc.com> <87c3a3db-d172-bc98-cf83-89b874c9fee7@linaro.org> <9e401641-1334-c0bc-c49a-481a8a9af2de@linaro.org> Content-Language: en-US From: Sridharan S N In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01c.na.qualcomm.com (10.47.97.35) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: 5vwHY_BDHPxdfBRppFQg_PzSoLMo5PRx X-Proofpoint-ORIG-GUID: 5vwHY_BDHPxdfBRppFQg_PzSoLMo5PRx X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.591,FMLib:17.11.176.26 definitions=2023-08-03_09,2023-08-03_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 impostorscore=0 lowpriorityscore=0 suspectscore=0 mlxlogscore=999 spamscore=0 bulkscore=0 priorityscore=1501 mlxscore=0 malwarescore=0 phishscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2306200000 definitions=main-2308030100 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/26/2023 12:51 PM, Krzysztof Kozlowski wrote: > On 26/07/2023 07:03, Sridharan S N wrote: >> On 7/20/2023 3:18 PM, Konrad Dybcio wrote: >>> On 20.07.2023 10:49, Krzysztof Kozlowski wrote: >>>> On 20/07/2023 10:45, Sridharan S N wrote: >>>>> Document the below listed (Reference Design Platform) RDP boards based on IPQ9574 >>>>> family of SoCs. >>>>> >>>>> AL02-C3 - rdp437 >>>>> AL02-C7 - rdp433-mht-phy >>>>> AL02-C10 - rdp433-mht-switch >>>>> AL02-C11 - rdp467 >>>>> AL02-C12 - rdp455 >>>>> AL02-C13 - rdp459 >>>>> AL02-C15 - rdp457 >>>>> AL02-C16 - rdp456 >>>>> AL02-C17 - rdp469 >>>>> AL02-C19 - rdp461 >>>>> AL03-C2 - rdp458 >>>>> >>>>> Signed-off-by: Sridharan S N >>>>> --- >>>>> .../devicetree/bindings/arm/qcom.yaml | 20 +++++++++++++++++++ >>>>> 1 file changed, 20 insertions(+) >>>>> >>>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml >>>>> index dd66fd872c31..d992261da691 100644 >>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml >>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml >>>>> @@ -89,10 +89,20 @@ description: | >>>>> adp >>>>> ap-al01-c1 >>>>> ap-al02-c2 >>>>> + ap-al02-c3 >>>>> ap-al02-c6 >>>>> ap-al02-c7 >>>>> ap-al02-c8 >>>>> ap-al02-c9 >>>>> + ap-al02-c10 >>>>> + ap-al02-c11 >>>>> + ap-al02-c12 >>>>> + ap-al02-c13 >>>>> + ap-al02-c15 >>>>> + ap-al02-c16 >>>>> + ap-al02-c17 >>>>> + ap-al02-c19 >>>> Why? I asked once, but there was no feedback from Qualcomm. >>>> >>>> Why do we need to do this? What's the point? >>> Another question would be, whether these boards are just one-off test >>> prototypes of which there exist like 5-10 units, or are they actually >>> going to be supported and useful. >>> >>> If it's the former, I don't think it makes sense to keep the device >>> trees upstream. >>> >>> Konrad >> These are all not test rdps and each rdps has its own configurations. >> IPQ9574 has four pcie instances and one QDSP processor. Not all rdps use >> all of the interfaces and it will vary for each rdp. In next version , >> will post with each rdp's configuration explicitly > > So still no answer why do we need to list it as possible boards. > Especially that it messes with compatible style, because c[1-9] looks > like board version. > > I suggest don't add these board types and drop existing ones. > > > Best regards, > Krzysztof Apologize for the late reply. IPQ bootloader doesn't need these info. we will send the patch to drop the existing ones Thanks, Sridharan