devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	devicetree@vger.kernel.org,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"Kamal Dasu" <kdasu.kdev@gmail.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	linux-mtd@lists.infradead.org,
	bcm-kernel-feedback-list@broadcom.com,
	"Richard Weinberger" <richard@nod.at>,
	"Brian Norris" <computersforpeace@gmail.com>
Subject: Re: [PATCH V3] dt-bindings: mtd: brcm,brcmnand: convert to the json-schema
Date: Wed, 21 Apr 2021 12:05:09 -0500	[thread overview]
Message-ID: <20210421170509.GA1299408@robh.at.kernel.org> (raw)
In-Reply-To: <20210420212008.13174-1-zajec5@gmail.com>

On Tue, 20 Apr 2021 23:20:08 +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
> 
> This helps validating DTS files.
> 
> Changes that require mentioning:
> 1. Property "clock" was renamed to "clocks"
> 2. Duplicated properties (defined in nand-controller.yaml) were dropped
> 3. Compatible "brcm,nand-bcm63168" was added
> 4. SoC specific "compatible" cases got limited controller versions
> 
> Examples changes:
> 1. Nodes "nand" were renamed to "nand-controller"
> 2. Nodes "nandcs" were renamed to "nand"
> 3. Dropped partitions as they were using old syntax and are well
>    documented elsewhere anyway
> 
> This rewritten binding validates cleanly using the "dt_binding_check".
> Some Linux stored DTS files will require updating to make "dtbs_check"
> happy.
> 
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> V2: Drop example partitions that were using deprecated syntax-thanks Rob
> V3: "SoC specific "compatible" cases got limited controller versions"
>     Thanks Rob for teaching me the items: enum [] trick (no "-")
> ---
>  .../devicetree/bindings/mtd/brcm,brcmnand.txt | 186 --------------
>  .../bindings/mtd/brcm,brcmnand.yaml           | 242 ++++++++++++++++++
>  2 files changed, 242 insertions(+), 186 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
>  create mode 100644 Documentation/devicetree/bindings/mtd/brcm,brcmnand.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-04-21 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 12:33 [PATCH] dt-bindings: mtd: brcm,brcmnand: convert to the json-schema Rafał Miłecki
2021-04-16 19:54 ` [PATCH V2] " Rafał Miłecki
2021-04-20 18:50   ` Rob Herring
2021-04-20 21:20   ` [PATCH V3] " Rafał Miłecki
2021-04-21 17:05     ` Rob Herring [this message]
2021-04-23  2:34     ` Brian Norris
2021-04-23  5:05     ` [PATCH V4] dt-bindings: mtd: brcm, brcmnand: " Rafał Miłecki
2021-05-10 10:02       ` Miquel Raynal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210421170509.GA1299408@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kdasu.kdev@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=rafal@milecki.pl \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    --cc=zajec5@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).