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 78E6FC3DA4A for ; Wed, 14 Aug 2024 14:27:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Et3EYwF2KfO+XlhYV3jcs5A3c5BPADGkr0DKGFMKvVs=; b=cliHi7p8dsrnvyc9l9bfKxf5cP lyx8n9Fyon6PzU5+n8XHsFpxz5stQSiNu4P+MgQKb8WBFKa6AWxQ+6+S/YmCVUBj32upL3Z8bY0/B hDKdH5pLAS2QTJrL61ttn8zp6Uq2gDYsbrwVLrz2Elq4/8++uWbV5v/ExY1wfFLOCOmtAdV8BMS2e c20jDlzI4OukqsjL/t//Xjxqtb8X5j3pikL+awwVaQGtlAVVnH9dWhtG9H+r8xZ7RGKwnGGVOUGQ9 orvmzxWuNOjGG00OyQf793H/7VWFZprnBVhV5SUC7s8InutLooYA/e8Ovtez0F/J0sxY+TeLqjeQD P/Ytc88w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1seEyL-00000007Glc-2RYq; Wed, 14 Aug 2024 14:27:33 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1seExh-00000007GcO-3P3v for linux-arm-kernel@lists.infradead.org; Wed, 14 Aug 2024 14:26:55 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id C1368CE1957; Wed, 14 Aug 2024 14:26:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 966F2C116B1; Wed, 14 Aug 2024 14:26:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1723645610; bh=DSAXxI8CR5eMEBxy+K143NKZS+eXuAmJNkaIp6iTpak=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=s+QEBhPUfwPxsH5kqHwQP+c3jeoQ0DFCSv6RAy0k2N87KrP7r1HWTVDTdAbW/vMEz 11Upjdov2H6DNPob7XvZIvEn4kN1opBXY2Sk6TH9iOGiKnm4uz8S+ummtAcvn+ZEBe RccUx0oDMuqMKALdzWbRqsNLTh8Hh3adCP7CRVRETGxvfFOfwAOFPhPKN2JRYoPYoZ +s/Fvhss/xaRd4qxSDZekjzNT8Ux6cctygVqKlg/EGyVf9+2EPvV/40qXOSw5a22cm RZmxSKLik1rxjT89HErWOHHXKEFvn7XGMR/R4yjloxNMh50kPLM1B/vfUvmDfGLE+n f9AvcZnNtQ7lQ== Date: Wed, 14 Aug 2024 15:26:45 +0100 From: Conor Dooley To: Jan Kiszka Cc: Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Bao Cheng Su , Diogo Ivo Subject: Re: [PATCH v3 2/3] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Message-ID: <20240814-passable-phrasing-7e78fce590f5@spud> References: <20240813-outrank-mumble-8dddbfc68586@spud> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6hKkgKvhDyD9KJ+A" Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240814_072654_248292_5219607A X-CRM114-Status: GOOD ( 22.61 ) 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --6hKkgKvhDyD9KJ+A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 14, 2024 at 06:49:39AM +0200, Jan Kiszka wrote: > On 13.08.24 17:40, Conor Dooley wrote: > > On Tue, Aug 13, 2024 at 08:04:59AM +0200, Jan Kiszka wrote: > >> From: Jan Kiszka > >> > >> Expand bindings to cover both the MCU and the main usage of the AM654 > >> system controller. > >> > >> Signed-off-by: Jan Kiszka > >> --- > >> .../soc/ti/ti,am654-system-controller.yaml | 25 +++++++++++++++++++ > >> 1 file changed, 25 insertions(+) > >> > >> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-= controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-= controller.yaml > >> index e79803e586ca..5a689ec3c5c9 100644 > >> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-control= ler.yaml > >> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-control= ler.yaml > >> @@ -29,11 +29,36 @@ properties: > >> =20 > >> ranges: true > >> =20 > >> + mux-controller: > >> + type: object > >> + ref: /schemas/mux/reg-mux.yaml# > >> + description: > >> + This is the SERDES lane control mux. > >> + > >> patternProperties: > >> "^phy@[0-9a-f]+$": > >> type: object > >> $ref: /schemas/phy/ti,phy-gmii-sel.yaml# > >> =20 > >> + "^clock@[0-9a-f]+$": > >=20 > > Could you explain to me why these are all patternProperties? Why are the > > addresses of these things not fixed for an am654? > >=20 >=20 > I could indeed spell out dss-oldi-io-ctrl@41e0 and > clock-controller@4140, and their addresses are likely fixed, indeed. But > there are also clock@4080 and clock@4090 - should I duplicate their > object descriptions while moving them to the regular properties? If you're going to itemise the 3 clocks, I think you should mention what's different about each of them. Otherwise, if they're all identical, leave them as a patternProperty. --6hKkgKvhDyD9KJ+A Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZry+pQAKCRB4tDGHoIJi 0l1bAQDFrc3ssqpzwfxRezLS45vOGDjY/enN3BWQZI2UUS1vAQEAq/5yTSLl7M3i 9lIfFZiKIjai97JDqtk5WtzakCI6OA8= =OoWi -----END PGP SIGNATURE----- --6hKkgKvhDyD9KJ+A--