[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Jun 2016 00:06:45 +0300
From: Aleksei Mamlin <mamlinav@...il.com>
To: Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc: Maxime Ripard <maxime.ripard@...e-electrons.com>,
Chen-Yu Tsai <wens@...e.org>,
Richard Weinberger <richard@....at>,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-sunxi@...glegroups.com
Subject: Re: [PATCH 5/7] mtd: nand: Add Hynix H27UBG8T2BTR-BC to nand_ids
table
On Mon, 6 Jun 2016 22:31:38 +0200
Boris Brezillon <boris.brezillon@...e-electrons.com> wrote:
> On Mon, 6 Jun 2016 22:59:03 +0300
> Aleksei Mamlin <mamlinav@...il.com> wrote:
>
> > On Mon, 6 Jun 2016 20:55:49 +0200
> > Boris Brezillon <boris.brezillon@...e-electrons.com> wrote:
> >
> > > On Mon, 6 Jun 2016 13:24:22 +0300
> > > Aleksei Mamlin <mamlinav@...il.com> wrote:
> > >
> > > > Add the full description of the Hynix H27UBG8T2BTR-BC NAND chip in the
> > > > nand_ids table so that we can later use the NAND ECC infos and ONFI timings
> > > > mode in controller drivers.
> > >
> > > Still hoping to get this series [1] merged in 4.8, but if that's
> > > not the case, I'll apply your patch.
> > >
> > > BTW, that would be great if you could test it on your platforms.
> > >
> >
> > It seems that Hynix-specific initialization code can't handle H27UBG8T2BTR-BC
> > chip:
> >
> > [ 0.886153] nand: Could not find valid ONFI parameter page; aborting
> > [ 0.892665] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xd7
> > [ 0.899025] nand: Hynix 1c03000.nand
> > [ 0.902596] nand: bus width 8 instead 16 bit
> > [ 0.906858] nand: No NAND device found
> > [ 0.910620] sunxi_nand 1c03000.nand: failed to init nand chips
> > [ 0.916528] sunxi_nand: probe of 1c03000.nand failed with error -22
>
> Can you try this patch? It should fix the problem [1].
>
> [1]http://code.bulix.org/6hjww1-100494
>
Yes, it fixes problem. What about ONFI parameter page? Should it be ignored?
[ 0.886068] nand: Could not find valid ONFI parameter page; aborting
[ 0.892571] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xd7
[ 0.898917] nand: Hynix NAND 4GiB 3,3V 8-bit
[ 0.903198] nand: 4096 MiB, MLC, erase size: 2048 KiB, page size: 8192, OOB size: 640
[ 0.911908] Bad block table found at page 524032, version 0x01
[ 0.918534] Bad block table found at page 523776, version 0x01
[ 0.972112] 5 ofpart partitions found on MTD device 1c03000.nand
[ 0.978116] Creating 5 MTD partitions on "1c03000.nand":
[ 0.983477] 0x000000000000-0x000000200000 : "boot0"
[ 0.988803] 0x000000200000-0x000000400000 : "boot0-rescue"
[ 0.994692] 0x000000400000-0x000000600000 : "uboot"
[ 0.999944] 0x000000600000-0x000000800000 : "uboot-rescue"
[ 1.005763] 0x000000800000-0x000100000000 : "main"
>
> --
> Boris Brezillon, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
--
Thanks and regards,
Aleksei Mamlin
Powered by blists - more mailing lists