linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
	Roger Quadros <rogerq@ti.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v3 1/7] memory: omap-gpmc: Refactor OneNAND support
Date: Thu, 9 Nov 2017 19:10:04 +0100	[thread overview]
Message-ID: <20171109181004.g55vx4iveo5sulpt@lenoch> (raw)
In-Reply-To: <20171109175626.GD28152@atomide.com>

On Thu, Nov 09, 2017 at 09:56:26AM -0800, Tony Lindgren wrote:
> Hi,
> 
> * Ladislav Michl <ladis@linux-mips.org> [171109 09:14]:
> > Use generic probe function to deal with OneNAND node and remove now useless
> > gpmc_probe_onenand_child function.
> > Import sync mode timing calculation function from mach-omap2/gpmc-onenand.c
> > and prepare for MTD driver DTfication.
> 
> I tried giving this series a try on n900, but looks like onenand is no longer
> seen on n900 after this first patch.

This first patch makes original driver stop working as it removes special
OneNAND handling. If it doesn't work even after applying whole serie, then:
- verify onenand node has compatible 'ti,omap2-onenand' property
- verify timings

On IGEPv2 bootlog shows:
[    1.544464] omap-gpmc 6e000000.gpmc: GPMC revision 5.0
[    1.550415] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000
[    1.560485] omap2-onenand 30000000.onenand: initializing on CS0, phys base 0x30000000, virtual base e0080000
[    1.571014] Muxed OneNAND(DDP) 512MB 1.8V 16-bit (0x58)
[    1.576507] OneNAND version = 0x0031
[    1.583435] Scanning device for bad blocks
[    1.620971] OneNAND eraseblock 597 is an initial bad block
[    1.657470] OneNAND eraseblock 1159 is an initial bad block
[    1.754577] OneNAND eraseblock 2812 is an initial bad block
[    1.832214] omap2-onenand 30000000.onenand: optimized timings for 83 MHz
[    1.842620] 2 ofpart partitions found on MTD device 30000000.onenand
[    1.849426] Creating 2 MTD partitions on "30000000.onenand":
[    1.855651] 0x000000000000-0x000000080000 : "SPL"
[    1.863464] 0x000000080000-0x000020000000 : "UBI"

For a start:

diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index 4acd32a1c4ef..aa5b1a439564 100644
--- a/arch/arm/boot/dts/omap3-n900.dts
+++ b/arch/arm/boot/dts/omap3-n900.dts
@@ -838,6 +838,7 @@
 	onenand@0,0 {
 		#address-cells = <1>;
 		#size-cells = <1>;
+		compatible = "ti,omap2-onenand";
 		reg = <0 0 0x20000>;	/* CS0, offset 0, IO size 128K */
 
 		gpmc,sync-read;

  reply	other threads:[~2017-11-09 18:10 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09  9:11 [PATCH v3 0/7] OMAP2+ OneNAND driver update Ladislav Michl
2017-11-09  9:12 ` [PATCH v3 1/7] memory: omap-gpmc: Refactor OneNAND support Ladislav Michl
2017-11-09 17:56   ` Tony Lindgren
2017-11-09 18:10     ` Ladislav Michl [this message]
2017-11-09 18:26       ` Tony Lindgren
2017-11-09 18:34         ` Ladislav Michl
2017-11-09 18:48           ` Tony Lindgren
2017-11-09 19:10             ` Ladislav Michl
2017-11-09 21:59               ` Tony Lindgren
2017-11-09 22:26                 ` Ladislav Michl
2017-11-10  8:12             ` Roger Quadros
2017-11-09  9:13 ` [PATCH v3 2/7] mtd: onenand: omap2: Remove regulator support Ladislav Michl
2017-11-10  8:17   ` Roger Quadros
2017-11-09  9:14 ` [PATCH v3 3/7] mtd: onenand: omap2: Remove skip initial unlocking support Ladislav Michl
2017-11-10  8:18   ` Roger Quadros
2017-11-09  9:14 ` [PATCH v3 4/7] mtd: onenand: omap2: Remove partitioning support from platform data Ladislav Michl
2017-11-10  8:19   ` Roger Quadros
2017-11-10  9:48     ` Ladislav Michl
2017-11-09  9:15 ` [PATCH v3 5/7] mtd: onenand: omap2: Unify OMAP2 and OMAP3 DMA implementation Ladislav Michl
2017-11-10  8:21   ` Roger Quadros
2017-11-10  9:51     ` Ladislav Michl
2017-11-10 15:26       ` Tony Lindgren
2017-11-10 18:19         ` Ladislav Michl
2017-11-10 18:29           ` Tony Lindgren
2017-11-11 12:50             ` Ladislav Michl
2017-11-13 20:10               ` Peter Ujfalusi
2017-11-14 14:47               ` Roger Quadros
2017-11-14 15:03                 ` Ladislav Michl
2017-11-10  8:25   ` Peter Ujfalusi
2017-11-10 10:04     ` Ladislav Michl
2017-11-10 15:24       ` Tony Lindgren
2017-11-10 18:26         ` Ladislav Michl
2017-11-10 18:48           ` Tony Lindgren
2017-11-10 21:39         ` Ladislav Michl
2017-11-14 21:53           ` Tony Lindgren
2017-11-14 22:32             ` Ladislav Michl
2017-11-15  2:11               ` Tony Lindgren
2017-11-13  8:22         ` Peter Ujfalusi
2017-11-13 12:15           ` Ladislav Michl
2017-11-13 14:36             ` Peter Ujfalusi
2017-11-13 15:23               ` Tony Lindgren
2017-11-13 15:27               ` Ladislav Michl
2017-11-14 15:05                 ` Roger Quadros
2017-11-14 15:22                   ` Ladislav Michl
2017-11-09  9:16 ` [PATCH v3 6/7] mtd: onenand: omap2: Do not make delay for GPIO OMAP3 specific Ladislav Michl
2017-11-09  9:17 ` [PATCH v3 7/7] mtd: onenand: omap2: Configure driver from DT Ladislav Michl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171109181004.g55vx4iveo5sulpt@lenoch \
    --to=ladis@linux-mips.org \
    --cc=boris.brezillon@free-electrons.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@ti.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).