Message ID | 20230307115022.12846-1-zhuyinbo@loongson.cn |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:5915:0:0:0:0:0 with SMTP id v21csp2397088wrd; Tue, 7 Mar 2023 04:22:05 -0800 (PST) X-Google-Smtp-Source: AK7set8kozT00bDepoqY+1YplUwn/LKKSW/kKXIbGBkZxpCO+1NHsEkyKSvt7X+/sgkEymFAnWRn X-Received: by 2002:a17:90b:3142:b0:237:a50e:1781 with SMTP id ip2-20020a17090b314200b00237a50e1781mr15057165pjb.24.1678191725472; Tue, 07 Mar 2023 04:22:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1678191725; cv=none; d=google.com; s=arc-20160816; b=BfbP4gdV+saWLhCBujdh95UIPgMBMIdec2bO8bkyW20oPq55P/AwgIREdzFkhxNHRL DpXghsF47fUWAvq0xm9Asm1pRY8MUtLaYMSiGZQk9zDhMazaHoSEeK70+h2T+l4e+zrZ 18QR+zplPnT3o+lqdFZuvUWvVxbI93LkmKHMmHWvUQZKxcxRjtVc3ZENZOVuKJ91XPxW cPyjLlifIiKPOjb56lhnCaxDLJgtPv26kVENZW8ljxHFsrwWJKg7c/bE7hLTNS1/qqpl msU1Ah6dTIGCM487opHMFRvh1pjHvuV4Zoh+fK7Ln64KeDsiVWIGB8nh6iqY6jemX0PQ gxmQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=WHeqZ91ktoHYPaseQwQh2/vlAXh9vhBgPwOc8Gn1/Wo=; b=SLxklQRgJztfr9tuFzjTBG6wzY2tHFDx7k7MgZQlJzXmExopyE3jG+PxA3fq7A3M7R ZZRQcIJr106j2EV0SbH9VY0BUaiKeWQO+etK0acx6fsn7qgpGHkqbQxFrfivbmAjQgls O1suuK3PP4PSikL64rGSSgjlZRawI8nvFVx6UoQE8vbgJV87T/XbimMqDyyw5xkmauEq FAYiqFVYJe0edHik4UPvTUMoACgt3WwiFFVv2nXFdwjBi84on6VPMTKN7Ye+Ndut15T6 6yncKnNKIvCiyzQjuEEht0HyrMDPzKYAS1M3Yq8QE9jWsBoV1UjxjJBZE5QBTMpP+Ycp lQbQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ce20-20020a17090aff1400b002299b06dca9si11354516pjb.83.2023.03.07.04.21.52; Tue, 07 Mar 2023 04:22:05 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231154AbjCGLvm (ORCPT <rfc822;toshivichauhan@gmail.com> + 99 others); Tue, 7 Mar 2023 06:51:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53690 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230474AbjCGLvU (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 7 Mar 2023 06:51:20 -0500 Received: from loongson.cn (mail.loongson.cn [114.242.206.163]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 45B037B102; Tue, 7 Mar 2023 03:50:29 -0800 (PST) Received: from loongson.cn (unknown [10.20.42.35]) by gateway (Coremail) with SMTP id _____8BxedkDJQdknlgJAA--.11831S3; Tue, 07 Mar 2023 19:50:27 +0800 (CST) Received: from user-pc.202.106.0.20 (unknown [10.20.42.35]) by localhost.localdomain (Coremail) with SMTP id AQAAf8AxHuT+JAdk6f9NAA--.33988S2; Tue, 07 Mar 2023 19:50:27 +0800 (CST) From: Yinbo Zhu <zhuyinbo@loongson.cn> To: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org Cc: Jianmin Lv <lvjianmin@loongson.cn>, Liu Peibao <liupeibao@loongson.cn>, wanghongliang@loongson.cn, loongson-kernel@lists.loongnix.cn, Yinbo Zhu <zhuyinbo@loongson.cn> Subject: [PATCH v13 1/2] dt-bindings: clock: add loongson-2 boot clock index Date: Tue, 7 Mar 2023 19:50:21 +0800 Message-Id: <20230307115022.12846-1-zhuyinbo@loongson.cn> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-CM-TRANSID: AQAAf8AxHuT+JAdk6f9NAA--.33988S2 X-CM-SenderInfo: 52kx5xhqerqz5rrqw2lrqou0/ X-Coremail-Antispam: 1Uk129KBjvJXoW7KFW8Wr4UAFykuw47Wry8Krg_yoW8XFW5pr 4kuFW7Kry2yF4xKw4vqr13Kr43u3yxGw1UAF47uF4UXF17A3WkJwsruF4fAryUXFykGFyx Za1DCw40va9rW37anT9S1TB71UUUUUJqnTZGkaVYY2UrUUUUj1kv1TuYvTs0mT0YCTnIWj qI5I8CrVACY4xI64kE6c02F40Ex7xfYxn0WfASr-VFAUDa7-sFnT9fnUUIcSsGvfJTRUUU bVxFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUXVWUAwA2ocxC64 kIII0Yj41l84x0c7CEw4AK67xGY2AK021l84ACjcxK6xIIjxv20xvE14v26r1I6r4UM28E F7xvwVC0I7IYx2IY6xkF7I0E14v26r4j6F4UM28EF7xvwVC2z280aVAFwI0_Cr1j6rxdM2 8EF7xvwVC2z280aVCY1x0267AKxVWxJr0_GcWln4kS14v26r1Y6r17M2AIxVAIcxkEcVAq 07x20xvEncxIr21l57IF6xkI12xvs2x26I8E6xACxx1l5I8CrVACY4xI64kE6c02F40Ex7 xfMcIj6xIIjxv20xvE14v26r1Y6r17McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Y z7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41l42xK82IYc2Ij64vIr41l42xK82IY6x8ErcxFaV Av8VWrMxC20s026xCaFVCjc4AY6r1j6r4UMxCIbckI1I0E14v26r1Y6r17MI8I3I0E5I8C rVAFwI0_Jr0_Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUtVW8Zw CIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x02 67AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcVC2z280aVAFwI0_Jr 0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxU7J3v UUUUU X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1759711566663611398?= X-GMAIL-MSGID: =?utf-8?q?1759711566663611398?= |
Series |
[v13,1/2] dt-bindings: clock: add loongson-2 boot clock index
|
|
Commit Message
Yinbo Zhu
March 7, 2023, 11:50 a.m. UTC
The Loongson-2 boot clock was used to spi and lio peripheral and
this patch was to add boot clock index number.
Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>
---
include/dt-bindings/clock/loongson,ls2k-clk.h | 25 ++++++++++---------
1 file changed, 13 insertions(+), 12 deletions(-)
Comments
On 07/03/2023 12:50, Yinbo Zhu wrote: > The Loongson-2 boot clock was used to spi and lio peripheral and > this patch was to add boot clock index number. > > Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn> > --- This is v13? Where is the changelog then? > include/dt-bindings/clock/loongson,ls2k-clk.h | 25 ++++++++++--------- > 1 file changed, 13 insertions(+), 12 deletions(-) > > diff --git a/include/dt-bindings/clock/loongson,ls2k-clk.h b/include/dt-bindings/clock/loongson,ls2k-clk.h > index db1e27e792ff1..e86804365e506 100644 > --- a/include/dt-bindings/clock/loongson,ls2k-clk.h > +++ b/include/dt-bindings/clock/loongson,ls2k-clk.h > @@ -13,17 +13,18 @@ > #define LOONGSON2_DC_PLL 3 > #define LOONGSON2_PIX0_PLL 4 > #define LOONGSON2_PIX1_PLL 5 > -#define LOONGSON2_NODE_CLK 6 > -#define LOONGSON2_HDA_CLK 7 > -#define LOONGSON2_GPU_CLK 8 > -#define LOONGSON2_DDR_CLK 9 > -#define LOONGSON2_GMAC_CLK 10 > -#define LOONGSON2_DC_CLK 11 > -#define LOONGSON2_APB_CLK 12 > -#define LOONGSON2_USB_CLK 13 > -#define LOONGSON2_SATA_CLK 14 > -#define LOONGSON2_PIX0_CLK 15 > -#define LOONGSON2_PIX1_CLK 16 > -#define LOONGSON2_CLK_END 17 > +#define LOONGSON2_BOOT_CLK 6 That's an ABI break and commit msg does not explain it. > +#define LOONGSON2_NODE_CLK 7 Best regards, Krzysztof
在 2023/3/7 下午8:47, Krzysztof Kozlowski 写道: > On 07/03/2023 12:50, Yinbo Zhu wrote: >> The Loongson-2 boot clock was used to spi and lio peripheral and >> this patch was to add boot clock index number. >> >> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn> >> --- > This is v13? Where is the changelog then? in fact, this is a new patch(v1), but another clock driver patch in this series had send as v13 and need depend on this patch so set current patch as v13. > > >> include/dt-bindings/clock/loongson,ls2k-clk.h | 25 ++++++++++--------- >> 1 file changed, 13 insertions(+), 12 deletions(-) >> >> diff --git a/include/dt-bindings/clock/loongson,ls2k-clk.h b/include/dt-bindings/clock/loongson,ls2k-clk.h >> index db1e27e792ff1..e86804365e506 100644 >> --- a/include/dt-bindings/clock/loongson,ls2k-clk.h >> +++ b/include/dt-bindings/clock/loongson,ls2k-clk.h >> @@ -13,17 +13,18 @@ >> #define LOONGSON2_DC_PLL 3 >> #define LOONGSON2_PIX0_PLL 4 >> #define LOONGSON2_PIX1_PLL 5 >> -#define LOONGSON2_NODE_CLK 6 >> -#define LOONGSON2_HDA_CLK 7 >> -#define LOONGSON2_GPU_CLK 8 >> -#define LOONGSON2_DDR_CLK 9 >> -#define LOONGSON2_GMAC_CLK 10 >> -#define LOONGSON2_DC_CLK 11 >> -#define LOONGSON2_APB_CLK 12 >> -#define LOONGSON2_USB_CLK 13 >> -#define LOONGSON2_SATA_CLK 14 >> -#define LOONGSON2_PIX0_CLK 15 >> -#define LOONGSON2_PIX1_CLK 16 >> -#define LOONGSON2_CLK_END 17 >> +#define LOONGSON2_BOOT_CLK 6 > That's an ABI break and commit msg does not explain it. you meaning is that need add a explanation in commit msg that why LOONGSON2_BOOT_CLK was added after LOONGSON2_PIX1_PLL and not add it in ending, right? > >> +#define LOONGSON2_NODE_CLK 7 > > > Best regards, > Krzysztof
On 08/03/2023 02:35, zhuyinbo wrote: > > 在 2023/3/7 下午8:47, Krzysztof Kozlowski 写道: >> On 07/03/2023 12:50, Yinbo Zhu wrote: >>> The Loongson-2 boot clock was used to spi and lio peripheral and >>> this patch was to add boot clock index number. >>> >>> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn> >>> --- >> This is v13? Where is the changelog then? > > in fact, this is a new patch(v1), but another clock driver patch in > this series had send as v13 and need depend on > > this patch so set current patch as v13. This should be explained in changelog. > >> >> >>> include/dt-bindings/clock/loongson,ls2k-clk.h | 25 ++++++++++--------- >>> 1 file changed, 13 insertions(+), 12 deletions(-) >>> >>> diff --git a/include/dt-bindings/clock/loongson,ls2k-clk.h b/include/dt-bindings/clock/loongson,ls2k-clk.h >>> index db1e27e792ff1..e86804365e506 100644 >>> --- a/include/dt-bindings/clock/loongson,ls2k-clk.h >>> +++ b/include/dt-bindings/clock/loongson,ls2k-clk.h >>> @@ -13,17 +13,18 @@ >>> #define LOONGSON2_DC_PLL 3 >>> #define LOONGSON2_PIX0_PLL 4 >>> #define LOONGSON2_PIX1_PLL 5 >>> -#define LOONGSON2_NODE_CLK 6 >>> -#define LOONGSON2_HDA_CLK 7 >>> -#define LOONGSON2_GPU_CLK 8 >>> -#define LOONGSON2_DDR_CLK 9 >>> -#define LOONGSON2_GMAC_CLK 10 >>> -#define LOONGSON2_DC_CLK 11 >>> -#define LOONGSON2_APB_CLK 12 >>> -#define LOONGSON2_USB_CLK 13 >>> -#define LOONGSON2_SATA_CLK 14 >>> -#define LOONGSON2_PIX0_CLK 15 >>> -#define LOONGSON2_PIX1_CLK 16 >>> -#define LOONGSON2_CLK_END 17 >>> +#define LOONGSON2_BOOT_CLK 6 >> That's an ABI break and commit msg does not explain it. > you meaning is that need add a explanation in commit msg that why You need good explanation to break the ABI. I don't understand the commit msg, but anyway I could not find there justification for ABI break. If you do not have good justification, don't break the ABI, Best regards, Krzysztof
在 2023/3/8 下午4:37, Krzysztof Kozlowski 写道: > On 08/03/2023 02:35, zhuyinbo wrote: >> 在 2023/3/7 下午8:47, Krzysztof Kozlowski 写道: >>> On 07/03/2023 12:50, Yinbo Zhu wrote: >>>> The Loongson-2 boot clock was used to spi and lio peripheral and >>>> this patch was to add boot clock index number. >>>> >>>> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn> >>>> --- >>> This is v13? Where is the changelog then? >> in fact, this is a new patch(v1), but another clock driver patch in >> this series had send as v13 and need depend on >> >> this patch so set current patch as v13. > This should be explained in changelog. okay I got it , and I whether need resend a v14 patch that in order to add this explain in changelog ? > >>> >>>> include/dt-bindings/clock/loongson,ls2k-clk.h | 25 ++++++++++--------- >>>> 1 file changed, 13 insertions(+), 12 deletions(-) >>>> >>>> diff --git a/include/dt-bindings/clock/loongson,ls2k-clk.h b/include/dt-bindings/clock/loongson,ls2k-clk.h >>>> index db1e27e792ff1..e86804365e506 100644 >>>> --- a/include/dt-bindings/clock/loongson,ls2k-clk.h >>>> +++ b/include/dt-bindings/clock/loongson,ls2k-clk.h >>>> @@ -13,17 +13,18 @@ >>>> #define LOONGSON2_DC_PLL 3 >>>> #define LOONGSON2_PIX0_PLL 4 >>>> #define LOONGSON2_PIX1_PLL 5 >>>> -#define LOONGSON2_NODE_CLK 6 >>>> -#define LOONGSON2_HDA_CLK 7 >>>> -#define LOONGSON2_GPU_CLK 8 >>>> -#define LOONGSON2_DDR_CLK 9 >>>> -#define LOONGSON2_GMAC_CLK 10 >>>> -#define LOONGSON2_DC_CLK 11 >>>> -#define LOONGSON2_APB_CLK 12 >>>> -#define LOONGSON2_USB_CLK 13 >>>> -#define LOONGSON2_SATA_CLK 14 >>>> -#define LOONGSON2_PIX0_CLK 15 >>>> -#define LOONGSON2_PIX1_CLK 16 >>>> -#define LOONGSON2_CLK_END 17 >>>> +#define LOONGSON2_BOOT_CLK 6 >>> That's an ABI break and commit msg does not explain it. >> you meaning is that need add a explanation in commit msg that why > You need good explanation to break the ABI. I don't understand the > commit msg, but anyway I could not find there justification for ABI > break. If you do not have good justification, don't break the ABI, The commit msg is the patch commit log, and I maybe not got it about break the ABI. You said about "break the ABI" is whether is location issue about "LOONGSON2_BOOT_CLK"? if yes, the LOONGSON2_BOOT_CLK was placed after LOONGSON2_PIX1_PLL that is due to their clock parent is same. and I whether need add this explanation in patch commit log description? > > > > Best regards, > Krzysztof
On 08/03/2023 10:24, zhuyinbo wrote: >>>> That's an ABI break and commit msg does not explain it. >>> you meaning is that need add a explanation in commit msg that why >> You need good explanation to break the ABI. I don't understand the >> commit msg, but anyway I could not find there justification for ABI >> break. If you do not have good justification, don't break the ABI, > > The commit msg is the patch commit log, and I maybe not got it about > break the ABI. You said about "break the ABI" > > is whether is location issue about "LOONGSON2_BOOT_CLK"? if yes, the > LOONGSON2_BOOT_CLK was placed > > after LOONGSON2_PIX1_PLL that is due to their clock parent is same. > and I whether need add this explanation > > in patch commit log description? Unfortunately I do not understand single thing from this. Best regards, Krzysztof
在 2023/3/8 下午6:38, Krzysztof Kozlowski 写道: > On 08/03/2023 10:24, zhuyinbo wrote: >>>>> That's an ABI break and commit msg does not explain it. >>>> you meaning is that need add a explanation in commit msg that why >>> You need good explanation to break the ABI. I don't understand the >>> commit msg, but anyway I could not find there justification for ABI >>> break. If you do not have good justification, don't break the ABI, >> The commit msg is the patch commit log, and I maybe not got it about >> break the ABI. You said about "break the ABI" >> >> is whether is location issue about "LOONGSON2_BOOT_CLK"? if yes, the >> LOONGSON2_BOOT_CLK was placed >> >> after LOONGSON2_PIX1_PLL that is due to their clock parent is same. >> and I whether need add this explanation >> >> in patch commit log description? > Unfortunately I do not understand single thing from this. > > Best regards, > Krzysztof The patch commit log description is patch desription. as follows: commit 592bc2b4106d787ea166ba16bfde6b3101ab1a8a Author: Yinbo Zhu <zhuyinbo@loongson.cn> Date: Tue Mar 7 17:18:32 2023 +0800 dt-bindings: clock: add loongson-2 boot clock index The Loongson-2 boot clock was used to spi and lio peripheral and this patch was to add boot clock index number. and your advice is "That's an ABI break and commit msg does not explain it." I got it from your advice that was to add a explanation about LOONGSON2_BOOT_CLK's location issue in patch description, right?
On 09/03/2023 02:43, zhuyinbo wrote: > > 在 2023/3/8 下午6:38, Krzysztof Kozlowski 写道: >> On 08/03/2023 10:24, zhuyinbo wrote: >>>>>> That's an ABI break and commit msg does not explain it. >>>>> you meaning is that need add a explanation in commit msg that why >>>> You need good explanation to break the ABI. I don't understand the >>>> commit msg, but anyway I could not find there justification for ABI >>>> break. If you do not have good justification, don't break the ABI, >>> The commit msg is the patch commit log, and I maybe not got it about >>> break the ABI. You said about "break the ABI" >>> >>> is whether is location issue about "LOONGSON2_BOOT_CLK"? if yes, the >>> LOONGSON2_BOOT_CLK was placed >>> >>> after LOONGSON2_PIX1_PLL that is due to their clock parent is same. >>> and I whether need add this explanation >>> >>> in patch commit log description? >> Unfortunately I do not understand single thing from this. >> >> Best regards, >> Krzysztof > > The patch commit log description is patch desription. as follows: > > > commit 592bc2b4106d787ea166ba16bfde6b3101ab1a8a > Author: Yinbo Zhu <zhuyinbo@loongson.cn> > Date: Tue Mar 7 17:18:32 2023 +0800 > > dt-bindings: clock: add loongson-2 boot clock index > > The Loongson-2 boot clock was used to spi and lio peripheral and > this patch was to add boot clock index number. I cannot understand this either. > > > and your advice is "That's an ABI break and commit msg does not explain it." > > I got it from your advice that was to add a explanation about > LOONGSON2_BOOT_CLK's > > location issue in patch description, right? ABI break needs justification, why do you think it is fine or who is/isn't affected etc. Your commit msg does not explain why ABI break is okay. It doesn't even explain to me why you need it. Best regards, Krzysztof
在 2023/3/9 下午2:25, Krzysztof Kozlowski 写道: > On 09/03/2023 02:43, zhuyinbo wrote: >> 在 2023/3/8 下午6:38, Krzysztof Kozlowski 写道: >>> On 08/03/2023 10:24, zhuyinbo wrote: >>>>>>> That's an ABI break and commit msg does not explain it. >>>>>> you meaning is that need add a explanation in commit msg that why >>>>> You need good explanation to break the ABI. I don't understand the >>>>> commit msg, but anyway I could not find there justification for ABI >>>>> break. If you do not have good justification, don't break the ABI, >>>> The commit msg is the patch commit log, and I maybe not got it about >>>> break the ABI. You said about "break the ABI" >>>> >>>> is whether is location issue about "LOONGSON2_BOOT_CLK"? if yes, the >>>> LOONGSON2_BOOT_CLK was placed >>>> >>>> after LOONGSON2_PIX1_PLL that is due to their clock parent is same. >>>> and I whether need add this explanation >>>> >>>> in patch commit log description? >>> Unfortunately I do not understand single thing from this. >>> >>> Best regards, >>> Krzysztof >> The patch commit log description is patch desription. as follows: >> >> >> commit 592bc2b4106d787ea166ba16bfde6b3101ab1a8a >> Author: Yinbo Zhu <zhuyinbo@loongson.cn> >> Date: Tue Mar 7 17:18:32 2023 +0800 >> >> dt-bindings: clock: add loongson-2 boot clock index >> >> The Loongson-2 boot clock was used to spi and lio peripheral and >> this patch was to add boot clock index number. > I cannot understand this either. I will rework commit msg . > >> >> and your advice is "That's an ABI break and commit msg does not explain it." >> >> I got it from your advice that was to add a explanation about >> LOONGSON2_BOOT_CLK's >> >> location issue in patch description, right? > ABI break needs justification, why do you think it is fine or who > is/isn't affected etc. Your commit msg does not explain why ABI break is > okay. It doesn't even explain to me why you need it. #define LOONGSON2_DC_PLL 3 #define LOONGSON2_PIX0_PLL 4 #define LOONGSON2_PIX1_PLL 5 -#define LOONGSON2_NODE_CLK 6 -#define LOONGSON2_HDA_CLK 7 -#define LOONGSON2_GPU_CLK 8 -#define LOONGSON2_DDR_CLK 9 -#define LOONGSON2_GMAC_CLK 10 -#define LOONGSON2_DC_CLK 11 -#define LOONGSON2_APB_CLK 12 -#define LOONGSON2_USB_CLK 13 -#define LOONGSON2_SATA_CLK 14 -#define LOONGSON2_PIX0_CLK 15 -#define LOONGSON2_PIX1_CLK 16 -#define LOONGSON2_CLK_END 17 +#define LOONGSON2_BOOT_CLK 6 +#define LOONGSON2_NODE_CLK 7 after add my patch, if dts still use above macro and not cause any issue. but if dts not use macro rather than use original clk number index that will cause a uncorrect clk, eg. -#define LOONGSON2_NODE_CLK 6 +#define LOONGSON2_NODE_CLK 7 this issue is that what you said about "ABI break", isn't it ? About your advice and question and I will use following description as patch commit msg, what do you think? dt-bindings: clock: add loongson-2 boot clock index The spi need to use boot clock and this patch is to add a boot clock index about LOONGSON2_BOOT_CLK and the LOONGSON2_BOOT_CLK was placed in after LOONGSON2_PIX1_PLL that due to LOONGSON2_PIX1_PLL, LOONGSON2_PIX0_PLL , LOONGSON2_DC_PLL and LOONGSON2_BOOT_CLK has same parent clock. In addition, the Loongson code of the community is still in the development stage, so this patch modification will not cause uncorrect clk quote issue at present. > > > Best regards, > Krzysztof
On 09/03/2023 13:44, zhuyinbo wrote: > > 在 2023/3/9 下午2:25, Krzysztof Kozlowski 写道: >> On 09/03/2023 02:43, zhuyinbo wrote: >>> 在 2023/3/8 下午6:38, Krzysztof Kozlowski 写道: >>>> On 08/03/2023 10:24, zhuyinbo wrote: >>>>>>>> That's an ABI break and commit msg does not explain it. >>>>>>> you meaning is that need add a explanation in commit msg that why >>>>>> You need good explanation to break the ABI. I don't understand the >>>>>> commit msg, but anyway I could not find there justification for ABI >>>>>> break. If you do not have good justification, don't break the ABI, >>>>> The commit msg is the patch commit log, and I maybe not got it about >>>>> break the ABI. You said about "break the ABI" >>>>> >>>>> is whether is location issue about "LOONGSON2_BOOT_CLK"? if yes, the >>>>> LOONGSON2_BOOT_CLK was placed >>>>> >>>>> after LOONGSON2_PIX1_PLL that is due to their clock parent is same. >>>>> and I whether need add this explanation >>>>> >>>>> in patch commit log description? >>>> Unfortunately I do not understand single thing from this. >>>> >>>> Best regards, >>>> Krzysztof >>> The patch commit log description is patch desription. as follows: >>> >>> >>> commit 592bc2b4106d787ea166ba16bfde6b3101ab1a8a >>> Author: Yinbo Zhu <zhuyinbo@loongson.cn> >>> Date: Tue Mar 7 17:18:32 2023 +0800 >>> >>> dt-bindings: clock: add loongson-2 boot clock index >>> >>> The Loongson-2 boot clock was used to spi and lio peripheral and >>> this patch was to add boot clock index number. >> I cannot understand this either. > I will rework commit msg . >> >>> >>> and your advice is "That's an ABI break and commit msg does not explain it." >>> >>> I got it from your advice that was to add a explanation about >>> LOONGSON2_BOOT_CLK's >>> >>> location issue in patch description, right? >> ABI break needs justification, why do you think it is fine or who >> is/isn't affected etc. Your commit msg does not explain why ABI break is >> okay. It doesn't even explain to me why you need it. > #define LOONGSON2_DC_PLL 3 > #define LOONGSON2_PIX0_PLL 4 > #define LOONGSON2_PIX1_PLL 5 > -#define LOONGSON2_NODE_CLK 6 > -#define LOONGSON2_HDA_CLK 7 > -#define LOONGSON2_GPU_CLK 8 > -#define LOONGSON2_DDR_CLK 9 > -#define LOONGSON2_GMAC_CLK 10 > -#define LOONGSON2_DC_CLK 11 > -#define LOONGSON2_APB_CLK 12 > -#define LOONGSON2_USB_CLK 13 > -#define LOONGSON2_SATA_CLK 14 > -#define LOONGSON2_PIX0_CLK 15 > -#define LOONGSON2_PIX1_CLK 16 > -#define LOONGSON2_CLK_END 17 > +#define LOONGSON2_BOOT_CLK 6 > +#define LOONGSON2_NODE_CLK 7 > > after add my patch, if dts still use above macro and not cause any > issue. but > > if dts not use macro rather than use original clk number index that will > cause a uncorrect clk, > > eg. > > -#define LOONGSON2_NODE_CLK 6 > > +#define LOONGSON2_NODE_CLK 7 > > this issue is that what you said about "ABI break", isn't it ? > > > About your advice and question and I will use following description as > patch commit msg, what do you think? > > > dt-bindings: clock: add loongson-2 boot clock index > > The spi need to use boot clock and this patch is to add a boot clock > index about LOONGSON2_BOOT_CLK > > and the LOONGSON2_BOOT_CLK was placed in after LOONGSON2_PIX1_PLL that > due to > > LOONGSON2_PIX1_PLL, LOONGSON2_PIX0_PLL , LOONGSON2_DC_PLL and > LOONGSON2_BOOT_CLK > > has same parent clock. In addition, the Loongson code of the community > is still in the development stage, > > so this patch modification will not cause uncorrect clk quote issue at > present. So the reason is same parent clock...? That's not much. These are IDs and parent clock do not matter. Drop the ID change. Best regards, Krzysztof
在 2023/3/10 上午12:12, Krzysztof Kozlowski 写道: > On 09/03/2023 13:44, zhuyinbo wrote: >> 在 2023/3/9 下午2:25, Krzysztof Kozlowski 写道: >>> On 09/03/2023 02:43, zhuyinbo wrote: >>>> 在 2023/3/8 下午6:38, Krzysztof Kozlowski 写道: >>>>> On 08/03/2023 10:24, zhuyinbo wrote: >>>>>>>>> That's an ABI break and commit msg does not explain it. >>>>>>>> you meaning is that need add a explanation in commit msg that why >>>>>>> You need good explanation to break the ABI. I don't understand the >>>>>>> commit msg, but anyway I could not find there justification for ABI >>>>>>> break. If you do not have good justification, don't break the ABI, >>>>>> The commit msg is the patch commit log, and I maybe not got it about >>>>>> break the ABI. You said about "break the ABI" >>>>>> >>>>>> is whether is location issue about "LOONGSON2_BOOT_CLK"? if yes, the >>>>>> LOONGSON2_BOOT_CLK was placed >>>>>> >>>>>> after LOONGSON2_PIX1_PLL that is due to their clock parent is same. >>>>>> and I whether need add this explanation >>>>>> >>>>>> in patch commit log description? >>>>> Unfortunately I do not understand single thing from this. >>>>> >>>>> Best regards, >>>>> Krzysztof >>>> The patch commit log description is patch desription. as follows: >>>> >>>> >>>> commit 592bc2b4106d787ea166ba16bfde6b3101ab1a8a >>>> Author: Yinbo Zhu <zhuyinbo@loongson.cn> >>>> Date: Tue Mar 7 17:18:32 2023 +0800 >>>> >>>> dt-bindings: clock: add loongson-2 boot clock index >>>> >>>> The Loongson-2 boot clock was used to spi and lio peripheral and >>>> this patch was to add boot clock index number. >>> I cannot understand this either. >> I will rework commit msg . >>>> and your advice is "That's an ABI break and commit msg does not explain it." >>>> >>>> I got it from your advice that was to add a explanation about >>>> LOONGSON2_BOOT_CLK's >>>> >>>> location issue in patch description, right? >>> ABI break needs justification, why do you think it is fine or who >>> is/isn't affected etc. Your commit msg does not explain why ABI break is >>> okay. It doesn't even explain to me why you need it. >> #define LOONGSON2_DC_PLL 3 >> #define LOONGSON2_PIX0_PLL 4 >> #define LOONGSON2_PIX1_PLL 5 >> -#define LOONGSON2_NODE_CLK 6 >> -#define LOONGSON2_HDA_CLK 7 >> -#define LOONGSON2_GPU_CLK 8 >> -#define LOONGSON2_DDR_CLK 9 >> -#define LOONGSON2_GMAC_CLK 10 >> -#define LOONGSON2_DC_CLK 11 >> -#define LOONGSON2_APB_CLK 12 >> -#define LOONGSON2_USB_CLK 13 >> -#define LOONGSON2_SATA_CLK 14 >> -#define LOONGSON2_PIX0_CLK 15 >> -#define LOONGSON2_PIX1_CLK 16 >> -#define LOONGSON2_CLK_END 17 >> +#define LOONGSON2_BOOT_CLK 6 >> +#define LOONGSON2_NODE_CLK 7 >> >> after add my patch, if dts still use above macro and not cause any >> issue. but >> >> if dts not use macro rather than use original clk number index that will >> cause a uncorrect clk, >> >> eg. >> >> -#define LOONGSON2_NODE_CLK 6 >> >> +#define LOONGSON2_NODE_CLK 7 >> >> this issue is that what you said about "ABI break", isn't it ? >> >> >> About your advice and question and I will use following description as >> patch commit msg, what do you think? >> >> >> dt-bindings: clock: add loongson-2 boot clock index >> >> The spi need to use boot clock and this patch is to add a boot clock >> index about LOONGSON2_BOOT_CLK >> >> and the LOONGSON2_BOOT_CLK was placed in after LOONGSON2_PIX1_PLL that >> due to >> >> LOONGSON2_PIX1_PLL, LOONGSON2_PIX0_PLL , LOONGSON2_DC_PLL and >> LOONGSON2_BOOT_CLK >> >> has same parent clock. In addition, the Loongson code of the community >> is still in the development stage, >> >> so this patch modification will not cause uncorrect clk quote issue at >> present. > So the reason is same parent clock...? That's not much. These are IDs > and parent clock do not matter. Drop the ID change. okay, I will add this marcro LOONGSON2_BOOT_CLK in ending. Thanks. > > Best regards, > Krzysztof
diff --git a/include/dt-bindings/clock/loongson,ls2k-clk.h b/include/dt-bindings/clock/loongson,ls2k-clk.h index db1e27e792ff1..e86804365e506 100644 --- a/include/dt-bindings/clock/loongson,ls2k-clk.h +++ b/include/dt-bindings/clock/loongson,ls2k-clk.h @@ -13,17 +13,18 @@ #define LOONGSON2_DC_PLL 3 #define LOONGSON2_PIX0_PLL 4 #define LOONGSON2_PIX1_PLL 5 -#define LOONGSON2_NODE_CLK 6 -#define LOONGSON2_HDA_CLK 7 -#define LOONGSON2_GPU_CLK 8 -#define LOONGSON2_DDR_CLK 9 -#define LOONGSON2_GMAC_CLK 10 -#define LOONGSON2_DC_CLK 11 -#define LOONGSON2_APB_CLK 12 -#define LOONGSON2_USB_CLK 13 -#define LOONGSON2_SATA_CLK 14 -#define LOONGSON2_PIX0_CLK 15 -#define LOONGSON2_PIX1_CLK 16 -#define LOONGSON2_CLK_END 17 +#define LOONGSON2_BOOT_CLK 6 +#define LOONGSON2_NODE_CLK 7 +#define LOONGSON2_HDA_CLK 8 +#define LOONGSON2_GPU_CLK 9 +#define LOONGSON2_DDR_CLK 10 +#define LOONGSON2_GMAC_CLK 11 +#define LOONGSON2_DC_CLK 12 +#define LOONGSON2_APB_CLK 13 +#define LOONGSON2_USB_CLK 14 +#define LOONGSON2_SATA_CLK 15 +#define LOONGSON2_PIX0_CLK 16 +#define LOONGSON2_PIX1_CLK 17 +#define LOONGSON2_CLK_END 18 #endif