All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Pratyush Yadav <pratyush@kernel.org>,
	Michael Walle <michael@walle.cc>,
	linux-mtd@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 02/17] dt-bindings: mtd: Create a file for raw NAND chip properties
Date: Mon, 19 Jun 2023 08:59:07 +0200	[thread overview]
Message-ID: <20230619085907.70218553@xps-13> (raw)
In-Reply-To: <f7218445-77e7-7429-5d81-ee7380a3e045@kernel.org>

Hi Krzysztof,

krzk@kernel.org wrote on Mon, 19 Jun 2023 08:28:28 +0200:

> On 06/06/2023 19:52, Miquel Raynal wrote:
> > In an effort to constrain as much as we can the existing binding, we
> > want to add "unevaluatedProperties: false" in all the NAND chip
> > descriptions part of NAND controller bindings. But in order to do that
> > properly, we also need to reference a file which contains all the
> > "allowed" properties. Right now this file is nand-chip.yaml but in
> > practice raw NAND controllers may use additional properties in their
> > NAND chip children node. These properties are listed under
> > nand-controller.yaml, which makes the "unevaluatedProperties" checks
> > fail while the description are valid. We need to move these NAND chip
> > related properties into another file, because we do not want to pollute
> > nand-chip.yaml which is also referenced by eg. SPI-NAND devices.
> > 
> > Let's create a raw-nand-chip.yaml file to reference all the properties a
> > raw NAND chip description can contain. The chain of inheritance becomes:
> >   nand-controller.yaml <- raw-nand-chip.yaml
> >   raw-nand-chip.yaml   <- nand-chip.yaml
> >   spi-nand.yaml        <- nand-chip.yaml  
> 
> ...
> 
> > -  The interpretation of these parameters is implementation-defined, so
> > -  not all implementations must support all possible
> > -  combinations. However, implementations are encouraged to further
> > -  specify the value(s) they support.
> > -
> >  properties:
> >    $nodename:
> >      pattern: "^nand-controller(@.*)?"
> > @@ -51,79 +41,8 @@ properties:
> >  
> >  patternProperties:
> >    "^nand@[a-f0-9]$":
> > -    $ref: "nand-chip.yaml#"  
> 
> You work on some old tree, judging by email addresses you CC and by
> this. I would expect here current next, but this is even pre v6.4-rc1!
> Working on something older than current master branch doss not make any
> sense.

This is really based on v6.4-rc1, I think Rob's tooling is applying the
patches against -rc1 so I try to keep the robots happy by picking that
tag as base. I know you are removing the quotes so I went through my
series and dropped them from all the files which now reference
raw-nand-chip.yaml, but of course I missed that one, I am sorry, I will
drop the quotes here as well.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Pratyush Yadav <pratyush@kernel.org>,
	Michael Walle <michael@walle.cc>,
	linux-mtd@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 02/17] dt-bindings: mtd: Create a file for raw NAND chip properties
Date: Mon, 19 Jun 2023 08:59:07 +0200	[thread overview]
Message-ID: <20230619085907.70218553@xps-13> (raw)
In-Reply-To: <f7218445-77e7-7429-5d81-ee7380a3e045@kernel.org>

Hi Krzysztof,

krzk@kernel.org wrote on Mon, 19 Jun 2023 08:28:28 +0200:

> On 06/06/2023 19:52, Miquel Raynal wrote:
> > In an effort to constrain as much as we can the existing binding, we
> > want to add "unevaluatedProperties: false" in all the NAND chip
> > descriptions part of NAND controller bindings. But in order to do that
> > properly, we also need to reference a file which contains all the
> > "allowed" properties. Right now this file is nand-chip.yaml but in
> > practice raw NAND controllers may use additional properties in their
> > NAND chip children node. These properties are listed under
> > nand-controller.yaml, which makes the "unevaluatedProperties" checks
> > fail while the description are valid. We need to move these NAND chip
> > related properties into another file, because we do not want to pollute
> > nand-chip.yaml which is also referenced by eg. SPI-NAND devices.
> > 
> > Let's create a raw-nand-chip.yaml file to reference all the properties a
> > raw NAND chip description can contain. The chain of inheritance becomes:
> >   nand-controller.yaml <- raw-nand-chip.yaml
> >   raw-nand-chip.yaml   <- nand-chip.yaml
> >   spi-nand.yaml        <- nand-chip.yaml  
> 
> ...
> 
> > -  The interpretation of these parameters is implementation-defined, so
> > -  not all implementations must support all possible
> > -  combinations. However, implementations are encouraged to further
> > -  specify the value(s) they support.
> > -
> >  properties:
> >    $nodename:
> >      pattern: "^nand-controller(@.*)?"
> > @@ -51,79 +41,8 @@ properties:
> >  
> >  patternProperties:
> >    "^nand@[a-f0-9]$":
> > -    $ref: "nand-chip.yaml#"  
> 
> You work on some old tree, judging by email addresses you CC and by
> this. I would expect here current next, but this is even pre v6.4-rc1!
> Working on something older than current master branch doss not make any
> sense.

