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 ACE2DEB64D7 for ; Fri, 16 Jun 2023 11:33:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244879AbjFPLdz (ORCPT ); Fri, 16 Jun 2023 07:33:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51916 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240018AbjFPLdy (ORCPT ); Fri, 16 Jun 2023 07:33:54 -0400 Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 076BD2952 for ; Fri, 16 Jun 2023 04:33:53 -0700 (PDT) Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-51a1d539ffaso1396994a12.0 for ; Fri, 16 Jun 2023 04:33:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1686915231; x=1689507231; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=vnCBULjwaeoKSSjtKcAIMInnLKiE524xqLou3I4mzIY=; b=BzjzuQgJYIshv6bcYud1qHQiywtb1eZ8d+MShkxuxN3EJDxICt070sEJ0JJL7EEZqt u/pHAQ2DsV8ngkLgbpYKLS/D2PuXq0Wc5uhV4XxQzWecNdsJQmKfFl3h2T/ndhDWq90i SxH3a6OkswRDlbuZ5UKmFpm0bwJWecwrCb3ou+GUVfA5dMQj1tWqNXc2WT/3977ka5+f vI7eGEX97OQRjPg4ZY1XQYpDwSqHcII1L4JzlIoRUyAClKNuZlmWidjutaM1NKaLbHkJ XfqIxSRJiCyCYD49u9Z5cXqTtls+ko5E0de6qSUDctt7lAU9e/8vUL0jx3n6PZvP01N4 N81w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686915231; x=1689507231; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=vnCBULjwaeoKSSjtKcAIMInnLKiE524xqLou3I4mzIY=; b=EdiO6ltMjSe/COIQAAUFmWsqyMmPzAywRVImCt3/OZ5w1yodyCvHFJFOudPDIVTukB f85VB6viDIqfI4U+Wta6QVXK3tqzhzW97dxG65fTUmCvEsDRqEXACOE30QX0xxaV0dV7 JNFT9m+i8qL4IpzMyZvBWtWHgOHQu+qV0aLxzjxTQAwImtcDycmvshQ8EbBTB831d7Ti lzdKkqtmyKfMgHPjgMmpI5vqqH2MRo7iuyFqtnk6FerWaCnZecyMVJph9XEuARR+U2EW bgplO/oaTjew8xFpR7/JFIHwVVOte+lUTj0nSbnUcVmh/hjA/Fn5iYkA0uNqARXYvpbB UiEA== X-Gm-Message-State: AC+VfDxbf1ZWwaH83c5KBevqsK7ZyU+UJan0Ay47q5F1y1azI6utK3wO nbC0YJIDkAxrYhZ13rZqnrbujQ== X-Google-Smtp-Source: ACHHUZ5cEJy8okqiTA6pGSDD4tP30kklvbaWhufgQI9cqL7BYN2Ux0OGcf6oNZHMSOUjHxJKR+CmEw== X-Received: by 2002:a05:6402:5216:b0:514:a5cf:745b with SMTP id s22-20020a056402521600b00514a5cf745bmr7337833edd.3.1686915231435; Fri, 16 Jun 2023 04:33:51 -0700 (PDT) Received: from [192.168.1.20] ([178.197.219.26]) by smtp.gmail.com with ESMTPSA id l14-20020aa7c30e000000b00514b0f6a75esm9684653edq.97.2023.06.16.04.33.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 16 Jun 2023 04:33:50 -0700 (PDT) Message-ID: Date: Fri, 16 Jun 2023 13:33:48 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH 1/2] dt-bindings: clock: Update GCC clocks for QDU1000 and QRU1000 SoCs To: Imran Shaik , Andy Gross , Bjorn Andersson , Konrad Dybcio , Michael Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , Conor Dooley Cc: Melody Olvera , Taniya Das , linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Jagadeesh Kona , Satya Priya Kakitapalli , Ajit Pandey References: <20230616104941.921555-1-quic_imrashai@quicinc.com> <20230616104941.921555-2-quic_imrashai@quicinc.com> Content-Language: en-US From: Krzysztof Kozlowski In-Reply-To: <20230616104941.921555-2-quic_imrashai@quicinc.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 16/06/2023 12:49, Imran Shaik wrote: > Update the qcom GCC clock bindings and add v2 compatible string for QDU1000 > and QRU1000 SoCs. > > Signed-off-by: Taniya Das > Signed-off-by: Imran Shaik > --- > .../devicetree/bindings/clock/qcom,qdu1000-gcc.yaml | 6 +++++- > include/dt-bindings/clock/qcom,qdu1000-gcc.h | 4 +++- > 2 files changed, 8 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/clock/qcom,qdu1000-gcc.yaml b/Documentation/devicetree/bindings/clock/qcom,qdu1000-gcc.yaml > index 767a9d03aa32..030953d258c1 100644 > --- a/Documentation/devicetree/bindings/clock/qcom,qdu1000-gcc.yaml > +++ b/Documentation/devicetree/bindings/clock/qcom,qdu1000-gcc.yaml > @@ -8,6 +8,8 @@ title: Qualcomm Global Clock & Reset Controller for QDU1000 and QRU1000 > > maintainers: > - Melody Olvera > + - Taniya Das > + - Imran Shaik I appreciate adding more maintainers, it is welcomed and needed. However many of Qualcomm folks, including some of you, did not care enough to fix their old/incorrect email in existing entries, thus we have hundreds of wrong addresses and email bounces. We already raised this internally and publicly, with just small effect, so I am not sure what to do more. For me, allowing to have outdated email in maintainers is an easiest proof that maintainer does not care. Adding more maintainer entries, while maintainer does not care, would not feel right. Maybe let's start with fixing existing entries? > > description: | > Qualcomm global clock control module which supports the clocks, resets and > @@ -17,7 +19,9 @@ description: | > > properties: > compatible: > - const: qcom,qdu1000-gcc > + enum: > + - qcom,qdu1000-gcc > + - qcom,qdu1000-gcc-v2 It's the same block, isn't it? What is the "v2" exactly? Best regards, Krzysztof