Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4158932yba; Sun, 12 May 2019 06:25:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqxh3rj2sEAPhUzI3jyrRILMPDgf3PmTHMdNqKcpheIIUupiUW9czAmrUOsZAJetUpVnrdbd X-Received: by 2002:a63:af44:: with SMTP id s4mr25327242pgo.411.1557667507405; Sun, 12 May 2019 06:25:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557667507; cv=none; d=google.com; s=arc-20160816; b=IGQMcK9K4rxEHrFfsah2K9iwqziiisoOhQFzU4pjwbYUMdjTRU4QfMVmgJh0miK0t+ AARi+KanPUrgT4BoaGcaB3p9NlOPdUqEx70QAmfAI2qy8eUExDbIt4HE4bzEs2+5TOBl M8piqUSGFp7AwPq2ynWPip7/LWHv1y4o+Liy69WqfAEIHd7S25r4XC56BdaKiUUoj7q9 Lpajw3WxNfjSeTnZhhUxDKoKJYrC4YP4NaDKg4PeXdzORgTW/X1m+ghmsclkxdFnigDq KG5sfR2A+FUDdIkyX09ShS7jS5wamXnzD7tImp8Ik2NFsDBSqhid1zBJHhSCDg+EjQh1 TxtQ== 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:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=nZUZUKo3kI5NzB/Kv4HV8pklIau9vhH3qQDUQjQ+QlM=; b=rgKLH3O/Qsl0hgWtayOwgG89hQpcNlGlyU60/YxGCfpD4NKz8vp1TSgV00mFaV2ywg +iAJE4l4mrosBU6pBvfkwCvjILvXwY2Gn58+f8FmSKwhWAZiZDWtAGt5bexGEoh0v/gF cHE7KEXYlOFBf68sn/xB5/jr8VbGIebfncWReZ3YlZGfu3l3Buy/58HTUAjbANQwLUjM 3qh+9SHsUFtl/xdUlbtxEamWUc5uN8ujPPoajaUNv6wSJT27hpDt/ZRU/rCVQFzX0AdE u1G1mwbgFAjQmbqaFIBoAX/RVtAV/zJii4jsSiHdiK/XOhP/nrm6Un9b05Ch8nSw3ei5 98bQ== 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 d16si14240448pgb.97.2019.05.12.06.24.50; Sun, 12 May 2019 06:25:07 -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 S1726736AbfELNYD convert rfc822-to-8bit (ORCPT + 99 others); Sun, 12 May 2019 09:24:03 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:51907 "EHLO relay12.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726415AbfELNYC (ORCPT ); Sun, 12 May 2019 09:24:02 -0400 Received: from xps13 (unknown [109.190.253.16]) (Authenticated sender: miquel.raynal@bootlin.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id CBA23200009; Sun, 12 May 2019 13:23:49 +0000 (UTC) Date: Sun, 12 May 2019 15:23:40 +0200 From: Miquel Raynal To: Mason Yang Cc: broonie@kernel.org, marek.vasut@gmail.com, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, bbrezillon@kernel.org, dwmw2@infradead.org, lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, computersforpeace@gmail.com, paul.burton@mips.com, stefan@agner.ch, christophe.kerello@st.com, liang.yang@amlogic.com, geert@linux-m68k.org, devicetree@vger.kernel.org, marcel.ziswiler@toradex.com, linux-mtd@lists.infradead.org, richard@nod.at, juliensu@mxic.com.tw, zhengxunli@mxic.com.tw Subject: Re: [PATCH v3 4/4] dt-bindings: mfd: Document Macronix MX25F0A controller bindings Message-ID: <20190512152328.49576a0f@xps13> In-Reply-To: <1555320234-15802-5-git-send-email-masonccyang@mxic.com.tw> References: <1555320234-15802-1-git-send-email-masonccyang@mxic.com.tw> <1555320234-15802-5-git-send-email-masonccyang@mxic.com.tw> Organization: Bootlin X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mason, Mason Yang wrote on Mon, 15 Apr 2019 17:23:54 +0800: > Document the bindings used by the Macronix MX25F0A MFD controller. > > Signed-off-by: Mason Yang > --- > .../devicetree/bindings/mfd/mxic-mx25f0a.txt | 51 ++++++++++++++++++++++ > 1 file changed, 51 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/mxic-mx25f0a.txt > > diff --git a/Documentation/devicetree/bindings/mfd/mxic-mx25f0a.txt b/Documentation/devicetree/bindings/mfd/mxic-mx25f0a.txt > new file mode 100644 > index 0000000..7f3e0f8 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/mxic-mx25f0a.txt > @@ -0,0 +1,51 @@ > +Macronix MX25F0A MultiFunction Device Tree Bindings > +---------------------------------------------------- > + > +MX25F0A is a MultiFunction Device with SPI and raw NAND, which > +supports either spi host controller or raw nand controller. Acronyms in plain English should be in upper case. > + > +Required properties: > +- compatible: should be "mxic,mx25f0a" > +- #address-cells: should be 1 > +- #size-cells: should be 0 > +- reg: should contain 2 entries, one for the registers and one for the direct > + mapping area in SPI mode. > +- reg-names: should contain "regs" and "dirmap" > +- interrupts: interrupt line connected to this MFD controller > +- SPI controller driver: > + - clock-names: should contain "ps_clk", "send_clk" and > + "send_dly_clk" > + - clocks: should contain 3 entries for the "ps_clk", "send_clk" > + and "send_dly_clk" clocks > + > +- Raw nand controller driver. > + - nand-ecc-mode = "soft"; > + - nand-ecc-algo = "bch"; > + > +Example: > + > + mxic: mx25f0a@43c30000 { > + compatible = "mxic,mx25f0a"; > + reg = <0x43c30000 0x10000>, <0xa0000000 0x4000000>; > + reg-names = "regs", "dirmap"; > + > + /* spi */ > + clocks = <&clkwizard 0>, <&clkwizard 1>, <&clkc 15>; > + clock-names = "send_clk", "send_dly_clk", "ps_clk"; > + #address-cells = <1>; > + #size-cells = <0>; > + > + flash@0 { > + compatible = "jedec,spi-nor"; > + reg = <0>; > + spi-max-frequency = <25000000>; > + spi-tx-bus-width = <4>; > + spi-rx-bus-width = <4>; > + }; > + > + /* nand */ > + nand-ecc-mode = "soft"; > + nand-ecc-algo = "bch"; > + nand-ecc-step-size = <512>; > + nand-ecc-strength = <8>; Any reason to enforce 512B/8b correction? Why not letting the core choose for you depending on the NAND chip's requirements? Anyway, I think you can have only one or the other (NAND or SPI), not both, and you probably should have a compatible or a property to tell the kernel which one you are using, right? Thanks, Miquèl