From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Aleksei Mamlin <mamlinav@gmail.com>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>, Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH 5/7] mtd: nand: Add Hynix H27UBG8T2BTR-BC to nand_ids table
Date: Mon, 6 Jun 2016 22:31:38 +0200 [thread overview]
Message-ID: <20160606223138.3c2032ee@bbrezillon> (raw)
In-Reply-To: <20160606225903.264abc01647eb1528cc226bd@gmail.com>
On Mon, 6 Jun 2016 22:59:03 +0300
Aleksei Mamlin <mamlinav@gmail.com> wrote:
> On Mon, 6 Jun 2016 20:55:49 +0200
> Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
>
> > On Mon, 6 Jun 2016 13:24:22 +0300
> > Aleksei Mamlin <mamlinav@gmail.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
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-06 20:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 10:24 [PATCH 0/7] dts: sunxi: Add sunxi NAND Flash Controller support Aleksei Mamlin
2016-06-06 10:24 ` [PATCH 1/7] ARM: dts: sun4i: Add A10 NAND controller pin definitions Aleksei Mamlin
2016-06-08 22:04 ` Maxime Ripard
2016-06-06 10:24 ` [PATCH 2/7] ARM: dts: sun4i: Add NFC node to Allwinner A10 SoC Aleksei Mamlin
2016-06-06 10:24 ` [PATCH 3/7] ARM: dts: sun7i: Add A20 NAND controller pin definitions Aleksei Mamlin
2016-06-06 10:24 ` [PATCH 4/7] ARM: dts: sun7i: Add NFC node to Allwinner A20 SoC Aleksei Mamlin
2016-06-07 17:21 ` Aleksei Mamlin
2016-06-06 10:24 ` [PATCH 5/7] mtd: nand: Add Hynix H27UBG8T2BTR-BC to nand_ids table Aleksei Mamlin
2016-06-06 18:55 ` Boris Brezillon
2016-06-06 19:59 ` Aleksei Mamlin
2016-06-06 20:31 ` Boris Brezillon [this message]
2016-06-06 21:06 ` Aleksei Mamlin
2016-06-07 5:48 ` Boris Brezillon
2016-06-07 5:49 ` Boris Brezillon
2016-06-06 10:24 ` [PATCH 6/7] ARM: dts: sun4i: Enable NAND on Marsboard A10 Aleksei Mamlin
2016-06-06 18:50 ` Boris Brezillon
2016-06-06 10:24 ` [PATCH 7/7] ARM: dts: sun7i: Enable NAND on Wexler TAB7200 Aleksei Mamlin
2016-06-06 18:51 ` Boris Brezillon
2016-06-08 22:03 ` Maxime Ripard
2016-06-09 8:11 ` Aleksei Mamlin
2016-06-10 8:56 ` Maxime Ripard
2016-06-14 11:17 ` [PATCH v2 0/4] dts: sunxi: Add sunxi NAND Flash Controller support Aleksei Mamlin
2016-06-14 11:17 ` [PATCH v2 1/4] ARM: dts: sun4i: Add A10 NAND controller pin definitions Aleksei Mamlin
2016-06-14 12:37 ` Maxime Ripard
2016-06-14 11:17 ` [PATCH v2 2/4] ARM: dts: sun4i: Add NFC node to Allwinner A10 SoC Aleksei Mamlin
2016-06-14 12:33 ` Maxime Ripard
2016-06-14 11:17 ` [PATCH v2 3/4] ARM: dts: sun7i: Add A20 NAND controller pin definitions Aleksei Mamlin
2016-06-14 11:17 ` [PATCH v2 4/4] ARM: dts: sun7i: Add NFC node to Allwinner A20 SoC Aleksei Mamlin
2016-06-14 12:33 ` Maxime Ripard
2016-06-14 13:11 ` kbuild test robot
2016-06-14 13:19 ` Aleksei Mamlin
2016-06-14 13:57 ` Maxime Ripard
2016-06-14 14:02 ` Aleksei Mamlin
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=20160606223138.3c2032ee@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mamlinav@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=richard@nod.at \
--cc=wens@csie.org \
/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).