Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2307362imm; Sun, 9 Sep 2018 21:47:50 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZwJqLypiaA7y8vgo8hIq+Ghsyl6PRbpKvugWTFa29wS6ccUgUdi18HMrw4qJvj5mlc4Rxj X-Received: by 2002:a17:902:e004:: with SMTP id ca4-v6mr19352977plb.252.1536554870154; Sun, 09 Sep 2018 21:47:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536554870; cv=none; d=google.com; s=arc-20160816; b=hLrpMbdY9bIVegm7TXyMAVrAUCBhAy1zeHeir5mBG0akLXL1bgffkhGZUXKvKkzODV W0C7S9RzrJtm/5x2rkREeOcOpQ3DXye4QDDJWLzWEpsirY9uqI7SzUeeaBLnraafGFoH gk6+0b2OIZ+6YY1sQBP9rKrrvv1/gRrNw2cP1LfTHBSQV8ql5IT9Z9UoDykiU8v2H1J/ yIPlK/Ae+zNtB+lxD0opgJT/OlNG8PflgTgC8H8R1iVAp8DEiurhDSrZB/h7M4NIfgeI +78Wd6HlNsojsllA2LM5cNef+95uMHx5zF8bIiEnTINNT8zWth1OO+lVrWaBaTAQEQrg HTZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=o0w0GL7ThpyHmKu4n5QzJ+XIazTB/R+0t8OCUbipUAI=; b=XzfKXvGolEjE3VxhLmqplnH38zWt4Js32Ye/I/zRzMzmTzRGfZ88OONCdBy7vWsS2w Eintqgijtg9l4dZ7f/KgDU+FtMP6/43FAp60+kK+j4BPiBV6wkTDjyxmh08WRapCxVOf wGwlbHSrNUHNRbmTrdRPsya35BO5v/HJ86/XpUG88KR4QKXtDr2PdgN71zL6m3x22vZ6 RwLJ0BZkOHockl7I9gPhDJszfgz5uGpDLgWN/7VTDhyoUwPRJP2bY69elp7oR6erhbtd AqXsbUAiEC82yR3jQZwmkwGqorerJJl2W3cCaiW6Y2TaLurgoIfsX7bQml/M+zfJ2Ox+ tobA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p7-v6si16666623pll.42.2018.09.09.21.47.34; Sun, 09 Sep 2018 21:47:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726949AbeIJJig (ORCPT + 99 others); Mon, 10 Sep 2018 05:38:36 -0400 Received: from mail-sz2.amlogic.com ([211.162.65.114]:60359 "EHLO mail-sz2.amlogic.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726114AbeIJJig (ORCPT ); Mon, 10 Sep 2018 05:38:36 -0400 Received: from [10.28.18.79] (10.28.18.79) by mail-sz2.amlogic.com (10.28.11.6) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 10 Sep 2018 12:46:44 +0800 Subject: Re: [RFC PATCH v3 1/2] dt-bindings: nand: meson: add Amlogic NAND controller driver To: Boris Brezillon , Jianxin Pan CC: , Yixun Lan , David Woodhouse , Brian Norris , Marek Vasut , Richard Weinberger , Jerome Brunet , Neil Armstrong , Martin Blumenstingl , Carlo Caione , Kevin Hilman , Rob Herring , Jian Hu , Hanjie Lin , Victor Wan , , , , References: <1536317831-58056-1-git-send-email-jianxin.pan@amlogic.com> <1536317831-58056-2-git-send-email-jianxin.pan@amlogic.com> <20180907141944.4dd4406b@bbrezillon> From: Liang Yang Message-ID: <824dd234-30d6-d47d-8abd-352578b232f6@amlogic.com> Date: Mon, 10 Sep 2018 12:46:44 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180907141944.4dd4406b@bbrezillon> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.28.18.79] X-ClientProxiedBy: mail-sz2.amlogic.com (10.28.11.6) To mail-sz2.amlogic.com (10.28.11.6) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi boric, Thanks for your quick reply. On 9/7/2018 8:19 PM, Boris Brezillon wrote: > On Fri, 7 Sep 2018 18:57:10 +0800 > Jianxin Pan wrote: > >> From: Liang Yang >> >> Add Amlogic NAND controller dt-bindings for Meson SoC, >> Current this driver support GXBB/GXL/AXG platform. >> >> Signed-off-by: Liang Yang >> Signed-off-by: Yixun Lan >> --- >> .../devicetree/bindings/mtd/amlogic,meson-nand.txt | 91 ++++++++++++++++++++++ >> 1 file changed, 91 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 0000000..655a778 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt >> @@ -0,0 +1,91 @@ >> +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 mean pinctrl-names and pinctrl-0, right? Not sure it's necessary to > document that, but if you do, please use the correct DT prop names. > I find no documentation for that in other xx_nand.txt; I will consider to remove it. >> +- amlogic,mmc-syscon : Required for NAND clocks, it's shared with SD/eMMC >> + controller port C >> + >> +Optional children nodes: >> +Children nodes represent the available nand chips. >> + >> + >> + > > One too many blank lines here. > ok, i will remove it. >> +Other properties: >> +see Documentation/devicetree/bindings/mtd/nand.txt for generic bindings. >> + >> +Example demonstrate on AXG SoC: >> + >> + sd_emmc_c_clkc: mmc@7000 { >> + compatible = "amlogic,meson-axg-mmc-clkc", "syscon"; >> + reg = <0x0 0x7000 0x0 0x800>; >> + status = "okay"; >> + }; >> + >> + nand: nfc@7800 { >> + compatible = "amlogic,meson-axg-nfc"; >> + reg = <0x0 0x7800 0x0 0x100>; >> + #address-cells = <1>; >> + #size-cells = <0>; >> + interrupts = ; >> + 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@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>; > > Drop nand-ecc- props. I guess you have a sensible default value and I > prefer when ECC requirements are directly extracted during chip > detection. Defining that in the DT is a bad habit. The only one that > could make sense (assuming you support it) is nand-ecc-maximize. > ok, i will drop them. we adopt auto detection during init stage, it works too. >> + >> + amlogic,nand-enable-scrambler; > > Please drop this property (it's not longer documented). > em, we should have removed it when nfc driver never use it. >> + >> + partition@0 { >> + label = "boot"; >> + reg = <0x00000000 0x00200000>; >> + read-only; >> + }; >> + partition@200000 { >> + label = "env"; >> + reg = <0x00200000 0x00400000>; >> + }; >> + partition@600000 { >> + label = "system"; >> + reg = <0x00600000 0x00a00000>; >> + }; >> + partition@1000000 { >> + label = "rootfs"; >> + reg = <0x01000000 0x03000000>; >> + }; >> + partition@4000000 { >> + label = "media"; >> + reg = <0x04000000 0x8000000>; >> + }; > > No need to define the partitions in your example, especially since they > should be placed in a partitions subnode with a "fixed-partitions" > compat. > ok, i will remove it. >> + }; >> + }; > > . >