From: Tim Sander <tim@krieglstein.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: mtd raw nand denali.c broken for Intel/Altera Cyclone V
Date: Fri, 06 Sep 2019 14:38:23 +0200 [thread overview]
Message-ID: <5143724.5TqzkYX0oI@dabox> (raw)
Hi
I have noticed that there multiple breakages piling up for the denali nand
driver on the Intel/Altera Cyclone V. Unfortunately i had no time to track the
mainline kernel closely. So the breakage seems to pile up. I am a little
disapointed that Intel is not on the lookout that the kernel works on the
chips they are selling. I was really happy about the state of the platform
before concerning mainline support.
The failure starts with kernel 4.19 or stable kernel release 4.18.19. The
commit is ba4a1b62a2d742df9e9c607ac53b3bf33496508f. The problem here is that
our platform works with a zero in the SPARE_AREA_SKIP_BYTES register. But in
this case the patch assumes the default value 8 which is straight out wrong
on this variant. Without this patch reverted all blocks of the nand flash are
beeing marked bad :-(.
When reverting the patch ba4a1b62a2d742df9e9c607ac53b3bf33496508f i can boot
4.19.10 again.
With 5.0 the it goes further down the drain and i didn't manage to boot it
even with the above patch reverted.
I also tried 5.3-rc7 with the above patch reverted and the variable t_x dirty hacked to the
value 0x1388 as i got the impression that the timing calculation is off too. I still get an
interrupt error and boot failure:
[ 0.817588] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 0.823946] nand: Micron MT29F2G08ABAEAWP
[ 0.827965] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.887052] denali-nand-dt ff900000.nand: timeout while waiting for irq 0x1000
[ 2.911056] denali-nand-dt ff900000.nand: timeout while waiting for irq 0x1000
I have seen this https://lore.kernel.org/patchwork/patch/983055/ thread and
this might fix at least the 4.19 boot problem.
I would be really happy for hints how to get the Intel Cyclone V working again.
Best regards
Tim
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2019-09-06 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 12:38 Tim Sander [this message]
2019-09-10 7:16 ` mtd raw nand denali.c broken for Intel/Altera Cyclone V Masahiro Yamada
2019-09-10 13:48 ` Tim Sander
2019-09-10 15:22 ` Dinh Nguyen
2019-09-11 2:37 ` Masahiro Yamada
2019-09-11 7:27 ` Tim Sander
2019-09-26 9:10 ` Tim Sander
2019-09-26 17:47 ` Masahiro Yamada
2020-01-10 16:46 ` Tim Sander
2020-01-10 17:13 ` Marek Vasut
2020-01-10 19:05 ` Masahiro Yamada
2020-01-10 22:38 ` Tim Sander
2020-01-11 2:38 ` Masahiro Yamada
2020-01-13 10:22 ` Tim Sander
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=5143724.5TqzkYX0oI@dabox \
--to=tim@krieglstein.org \
--cc=computersforpeace@gmail.com \
--cc=dinguyen@kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yamada.masahiro@socionext.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).