From: boris.brezillon@bootlin.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 1/2] dt-bindings: nand: meson: add Amlogic NAND controller driver
Date: Thu, 19 Jul 2018 11:57:51 +0200 [thread overview]
Message-ID: <20180719115751.34ff1a51@bbrezillon> (raw)
In-Reply-To: <20180719094612.5833-2-yixun.lan@amlogic.com>
On Thu, 19 Jul 2018 17:46:11 +0800
Yixun Lan <yixun.lan@amlogic.com> wrote:
> From: Liang Yang <liang.yang@amlogic.com>
>
> Add Amlogic NAND controller dt-bindings for Meson SoC,
> Current this driver support GXBB/GXL/AXG platform.
>
> Signed-off-by: Liang Yang <liang.yang@amlogic.com>
> Signed-off-by: Yixun Lan <yixun.lan@amlogic.com>
> ---
> .../bindings/mtd/amlogic,meson-nand.txt | 95 +++++++++++++++++++
> 1 file changed, 95 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt
>
> diff --git a/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt
> new file mode 100644
> index 000000000000..31f910dcd27a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt
> @@ -0,0 +1,95 @@
> +Amlogic NAND Flash Controller (NFC) for GXBB/GXL/AXG family SoCs
> +
> +This file documents the properties in addition to those available in
> +the MTD NAND bindings.
> +
> +Required properties:
> +- compatible : contains one of:
> + - "amlogic,meson-gxl-nfc"
> + - "amlogic,meson-axg-nfc"
> +- clocks :
> + A list of phandle + clock-specifier pairs for the clocks listed
> + in clock-names.
> +
> +- clock-names: Should contain the following:
> + "core" - NFC module gate clock
> + "device" - device clock from eMMC sub clock controller
> +
> +- pins : Select pins which NFC need.
> +- nand_pins: Detail NAND pins information.
You should document pinctrl-0 and pinctrl-names, not pins and nand_pins.
> +- amlogic,mmc-syscon : Required for NAND clocks, it's shared with SD/eMMC
> + controller port C
Are you sure this is still needed, even after exposing MMC/NAND clks
through the CCF?
You forgot
- #address-cells
- #size-cells
- reg
- interrupts
-
> +
> +Optional children nodes:
> +Children nodes represent the available nand chips.
> +
> +Optional properties:
> +- amlogic,nand-enable-scrambler: enable the NAND scrambler feature.
> + - (absent) = scrambler is disabled
> + - (present) = scrambler is enabled
I keep thinking this is not needed if you have the NAND chip properly
defined (NAND_NEED_SCRAMBLING flag set in chip->options).
> +
> +
> +Other properties:
> +see Documentation/devicetree/bindings/mtd/nand.txt for generic bindings.
> +
> +Example demonstrate on AXG SoC:
> +
> + sd_emmc_c_clkc: mmc at 7000 {
> + compatible = "amlogic,meson-axg-mmc-clkc", "syscon";
> + reg = <0x0 0x7000 0x0 0x800>;
> + status = "okay";
> + };
> +
> + nand: nfc at 7800 {
> + compatible = "amlogic,meson-axg-nfc";
> + reg = <0x0 0x7800 0x0 0x100>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + interrupts = <GIC_SPI 34 IRQ_TYPE_EDGE_RISING>;
> + status = "disabled";
> +
> + clocks = <&clkc CLKID_SD_EMMC_C>,
> + <&sd_emmc_c_clkc CLKID_MMC_DIV>;
> + clock-names = "core", "device";
> + amlogic,mmc-syscon = <&sd_emmc_c_clkc>;
> +
> + status = "okay";
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&nand_pins>;
> +
> + nand at 0 {
> + reg = <0>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + nand-on-flash-bbt;
> + nand-ecc-mode = "hw";
> + nand-ecc-strength = <8>;
> + nand-ecc-step-size = <1024>;
I'd recommend not forcing a specific ECC config in the example.
> +
> + amlogic,nand-enable-scrambler;
> +
> + partition at 0 {
> + label = "boot";
> + reg = <0x00000000 0x00200000>;
> + read-only;
> + };
Blank line here.
> + partition at 200000 {
> + label = "env";
> + reg = <0x00200000 0x00400000>;
> + };
> + partition at 600000 {
> + label = "system";
> + reg = <0x00600000 0x00a00000>;
> + };
> + partition at 1000000 {
> + label = "rootfs";
> + reg = <0x01000000 0x03000000>;
> + };
> + partition at 4000000 {
> + label = "media";
> + reg = <0x04000000 0x8000000>;
> + };
> + };
> + };
next prev parent reply other threads:[~2018-07-19 9:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 9:46 [RFC PATCH v2 0/2] mtd: rawnand: meson: add Amlogic NAND driver support Yixun Lan
2018-07-19 9:46 ` [RFC PATCH v2 1/2] dt-bindings: nand: meson: add Amlogic NAND controller driver Yixun Lan
2018-07-19 9:57 ` Boris Brezillon [this message]
2018-07-19 10:07 ` Yixun Lan
2018-07-19 9:46 ` [RFC PATCH v2 2/2] mtd: rawnand: meson: add support for Amlogic NAND flash controller Yixun Lan
2018-08-01 21:50 ` Boris Brezillon
2018-08-02 14:04 ` Yixun Lan
2018-08-17 13:03 ` Liang Yang
2018-08-17 13:56 ` Boris Brezillon
2018-08-21 3:33 ` Liang Yang
2018-08-22 14:08 ` Liang Yang
2018-08-24 12:48 ` Boris Brezillon
2018-08-28 13:21 ` Liang Yang
2018-08-28 13:26 ` Boris Brezillon
2018-08-29 10:08 ` Liang Yang
2018-08-29 10:29 ` Liang Yang
2018-08-29 10:31 ` Boris Brezillon
2018-08-17 8:46 ` Boris Brezillon
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=20180719115751.34ff1a51@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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