Received: by 2002:a5d:925a:0:0:0:0:0 with SMTP id e26csp1246383iol; Fri, 10 Jun 2022 03:34:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxUUNuiw7k24sC22XzPLeYbUt4g++5V9HwkIYnrEtZHzU0Zqju/2aEghqqwSa0X0ekxzW2p X-Received: by 2002:a05:6a00:1344:b0:51b:e3b5:54e2 with SMTP id k4-20020a056a00134400b0051be3b554e2mr37479852pfu.6.1654857281262; Fri, 10 Jun 2022 03:34:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654857281; cv=none; d=google.com; s=arc-20160816; b=hyZlUF8W+43ECkBSaCYU7SPOrGA99OE5GRLuUQYfDspiDOAZhox9o9wmgCO07b5dwi +bevUV9Ik4mjLFu+74bEfMdL79Xa35yUzjXopLBZuu82mDEdZtcrnZN4G/SrmvMuw0JK RG6k55HOOfdagIW8UQNqDZKK7qXP3a9pqWqIEJw1fNnSEsetiUjtDUsKQGHJ/p2I6EGe HiTh1hDbIeM8c/YVbdQTdRAFn5jRWVjpr3WnTHvIZzw3HfJ+Pz8kOqgV8A0k+8mP+/UI DcPHkq3MMYc1EivTyAfIaf0/KEAWiSEOtz1JJMofTarcurPwJwhux9Oa5gcpFnyVbTDo JLhw== 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=Rt0vsBETdsgUvTDEEF7Ic9okr/eCyvwvGWQNcegTZ1U=; b=i+0X0tws7N50GkpxqwWpTwiZQmvo+nOCs0e/RU2jw+72on6b77234gnwiIb8Q9BubW YPYjTpFMO0wngRhABECBe3XrX5NNE0zjCRtDctbQfDK2rxQh+pqDLS9FtQHUr61ODn2Z VSwWPDIKg3qORV4tZjJjL5gE1Fkf42lr/hTV5XME/V0FEh0/b6wQV0FTSjCWlwus+czj 82h1nWToYdeGm7Hx6Z+8UJUZcM7vl2tTsbnDg1Coe7F65It9QrsIpcHAWT7MpdOp8Ugj 4XDL55lezDw19yPN/ykEBUZ9N+x1FoW2X5TfA6mGftf+AYl2owsjp4uoHjCBkzZ/EWJY kGUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="K/yzPSh9"; 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=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q14-20020a632a0e000000b003fd69ac1f4asi25801619pgq.873.2022.06.10.03.34.28; Fri, 10 Jun 2022 03:34: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=@linaro.org header.s=google header.b="K/yzPSh9"; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346721AbiFJJuM (ORCPT + 99 others); Fri, 10 Jun 2022 05:50:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58488 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346666AbiFJJuH (ORCPT ); Fri, 10 Jun 2022 05:50:07 -0400 Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4832F6D1B3 for ; Fri, 10 Jun 2022 02:50:01 -0700 (PDT) Received: by mail-ed1-x530.google.com with SMTP id x62so34533460ede.10 for ; Fri, 10 Jun 2022 02:50:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=Rt0vsBETdsgUvTDEEF7Ic9okr/eCyvwvGWQNcegTZ1U=; b=K/yzPSh9wFBjDJiOA6mpuNoAmJIKYwK3g8Env7ES4l8idYzYh5vHjgqeOxkl5OR6bn IMj7pH0hNN2Hbo7fdFYujHzzlaDKoaPPfHTj7ois4W2c1KFVLn0j1kc8kPreMz+fwBD2 8Y7cGMwLibjZGW9UUAyX77himHkESzcNGvtnAlQuUpORd6vmIxb5pD+jpchqbs8DPaIj QJpE1T69z+wZwgdXiAnaQrf79KtOQD3foIrBEiB1NjabSUmVvNpTXF/nBck0nNsBEuBA 7BUPkg6E92dCrSV3VCVSZUnCfAbpDLrtjYK2KcdxC1RkfdaaJ1EXR9xblSWsZT6vQHQW b6Dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=Rt0vsBETdsgUvTDEEF7Ic9okr/eCyvwvGWQNcegTZ1U=; b=IPz00jLv1r41OUSK/Lh0XCyaLvphCabciNIErt4OtWTuDIF5LQO2JwRTWQTXPXF/q2 1/ygQDc9/bVFTAd7PeIPwfbooa8C+XUPmo6k0udvzFCOBp4d+KXBCfOEybwfgBQllzr7 ZuUVwhBeD6p/pUz6fYUuGrspl4HS1D7T67enPVc+4F7wYz1J8Mfh64xcZJGgx7kTNRm2 z8FbxTrkbwF6a3KmpkI1c4TFSjwryRo1Oo/EVvOdKjPqcMTEcAwZ9LHrcW38lPIQ+ONh cFdABKq9B59M5piTNKtL7E488FfczByZx63YcTHdI0OJu9YPgUsPhovWZhgpPkS7Se3J gRIA== X-Gm-Message-State: AOAM530JHpOUOr1LpWCNSKEnvBfL3vKbLrqmEk70Y8+YkLQdA+RSudTf DK/dX7y3pPAhagpJ+O1lWHoYXw== X-Received: by 2002:a05:6402:3551:b0:431:51e1:856f with SMTP id f17-20020a056402355100b0043151e1856fmr30811673edd.323.1654854599932; Fri, 10 Jun 2022 02:49:59 -0700 (PDT) Received: from [192.168.0.201] (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id yz17-20020a170906dc5100b0070b1ecdc12bsm10807528ejb.112.2022.06.10.02.49.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Jun 2022 02:49:59 -0700 (PDT) Message-ID: <073fcd16-12ae-ed4f-5eac-534bf73e68fe@linaro.org> Date: Fri, 10 Jun 2022 11:49:57 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH v2 06/20] dt-binding: clk: npcm845: Add binding for Nuvoton NPCM8XX Clock Content-Language: en-US To: Tomer Maimon Cc: Avi Fishman , Tali Perry , Joel Stanley , Patrick Venture , Nancy Yuen , Benjamin Fair , Rob Herring , Krzysztof Kozlowski , Michael Turquette , Stephen Boyd , Philipp Zabel , Greg KH , Daniel Lezcano , Thomas Gleixner , Wim Van Sebroeck , Guenter Roeck , Catalin Marinas , Will Deacon , Arnd Bergmann , Olof Johansson , Jiri Slaby , Shawn Guo , Bjorn Andersson , Geert Uytterhoeven , Marcel Ziswiler , Vinod Koul , Biju Das , Nobuhiro Iwamatsu , Robert Hancock , =?UTF-8?Q?Jonathan_Neusch=c3=a4fer?= , Lubomir Rintel , devicetree , Linux Kernel Mailing List , linux-clk , "open list:SERIAL DRIVERS" , LINUXWATCHDOG , Linux ARM References: <20220608095623.22327-1-tmaimon77@gmail.com> <20220608095623.22327-7-tmaimon77@gmail.com> <082366b0-6811-b492-c68c-12f9a9ee512e@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 09/06/2022 23:21, Tomer Maimon wrote: > Hi Krzysztof, > > > On Thu, 9 Jun 2022 at 16:22, Krzysztof Kozlowski > wrote: >> >> On 09/06/2022 15:17, Tomer Maimon wrote: >>> Hi Krzysztof, >>> >>> Thanks for your comments. >>> >>> On Wed, 8 Jun 2022 at 13:03, Krzysztof Kozlowski >>> wrote: >>>> >>>> On 08/06/2022 11:56, Tomer Maimon wrote: >>>>> Add binding for the Arbel BMC NPCM8XX Clock controller. >>>>> >>>>> Signed-off-by: Tomer Maimon >>>>> --- >>>>> .../bindings/clock/nuvoton,npcm845-clk.yaml | 63 +++++++++++++++++++ >>>>> .../dt-bindings/clock/nuvoton,npcm8xx-clock.h | 50 +++++++++++++++ >>>>> 2 files changed, 113 insertions(+) >>>>> create mode 100644 Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml >>>>> create mode 100644 include/dt-bindings/clock/nuvoton,npcm8xx-clock.h >>>>> >>>>> diff --git a/Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml b/Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml >>>>> new file mode 100644 >>>>> index 000000000000..e1f375716bc5 >>>>> --- /dev/null >>>>> +++ b/Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml >>>>> @@ -0,0 +1,63 @@ >>>>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause >>>>> +%YAML 1.2 >>>>> +--- >>>>> +$id: http://devicetree.org/schemas/clock/nuvoton,npcm845-clk.yaml# >>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>>>> + >>>>> +title: Nuvoton NPCM8XX Clock Controller Binding >>>>> + >>>>> +maintainers: >>>>> + - Tomer Maimon >>>>> + >>>>> +description: | >>>>> + Nuvoton Arbel BMC NPCM8XX contains an integrated clock controller, which >>>>> + generates and supplies clocks to all modules within the BMC. >>>>> + >>>>> +properties: >>>>> + compatible: >>>>> + enum: >>>>> + - nuvoton,npcm845-clk >>>>> + >>>>> + reg: >>>>> + maxItems: 1 >>>>> + >>>>> + clocks: >>>>> + items: >>>>> + - description: 25M reference clock >>>>> + - description: CPU reference clock >>>>> + - description: MC reference clock >>>>> + >>>>> + clock-names: >>>>> + items: >>>>> + - const: refclk >>>>> + - const: sysbypck >>>>> + - const: mcbypck >>>>> + >>>> >>>> I asked what is the suffix about and you replied "ck"... ok, so let's >>>> make clear. This should be: >>>> >>>> items: >>>> - const: ref >>>> - const: sysbyp >>>> - const: mcbyp >>>> >>>> or something similar, without the same suffix all over. >>> The clock names are the same clock name in our spec, this why we >>> prefer to leave the clock names as is. >> >> The naming with useless suffixes does not help. If your spec had >> "refclk_really_clock_this_is_a_clock" you also would insist on that? It >> does not make sense. > Sorry but I don't understand why the clock name cause an issue, we > prefer it will be the same as in our spec-clock diagram > BTW, the same naming found in NPCM7XX > https://elixir.bootlin.com/linux/v5.19-rc1/source/Documentation/devicetree/bindings/clock/nuvoton,npcm750-clk.txt#L36 Because the names should not have irrelevant information. interrupt-names should have "txirq". dma-names should not have "txdma". clock-names should not have "refclock" or "refclk" because it is irrelevant duplication. These are bindings, not DTS, so whatever you have in your spec matters less. DTS is the representation of hardware and there you can name clocks closer to the spec so it is easier for you, if that's your preference. And if your spec has "refclk_really_clock_this_is_a_clock" you still should not use it. Anyway, you should discuss it last time when I pointed it out. Instead my comments were ignored and you decided to send v2. That's not how discussion works and it will not bring you closer to your point. Best regards, Krzysztof