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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 88499C7EE23 for ; Mon, 5 Jun 2023 21:26:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232745AbjFEV0k (ORCPT ); Mon, 5 Jun 2023 17:26:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42240 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229790AbjFEV0i (ORCPT ); Mon, 5 Jun 2023 17:26:38 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 67A36D9; Mon, 5 Jun 2023 14:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=pjkBZVUgc3CiLu0gi0p3NgsM5Xuycekxxtcs51fqFw8=; b=LxF5UxaufA4Sp8u2YbbNXlz7Cy 6Mrb3XFZ3WVTzuZkC/ngcGvAzcJs13Eg/khUwkc5te1pigBfwwVzXm0LzLBYq8x7U6i21YssND6ya 6Joxt8oq5bSsm5+xLTTTHFUqNKkZyGGUUs7OVFx46OvUvIUBP9uGPeW6oQJvRn6Hu1GU=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1q6HiJ-00EwXx-SM; Mon, 05 Jun 2023 23:26:07 +0200 Date: Mon, 5 Jun 2023 23:26:07 +0200 From: Andrew Lunn To: Chris Packham Cc: Krzysztof Kozlowski , "miquel.raynal@bootlin.com" , "richard@nod.at" , "vigneshr@ti.com" , "robh+dt@kernel.org" , "krzysztof.kozlowski+dt@linaro.org" , "conor+dt@kernel.org" , "gregory.clement@bootlin.com" , "sebastian.hesselbarth@gmail.com" , "conor@kernel.org" , "linux-mtd@lists.infradead.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "enachman@marvell.com" , Vadym Kochan Subject: Re: [PATCH v8 3/3] dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme Message-ID: <609c032d-0912-4ef0-b04a-4d40a7d2f0d0@lunn.ch> References: <20230531234923.2307013-1-chris.packham@alliedtelesis.co.nz> <20230531234923.2307013-4-chris.packham@alliedtelesis.co.nz> <785368df-1881-e62e-6172-d902cee814a8@alliedtelesis.co.nz> <4ea0b16e-0cec-00db-c598-e0364a7edef8@alliedtelesis.co.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ea0b16e-0cec-00db-c598-e0364a7edef8@alliedtelesis.co.nz> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Then you are doing something different than all other bindings. > > Not intentionally. I should probably check that the existing bindings > actually work as expected. This binding supports marvell,pxa3xx-nand. That is really really old. So it could well be it works in the kernel, but the YAML does not fully implement what the kernel actually supports. Best practices could of pushed modern day DT to a subset, and YAML only supports that subset of reality. And once you get outside of this subset, you run into trouble. I don't actually know this is the case, but you should keep it in mind. Andrew