From mboxrd@z Thu Jan 1 00:00:00 1970 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0B4E6C25B77 for ; Mon, 20 May 2024 21:20:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=R1PrCqaTpPx0ueSxZhlSR8OCEGMpcCqEnJOh52Xsu94=; b=0EhOKE1UVVlGjI ekTQrMvHXvwz3MB3uS/U9r03IqOIAy3xm+XyxBRg0BK0olYR/Wt8qExY2iMjAoZdZ7UiVGbH4/eiN KhYcFVCIRpZqX2W/6nboNLyROMdLV7BD/Wce17IKdH+90V8w8uglaP1WMX6lVYJtf0fZJr2kIzD/p xCaLHHLOyVT6/weK8peKKMwZTvNVq9q0GBFcmPdgn0wThkI10X+LWHz7wSIlMVgTTxW1P3uA8Qctj XhL30zzj4pjOUFxHON/j6txsgxTImY6Q16WykGsNl37wLytkmChF3q42G/WRGmBSt57qSAN/piSt6 1AmSXdvRHvzm8FrnHzPw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1s9AQp-0000000FZnw-1laL; Mon, 20 May 2024 21:20:31 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1s9AQl-0000000FZmI-42dm; Mon, 20 May 2024 21:20:29 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 1376361F2B; Mon, 20 May 2024 21:20:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8139FC2BD10; Mon, 20 May 2024 21:20:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1716240026; bh=6q4cLeteQnmYBt4L+ImO6U2iWiRK+PBZwIQS3r+LLZA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=bWOl8kw56ZVeviGOGsr0lbv+k+xZE2NAALVSx796jSXun/d+7j1KNYBiJ+vUA1OEf ZQGpZdpKHadB1Mg2GFYGx+uiBNU7m04hMWVL802Lt3e4JD7G1z7jCXDmxGBreOgtt7 qclg7Peh7mOecKxMJyocc/JQaBGChHHBtgRDgeckbKkOPo4xn326QKtKjzKVgyx3Ci v5ll50neonGDnT6+EMyhLewvzL3eXZN7Px0WLszK7SlbA0B9WllUQuugAmRj6XTiw8 X1hyjcj3pydyv68yzY6IUTSquK+17pYqWXlDvEyLL+Obo4SIq7BXvl3WZ5v1u2wHoO yWYMjK9x4PfKg== Date: Mon, 20 May 2024 16:20:25 -0500 From: Rob Herring To: Krzysztof Kozlowski Cc: Lee Jones , Krzysztof Kozlowski , Conor Dooley , Lars Povlsen , Steen Hegelund , Daniel Machon , UNGLinuxDriver@microchip.com, Nishanth Menon , Matthias Brugger , AngeloGioacchino Del Regno , Jiaxun Yang , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH 6/8] dt-bindings: mfd: syscon: Split and enforce documenting MFD children Message-ID: <20240520212025.GA1531862-robh@kernel.org> References: <20240519-dt-bindings-mfd-syscon-split-v1-0-aaf996e2313a@linaro.org> <20240519-dt-bindings-mfd-syscon-split-v1-6-aaf996e2313a@linaro.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240519-dt-bindings-mfd-syscon-split-v1-6-aaf996e2313a@linaro.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240520_142028_132481_0E4F03BF X-CRM114-Status: GOOD ( 24.97 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sun, May 19, 2024 at 08:42:21PM +0200, Krzysztof Kozlowski wrote: > Simple syscon nodes can be documented in common syscon.yaml, however > devices with simple-mfd compatible, thus with some children, should have > their own schema listing these children. Such listing makes the binding > specific, allows better validation (so the incorrect child would not > appear in the simple-mfd node) and actually enforces repeated rule for > simple-mfd devices: > > "simple-mfd" is only for simple devices, where the children do not > depend on the parent. > > Currently the syscon+simple-mfd binding is quite broad and allows > any child or property, thus above rule cannot be enforced. > > Split the syscon.yaml binding into: > 1. Common syscon properties, used potentially by many bindings. > 2. Simple syscon devices (NO simple-mfd!). > > Signed-off-by: Krzysztof Kozlowski > > --- > > Depends on: > 1. https://lore.kernel.org/r/20240510123018.3902184-1-robh@kernel.org > 2. Previous patches in the series. > --- > .../devicetree/bindings/mfd/syscon-common.yaml | 72 +++++++ > Documentation/devicetree/bindings/mfd/syscon.yaml | 212 +++++++++------------ > 2 files changed, 162 insertions(+), 122 deletions(-) > > diff --git a/Documentation/devicetree/bindings/mfd/syscon-common.yaml b/Documentation/devicetree/bindings/mfd/syscon-common.yaml > new file mode 100644 > index 000000000000..c3ff3a7afce3 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/syscon-common.yaml > @@ -0,0 +1,72 @@ > +# SPDX-License-Identifier: GPL-2.0 > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/mfd/syscon-common.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: System Controller Registers R/W Common Properties > + > +description: | > + System controller node represents a register region containing a set > + of miscellaneous registers. The registers are not cohesive enough to > + represent as any specific type of device. The typical use-case is > + for some other node's driver, or platform-specific code, to acquire > + a reference to the syscon node (e.g. by phandle, node path, or > + search using a specific compatible value), interrogate the node (or > + associated OS driver) to determine the location of the registers, > + and access the registers directly. > + > +maintainers: > + - Lee Jones > + > +select: > + properties: > + compatible: > + contains: > + enum: > + - syscon > + > + required: > + - compatible > + > +properties: > + compatible: > + contains: > + const: syscon > + minItems: 2 > + maxItems: 5 # Should be enough > + > + reg: > + maxItems: 1 > + > + reg-io-width: > + description: | > + The size (in bytes) of the IO accesses that should be performed > + on the device. > + enum: [1, 2, 4, 8] > + > +required: > + - compatible > + - reg > + > +allOf: > + - if: > + properties: > + compatible: > + contains: > + const: simple-mfd > + then: > + properties: > + compatible: > + minItems: 3 > + maxItems: 5 > + > +additionalProperties: true > + > +examples: > + - | > + syscon: syscon@1c00000 { > + compatible = "allwinner,sun8i-h3-system-controller", "syscon"; > + reg = <0x01c00000 0x1000>; > + }; > +... > diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml > index b17fa0487178..70e3961bc96f 100644 > --- a/Documentation/devicetree/bindings/mfd/syscon.yaml > +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml > @@ -4,7 +4,7 @@ > $id: http://devicetree.org/schemas/mfd/syscon.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: System Controller Registers R/W > +title: System Controller Devices > > description: | > System controller node represents a register region containing a set > @@ -19,122 +19,99 @@ description: | > maintainers: > - Lee Jones > > -select: > - properties: > - compatible: > - contains: > - enum: > - - syscon > - > - required: > - - compatible > - Removing this is only going to work with v2024.04. The only way it works for older versions is listing all the compatibles here. That's a bit new for us to require it. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel