From: Lucas Stach <dev@lynxeye.de>
To: Marcel Ziswiler <marcel@ziswiler.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Stefan Agner <stefan@agner.ch>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Tegra 2 T20 NAND Flash Support
Date: Wed, 04 Jun 2014 09:18:03 +0200 [thread overview]
Message-ID: <1401866283.2173.3.camel@tellur> (raw)
In-Reply-To: <538E6FB5.5020806@ziswiler.com>
Hi Marcel,
Am Mittwoch, den 04.06.2014, 03:00 +0200 schrieb Marcel Ziswiler:
> Sorry for referring to an old post of yours:
>
> > From: Thierry Reding <thierry.reding@...>
> > Subject: Re: [PATCH V5 7/9] ARM: dts: tegra: add non-removable and
> keep-power-in-suspend property for MMC
> > Date: 2013-04-03 05:45:49 GMT (1 year, 8 weeks, 5 days, 12 hours and
> 59 minutes ago)
> > ...
> > For Tegra20 Tamonten we don't use eMMC. Ideally we'd be using NAND to
> > boot from but that doesn't have mainline support. I have a semi-working
> > patch and will probably spend some more time getting it ready. The MMC
> > cards are all removable, though I guess since they are the boot device
> > they still should remain powered in suspend?
>
> You might have noticed our current effort in further mainlining
> Apalis/Colibri T30 module support. In the same respect we are looking at
> further improving Colibri T20 support. One of the major missing pieces
> is of course the NAND support you were mentioning in that 14 months old
> post. Have you by any chance made any progress on this? As me (on PXA)
> and Stefan (on Vybrid) do have quite some experience in the MTD NAND
> infrastructure there might be a chance for some joint effort in that
> respect. What do you think? Of course any other contribution/feedback is
> also most welcome.
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.
Regards,
Lucas
WARNING: multiple messages have this Message-ID (diff)
From: dev@lynxeye.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra 2 T20 NAND Flash Support
Date: Wed, 04 Jun 2014 09:18:03 +0200 [thread overview]
Message-ID: <1401866283.2173.3.camel@tellur> (raw)
In-Reply-To: <538E6FB5.5020806@ziswiler.com>
Hi Marcel,
Am Mittwoch, den 04.06.2014, 03:00 +0200 schrieb Marcel Ziswiler:
> Sorry for referring to an old post of yours:
>
> > From: Thierry Reding <thierry.reding@...>
> > Subject: Re: [PATCH V5 7/9] ARM: dts: tegra: add non-removable and
> keep-power-in-suspend property for MMC
> > Date: 2013-04-03 05:45:49 GMT (1 year, 8 weeks, 5 days, 12 hours and
> 59 minutes ago)
> > ...
> > For Tegra20 Tamonten we don't use eMMC. Ideally we'd be using NAND to
> > boot from but that doesn't have mainline support. I have a semi-working
> > patch and will probably spend some more time getting it ready. The MMC
> > cards are all removable, though I guess since they are the boot device
> > they still should remain powered in suspend?
>
> You might have noticed our current effort in further mainlining
> Apalis/Colibri T30 module support. In the same respect we are looking at
> further improving Colibri T20 support. One of the major missing pieces
> is of course the NAND support you were mentioning in that 14 months old
> post. Have you by any chance made any progress on this? As me (on PXA)
> and Stefan (on Vybrid) do have quite some experience in the MTD NAND
> infrastructure there might be a chance for some joint effort in that
> respect. What do you think? Of course any other contribution/feedback is
> also most welcome.
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.
Regards,
Lucas
next prev parent reply other threads:[~2014-06-04 7:18 UTC|newest]
Thread overview: 14+ 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 1:00 ` Marcel Ziswiler
2014-06-04 7:18 ` Lucas Stach [this message]
2014-06-04 7:18 ` Lucas Stach
2014-06-04 7:23 ` Marcel Ziswiler
2014-06-04 7:23 ` Marcel Ziswiler
[not found] ` <538EC96A.4050702-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>
2014-06-04 14:41 ` Thierry Reding
2014-06-04 14:41 ` Thierry Reding
2014-06-04 17:32 ` Lucas Stach
2014-06-04 17:32 ` Lucas Stach
2015-01-03 19:50 ` Lucas Stach
2015-01-03 19:50 ` Lucas Stach
[not found] ` <1420314624.2169.6.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-01-04 6:33 ` Stephen Warren
2015-01-04 6:33 ` Stephen Warren
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=1401866283.2173.3.camel@tellur \
--to=dev@lynxeye.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=marcel@ziswiler.com \
--cc=stefan@agner.ch \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.