All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: boris.brezillon@bootlin.com, dwmw2@infradead.org,
	computersforpeace@gmail.com, marek.vasut@gmail.com,
	mark.rutland@arm.com, thierry.reding@gmail.com, dev@lynxeye.de,
	miquel.raynal@bootlin.com, richard@nod.at, marcel@ziswiler.com,
	krzk@kernel.org, digetx@gmail.com, benjamin.lindqvist@endian.se,
	jonathanh@nvidia.com, pdeschrijver@nvidia.com,
	pgaikwad@nvidia.com, mirza.krak@gmail.com, gaireg@gaireg.de,
	linux-mtd@lists.infradead.org, linux-tegra@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/6] mtd: rawnand: add an option to specify NAND chip as a boot device
Date: Mon, 25 Jun 2018 08:47:52 -0600	[thread overview]
Message-ID: <20180625144752.GA19064@rob-hp-laptop> (raw)
In-Reply-To: <20180624212727.21672-3-stefan@agner.ch>

On Sun, Jun 24, 2018 at 11:27:23PM +0200, Stefan Agner wrote:
> Allow to define a NAND chip as a boot device. This can be helpful
> for the selection of the ECC algorithm and strength in case the boot
> ROM supports only a subset of controller provided options.
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> Reviewed-by: Boris Brezillon <boris.brezillon@bootlin.com>
> ---
>  Documentation/devicetree/bindings/mtd/nand.txt | 4 ++++

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

>  drivers/mtd/nand/raw/nand_base.c               | 3 +++
>  include/linux/mtd/rawnand.h                    | 6 ++++++
>  3 files changed, 13 insertions(+)

  reply	other threads:[~2018-06-25 14:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24 21:27 [PATCH v8 0/6] mtd: rawnand: add NVIDIA Tegra NAND flash support Stefan Agner
2018-06-24 21:27 ` [PATCH v8 1/6] mtd: rawnand: add Reed-Solomon error correction algorithm Stefan Agner
2018-06-24 21:27   ` Stefan Agner
2018-06-24 21:27 ` [PATCH v8 2/6] mtd: rawnand: add an option to specify NAND chip as a boot device Stefan Agner
2018-06-25 14:47   ` Rob Herring [this message]
2018-06-24 21:27 ` [PATCH v8 3/6] mtd: rawnand: tegra: add devicetree binding Stefan Agner
2018-06-24 21:27 ` [PATCH v8 4/6] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver Stefan Agner
2018-06-24 21:27 ` [PATCH v8 5/6] ARM: dts: tegra: add Tegra20 NAND flash controller node Stefan Agner
2018-06-24 21:27 ` [PATCH v8 6/6] ARM: dts: tegra: enable NAND flash on Colibri T20 Stefan Agner
2018-06-25 12:34 ` [PATCH v8 0/6] mtd: rawnand: add NVIDIA Tegra NAND flash support Miquel Raynal
2018-07-04  7:33   ` Stefan Agner
2018-07-04  7:45     ` 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=20180625144752.GA19064@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=benjamin.lindqvist@endian.se \
    --cc=boris.brezillon@bootlin.com \
    --cc=computersforpeace@gmail.com \
    --cc=dev@lynxeye.de \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=gaireg@gaireg.de \
    --cc=jonathanh@nvidia.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marcel@ziswiler.com \
    --cc=marek.vasut@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=mirza.krak@gmail.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=richard@nod.at \
    --cc=stefan@agner.ch \
    --cc=thierry.reding@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 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.