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 78C7AC7EE2D for ; Wed, 1 Mar 2023 03:41:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229906AbjCADlE (ORCPT ); Tue, 28 Feb 2023 22:41:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43084 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229530AbjCADlC (ORCPT ); Tue, 28 Feb 2023 22:41:02 -0500 Received: from ex01.ufhost.com (ex01.ufhost.com [61.152.239.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC2A0149A4; Tue, 28 Feb 2023 19:40:57 -0800 (PST) Received: from EXMBX165.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX165", Issuer "EXMBX165" (not verified)) by ex01.ufhost.com (Postfix) with ESMTP id E511C24E21E; Wed, 1 Mar 2023 11:40:41 +0800 (CST) Received: from EXMBX061.cuchost.com (172.16.6.61) by EXMBX165.cuchost.com (172.16.6.75) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Wed, 1 Mar 2023 11:40:41 +0800 Received: from [192.168.125.128] (113.72.145.171) by EXMBX061.cuchost.com (172.16.6.61) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Wed, 1 Mar 2023 11:40:40 +0800 Message-ID: <8b070b58-a031-5ff5-ea69-08bb750442cb@starfivetech.com> Date: Wed, 1 Mar 2023 11:40:56 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v3 2/2] drivers: watchdog: Add StarFive Watchdog driver Content-Language: en-US To: Emil Renner Berthing , Guenter Roeck , Conor Dooley , "Krzysztof Kozlowski" CC: , , , Wim Van Sebroeck , Krzysztof Kozlowski , Rob Herring , Paul Walmsley , "Palmer Dabbelt" , Albert Ou , "Philipp Zabel" , Samin Guo , , Conor Dooley References: <20230220081926.267695-1-xingyu.wu@starfivetech.com> <20230220081926.267695-3-xingyu.wu@starfivetech.com> <0ffb02d2-0bbd-fd0d-b0f6-cb5605570050@starfivetech.com> <545c23f3-1d68-2bff-89d9-584e3ca31044@linaro.org> From: Xingyu Wu In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [113.72.145.171] X-ClientProxiedBy: EXCAS064.cuchost.com (172.16.6.24) To EXMBX061.cuchost.com (172.16.6.61) X-YovoleRuleAgent: yovoleflag Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023/2/28 23:32, Emil Renner Berthing wrote: > On Tue, 28 Feb 2023 at 16:10, Guenter Roeck wrote: >> On 2/28/23 05:16, Xingyu Wu wrote: >> > On 2023/2/28 19:11, Conor Dooley wrote: >> >> On Tue, Feb 28, 2023 at 11:57:58AM +0100, Krzysztof Kozlowski wrote: >> >>> On 28/02/2023 11:51, Conor Dooley wrote: >> >>>> On Tue, Feb 28, 2023 at 11:36:49AM +0100, Emil Renner Berthing wrote: >> >>>>> On Tue, 28 Feb 2023 at 10:44, Xingyu Wu wrote: >> >>>>>> On 2023/2/26 22:14, Emil Renner Berthing wrote: >> >>>>>>> On Mon, 20 Feb 2023 at 09:21, Xingyu Wu wrote: >> >>>> >> >>>>>> So the dt-bingdings need to rename, and which one could be better, >> >>>>>> 'starfive,jh71x0-wdt.yaml' or 'starfive,jh-wdt.yaml'? >> >>>>> >> >>>>> Sure, starfive,jh71x0-wdt.yaml sounds good to me. >> >>>> >> >>>> I feel like a common comment I see from the dt folks is to not put >> >>>> wildcards in filenames & just pick the first compatible. >> >>>> I could very well be wrong on that front though... >> >>> >> >>> First compatible is a bit better, unless you are sure this will cover >> >>> all such compatibles now and in the future. For many bindings the >> >>> family/wildcards were fine in filename. >> >> >> >> Ahh cool, good to know what the specific policy is - thanks! >> > >> > If this watchdog driver is improved to also support JH7100 in next patch, >> > it seems more reasonable to rename the dt-bingdings to 'starfive,jh71x0-wdt.yaml'. >> >> >> Up to the devicetree maintainers to decide, but I for my part never accept >> wildcards in file names. You can not guarantee that all of jh71[0-9]0 will >> be supported by this set of bindings. On top of that, when / if you add >> support for anything outside that range (say, jh7200 or jh8100 or jh7101 >> or whatever) you'd have an even worse problem. Are you then going to suggest >> renaming the file to jhxxxx-wdt ? Or one digit at a time ? > > Makes sense to me, in which case this should be called > starfive,jh7100-wdt since that's the first SoC to feature this > watchdog and will hopefully be supported in the next version of this > patchset. > Thanks for your suggestions. I will use starfive,jh7100-wdt and improve this driver to support 7100 in the next patchset. Best regards, Xingyu Wu