From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fd01.gateway.ufhost.com (fd01.gateway.ufhost.com [61.152.239.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1AC48D0; Wed, 13 Dec 2023 21:18:06 -0800 (PST) Received: from EXMBX166.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX166", Issuer "EXMBX166" (not verified)) by fd01.gateway.ufhost.com (Postfix) with ESMTP id 97AA980A4; Thu, 14 Dec 2023 13:17:58 +0800 (CST) Received: from EXMBX072.cuchost.com (172.16.6.82) by EXMBX166.cuchost.com (172.16.6.76) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 14 Dec 2023 13:17:58 +0800 Received: from localhost.localdomain (202.188.176.82) by EXMBX072.cuchost.com (172.16.6.82) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 14 Dec 2023 13:17:52 +0800 From: Ji Sheng Teoh To: CC: , , , , , , , , , , , Subject: Re: [PATCH v2 1/1] dt-bindings: watchdog: starfive,jh7100-wdt: Add compatible for JH8100 Date: Thu, 14 Dec 2023 13:17:17 +0800 Message-ID: <20231214051717.9795-1-jisheng.teoh@starfivetech.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20231213-rectified-unmindful-4064c852930f@spud> References: <20231213-rectified-unmindful-4064c852930f@spud> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-ClientProxiedBy: EXCAS062.cuchost.com (172.16.6.22) To EXMBX072.cuchost.com (172.16.6.82) X-YovoleRuleAgent: yovoleflag Content-Transfer-Encoding: quoted-printable On Wed, 13 Dec 2023 16:35:39 +0000 Conor Dooley wrote: > On Wed, Dec 13, 2023 at 10:57:59AM +0800, Ji Sheng Teoh wrote: > > On Tue, 12 Dec 2023 16:47:59 +0000 > > Conor Dooley wrote: > > =20 > > > On Tue, Dec 12, 2023 at 04:46:00PM +0000, Conor Dooley wrote: =20 > > > > On Tue, Dec 12, 2023 at 11:17:31AM +0800, Ji Sheng Teoh wrote: > > > > =20 > > > > > Add "starfive,jh8100-wdt" compatible string for StarFive's > > > > > JH8100 watchdog. > > > > > Since JH8100 watchdog only has 1 reset signal, update binding > > > > > document to support one reset for "starfive,jh8100-wdt" > > > > > compatible. > > > > >=20 > > > > > Signed-off-by: Ley Foon Tan > > > > > Signed-off-by: Ji Sheng Teoh > > > > > --- > > > > > .../devicetree/bindings/watchdog/starfive,jh7100-wdt.yaml > > > > > | 2 ++ 1 file changed, 2 insertions(+) > > > > >=20 > > > > > diff --git > > > > > a/Documentation/devicetree/bindings/watchdog/starfive,jh7100-wd= t.yaml > > > > > b/Documentation/devicetree/bindings/watchdog/starfive,jh7100-wd= t.yaml > > > > > index 68f3f6fd08a6..02572b16ac08 100644 --- > > > > > a/Documentation/devicetree/bindings/watchdog/starfive,jh7100-wd= t.yaml > > > > > +++ > > > > > b/Documentation/devicetree/bindings/watchdog/starfive,jh7100-wd= t.yaml > > > > > @@ -27,6 +27,7 @@ properties: enum: > > > > > - starfive,jh7100-wdt > > > > > - starfive,jh7110-wdt > > > > > + - starfive,jh8100-wdt > > > > > =20 > > > > > reg: > > > > > maxItems: 1 > > > > > @@ -45,6 +46,7 @@ properties: > > > > > - const: core > > > > > =20 > > > > > resets: > > > > > + minItems: 1 > > > > > items: > > > > > - description: APB reset > > > > > - description: Core reset =20 > > > >=20 > > > > This relaxes the constraints for the existing devices, please > > > > add per compatible constraints to avoid doing so. =20 > > > =20 > > Thanks Conor. Just to clarify, are you suggesting to add what was > > done in v1? > > v1: > > https://lore.kernel.org/all/20231209142723.2060196-3-jisheng.teoh@sta= rfivetech.com/ > > =20 >=20 > No, but similar. Add numerical constraints that vary per SoC without > changing the names of the resets on a per-SoC basis.:wq >=20 Sent out v3, hope it addresses the comments. v3: https://lore.kernel.org/all/20231214033056.3953143-2-jisheng.teoh@starfiv= etech.com/