This is really based on v6.4-rc1, I think Rob's tooling is applying the
patches against -rc1 so I try to keep the robots happy by picking that
tag as base. I know you are removing the quotes so I went through my
series and dropped them from all the files which now reference
raw-nand-chip.yaml, but of course I missed that one, I am sorry, I will
drop the quotes here as well.

Thanks,
Miquèl

  reply	other threads:[~2023-06-19  6:59 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 17:52 [PATCH v2 00/17] Prevent NAND chip unevaluated properties Miquel Raynal
2023-06-06 17:52 ` Miquel Raynal
2023-06-06 17:52 ` [PATCH v2 01/17] dt-bindings: mtd: Accept nand related node names Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-19  6:28   ` Krzysztof Kozlowski
2023-06-19  6:28     ` Krzysztof Kozlowski
2023-06-06 17:52 ` [PATCH v2 02/17] dt-bindings: mtd: Create a file for raw NAND chip properties Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-19  6:28   ` Krzysztof Kozlowski
2023-06-19  6:28     ` Krzysztof Kozlowski
2023-06-19  6:59     ` Miquel Raynal [this message]
2023-06-19  6:59       ` Miquel Raynal
2023-06-06 17:52 ` [PATCH v2 03/17] dt-bindings: mtd: Mark nand-ecc-placement deprecated Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-19  6:34   ` Krzysztof Kozlowski
2023-06-19  6:34     ` Krzysztof Kozlowski
2023-06-06 17:52 ` [PATCH v2 04/17] dt-bindings: mtd: Describe nand-ecc-mode Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-19  6:51   ` Krzysztof Kozlowski
2023-06-19  6:51     ` Krzysztof Kozlowski
2023-06-06 17:52 ` [PATCH v2 05/17] dt-bindings: mtd: qcom: Fix a property position Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-19  6:54   ` Krzysztof Kozlowski
2023-06-19  6:54     ` Krzysztof Kozlowski
2023-06-19  7:19     ` Miquel Raynal
2023-06-19  7:19       ` Miquel Raynal
2023-06-06 17:52 ` [PATCH v2 06/17] dt-bindings: mtd: qcom: Prevent NAND chip unevaluated properties Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 22:27   ` Chris Packham
2023-06-06 22:27     ` Chris Packham
2023-06-07  7:53     ` Miquel Raynal
2023-06-07  7:53       ` Miquel Raynal
2023-06-07 20:47       ` Chris Packham
2023-06-07 20:47         ` Chris Packham
2023-06-06 17:52 ` [PATCH v2 07/17] dt-bindings: mtd: ingenic: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-07  9:33     ` Miquel Raynal
2023-06-07  9:33       ` Miquel Raynal
2023-06-08 15:20       ` Rob Herring
2023-06-08 15:20         ` Rob Herring
2023-06-09  8:36         ` Miquel Raynal
2023-06-09  8:36           ` Miquel Raynal
2023-06-06 17:52 ` [PATCH v2 08/17] dt-bindings: mtd: sunxi: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 09/17] dt-bindings: mtd: meson: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 10/17] dt-bindings: mtd: brcmnand: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 11/17] dt-bindings: mtd: denali: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 12/17] dt-bindings: mtd: intel: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 13/17] dt-bindings: mtd: rockchip: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 14/17] dt-bindings: mtd: stm32: " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 17:52 ` [PATCH v2 15/17] dt-bindings: mtd: mediatek: Reference raw-nand-chip.yaml Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 16/17] dt-bindings: mtd: mediatek: Prevent NAND chip unevaluated properties Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-06 18:52   ` Rob Herring
2023-06-06 18:52     ` Rob Herring
2023-06-06 17:52 ` [PATCH v2 17/17] dt-bindings: mtd: ti,am654: Prevent " Miquel Raynal
2023-06-06 17:52   ` Miquel Raynal
2023-06-09 20:51 ` [PATCH v2 00/17] Prevent NAND chip " Rob Herring
2023-06-09 20:51   ` Rob Herring
2023-06-10  9:27 ` Krzysztof Kozlowski
2023-06-10  9:27   ` Krzysztof Kozlowski
2023-06-13 11:43   ` Miquel Raynal
2023-06-13 11:43     ` Miquel Raynal
2023-06-15  8:26     ` Miquel Raynal
2023-06-15  8:26       ` Miquel Raynal
2023-09-27  7:20 ` Maxime Ripard
2023-09-27  7:20   ` Maxime Ripard
2023-09-27 15:35   ` Maxime Ripard
2023-09-27 15:35     ` Maxime Ripard
2023-09-27  7:20 ` Maxime Ripard
2023-09-27  7:20   ` Maxime Ripard
2023-09-27  7:20 ` Maxime Ripard
2023-09-27  7:20   ` Maxime Ripard
2023-09-27  7:21 ` Maxime Ripard
2023-09-27  7:21   ` Maxime Ripard

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=20230619085907.70218553@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.