Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1271511pxj; Fri, 18 Jun 2021 03:31:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwNDNvM+c74PrKWPKwIDXgD9ajKh2xjchdmXGkXxtggTldzjDVUjg1S368eU03HhkBFBDZO X-Received: by 2002:a05:6402:1153:: with SMTP id g19mr3879264edw.179.1624012287926; Fri, 18 Jun 2021 03:31:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624012287; cv=none; d=google.com; s=arc-20160816; b=wKUu3/EeqwUDtv+OFYEXJA/ENLvxDAD2Ktce+U+X8ty0KkaauQRRfjSoerGKLxr1DN hP5EwH2KvhifSRCWy8CpbA1R1YA94tJgTGSCVn+rQdLg2G0SJWZewN3fhhLYpPkfiXgM +TUyNU8HuoWOLAZCypwjnDkVL4Cylz/PEjfowriyY1qhKhnMugCsWK0PN0hZGxbyDHJE guUYpOOOAmKmPGECTyzk3Asybf2Pc376M9spOmXNPaoSDfxZ7LIsjlP0pUjW32uqqMVM GsZ8i0fik3jtw+KNcqao8WuXXHAU9UVy5/FFH1c2aUD3vABcbge3DPcgCOs9zDkLtQtD +pDw== 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 :references:in-reply-to:message-id:date:subject:cc:to:from; bh=nOXLrEPOZV+kGZd3TsYS9w2GJ65+WvSFJcQx44g04r0=; b=cP+PtwTAiMj2pSbCjp6NzmGaWnkKI1w+RbfUXy8/OjLJToNtMPx6VLzopIWmHv5rSH zIo2GJpBL/C3GtT0jxI5xXzWrAJ+DZ9W/l9k8Y+8JKTyoFyL5UD/72QklkJFKfePpjOI IQ/KxwH9FkpB2aLyBO3AZpvvFo9kos5IPtnsWPiaCnH+vIkK54bBTqnU8dafIPW1+ikH /VQdGLZpmJlx02d+UQsh/CTn8fvgypXk9uXNdbWSh6v58J17gjo8nzRXq+9zkG6I3gF1 a68DQh8U6gMS199yVXu25BUhuh08y7l/7FC/odWBdeU8VX3ut2b9zrdbBKLl33/ktmbZ EnOQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id rv24si1976856ejb.690.2021.06.18.03.30.53; Fri, 18 Jun 2021 03:31:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232253AbhFRHEf (ORCPT + 99 others); Fri, 18 Jun 2021 03:04:35 -0400 Received: from gloria.sntech.de ([185.11.138.130]:41946 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231826AbhFRHEe (ORCPT ); Fri, 18 Jun 2021 03:04:34 -0400 Received: from ip5f5aa64a.dynamic.kabel-deutschland.de ([95.90.166.74] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lu8Vs-00006s-P5; Fri, 18 Jun 2021 09:02:00 +0200 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: cl , "jay.xu@rock-chips.com" Cc: robh+dt , jagan , wens , uwe , mail , Johan Jonker , linux-arm-kernel , "open list:ARM/Rockchip SoC..." , Linux Kernel Mailing List , jensenhuang , michael , cnsztl , devicetree , "ulf. hansson" , linux-mmc , gregkh , linux-serial , linux-i2c , =?utf-8?B?5p6X5rabKOW6leWxguW5s+WPsCk=?= , =?utf-8?B?5ZC06L6+6LaF?= , zhangqing , Tao Huang , cl , wim , linux , jamie , linux-watchdog , maz Subject: Re: [RESEND PATCH v4 06/10] dt-bindings: gpio: change items restriction of clock for rockchip,gpio-bank Date: Fri, 18 Jun 2021 09:01:59 +0200 Message-ID: <3493815.vrqWZg68TM@diego> In-Reply-To: <2021061814414460293612@rock-chips.com> References: <20210429081151.17558-1-cl@rock-chips.com> <5026524.44csPzL39Z@phil> <2021061814414460293612@rock-chips.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jay, Am Freitag, 18. Juni 2021, 08:41:45 CEST schrieb jay.xu@rock-chips.com: > Hi Heiko > > -------------- > jay.xu@rock-chips.com > >Hi, > > > >Am Donnerstag, 13. Mai 2021, 08:46:06 CEST schrieb cl@rock-chips.com: > >> From: Liang Chen > >> > >> The clock property need 2 items on some rockchip chips. > >> > >> Signed-off-by: Liang Chen > > > >this patch should definitly move over to Jianquns gpio driver series, > >as it introduces the usage of these new clocks. > > > >Also while the single-clock variant definitly doesn't need it, > >I think we may want clock-names "apb_pclk", "debounce-ref" for the > >2-clock variants? > > > Okay, I think it's very good idea, > but is it possible to post the reg-name patch after these dts serial and gpio serial patches ? You're already creating a new binding when changing the max-items. So when we change that again later, in theory you'd need to support both cases (with and without clock-names) So I'd really prefer to get the binding right the first time and identifying multiple clocks by clock-names instead of an implicit ordering is way better in the long run as well. Heiko > > > > >Heiko > > > >> --- > >> Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml | 5 ++++- > >> 1 file changed, 4 insertions(+), 1 deletion(-) > >> > >> diff --git a/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml b/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml > >> index d993e00..0d62c28 100644 > >> --- a/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml > >> +++ b/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml > >> @@ -22,7 +22,10 @@ properties: > >> maxItems: 1 > >> > >> clocks: > >> - maxItems: 1 > >> + minItems: 1 > >> + items: > >> + - description: APB interface clock source > >> + - description: GPIO debounce reference clock source > >> > >> gpio-controller: true > >> > >> > > > > > > > > > > > > > > >