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 B3CA2D2A537 for ; Wed, 16 Oct 2024 17:28:23 +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=PNrB6mffeOMJdrN9BgSsAYLj95/yCQj648hJWBnuWek=; b=r0ElqqrGTr+ySrL4l+/xPeUUoW QMW4zqVgStL+KvSlybqMMiUS492oU5ri69yDz1HQKWBLAmToddjKGZLUcDk2x2SglRHa1PJB4vAY6 wumfqeZfBMmhvnKS9avLhOIaV7ueB7ymO5JWMFXkNxqutVblWl9CSf4PMDgAyByH651QvN+v+BIzk /2/ggb52u+zGmproPJ1/hUPrRe4cusIFhtKbEPPRnUOCAKIAhymgPKEZNlRkp0B1Af/WsvYha03TP rtmfUia8cq/sYWnxJTTuUfcOlBR11EHesh1AhEK+byJp6R9ubNaJg/zTbVRN3nfN5esJGwxiiv+ZD QIfzdjXw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1t17oj-0000000CY1U-44ls; Wed, 16 Oct 2024 17:28:13 +0000 Received: from nyc.source.kernel.org ([2604:1380:45d1:ec00::3]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1t17nI-0000000CXsf-40Ga for linux-arm-kernel@lists.infradead.org; Wed, 16 Oct 2024 17:26:46 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id A73F1A410D3; Wed, 16 Oct 2024 17:26:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2E384C4CEC5; Wed, 16 Oct 2024 17:26:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1729099603; bh=hVlu1hU3ASIiy3+g6KLNJAuWniSogilK3Nzm74AlCoE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pXKGxwgah5bwH0E7RiU/V1xffhKnQabV9zZ5cSasYKnygfFLqWf0q0crRw8N1EwAr yM5F/+zzdmq4YIqfMASGO/QBFMSoiRelopd0vrZgodEMzhfVp/qtT9aT+1Y/+TulJJ KyQ/IDhCNSk7xy/dw5VF7o/RnMeVAeKyCxEUxpE74Z89d1WLZaneeu8cmombhLK5Cq +2Ey0DBWr4xLp3DQ/IRSC8NDIbXHeVQhAZveYptNeq3X8DTd8UvjMq2+B29xNlACr8 W1EJkKJITRZM9HtourFnwdvTbsyRms+Q6VOgoBml+9ORgcrIs/jKRg6WhTbYfLkk9F 0FehuVNr9fhTQ== Date: Wed, 16 Oct 2024 12:26:42 -0500 From: Rob Herring To: Marek Vasut Cc: devicetree@vger.kernel.org, Conor Dooley , Dong Aisheng , Fabio Estevam , Jacky Bai , Krzysztof Kozlowski , Linus Walleij , Pengutronix Kernel Team , Sascha Hauer , Shawn Guo , imx@lists.linux.dev, kernel@dh-electronics.com, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org Subject: Re: [PATCH] dt-bindings: pinctrl: fsl,imx6ul-pinctrl: Convert i.MX35/5x/6 to YAML Message-ID: <20241016172642.GA1991636-robh@kernel.org> References: <20241015232107.100771-1-marex@denx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241015232107.100771-1-marex@denx.de> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241016_102645_078447_A4873478 X-CRM114-Status: GOOD ( 12.98 ) 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 On Wed, Oct 16, 2024 at 01:20:51AM +0200, Marek Vasut wrote: > The IOMUXC controller description is almost identical on i.MX35/5x/6 SoCs, > except for the configuration bits which differ across SoCs. Rename the > fsl,imx6ul-pinctrl.yaml to fsl,imx35-pinctrl.yaml, fill in compatible > strings for the other SoCs and fill in the various bits into desciption. > This way, i.MX35/5x/6 series SoCs can all be converted to YAML DT. Remove > the old text DT bindings description. Just a nit, but I prefer 'DT schema' over using 'YAML DT' or just 'YAML'. YAML is just the file format we use and YAML is a lot of things that's not DT schema including other uses/attempts with DT. This generates lots of warnings (patchwork has the output) for pincfg nodes which don't match 'grp$' node name convention. Do we really want to "fix" all of those? We could allow anything, but then we don't enforce anything on new stuff. Or this could be split between new and old platforms. If we decide to fix any old ones, then just have to move them to the "new" schema. Rob