From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Stefan Agner <stefan@agner.ch>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
marek.vasut@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
thierry.reding@gmail.com, benjamin.lindqvist@endian.se,
pgaikwad@nvidia.com, dev@lynxeye.de, mirza.krak@gmail.com,
richard@nod.at, pdeschrijver@nvidia.com,
linux-kernel@vger.kernel.org, krzk@kernel.org,
jonathanh@nvidia.com, devicetree@vger.kernel.org,
linux-mtd@lists.infradead.org, marcel@ziswiler.com,
miquel.raynal@bootlin.com, linux-tegra@vger.kernel.org,
digetx@gmail.com
Subject: Re: [PATCH v3 2/6] mtd: rawnand: add an option to specify NAND chip as a boot device
Date: Fri, 1 Jun 2018 09:26:52 +0200 [thread overview]
Message-ID: <20180601092652.2e9716ac@bbrezillon> (raw)
In-Reply-To: <20180531221637.6017-3-stefan@agner.ch>
On Fri, 1 Jun 2018 00:16:33 +0200
Stefan Agner <stefan@agner.ch> 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 ++++
> drivers/mtd/nand/raw/nand_base.c | 3 +++
> include/linux/mtd/rawnand.h | 6 ++++++
> 3 files changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/nand.txt b/Documentation/devicetree/bindings/mtd/nand.txt
> index 8bb11d809429..8daf81b9748c 100644
> --- a/Documentation/devicetree/bindings/mtd/nand.txt
> +++ b/Documentation/devicetree/bindings/mtd/nand.txt
> @@ -43,6 +43,10 @@ Optional NAND chip properties:
> This is particularly useful when only the in-band area is
> used by the upper layers, and you want to make your NAND
> as reliable as possible.
> +- nand-is-boot-medium: Whether the NAND chip is a boot medium. Drivers might use
> + this information to select ECC algorithms supported by
> + the boot ROM or similar restrictions.
> +
> - nand-rb: shall contain the native Ready/Busy ids.
>
> The ECC strength and ECC step size properties define the correction capability
> diff --git a/drivers/mtd/nand/raw/nand_base.c b/drivers/mtd/nand/raw/nand_base.c
> index 9eb5678dd6d0..c8fb7c9855e2 100644
> --- a/drivers/mtd/nand/raw/nand_base.c
> +++ b/drivers/mtd/nand/raw/nand_base.c
> @@ -5826,6 +5826,9 @@ static int nand_dt_init(struct nand_chip *chip)
> if (of_get_nand_bus_width(dn) == 16)
> chip->options |= NAND_BUSWIDTH_16;
>
> + if (of_property_read_bool(dn, "nand-is-boot-medium"))
> + chip->options |= NAND_IS_BOOT_MEDIUM;
> +
> if (of_get_nand_on_flash_bbt(dn))
> chip->bbt_options |= NAND_BBT_USE_FLASH;
>
> diff --git a/include/linux/mtd/rawnand.h b/include/linux/mtd/rawnand.h
> index 6a82da8c44ce..8e54fcf2fa94 100644
> --- a/include/linux/mtd/rawnand.h
> +++ b/include/linux/mtd/rawnand.h
> @@ -212,6 +212,12 @@ enum nand_ecc_algo {
> */
> #define NAND_WAIT_TCCS 0x00200000
>
> +/*
> + * Whether the NAND chip is a boot medium. Drivers might use this information
> + * to select ECC algorithms supported by the boot ROM or similar restrictions.
> + */
> +#define NAND_IS_BOOT_MEDIUM 0x00400000
> +
> /* Options set by nand scan */
> /* Nand scan has allocated controller struct */
> #define NAND_CONTROLLER_ALLOC 0x80000000
next prev parent reply other threads:[~2018-06-01 7:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 22:16 [PATCH v3 0/6] mtd: rawnand: add NVIDIA Tegra NAND flash support Stefan Agner
2018-05-31 22:16 ` [PATCH v3 1/6] mtd: rawnand: add Reed-Solomon error correction algorithm Stefan Agner
2018-06-01 7:26 ` Boris Brezillon
2018-06-01 9:25 ` Boris Brezillon
2018-06-01 13:34 ` Stefan Agner
2018-06-01 13:43 ` Boris Brezillon
2018-05-31 22:16 ` [PATCH v3 2/6] mtd: rawnand: add an option to specify NAND chip as a boot device Stefan Agner
2018-06-01 7:26 ` Boris Brezillon [this message]
2018-06-05 20:11 ` Rob Herring
2018-06-06 7:28 ` Boris Brezillon
2018-05-31 22:16 ` [PATCH v3 3/6] mtd: rawnand: tegra: add devicetree binding Stefan Agner
2018-06-01 7:30 ` Boris Brezillon
2018-06-05 20:19 ` Dmitry Osipenko
2018-06-06 10:39 ` Thierry Reding
2018-06-06 10:45 ` Boris Brezillon
2018-06-06 11:07 ` Thierry Reding
2018-06-06 12:14 ` Stefan Agner
2018-06-06 12:31 ` Boris Brezillon
2018-06-05 20:13 ` Rob Herring
2018-05-31 22:16 ` [PATCH v3 4/6] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver Stefan Agner
2018-06-01 9:20 ` Dmitry Osipenko
2018-06-08 21:51 ` Stefan Agner
2018-06-09 5:52 ` Boris Brezillon
2018-06-09 6:23 ` Stefan Agner
2018-06-09 6:41 ` Boris Brezillon
2018-06-09 6:46 ` Boris Brezillon
2018-06-09 6:55 ` Boris Brezillon
2018-06-09 6:51 ` Stefan Agner
2018-06-09 12:21 ` Dmitry Osipenko
2018-06-10 11:09 ` Stefan Agner
2018-06-10 15:00 ` Dmitry Osipenko
2018-06-10 15:32 ` Boris Brezillon
2018-06-11 11:45 ` Dmitry Osipenko
2018-06-11 11:50 ` Boris Brezillon
2018-06-11 13:10 ` Dmitry Osipenko
2018-06-04 17:16 ` Randolph Maaßen
2018-06-04 20:56 ` Stefan Agner
2018-06-09 5:55 ` Boris Brezillon
2018-06-09 7:18 ` Boris Brezillon
2018-05-31 22:16 ` [PATCH v3 5/6] ARM: dts: tegra: add Tegra20 NAND flash controller node Stefan Agner
2018-05-31 22:16 ` [PATCH v3 6/6] ARM: dts: tegra: enable NAND flash on Colibri T20 Stefan Agner
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=20180601092652.2e9716ac@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=benjamin.lindqvist@endian.se \
--cc=computersforpeace@gmail.com \
--cc=dev@lynxeye.de \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=dwmw2@infradead.org \
--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=robh+dt@kernel.org \
--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 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).