All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Tudor Ambarus <Tudor.Ambarus@microchip.com>,
	Michal Simek <monstr@monstr.eu>,
	linux-mtd@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	devicetree@vger.kernel.org, Richard Weinberger <richard@nod.at>,
	Naga Sureshkumar Relli <nagasure@xilinx.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v4] dt-binding: mtd: nand: Document the cs-gpios property
Date: Tue, 11 May 2021 11:24:40 -0500	[thread overview]
Message-ID: <20210511162440.GA2227381@robh.at.kernel.org> (raw)
In-Reply-To: <20210510171800.27225-1-miquel.raynal@bootlin.com>

On Mon, 10 May 2021 19:18:00 +0200, Miquel Raynal wrote:
> To reach higher capacities, arrays of chips are now pretty common.
> Unfortunately, most of the controllers have been designed a decade ago
> and did not all anticipate the need for several chip-selects. The new
> cs-gpios property allows to workaround this limitation by adding as many
> GPIO chip-select as needed.
> 
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> 
> Resending only the binding patch of the series, with the following
> changes requested by Rob:
> * Fixed the coherency between cs-gpios and gpios-cs
> * Added maxItems: 8 (this is a good enough value for most of the cases I
>   guess, this can be increased later if needed).
> * Adding maxItems: 8 lead to an error when checking the example,
>   minItems: 8 had to be added as well to the schema to fix it, not sure
>   this was expected or not.
> 
>  .../bindings/mtd/nand-controller.yaml          | 18 +++++++++++++++++-
>  1 file changed, 17 insertions(+), 1 deletion(-)
> 

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

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Tudor Ambarus <Tudor.Ambarus@microchip.com>,
	Michal Simek <monstr@monstr.eu>,
	linux-mtd@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	devicetree@vger.kernel.org, Richard Weinberger <richard@nod.at>,
	Naga Sureshkumar Relli <nagasure@xilinx.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v4] dt-binding: mtd: nand: Document the cs-gpios property
Date: Tue, 11 May 2021 11:24:40 -0500	[thread overview]
Message-ID: <20210511162440.GA2227381@robh.at.kernel.org> (raw)
In-Reply-To: <20210510171800.27225-1-miquel.raynal@bootlin.com>

On Mon, 10 May 2021 19:18:00 +0200, Miquel Raynal wrote:
> To reach higher capacities, arrays of chips are now pretty common.
> Unfortunately, most of the controllers have been designed a decade ago
> and did not all anticipate the need for several chip-selects. The new
> cs-gpios property allows to workaround this limitation by adding as many
> GPIO chip-select as needed.
> 
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> 
> Resending only the binding patch of the series, with the following
> changes requested by Rob:
> * Fixed the coherency between cs-gpios and gpios-cs
> * Added maxItems: 8 (this is a good enough value for most of the cases I
>   guess, this can be increased later if needed).
> * Adding maxItems: 8 lead to an error when checking the example,
>   minItems: 8 had to be added as well to the schema to fix it, not sure
>   this was expected or not.
> 
>  .../bindings/mtd/nand-controller.yaml          | 18 +++++++++++++++++-
>  1 file changed, 17 insertions(+), 1 deletion(-)
> 

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

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

  reply	other threads:[~2021-05-12 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 17:18 [PATCH v4] dt-binding: mtd: nand: Document the cs-gpios property Miquel Raynal
2021-05-10 17:18 ` Miquel Raynal
2021-05-11 16:24 ` Rob Herring [this message]
2021-05-11 16:24   ` Rob Herring
2021-05-26  9:03 ` Miquel Raynal
2021-05-26  9:03   ` 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=20210511162440.GA2227381@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=monstr@monstr.eu \
    --cc=nagasure@xilinx.com \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --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.