From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1ghLlt-0003wH-OV for linux-mtd@lists.infradead.org; Wed, 09 Jan 2019 21:52:23 +0000 Date: Wed, 9 Jan 2019 22:52:08 +0100 From: Boris Brezillon To: Linus Walleij Cc: Boris Brezillon , Maxim Levitsky , Tudor Ambarus , Masahiro Yamada , Richard Weinberger , Marc Gonzalez , Janusz Krzysztofik , Stefan Agner , Marek Vasut , Harvey Hunt , linux-mtd@lists.infradead.org, Miquel Raynal , Han Xu , Xiaolei Li , Brian Norris , David Woodhouse Subject: Re: [PATCH v3 15/22] mtd: rawnand: fsmc: Stop implementing ->select_chip() Message-ID: <20190109225208.47d95771@bbrezillon> In-Reply-To: References: <20181111075524.13123-1-boris.brezillon@bootlin.com> <20181111075524.13123-16-boris.brezillon@bootlin.com> <20190109204441.6aeab463@bbrezillon> <20190109215443.67cec30c@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 9 Jan 2019 22:30:18 +0100 Linus Walleij wrote: > On Wed, Jan 9, 2019 at 9:54 PM Boris Brezillon wrote: > > [Me] > > > I guess that is normal for FSMC: only one CS. It seems a bit > > > aggressive to toggle CS on/off between every command like this, > > > I suspect the FSMC isn't really built for that but shakes apart > > > or something. > > > > Hm, that would be weird. There's indeed timing constraints on the NAND > > chip side, but none infringing those constraints should not trigger an > > external abort exception. > > The manual contains this (the same bit, just another name than > in the driver): > > PBKEN PC-card/NAND-Flash chip-select enable. > Enables the corresponding chip-select. > If a disabled chip-select is accessed, an HRESP = ERROR is generated > on the AHB bus. > 0: disabled (default after reset) > 1: enabled It's still not clear what this bit does. Do you have access to the CS pin on the board? > > > Can you check which phys range is remapped at > > 0xcc960000? > > No idea how to do that but I'll see if I can figure it out... print the __iomem values returned by devm_ioremap_resource() and find the one that matches this address.