From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra 2 T20 NAND Flash Support
Date: Sat, 03 Jan 2015 23:33:25 -0700 [thread overview]
Message-ID: <54A8DEB5.4030208@wwwdotorg.org> (raw)
In-Reply-To: <1420314624.2169.6.camel@lynxeye.de>
On 01/03/2015 12:50 PM, Lucas Stach wrote:
> Am Mittwoch, den 04.06.2014, 19:32 +0200 schrieb Lucas Stach:
>> Am Mittwoch, den 04.06.2014, 16:41 +0200 schrieb Thierry Reding:
>>> On Wed, Jun 04, 2014 at 09:23:22AM +0200, Marcel Ziswiler wrote:
>>>> On 06/04/2014 09:18 AM, Lucas Stach wrote:
>>>>> I took the Linux Tegra NAND driver from Thierry and cleaned it up quite
>>>>> a bit. It now works with both ONFI and non-ONFI NAND, at least for
>>>>> reading. Writing doesn't quite work yet and I've got side-tracked with
>>>>> other stuff.
>>>>>
>>>>> If you are interested in moving this forward I can put up my WIP patches
>>>>> to some public location.
>>>>
>>>> Sounds great, yes. That would be perfect, thanks.
>>>>
>>>> We even once got an universal NAND test infrastructure from Micron based on
>>>> a re-worked Colibri T20 which we could use to validate it with various NAND
>>>> flash parts.
>>>
>>> Excellent, I would've had a hard time digging up those patches. It's
>>> really been quite a while.
>>>
>> I've put up a rebased version of the patches at
>>
>> git://git.pengutronix.de/git/lst/linux.git tegra-nand
>>
> For those still interested:
> I've continued to work on this for the last few days and pushed a new
> version of my WIP to the above location.
>
> It is now in a state where the in-kernel mtd tests seem to be happy with
> it. Also creating/using a filesystem on top of the mtdblock device seems
> to work properly.
>
> I still need to validate that anything using the OOB areas is working
> properly. The last missing feature is BCH ECC support, but that should
> be easy to add.
>
> I don't know if it still needs some performance tuning. 5MB/s write and
> 12,5MB/s read on a Colibri T20 seem pretty slow me, but I have nothing
> to compare with ATM.
> Marcel could you maybe dig out some benchmarks with L4T?
That sounds pretty similar to the eMMC on devices of that age (at least
with the upstream drivers that don't support fast transfer modes) so
it's probably not bad...
prev parent reply other threads:[~2015-01-04 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 1:00 Tegra 2 T20 NAND Flash Support Marcel Ziswiler
2014-06-04 7:18 ` Lucas Stach
2014-06-04 7:23 ` Marcel Ziswiler
2014-06-04 14:41 ` Thierry Reding
2014-06-04 17:32 ` Lucas Stach
2015-01-03 19:50 ` Lucas Stach
2015-01-04 6:33 ` Stephen Warren [this message]
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=54A8DEB5.4030208@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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).