Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp7724857rwb; Wed, 23 Nov 2022 09:55:45 -0800 (PST) X-Google-Smtp-Source: AA0mqf5LWVnsFL1mXmCK3QGQH5knS0o8tZs06IrrH33T6LDqQdkIsS6dXrTPOvH5R/tcIKXzbkWM X-Received: by 2002:a05:6a00:d66:b0:56a:fd45:d054 with SMTP id n38-20020a056a000d6600b0056afd45d054mr15969666pfv.3.1669226145026; Wed, 23 Nov 2022 09:55:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669226145; cv=none; d=google.com; s=arc-20160816; b=HaPmC61bzEPyfn6JBOHE1J1HlZWxEiXVQ2ID1HLJKMQo+E/tXSNnzSZWnzsyy0IUT+ IRN4l5SC5Wp4wtuC+3btrAt5QQS7mQSss5GskMoQ3f9yY++HbB10bsdfYBhxoA4wMjCc 1jpwr2O36JuvhauNHNbQLLHoAvGP9rdMWlbNSoufMdBS51EDDS0QCnJT3n0F1/+BGeW2 WHoln83DdOpb6hgph5a5oIIBOD3BJMIbQQiNYFtcKNEoS3Bto6U1tq2oe3pSjvdlxyg+ ANafnZqBf22+NoE8Cy0QkPDLLrnNXRy/ZqXwFvIr2Js2iTh25I+7tp27/xCxGUBJ1BoS UAVA== 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 :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=ZT9WVned9qGMAlH0r6W65dY8aAfAq0l2ES0Gvi1OpwI=; b=Yonj8ObowFFon1yDdkaGM7DfI/0c9EmSIasieKKr2BENk1ts4WkggH6Y5THLWdyPUg nJoYVxpOp7u6sp8edUpFQjHkDYB58+ZVnrNREOivmTWgI0Br4fistMbiBTG7RU1bk1mx daNmpfF8FtngA+/JUv37ry+LHZKhKgzz4iAWWQLXD7XNFuHPHlncUrKpldh+ANkIv2ML tLxfkVbKdSw2ZbbGBmpA6FEQ2EcDvBJXvUQZG+WNf/8L0F+qMf0x8oWs9aNFvTXjnDnW 2IqK/oiDADonqb1q+bvtmlteELebZKfHgp71U7fviTRZLTOQ5xlmX+YV8yn7BRY0H+MP kfyA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcdkim header.b=nnHKdSPT; 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 ng6-20020a17090b1a8600b00202c7f4631esi2836889pjb.19.2022.11.23.09.55.33; Wed, 23 Nov 2022 09:55:45 -0800 (PST) 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=qcdkim header.b=nnHKdSPT; 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 S238580AbiKWRam (ORCPT + 88 others); Wed, 23 Nov 2022 12:30:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48046 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238866AbiKWRaN (ORCPT ); Wed, 23 Nov 2022 12:30:13 -0500 Received: from alexa-out-sd-01.qualcomm.com (alexa-out-sd-01.qualcomm.com [199.106.114.38]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5DDB88E295; Wed, 23 Nov 2022 09:30:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1669224612; x=1700760612; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=ZT9WVned9qGMAlH0r6W65dY8aAfAq0l2ES0Gvi1OpwI=; b=nnHKdSPTYo47b6DAIhIVApHTAOdpOozQLnW/MQPB27rGarHhpDtCREnX j3g4oBm2h17QBYN0wTEwgqKUVrS+LEUlbJ0TjHzXB7xvgXYJsa0jsqgft mM6mF5HQOqHdycX5VTNVISbT2Tj0lfW98FMXb6DdYemAk9EQM5jFaxpjP k=; Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30]) by alexa-out-sd-01.qualcomm.com with ESMTP; 23 Nov 2022 09:30:12 -0800 X-QCInternal: smtphost Received: from nasanex01b.na.qualcomm.com ([10.46.141.250]) by ironmsg-SD-alpha.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Nov 2022 09:30:11 -0800 Received: from [10.110.94.74] (10.80.80.8) by nasanex01b.na.qualcomm.com (10.46.141.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.36; Wed, 23 Nov 2022 09:30:10 -0800 Message-ID: <85a0af2c-5f79-3d84-c946-a4960aee2958@quicinc.com> Date: Wed, 23 Nov 2022 11:30:09 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [PATCH v4 1/2] dt-bindings: pinctrl: qcom: Add QDU1000 and QRU1000 pinctrl To: Krzysztof Kozlowski , Andy Gross , Bjorn Andersson , Konrad Dybcio , Linus Walleij , Rob Herring , Krzysztof Kozlowski CC: , , , References: <20221118182039.29236-1-quic_molvera@quicinc.com> <20221118182039.29236-2-quic_molvera@quicinc.com> <528648f2-17df-ab19-8ad4-76423bbc0ae4@linaro.org> <03174a04-440d-a840-1e54-fbdbdfe296c3@linaro.org> <2a50b68f-d2dd-bae5-29b3-f608813d5a3f@quicinc.com> <1d13e913-d425-8cb0-d954-d1d7bc340f38@linaro.org> Content-Language: en-US From: Melody Olvera In-Reply-To: <1d13e913-d425-8cb0-d954-d1d7bc340f38@linaro.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nasanex01b.na.qualcomm.com (10.46.141.250) X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham 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 11/23/2022 2:06 AM, Krzysztof Kozlowski wrote: > On 22/11/2022 16:23, Melody Olvera wrote: >> >> On 11/22/2022 1:48 AM, Krzysztof Kozlowski wrote: >>> On 21/11/2022 21:38, Melody Olvera wrote: >>>> On 11/20/2022 4:58 AM, Krzysztof Kozlowski wrote: >>>>> On 18/11/2022 19:20, Melody Olvera wrote: >>>>>> Add device tree bindings for QDU1000 and QRU1000 TLMM devices. >>>>>> >>>>>> Signed-off-by: Melody Olvera >>>>>> --- >>>>>> .../bindings/pinctrl/qcom,qdu1000-tlmm.yaml | 134 ++++++++++++++++++ >>>>>> 1 file changed, 134 insertions(+) >>>>>> create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,qdu1000-tlmm.yaml >>>>>> >>>>>> diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,qdu1000-tlmm.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,qdu1000-tlmm.yaml >>>>>> new file mode 100644 >>>>>> index 000000000000..cb0c496d8666 >>>>>> --- /dev/null >>>>>> +++ b/Documentation/devicetree/bindings/pinctrl/qcom,qdu1000-tlmm.yaml >>>>>> @@ -0,0 +1,134 @@ >>>>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >>>>>> +%YAML 1.2 >>>>>> +--- >>>>>> +$id: http://devicetree.org/schemas/pinctrl/qcom,qdu1000-tlmm.yaml# >>>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>>>>> + >>>>>> +title: Qualcomm Technologies, Inc. QDU1000/QRU1000 TLMM block >>>>>> + >>>>>> +maintainers: >>>>>> + - Melody Olvera >>>>>> + >>>>>> +description: | >>>>>> + This Top Level Mode Multiplexer block (TLMM) is found in the QDU1000 and >>>>>> + QRU1000 platforms. >>>>> It's better to keep consistent style which allows to do easy >>>>> search/replace, than to have new files using their own sentences. So >>>>> keep it the same as was unified in few recent commits. >>>> Ok... Just making sure that's what you want. Last PS you gave comments to change >>>> the wording of this description to remove "This binding describes..." as we've done >>>> in all the other qcom pinctrl/tlmm bindings. I can change the wording back to the >>>> original, just want to be clear here. >>> I propose to have the same wording as other Qualcomm TLMM bindings, >>> however you changed it to something not the same. Therefore I wonder - >>> why having here different wording than all other bindings? >>> >>> By going back to original - what do you mean? If it matches all others, >>> then yes, but I doubt it. >>> >>> Just to be sure - are you working on proper (recent) trees or something old? >> Original matched how it was done on other Qualcomm TLMM bindings. Feedback >> was to drop "This binding describes..." from [1], but all the Qualcomm TLMM >> bindings start with "This binding describes...". I'm looking at qcom tree for-next >> branch; should be recent, no? > No. It's not recent for anything else than managed by Bjorn. You need to > base the patches on maintainer's trees, which is usually the easiest to > achieve via linux-next (especially that these changes were in my tree > for some time before I sent them to Linus). Ah ok; looking at linux-next looks like it should be "Top Level Mode Multiplexer pin controller in Qualcomm QDU1000 and QRU1000 SoCs." Thanks, Melody > > Your all other patches might have similar issues - wrong base or not > good example/starting point. > > Best regards, > Krzysztof >