Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1900314rwl; Thu, 6 Apr 2023 03:01:41 -0700 (PDT) X-Google-Smtp-Source: AKy350YJas9xOOcqTBMZ5NJRbtCNNJCrqUQB8W3kBFJMV8yzeeQ/NHCs0PtfLthwAkBriQHbyZ5V X-Received: by 2002:a62:19c5:0:b0:627:f740:51f9 with SMTP id 188-20020a6219c5000000b00627f74051f9mr6075722pfz.3.1680775301318; Thu, 06 Apr 2023 03:01:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680775301; cv=none; d=google.com; s=arc-20160816; b=bKA0NpOtyOb0Yck59Uk08k1Z4ZFYhz06NjG9pOVDisN6SFWPriF731c7HXveMKWa8u h0D3YLWyPhkMrWJesMtpIjmxhjOa0mS6If4zxZr0WpXXOanM7kYfW0nlQBx5Jk17AmIi p8tOiqGZdGuk0UBhrsayIFpANct14umZvzlmk0iKLt7lZxNXqkYvBybCYwSlaKnrNpct DsAv5vM1D7qT/VJbSP2fyvSjcfOWsh5MgtBJm+JZBd8wfO3LqywHry+c5U9SDUWIVTym GNEia8rzUkz239xhAQMFJjrshv2Jw+ANvECvXCvDZFWBA+9JuWe7TWDv2q2d1PhhMArd 0ARA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=jZgMGdmZaVAzkO0q+pB6WHfwcscuTH1O+8bqLAYLeyc=; b=VsXcjwA16BH3CGu3UseYtfPpx74Akl/5xbIqK6Cd8zncHnvBKbmADokPjYo3yfqTsd u2lhRWq2NC8wM1Amke6KIdhFd+l1LxMw8lF5zoe/PzA/ynJpo0Vv/4QWVRZduEiz1LyV yb9Z/8PL3LKub26HqUPFLuh/9vUCywMyq1Br2jlcafQW2G8BZFe+RDipL66jcoc+3f68 wyLD13V/yMvIqS1ngMEmXAUAh1WZZL2noYmgBUyGS3++Q5uOVrUQ+xMjFTOB7UCLffU7 3+BcgCXeE1TaAt02TEKRwrWXWaoHPGoVHB1z6BR3HOrbrVOa7q/iYiv6bpcAmGwLM4PK Z/Zw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b="Zwl4k/j1"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b27-20020aa78edb000000b005dd190cfc54si970543pfr.349.2023.04.06.03.01.22; Thu, 06 Apr 2023 03:01:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b="Zwl4k/j1"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236746AbjDFJ41 (ORCPT + 99 others); Thu, 6 Apr 2023 05:56:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46116 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236507AbjDFJ4A (ORCPT ); Thu, 6 Apr 2023 05:56:00 -0400 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 80053A268; Thu, 6 Apr 2023 02:54:02 -0700 (PDT) Received: from pps.filterd (m0279863.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3368Q17c022412; Thu, 6 Apr 2023 09:52:48 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=jZgMGdmZaVAzkO0q+pB6WHfwcscuTH1O+8bqLAYLeyc=; b=Zwl4k/j1cjaHvl2by5ChTWp8ZGbwPG+BRgzzQxrt5OgN9o+Rr+X8SetOu7KKn8B5uC27 aNd+0FJvUPZs0a52AVNkXZPQTh9j3150AsbL4IJqI/sKfU/mc+vE90prcN6dmtXAPOs6 wD/lVXK0ruONC254vvN2wtugU3XIxfAOU3s7Qsy4J7z14QgXVhsJgu5DG2T+cjGPski8 3Z7oZhkBTovHWicnpaDklaxbRe1m9bWva4k9UkGaHxBeOPK4pZzbUpcqRPGeZGeq6TRg WiIO8PH94//HnUeC+1EokYIzpwNqnVUvQVkp0F6CdN/CI3YAToirra3zgIjUmEZml5rt eg== Received: from nasanppmta01.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3psnmj0uh4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 06 Apr 2023 09:52:47 +0000 Received: from nasanex01c.na.qualcomm.com (nasanex01c.na.qualcomm.com [10.45.79.139]) by NASANPPMTA01.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 3369qlbP009820 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 6 Apr 2023 09:52:47 GMT Received: from [10.216.2.94] (10.80.80.8) by nasanex01c.na.qualcomm.com (10.45.79.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42; Thu, 6 Apr 2023 02:52:42 -0700 Message-ID: Date: Thu, 6 Apr 2023 15:22:39 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v2 2/5] dt-bindings: arm: msm: Add bindings for multi channel DDR in LLCC Content-Language: en-US To: Komal Bajaj , Manivannan Sadhasivam , Krzysztof Kozlowski CC: Rob Herring , Bjorn Andersson , Konrad Dybcio , Abel Vesa , Rishabh Bhatnagar , Prakash Ranjan , Krzysztof Kozlowski , Andy Gross , , , References: <20230313124040.9463-1-quic_kbajaj@quicinc.com> <20230313124040.9463-3-quic_kbajaj@quicinc.com> <2b3e39b9-ea70-db9b-89f7-09054df363c3@linaro.org> <20230315134814.GA98488@thinkpad> From: Mukesh Ojha 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: nasanex01a.na.qualcomm.com (10.52.223.231) To nasanex01c.na.qualcomm.com (10.45.79.139) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: 8zsLpEULLto8r0fDRQMYpqpfDWjio-uH X-Proofpoint-ORIG-GUID: 8zsLpEULLto8r0fDRQMYpqpfDWjio-uH X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-04-06_04,2023-04-05_01,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxscore=0 lowpriorityscore=0 suspectscore=0 mlxlogscore=999 adultscore=0 malwarescore=0 spamscore=0 bulkscore=0 phishscore=0 clxscore=1011 priorityscore=1501 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2304060086 X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/6/2023 2:49 PM, Komal Bajaj wrote: > Didn't see my reply on the list, so sending it again. > And also I see that the dt patch is already applied. The reason why you are not seeing your replies at https://lore.kernel.org/lkml/20230313124040.9463-1-quic_kbajaj@quicinc.com/ is because your reply cc-list contain some invalid domain (codeaurora.org) email id's and any list/email mentioned after that would not be getting your emails. -- Mukesh > > Thanks Krzysztof and Manivannan for reviewing the patch. > > > On 3/15/2023 7:18 PM, Manivannan Sadhasivam wrote: >> On Wed, Mar 15, 2023 at 08:41:21AM +0100, Krzysztof Kozlowski wrote: >>> On 13/03/2023 13:40, Komal Bajaj wrote: >>>> Add description for additional nodes needed to support >>>> mulitple channel DDR configurations in LLCC. >>>> >>>> Signed-off-by: Komal Bajaj >>> +Cc Mani, >>> >> Thanks, Krzysztof! >> >>> This will conflict with: >>> https://lore.kernel.org/all/20230314080443.64635-3-manivannan.sadhasivam@linaro.org/ >>> >>> Please rebase on top of Mani's patches (assuming they are not >>> conflicting in principle) >>> >>>> --- >>>> Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml | 9 +++++++++ >>>> 1 file changed, 9 insertions(+) >>>> >>>> diff --git a/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml >>>> index 38efcad56dbd..9a4a76caf490 100644 >>>> --- a/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml >>>> +++ b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml >>>> @@ -37,15 +37,24 @@ properties: >>>> items: >>> minItems: 2 >>> >>>> - description: LLCC base register region >>>> - description: LLCC broadcast base register region >>>> + - description: Feature register to decide which LLCC configuration >>>> + to use, this is optional >>>> >>>> reg-names: >>> minItems: 2 >>> >>>> items: >>>> - const: llcc_base >>>> - const: llcc_broadcast_base >>>> + - const: multi_channel_register >> Is this the actual register region or a specific register offset? We generally >> try to pass the base address of the region along with the size and use the >> offset inside the driver to access any specific registers. >> >> Thanks, >> Mani > > This is a specific register offset outside the LLCC register region which has the > information of number of DDR channel. > >>>> >>>> interrupts: >>>> maxItems: 1 >>>> >>>> + multi-ch-bit-off: >>>> + items: >>>> + - description: Specifies the offset in bits into the multi_channel_register >>>> + and the number of bits used to decide which LLCC configuration >>>> + to use >>> There are here few issues. >>> First, I don't fully understand the property. What is an LLCC >>> configuration? Like some fused values? > > There are different configuration for LLCC based on the number of > DDR channel it uses. Here, we are basically trying to get information > about the same. > >>> Second, don't make it a register specific, it will not scale easily to >>> any new version of this interface. Although how this should look like >>> depends on what is it. > > LLCC driver can only get DDR channel information from the register. > >>> Third, you need vendor prefix and type (unless this is a generic >>> property, but does not look like). Then "items" is probably wrong. Line >>> break after "description: " > > Noted, will take care of this in the next patchset. > > Thanks > Komal > >>> Best regards, >>> Krzysztof >>> >