Message ID | 20230530005337.3687938-1-chris.packham@alliedtelesis.co.nz |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp1857229vqr; Mon, 29 May 2023 17:59:44 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6+RwqSAanmIonVv5hO4XzlpfIoNCv7N7f7FSFzhf4Ftxj/j6+mFQMNUsrOGB1YYl6GX+1d X-Received: by 2002:a17:902:da83:b0:1ad:d95d:ca9c with SMTP id j3-20020a170902da8300b001add95dca9cmr823833plx.15.1685408384346; Mon, 29 May 2023 17:59:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685408384; cv=none; d=google.com; s=arc-20160816; b=Ga7NwgCQ1FbGExMALlcn5cMo9fYFu8qxhyWvlim+ALg9ZCc/XZ/bxCkb5KvslKo0Sa +Ag80HXETvq1mL7rZX64VUj0xuozNuI0h+RuY5pOuTl37Z4bKorIaZ2IvqvYAzhCdG1Z S2b9T7J1+BXw2vZ4DckBP0/u8j8+ZCcYaGmVCAl2XQQB7lA6iTEOlx58saP+6BoCDunT NHCpS881UfnxziAmeQwL7Wdd8/feaBuuhsDfQZcZR/HEfsD0Vmax1850H1BU9t2IVED/ OISLkgTgoTHjhlaB/W3vVTevMdoyblNQKDHzUNrfFGTRVzwUl7sb9jV7aDyStnwKiJEV BTFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=9oONG5DFPFlhzS1QB858urQ+CpfCihmaDd33W3cYZy8=; b=QzPdLH/Jlnqgq3CwAAFzCoLctLOeVw23/Nrl7fiA8MjekifcVGru6FxdJGCq1Wn/LH R8U9xVDv7biH+FNiIxbDztrhFHwx7vuaVVfDy5xiVh4lzUD2tJik7CxBTXme9l+cxgJu JqqlMfCzXr2/eyqhbsIy+7CH2VPBdWMTp/nDnTwbWWasjL+lTmJzEhgi7zZ5Z4Rel2Us kdZEbmPCVakiWjjbVA9Iz42CVnGkXZ9jAJI7Fj9LFS8hDmNyNnyyanhvukj4Fn5r94Xp rI8FiSCn/cd9wy3c15WcVFmiQ1HyJxPeXEEfxT8mYgOO0G01oHorD6wQNu5Hpkmd1x8q lSiA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alliedtelesis.co.nz header.s=mail181024 header.b=e76VX0Oa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=REJECT dis=NONE) header.from=alliedtelesis.co.nz Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q12-20020a170902dacc00b001afbb27f554si3044324plx.623.2023.05.29.17.59.29; Mon, 29 May 2023 17:59:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@alliedtelesis.co.nz header.s=mail181024 header.b=e76VX0Oa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=REJECT dis=NONE) header.from=alliedtelesis.co.nz Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229478AbjE3Axy (ORCPT <rfc822;callmefire3@gmail.com> + 99 others); Mon, 29 May 2023 20:53:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51410 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229571AbjE3Axu (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 29 May 2023 20:53:50 -0400 Received: from gate2.alliedtelesis.co.nz (gate2.alliedtelesis.co.nz [202.36.163.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2092BDB for <linux-kernel@vger.kernel.org>; Mon, 29 May 2023 17:53:46 -0700 (PDT) Received: from svr-chch-seg1.atlnz.lc (mmarshal3.atlnz.lc [10.32.18.43]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by gate2.alliedtelesis.co.nz (Postfix) with ESMTPS id 7073C2C0274; Tue, 30 May 2023 12:53:44 +1200 (NZST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alliedtelesis.co.nz; s=mail181024; t=1685408024; bh=9oONG5DFPFlhzS1QB858urQ+CpfCihmaDd33W3cYZy8=; h=From:To:Cc:Subject:Date:From; b=e76VX0Oa5F2rjWhxJ9xKbie3DpqXYr0+taEfAv0B2s07Wo5aFmXkUSZPaE0nVwwJ5 FAwm2qYgqW3AmS4RjJi5+178eyhPe2b6wtOCEPr3LMQdRl7WkrILIvmpcgCZGZVzy8 csNWT0X9tPTiHAkXnE/GcZqoFoO29e3jMxIFQd7ycMjwqpYZpRO1pflC9Bz3vEjt+m we/wbwzlUSgnb+rHHn6pv138f1zgDX8HGF8S3crc/C0t1gs89mP1XzimiSbBAW/t+z aO31k8XI3HozoiurgLKxBn+NA2Zf6dbxx/jcJOllm0aO2H5PqPE+xVx6nIqOMdL25q 9M9g+iGBo7sDQ== Received: from pat.atlnz.lc (Not Verified[10.32.16.33]) by svr-chch-seg1.atlnz.lc with Trustwave SEG (v8,2,6,11305) id <B647549180000>; Tue, 30 May 2023 12:53:44 +1200 Received: from chrisp-dl.ws.atlnz.lc (chrisp-dl.ws.atlnz.lc [10.33.22.30]) by pat.atlnz.lc (Postfix) with ESMTP id 3AAD813EE41; Tue, 30 May 2023 12:53:44 +1200 (NZST) Received: by chrisp-dl.ws.atlnz.lc (Postfix, from userid 1030) id 38E2E283D16; Tue, 30 May 2023 12:53:44 +1200 (NZST) From: Chris Packham <chris.packham@alliedtelesis.co.nz> To: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, andrew@lunn.ch, gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com, vadym.kochan@plvision.eu Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, enachman@marvell.com, Chris Packham <chris.packham@alliedtelesis.co.nz> Subject: [PATCH v6 0/2] dt-bindings: mtd: marvell-nand: Add YAML scheme Date: Tue, 30 May 2023 12:53:35 +1200 Message-Id: <20230530005337.3687938-1-chris.packham@alliedtelesis.co.nz> X-Mailer: git-send-email 2.40.1 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-SEG-SpamProfiler-Analysis: v=2.3 cv=cLieTWWN c=1 sm=1 tr=0 a=KLBiSEs5mFS1a/PbTCJxuA==:117 a=P0xRbXHiH_UA:10 a=YqPRQZ2WnNP4KUIKbxQA:9 X-SEG-SpamProfiler-Score: 0 x-atlnz-ls: pat X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1767278781880007853?= X-GMAIL-MSGID: =?utf-8?q?1767278781880007853?= |
Series |
dt-bindings: mtd: marvell-nand: Add YAML scheme
|
|
Message
Chris Packham
May 30, 2023, 12:53 a.m. UTC
Add YAML scheme for the Marvell's NAND controller to validate it's DT bindings. Old txt file is deleted, not included the compatibles and properties which were marked as deprecated. Also fix node name in cp11x DTSI acording to nand-controller.yaml I've picked up this series to hopefully get it over the line. I think I've addressed all the feedback from the last round of review. Vadym Kochan (2): dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme arm64: dts: marvell: cp11x: Fix nand_controller node name according to YAML .../bindings/mtd/marvell,nand-controller.yaml | 190 ++++++++++++++++++ .../devicetree/bindings/mtd/marvell-nand.txt | 126 ------------ MAINTAINERS | 1 - arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 2 +- 4 files changed, 191 insertions(+), 128 deletions(-) create mode 100644 Documentation/devicetree/bindings/mtd/marvell,nand-controller.yaml delete mode 100644 Documentation/devicetree/bindings/mtd/marvell-nand.txt
Comments
Chris Packham <chris.packham@alliedtelesis.co.nz> writes: > Add YAML scheme for the Marvell's NAND controller > to validate it's DT bindings. Old txt file is deleted, > not included the compatibles and properties which were marked as > deprecated. > > Also fix node name in cp11x DTSI acording to nand-controller.yaml > > I've picked up this series to hopefully get it over the line. I think I've > addressed all the feedback from the last round of review. > > Vadym Kochan (2): > dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme > arm64: dts: marvell: cp11x: Fix nand_controller node name according to > YAML Both patch applied on mvebu/dt64 However if the first patch should be merged through another tree, let me know. Thanks, Gregory > > .../bindings/mtd/marvell,nand-controller.yaml | 190 ++++++++++++++++++ > .../devicetree/bindings/mtd/marvell-nand.txt | 126 ------------ > MAINTAINERS | 1 - > arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 2 +- > 4 files changed, 191 insertions(+), 128 deletions(-) > create mode 100644 Documentation/devicetree/bindings/mtd/marvell,nand-controller.yaml > delete mode 100644 Documentation/devicetree/bindings/mtd/marvell-nand.txt > > -- > 2.40.1 >
Gregory CLEMENT <gregory.clement@bootlin.com> writes: > Chris Packham <chris.packham@alliedtelesis.co.nz> writes: > >> Add YAML scheme for the Marvell's NAND controller >> to validate it's DT bindings. Old txt file is deleted, >> not included the compatibles and properties which were marked as >> deprecated. >> >> Also fix node name in cp11x DTSI acording to nand-controller.yaml >> >> I've picked up this series to hopefully get it over the line. I think I've >> addressed all the feedback from the last round of review. >> >> Vadym Kochan (2): >> dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme >> arm64: dts: marvell: cp11x: Fix nand_controller node name according to >> YAML > > > Both patch applied on mvebu/dt64 > > However if the first patch should be merged through another tree, let me > know. Finally I removed these both patches, I missed the version 9! I applied the 2 patches for the dts files from v9. Thanks, Gregory > > >> >> .../bindings/mtd/marvell,nand-controller.yaml | 190 ++++++++++++++++++ >> .../devicetree/bindings/mtd/marvell-nand.txt | 126 ------------ >> MAINTAINERS | 1 - >> arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 2 +- >> 4 files changed, 191 insertions(+), 128 deletions(-) >> create mode 100644 Documentation/devicetree/bindings/mtd/marvell,nand-controller.yaml >> delete mode 100644 Documentation/devicetree/bindings/mtd/marvell-nand.txt >> >> -- >> 2.40.1 >> > > -- > Gregory Clement, Bootlin > Embedded Linux and Kernel engineering > http://bootlin.com
On 16/06/23 23:58, Gregory CLEMENT wrote: > Gregory CLEMENT <gregory.clement@bootlin.com> writes: > >> Chris Packham <chris.packham@alliedtelesis.co.nz> writes: >> >>> Add YAML scheme for the Marvell's NAND controller >>> to validate it's DT bindings. Old txt file is deleted, >>> not included the compatibles and properties which were marked as >>> deprecated. >>> >>> Also fix node name in cp11x DTSI acording to nand-controller.yaml >>> >>> I've picked up this series to hopefully get it over the line. I think I've >>> addressed all the feedback from the last round of review. >>> >>> Vadym Kochan (2): >>> dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme >>> arm64: dts: marvell: cp11x: Fix nand_controller node name according to >>> YAML >> >> Both patch applied on mvebu/dt64 >> >> However if the first patch should be merged through another tree, let me >> know. > Finally I removed these both patches, I missed the version 9! > > I applied the 2 patches for the dts files from v9. > > Thanks, > > Gregory Thanks and sorry for the confusion. There's a v10 on the way but I can drop out the dts changes from that now. >> >>> .../bindings/mtd/marvell,nand-controller.yaml | 190 ++++++++++++++++++ >>> .../devicetree/bindings/mtd/marvell-nand.txt | 126 ------------ >>> MAINTAINERS | 1 - >>> arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 2 +- >>> 4 files changed, 191 insertions(+), 128 deletions(-) >>> create mode 100644 Documentation/devicetree/bindings/mtd/marvell,nand-controller.yaml >>> delete mode 100644 Documentation/devicetree/bindings/mtd/marvell-nand.txt >>> >>> -- >>> 2.40.1 >>> >> -- >> Gregory Clement, Bootlin >> Embedded Linux and Kernel engineering >> http://scanmail.trustwave.com/?c=20988&d=0c6M5H8PBagWXDuSKsjbXpd1zLX-HHHRk3xSZOdFDw&u=http%3a%2f%2fbootlin%2ecom