Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2819449imm; Mon, 24 Sep 2018 10:24:49 -0700 (PDT) X-Google-Smtp-Source: ACcGV61ProjoH4tPSA2s3nayUYqmiKB67ASa2J9m0rmMbvyCQH636jnLkyJkuWuhx2+/jo8MMDls X-Received: by 2002:a17:902:f096:: with SMTP id go22mr11807040plb.183.1537809889474; Mon, 24 Sep 2018 10:24:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537809889; cv=none; d=google.com; s=arc-20160816; b=p+O544CtYt5Ka1WC0cbAfQ5Ykas+mCIvfv60q48+zGQ5FqK0ClBZPjpFUXVhMxPsxV uSg1FWSM1RY3VeOrlQDZd1kEPux7V1cwLcGbfoHvBZGC6MH6JmfBxdV0FodiOiQqPnSF 6qJPP/gehVkajhoJucYMsnhiZ7aPUg1SWAlfYtVlbXr7thVwj2lP8x8B0pmhHuJxcwVj 1vSij5cvFwipnjqkACx/MCBhFoE7UiGz9BVjqJnhm8We8MvQB1AjwMJz98UhG0oiC7X7 qiZsfWy3GpJxGuFXmCNbzFE7s0sKiO7VSlFOQFh7GlfjW/eyzkM9RdqJ1+rpvC6jjDhu 8YPw== 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 :references:in-reply-to:message-id:subject:cc:to:from:date; bh=PwvbKFvzAsMkHoNEZb+A2zOXw8NjCeT+b9MZUqv4AqQ=; b=U4+2cUEbQiW+Pv7nLiHXWKXoaNlLCfgZPLM6gKxM4yBA+ZqgjTXDNhM3u3D8udraRl J9/Gt99wFfCd9qEag7b6JVhVVFpPPLqiEepQ+LlSJgo9uCBP8Lgo13VbtIf7Eg67ADUv A79y4bIZG7zbXjIUTkTqlC/paoosCihBJnPmPpk158avqas25XdV5dHWXwRB+x9Uygzo UpjLgDW4ZZg44knnidqm0Y0FhSrMiYiAY5tElv2BLZQMc8jlCBiaaFgVKGRYZabe+leQ d4pxp7lTiF7Kg/iA3JMxs3tsWOWCsfbUFYSvkyC2nu96Q3Po/O4iSOGVDsqdGeFF+QMr 0YkA== 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 t190-v6si38219885pfb.344.2018.09.24.10.24.33; Mon, 24 Sep 2018 10:24:49 -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 S1731813AbeIXX1U (ORCPT + 99 others); Mon, 24 Sep 2018 19:27:20 -0400 Received: from mail.bootlin.com ([62.4.15.54]:46826 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726133AbeIXX1U (ORCPT ); Mon, 24 Sep 2018 19:27:20 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id B65F220731; Mon, 24 Sep 2018 19:24:06 +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 bbrezillon (91-160-177-164.subs.proxad.net [91.160.177.164]) by mail.bootlin.com (Postfix) with ESMTPSA id 7065720379; Mon, 24 Sep 2018 19:23:56 +0200 (CEST) Date: Mon, 24 Sep 2018 19:23:56 +0200 From: Boris Brezillon To: Cc: , , , , , , , , , , Subject: Re: [PATCH 2/3] mtd: rawnand: stm32_fmc2: add STM32 FMC2 NAND flash controller driver Message-ID: <20180924192356.5f2e56fd@bbrezillon> In-Reply-To: <1537199260-7280-3-git-send-email-christophe.kerello@st.com> References: <1537199260-7280-1-git-send-email-christophe.kerello@st.com> <1537199260-7280-3-git-send-email-christophe.kerello@st.com> 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 Christophe, On Mon, 17 Sep 2018 17:47:39 +0200 wrote: > +struct stm32_fmc2 { > + struct nand_chip chip; > + struct device *dev; > + void __iomem *io_base; > + void __iomem *data_base[FMC2_MAX_CE]; > + void __iomem *cmd_base[FMC2_MAX_CE]; > + void __iomem *addr_base[FMC2_MAX_CE]; > + phys_addr_t io_phys_addr; > + phys_addr_t data_phys_addr[FMC2_MAX_CE]; > + struct clk *clk; > + > + struct dma_chan *dma_tx_ch; > + struct dma_chan *dma_rx_ch; > + struct dma_chan *dma_ecc_ch; > + struct sg_table dma_data_sg; > + struct sg_table dma_ecc_sg; > + u8 *ecc_buf; > + int dma_ecc_len; > + > + struct completion complete; > + struct completion dma_data_complete; > + struct completion dma_ecc_complete; > + > + struct stm32_fmc2_timings timings; > + u8 cs_assigned; > + int cs_sel; > + int ncs; > + int cs_used[FMC2_MAX_CE]; > +}; Can we have a clear separation between the NAND controller and NAND chip structures. I know you only support a single chip per-controller right now, but I prefer to have things clearly separated from the beginning. Regards, Boris