Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2324938imm; Thu, 7 Jun 2018 08:48:47 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIBrKmBp+BtTVunaP46a0yDVr5Y/MHiISnCRy13dDVysVbJhCYFcmBZreVseqX8eYip1ztu X-Received: by 2002:aa7:84cf:: with SMTP id x15-v6mr2270430pfn.220.1528386527274; Thu, 07 Jun 2018 08:48:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528386527; cv=none; d=google.com; s=arc-20160816; b=X2K6QoOhpgdgejbHhMHTC9/u8c0N2ZbddWGrAZOARJ5HHJXDfNXQTnrmF6ahasGDoM 4GkMxqmHDQOieDYu+gke47gwjnij2LS+0DPlz1/1ZBG9KHACHoj5nyrUlYUd9UYmy3FN vSXHpSBe7yRT8vd+eQ3mCXs+zg15yoe1EGjnLRbr6nupFkxO/o7KG8rKchDhPSoZ28VO UHq61bwcHUs6VCgEaToUkVPky3kopEosE4n46FnrM4CYAA5I8tvNt0SEnGyW4D10DXVP 9LvozDsb2nEUAakzoRsmdodahpYFc2GG2Yx/MN4zOENRd3DPl4MzvjA95LaJN12qfleJ Hvdw== 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:arc-authentication-results; bh=zw/QR+ZqTpJuuPG6hOUVMSAeXwTfCmMeIg2P0V2OzCg=; b=iun3EbLZCNRwAvFdV43UpetKDU3t2T6iQGQ57CM931+9/5vudwtmQQDDz5OGTQt7r2 KY16T7KTcy89NZ14lTACIv+3mG3Inet0SNNcOEw8fHrQU3odnECjOkm3fE8d1KERgIHB 8yWt3Me4u1HuSXv6UX5YJJuGI61uJunX8e2pu1W/RXhPj//df3Yo9EcpdG6Ut2D6Vest Wq//9v5XBDUCB1p1GytL9eskXSkjlL3TmaGBzHtcL4Mj0Gru/L9k8k7mpcPwGoCCa8PG ZXBdThySjWdE2fGWjyVCoIVMP9hSR1ocjKGd5b0qSNC+b8F+hSAKapKoiKd760r8cZ7H tLMw== 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 o1-v6si53204393pld.424.2018.06.07.08.48.32; Thu, 07 Jun 2018 08:48:47 -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 S934517AbeFGPrb (ORCPT + 99 others); Thu, 7 Jun 2018 11:47:31 -0400 Received: from mail.bootlin.com ([62.4.15.54]:50331 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932578AbeFGPra (ORCPT ); Thu, 7 Jun 2018 11:47:30 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id 3DA8520799; Thu, 7 Jun 2018 17:47:28 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.bootlin.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.4.0 Received: from xps13 (AAubervilliers-681-1-128-7.w90-88.abo.wanadoo.fr [90.88.9.7]) by mail.bootlin.com (Postfix) with ESMTPSA id C646920012; Thu, 7 Jun 2018 17:47:27 +0200 (CEST) Date: Thu, 7 Jun 2018 17:47:27 +0200 From: Miquel Raynal To: Naga Sureshkumar Relli Cc: , , , , , , , , , , , , , Subject: Re: [LINUX PATCH v9 1/4] Devicetree: Add pl353 smc controller devicetree binding information Message-ID: <20180607174727.6fcebde2@xps13> In-Reply-To: <20180607174203.035f187d@xps13> References: <1528271382-21690-1-git-send-email-naga.sureshkumar.relli@xilinx.com> <1528271382-21690-2-git-send-email-naga.sureshkumar.relli@xilinx.com> <20180607174203.035f187d@xps13> Organization: Bootlin X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Miquel, On Thu, 7 Jun 2018 17:42:03 +0200, Miquel Raynal wrote: > Hi Naga, > > On Wed, 6 Jun 2018 13:19:39 +0530, Naga Sureshkumar Relli > wrote: > > > Add pl353 static memory controller devicetree binding information. > > > > Signed-off-by: Naga Sureshkumar Relli > > --- > > Changes in v9: > > - Addressed commens given by Randy Dunlap and Miquel Raynal > > Can you please be more specific in your next changelog? I don't > remember what I suggested a few months ago :) > > > Changes in v8: > > - None > > Changes in v7: > > - Corrected clocks description > > - prefixed '#' for address and size cells > > Changes in v6: > > - None > > Changes in v5: > > - Removed timing properties > > Changes in v4: > > - none > > Changes in v3: > > - none > > Changes in v2: > > - modified timing binding info as per onfi timing parameters > > - add suffix nano second as timing unit > > - modified the clock names as per the IP spec > > --- > > .../bindings/memory-controllers/pl353-smc.txt | 53 ++++++++++++++++++++++ > > 1 file changed, 53 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/memory-controllers/pl353-smc.txt > > > > diff --git a/Documentation/devicetree/bindings/memory-controllers/pl353-smc.txt b/Documentation/devicetree/bindings/memory-controllers/pl353-smc.txt > > new file mode 100644 > > index 0000000..551e66b > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/memory-controllers/pl353-smc.txt > > @@ -0,0 +1,53 @@ > > +Device tree bindings for ARM PL353 static memory controller > > + > > +PL353 static memory controller supports two kinds of memory > > +interfaces.i.e NAND and SRAM/NOR interfaces. > > +The actual devices are instantiated from the child nodes of pl353 smc node. > > + > > +Required properties: > > +- compatible : Should be "arm,pl353-smc-r2p1" > > I thing Rob prefers: > > - compatible: Must be one of: > * arm, pl353-smc-r2p1 > > > +- reg : Controller registers map and length. > > +- clock-names : List of input clock names - "ref_clk", "aper_clk" > > + (See clock bindings for details). > > +- clocks : Clock phandles (see clock bindings for details). > > +- address-cells : Address cells, must be 1. > > +- size-cells : Size cells. Must be 1. > > Please avoid padding, just this is enough: > > - something: And another thing. > > > + > > +Child nodes: > > + For NAND the "arm,pl353-nand-r2p1" and for NOR the "cfi-flash" drivers are > > +supported as child nodes. > > + > > +Mandatory timing properties for child nodes: > > +- arm,nand-cycle-t0 : Read cycle time(t_rc). > > +- arm,nand-cycle-t1 : Write cycle time(t_wc). > > +- arm,nand-cycle-t2 : re_n assertion delay(t_rea). > > +- arm,nand-cycle-t3 : we_n de-assertion delay(t_wp). > > +- arm,nand-cycle-t4 : Status read time(t_clr) > > +- arm,nand-cycle-t5 : ID read time(t_ar) > > +- arm,nand-cycle-t6 : busy to re_n(t_rr) > > I think this has nothing to do in the DT, you should handle timings > from the ->setup_data_interface() hook. If you need, you may use > different compatibles to distinguish different platform data. Actually these are NAND-chip dependant and should be derived from the timings given by the core in the SDR interface structure by ->setup_data_interface().