From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
Cc: computersforpeace@gmail.com, dwmw2@infradead.org,
matthias.bgg@gmail.com, robh@kernel.org,
linux-mtd@lists.infradead.org, xiaolei.li@mediatek.com,
linux-mediatek@lists.infradead.org, erin.lo@mediatek.com,
daniel.thompson@linaro.org, blogic@openwrt.org
Subject: Re: [PATCH v4 1/2] mtd: mediatek: device tree docs for MTK Smart Device Gen1 NAND
Date: Fri, 6 May 2016 15:38:16 +0200 [thread overview]
Message-ID: <20160506153816.7ca581ac@bbrezillon> (raw)
In-Reply-To: <1461946642-1842-2-git-send-email-jorge.ramirez-ortiz@linaro.org>
Hi Jorge,
On Fri, 29 Apr 2016 12:17:21 -0400
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org> wrote:
> This patch adds documentation support for Smart Device Gen1 type of
> NAND controllers.
>
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
> ---
> Documentation/devicetree/bindings/mtd/mtk-nand.txt | 161 +++++++++++++++++++++
> 1 file changed, 161 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/mtk-nand.txt
>
> diff --git a/Documentation/devicetree/bindings/mtd/mtk-nand.txt b/Documentation/devicetree/bindings/mtd/mtk-nand.txt
> new file mode 100644
> index 0000000..175767d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/mtk-nand.txt
[...]
> +
> +Children nodes properties:
> +- reg: Chip Select Signal, default 0.
> + Set as reg = <0>, <1> when need 2 CS.
> +Optional:
> +- nand-on-flash-bbt: Store BBT on NAND Flash.
> +- nand-ecc-mode: the NAND ecc mode (check driver for supported modes)
> +- nand-ecc-step-size: Number of data bytes covered by a single ECC step.
> + The controller only supports 512 and 1024.
> + For large page NANDs ther recommended value is 1024.
> +- nand-ecc-strength: Number of bits to correct per ECC step.
> + The valid values that the controller supports are: 4, 6,
> + 8, 10, 12, 14, 16, 18, 20, 22, 24, 28, 32, 36, 40, 44,
> + 48, 52, 56, 60.
> + The strength should be calculated as follows:
> + E = (S - F) * 8 / 14
> + S = O / (P / Q)
> + E :nand-ecc-strength;
> + S :spare size per sector;
> + F : FDM size, should be in the range [1,8].
> + It is used to store free oob data.
> + O : oob size;
> + P : page size;
> + Q :nand-ecc-step-size
> + If the result does not match any one of the listed
> + choices above, please select the smaller valid value from
> + the list.
> + (otherwise the driver will do the clamping at runtime).
> +- vmch-supply: NAND power supply.
Where is this supply name coming from? I most datasheets I see Vdd or
Vcc, but nothing close to Vmch.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-06 13:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 16:17 [PATCH v4 0/2] MTK Smart Device Gen1 NAND Driver Jorge Ramirez-Ortiz
2016-04-29 16:17 ` [PATCH v4 1/2] mtd: mediatek: device tree docs for MTK Smart Device Gen1 NAND Jorge Ramirez-Ortiz
2016-05-06 13:38 ` Boris Brezillon [this message]
2016-05-10 11:57 ` Jorge Ramirez
2016-05-10 12:22 ` Boris Brezillon
2016-04-29 16:17 ` [PATCH v4 2/2] mtd: mediatek: driver " Jorge Ramirez-Ortiz
2016-05-01 7:32 ` John Crispin
[not found] ` <1462165406.8414.196.camel@mhfsdcap03>
2016-05-02 6:13 ` John Crispin
2016-05-02 11:38 ` Jorge Ramirez
2016-05-02 17:43 ` John Crispin
2016-05-10 12:13 ` Boris Brezillon
2016-05-10 14:37 ` Jorge Ramirez
2016-05-10 14:55 ` Boris Brezillon
2016-05-10 14:45 ` Jorge Ramirez
2016-05-10 14:59 ` Boris Brezillon
2016-05-10 15:18 ` Jorge Ramirez
2016-05-10 14:50 ` Jorge Ramirez
2016-05-10 15:13 ` Boris Brezillon
2016-05-10 15:37 ` Jorge Ramirez
2016-05-10 14:53 ` Jorge Ramirez
2016-05-10 18:14 ` Jorge Ramirez
2016-05-10 18:19 ` Boris Brezillon
2016-05-10 14:53 ` Jorge Ramirez
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=20160506153816.7ca581ac@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=blogic@openwrt.org \
--cc=computersforpeace@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=dwmw2@infradead.org \
--cc=erin.lo@mediatek.com \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=xiaolei.li@mediatek.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).