Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp753643rwb; Tue, 27 Sep 2022 04:20:03 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4EGOOFrP52bdOPt4Nu9VB07JnGR0dGvsm2MPa4hVKMxB4XwqLs/xt6ioNJ4vD0IzLDi4Ym X-Received: by 2002:a17:90b:1e02:b0:203:21f3:f233 with SMTP id pg2-20020a17090b1e0200b0020321f3f233mr3972837pjb.189.1664277603021; Tue, 27 Sep 2022 04:20:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664277603; cv=none; d=google.com; s=arc-20160816; b=I0BoQG4ki7YufvPqK4/XROYaStrqQihFQ43kt2gkfElPskjRx8SzMWwiynYsW7lNl7 Dt7fRVa2u5RiEHGS+eoAN4h0OuGbUMWK9ir33KN/E28FVMnxu+a6qKUymeAy2sgsAKE2 wPqkRSrcOkrTrKrDPLTyE9pMAo/a2I+OJs2FlfhKV0Adm/ykHNsaQzEVX1AYc/UzINZD n0pu60i/huXLieZ7teLm9dYmaAnazMeCW9mvU//j/jO2+mFHwOGf4lZiPbN2hL64k+KF RTvpb6dU5R5o+PrHABTIziOWqu6AvMGO5WtyEUEB2RzIt6MNd+TFz5X3fm6sqxAbaTwq FyEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=6xjxDQa07YjuWMR2yGnd+y4znqJpdpsSP1WDZWgN5Yg=; b=DdGFyDKzGUOL3NnHkjR8wxcRqvlwQlMJW4frePIkruMCH7ihy8nFgYjQHI9Ht7Je1Q okZJEkmxo7soP0y9ZgCNgUwIMB7a3lM7vzczfKipI+j797CJckoybr4L1wPtnm4lK9IP C40BbCl1bOo/ZJFForewJd89VCKtTJYeGlcu0+eyaPL1j60hlXt6Iur1IJO6YaBl+gZS p2tFCLfMUZTKFDKrhjaAJ9zSjBUadr2Q/IVoPA62fv0xI4xI5kBdWkMMPZBImOyxHayA 6z91kKl4zsdzYM1vEiUnGrKFFlajJmlFg5MeSpUwu+sVL0uwnxfsERKNvZIdr2ph+WEf xAWQ== 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y64-20020a633243000000b00434c99c5359si1552217pgy.754.2022.09.27.04.19.48; Tue, 27 Sep 2022 04:20:03 -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; 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 S231927AbiI0LLI (ORCPT + 99 others); Tue, 27 Sep 2022 07:11:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48176 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231708AbiI0LKl (ORCPT ); Tue, 27 Sep 2022 07:10:41 -0400 Received: from loongson.cn (mail.loongson.cn [114.242.206.163]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D17B551A0C; Tue, 27 Sep 2022 04:08:31 -0700 (PDT) Received: from [10.180.13.64] (unknown [10.180.13.64]) by localhost.localdomain (Coremail) with SMTP id AQAAf8DxBOKo2TJjNbsiAA--.63954S2; Tue, 27 Sep 2022 19:08:25 +0800 (CST) Subject: Re: [PATCH v2 2/3] dt-bindings: thermal: Convert loongson2 to json-schema To: Krzysztof Kozlowski Cc: Krzysztof Kozlowski , "Rafael J . Wysocki" , Daniel Lezcano , Amit Kucheria , Zhang Rui , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, zhanghongchen , =?UTF-8?B?5YiY5L2p5a6d?= , zhuyinbo@loongson.cn, Daniel Lezcano , Amit Kucheria , Zhang Rui , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, zhanghongchen , =?UTF-8?B?5YiY5L2p5a6d?= References: <20220921015605.17078-1-zhuyinbo@loongson.cn> <20220921015605.17078-2-zhuyinbo@loongson.cn> <28a78a10.a7dd.1835f5aaf90.Coremail.zhuyinbo@loongson.cn> <4febe7e4.a96c.18362d997e3.Coremail.zhuyinbo@loongson.cn> <20220924174258.GA1011284-robh@kernel.org> <4ce14e3c.bf79.18377f44118.Coremail.zhuyinbo@loongson.cn> <1f3e153b-da8a-43fa-162f-9bea2ed3ef78@linaro.org> From: Yinbo Zhu Message-ID: <08dd2ab1-552f-d139-ce01-5d82f6c05a6a@loongson.cn> Date: Tue, 27 Sep 2022 19:08:24 +0800 User-Agent: Mozilla/5.0 (X11; Linux loongarch64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <1f3e153b-da8a-43fa-162f-9bea2ed3ef78@linaro.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CM-TRANSID: AQAAf8DxBOKo2TJjNbsiAA--.63954S2 X-Coremail-Antispam: 1UD129KBjvJXoWxtF4UGF4UtrWrJw4rAry5Jwb_yoWfJw4kpF 47CayUCr4kJr1UZw1xK3WUCFn0q3s8tr4DXrnxGw18Jryqqw13XF42qr15uryxGr1jqFWU ZrWvgw12gFyDA3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU9m14x267AKxVW5JVWrJwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26r4j6ryUM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26F4j 6r4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aVCY1x0267AKxVW0oV Cq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAKzVAqx4xG6I80ewAv7VC0 I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r 4UM4x0Y48IcVAKI48JM4x0x7Aq67IIx4CEVc8vx2IErcIFxwACI402YVCY1x02628vn2kI c2xKxwCYjI0SjxkI62AI1cAE67vIY487MxkIecxEwVCm-wCF04k20xvY0x0EwIxGrwCFx2 IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v2 6r106r1rMI8E67AF67kF1VAFwI0_GFv_WrylIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67 AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Gr0_Cr1lIxAIcVCF04k26cxKx2IY s7xG6r1j6r1xMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Gr 0_Gr1UYxBIdaVFxhVjvjDU0xZFpf9x0JUQvtAUUUUU= X-CM-SenderInfo: 52kx5xhqerqz5rrqw2lrqou0/ X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,NICE_REPLY_A, 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: X-Mailing-List: linux-kernel@vger.kernel.org 在 2022/9/26 下午2:21, Krzysztof Kozlowski 写道: > On 26/09/2022 06:00, Yinbo Zhu wrote: >> >> >>> -----原始邮件----- >>> 发件人: "Rob Herring" >>> 发送时间:2022-09-25 01:42:58 (星期日) >>> 收件人: "朱银波" >>> 抄送: "Krzysztof Kozlowski" , "Rafael J . Wysocki" , "Daniel Lezcano" , "Amit Kucheria" , "Zhang Rui" , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, zhanghongchen >>> 主题: Re: Re: [PATCH v2 2/3] dt-bindings: thermal: Convert loongson2 to json-schema >>> >>> On Thu, Sep 22, 2022 at 09:39:30AM +0800, 朱银波 wrote: >>>> >>>> >>>>> -----原始邮件----- >>>>> 发件人: "Krzysztof Kozlowski" >>>>> 发送时间:2022-09-21 17:31:11 (星期三) >>>>> 收件人: "朱银波" >>>>> 抄送: "Rafael J . Wysocki" , "Daniel Lezcano" , "Amit Kucheria" , "Zhang Rui" , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, zhanghongchen >>>>> 主题: Re: [PATCH v2 2/3] dt-bindings: thermal: Convert loongson2 to json-schema >>>>> >>>>> On 21/09/2022 11:22, 朱银波 wrote: >>>>>>> -----原始邮件----- >>>>>>> 发件人: "Krzysztof Kozlowski" >>>>>>> 发送时间:2022-09-21 15:05:00 (星期三) >>>>>>> 收件人: "Yinbo Zhu" , "Rafael J . Wysocki" , "Daniel Lezcano" , "Amit Kucheria" , "Zhang Rui" , "Rob Herring" , "Krzysztof Kozlowski" , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org >>>>>>> 抄送: zhanghongchen >>>>>>> 主题: Re: [PATCH v2 2/3] dt-bindings: thermal: Convert loongson2 to json-schema >>>>>>> >>>>>>> On 21/09/2022 03:56, Yinbo Zhu wrote: >>>>>>>> Convert the loongson2 thermal binding to DT schema format using >>>>>>>> json-schema. >>>>>>> Incorrect subject and incorrect commit msg. There is no conversion here. >>>>>> Our soc architecture is the loongson2 series, so we will modify it accordingly. >>>>> How the soc architecture is related to my comment that you do not >>>>> perform conversion? >>>> I got it, and I will aad a conversion. >>>>>>>> Signed-off-by: Yinbo Zhu >>>>>>>> --- >>>>>>>> Change in v2: >>>>>>>> 1. Add description and type about the "id". >>>>>>>> 2. Make the filename was based on compatible. >>>>>>>> >>>>>>>> .../bindings/thermal/loongson2-thermal.yaml | 52 +++++++++++++++++++ >>>>>>>> 1 file changed, 52 insertions(+) >>>>>>>> create mode 100644 Documentation/devicetree/bindings/thermal/loongson2-thermal.yaml >>>>>>>> >>>>>>>> diff --git a/Documentation/devicetree/bindings/thermal/loongson2-thermal.yaml b/Documentation/devicetree/bindings/thermal/loongson2-thermal.yaml >>>>>>>> new file mode 100644 >>>>>>>> index 000000000000..2994ae3a56aa >>>>>>>> --- /dev/null >>>>>>>> +++ b/Documentation/devicetree/bindings/thermal/loongson2-thermal.yaml >>>>>>> >>>>>>> No improvements here. You ignore my comments, so I am going to NAK it. >>>>>> I don't get your point, that dts compatible is "loongson,loongson2-thermal", so this driver file name is named >>>>>> loongson2-thermal that according what you said about "Filename based on compatible." >>>>>> If what I understand is not what you expect, please tell me how to modify it. >>>>> >>>>> Filename must match the compatible, so: loongson,loongson2-thermal.yaml >>>> I got it, and I will add a conversion. >>>>>>> >>>>>>>> @@ -0,0 +1,52 @@ >>>>>>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >>>>>>>> +%YAML 1.2 >>>>>>>> +--- >>>>>>>> +$id: http://devicetree.org/schemas/thermal/loongson2-thermal.yaml# >>>>>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>>>>>>> + >>>>>>>> +title: Thermal sensors on loongson2 SoCs >>>>>>>> + >>>>>>>> +maintainers: >>>>>>>> + - zhanghongchen >>>>>>>> + - Yinbo Zhu >>>>>>>> + >>>>>>>> +properties: >>>>>>>> + compatible: >>>>>>>> + const: loongson,loongson2-thermal >>>>>>>> + >>>>>>>> + reg: >>>>>>>> + maxItems: 1 >>>>>>>> + >>>>>>>> + id: >>>>>>>> + $ref: '//schemas/types.yaml#/definitions/uint32' >>>>>>> No improvements here, so let me be specific - you need to really justify >>>>>>> such property or it cannot go to schema. >>>>>> The loongson2_thermal.c driver need parse this "id" property. >>>>> This is not reason to add properties to DT. DT describes the hardware, >>>>> not driver behavior. >>>>> >>>>> Why hardware needs arbitrary, additional addressing number instead of >>>>> standard unit address? >>>> The loongson2 series soc supports up to four sensors, but the 2K1000 has only one sensor, so the ID must be 0. >>>> For the 2K1000, in order to distinguish the differences between different hardware in the Loongson2 SoC series, >>>> the ID is added to the dts >>> Differences in SoCs is what 'compatible' is for. If 'loongson2' is not a >>> specific SoC, then your compatible string is not specific enough. >> If other loongson2 platforms are different from the thermal sensor, I will add compatible >> "loongson,loongson2-thermal-xxx", please you note. > No, this compatible looks wrong then. What is your SoC model number? You > called loongson2 a "series", so that's not appropriate. Compatible > should be specific. okay, I got it. I will add this change in v4. > >>>>>>>> + description: | >>>>>>>> + Specify the thermal sensor id. >>>>>>>> + minimum: 0 >>>>>>>> + maximum: 3 >>>>>>>> + >>>>>>>> + interrupts: >>>>>>>> + maxItems: 1 >>>>>>>> + >>>>>>>> + "#thermal-sensor-cells": >>>>>>>> + const: 1 >>> If one SoC only has 1 sensor, then this could be 0. However, you don't >>> have to do that, but it's another way to distinguish differences. >> okay ,I got it. >>>>>>>> + >>>>>>>> +required: >>>>>>>> + - compatible >>>>>>>> + - reg >>>>>>>> + - id >>>>>>>> + - interrupt-parent >>>>>>> Why? >>>>>> The interrupts of our dts do not specify an interrupt parent, >>>>>> eg. interrupts = <7 IRQ_TYPE_LEVEL_LOW> >>>>>> so we need to add an interrupt parent property. >>>>> You can add but I am asking why is it required? >>>> Since there is more than one interrupt controller in the Loongson2 series soc, that need to specify the interrupt >>>> controller in the dts, that is, the interrupt parent. If different interrupt parents are used in dts, the interrupt >>>> numbers are different. >>> It is perfectly valid for the 'interrupt-parent' to be in *any* parent >>> node. So it is never required by any binding. >> I don't get your meaning, You mean I can add it in the dts, but I don't need to add it in the binding file, right? > You should not add it to the binding because it is not related to the > device itself. okay, I got it. > >>> Rob >> >> 本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。 >> This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it. > Don't include such footers. We cannot talk over confidential emails and > you clearly state that here. > > Best regards, > Krzysztof sorry, I will remove it. TKs, Yinbo Zhu