Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3040059ybz; Mon, 27 Apr 2020 08:57:22 -0700 (PDT) X-Google-Smtp-Source: APiQypIYFrCyScXFxO0bNcrmQPeDm1dKitENBpo59ZoyEoOOaDJZ8kR/Xq3HITGyKo3CU7tOd8GJ X-Received: by 2002:a50:ee0e:: with SMTP id g14mr19423356eds.34.1588003042272; Mon, 27 Apr 2020 08:57:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588003042; cv=none; d=google.com; s=arc-20160816; b=vLHEckzu9rq8iNfG3nJYU4L2j9WFwsOcKpK1MlRXDINBQaziCG+wEDM7H4W/l2LSKf uLmhPLIvQxG1/ufIW4mthfgZ+f/oJhUYhK2sLC0aG409cs9CwTbskJc9fStYuuvg4LTY kdASvD7yekPdZK8k2NjxA1xNcAPkDyAZ5bFS6c/UH+P+0hldC8xGnoc1oHfvFel8d2Gi thdfGgMh3zhHaNhyyhVC56iAymDgZgDDYB1mxIdt0+J13ixtWdLVainH0+L4ip+AIpPu w6etBMTI12NXGHx2QQQuTRDt3sDpcaRxwqTDstsdBqyu0PlKJJ5QUH9u7JPjbibvKo2Z p2ag== 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=C8Qw2RuQ2fNQph5bCPnhf99DaDf4lTkQOH3WQB3yVLg=; b=wGgJMgLVMb+8STbUcnSDzZXsmA20IwcgGB+pC+fsjHHYD4+UQsNmO3HsjcnG0NFBKd GVdNKCB0yT+DCgF5HgANBhNb0wtUfI4igId1ht9KxE9Kx7ai4lOjmGLzkxz/TTNtV6Y0 5+zy8Dy4WsXOrRMsN2J07hXSH0W0k+yWZLX/9cbEx56j3G6dZhVRkbCtm+3meOHwvT/f jgWtWAIQMNfw8UisRbqePA1zgS61YajC2fNzKOT+e4rosAceyVXnerxJk4bPfQJiu//G ONrIyKbHq/shXK6aSH8OGBQDx6XvCGkMqtTQh1EBsuRXtwkeYfCgp/PnI/qErIsbZh89 xVNg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k9si5336edj.96.2020.04.27.08.56.58; Mon, 27 Apr 2020 08:57:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728536AbgD0Pvg convert rfc822-to-8bit (ORCPT + 99 others); Mon, 27 Apr 2020 11:51:36 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:35021 "EHLO relay12.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726185AbgD0Pvf (ORCPT ); Mon, 27 Apr 2020 11:51:35 -0400 Received: from xps13 (unknown [91.224.148.103]) (Authenticated sender: miquel.raynal@bootlin.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 43A08200005; Mon, 27 Apr 2020 15:51:29 +0000 (UTC) Date: Mon, 27 Apr 2020 17:51:27 +0200 From: Miquel Raynal To: Boris Brezillon Cc: "Ramuthevar, Vadivel MuruganX" , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, cheol.yong.kim@intel.com, hauke.mehrtens@intel.com, qi-ming.wu@intel.com, anders.roxell@linaro.org, vigneshr@ti.com, arnd@arndb.de, richard@nod.at, brendanhiggins@google.com, linux-mips@vger.kernel.org, robh+dt@kernel.org, tglx@linutronix.de, masonccyang@mxic.com.tw, andriy.shevchenko@intel.com Subject: Re: [PATCH v3 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Message-ID: <20200427175127.0518c193@xps13> In-Reply-To: <20200424183612.4cfdbb6a@collabora.com> References: <20200423162113.38055-1-vadivel.muruganx.ramuthevar@linux.intel.com> <20200423162113.38055-3-vadivel.muruganx.ramuthevar@linux.intel.com> <20200424183612.4cfdbb6a@collabora.com> Organization: Bootlin X-Mailer: Claws Mail 3.17.4 (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 Ramuthevar, > > +static int ebu_nand_probe(struct platform_device *pdev) > > +{ > > + struct device *dev = &pdev->dev; > > + struct ebu_nand_controller *ebu_host; > > + struct nand_chip *nand; > > + phys_addr_t nandaddr_pa; > > + struct mtd_info *mtd; > > + struct resource *res; > > + int ret; > > + u32 cs; > > + > > + ebu_host = devm_kzalloc(dev, sizeof(*ebu_host), GFP_KERNEL); > > + if (!ebu_host) > > + return -ENOMEM; > > + > > + ebu_host->dev = dev; > > + nand_controller_init(&ebu_host->controller); > > + > > + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "ebunand"); > > + ebu_host->ebu_addr = devm_ioremap_resource(&pdev->dev, res); > > + if (IS_ERR(ebu_host->ebu_addr)) > > + return PTR_ERR(ebu_host->ebu_addr); > > + > > + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "hsnand"); > > + ebu_host->nand_addr = devm_ioremap_resource(&pdev->dev, res); > > + if (IS_ERR(ebu_host->nand_addr)) > > + return PTR_ERR(ebu_host->nand_addr); > > + > > + ret = device_property_read_u32(dev, "nand,cs", &cs); > > CS ids should be encoded in the reg property (see [1]). Is it your choice to only support a single CS or is it actually a controller limitation? If the latter, it would be much better I think to anticipate the addition of the support for another CS. And in this case there are many places in this driver that should be more generic. > > + if (ret) { > > + dev_err(dev, "failed to get chip select: %d\n", ret); > > + return ret; > > + } > > + > > + ebu_host->cs = cs; > > + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "nand_cs0"); Thanks, Miquèl