From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>, Afzal Mohammed <afzal@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Igor Grinberg <grinberg@compulab.co.il>
Subject: Re: [PATCH 3/3] omap3 nand : use NAND_BUSWIDTH_AUTO
Date: Thu, 22 Nov 2012 18:48:33 +0100 [thread overview]
Message-ID: <50AE6571.5030100@parrot.com> (raw)
In-Reply-To: <1353054136.3618.2.camel@sauron.fi.intel.com>
Artem Bityutskiy a écrit :
> On Tue, 2012-11-06 at 10:40 -0800, Tony Lindgren wrote:
>>> Where such tree could be found ?
>> You should be able to use omap-for-v3.8/cleanup-headers-gpmc
>> branch as a base for your patches [1].
>
> Is this a stable branch which I may pull into l2-mtd.git? Then I could
> merge Matthieu's patches.
>
patch 1 and 2 are not controller dependent.
I added the support for the omap controller because I can easily test on it (and
beagleboard got a x16 onfi flash).
What a shame that omap workflow is so complex :
- I think Artem want support for at least one controller before merging generic code
- I can rebase on omap-for-v3.8/cleanup-headers-gpmc, but this is weird to add
generic code for nand that is not specific to omap on it ?
Matthieu
WARNING: multiple messages have this Message-ID (diff)
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>, Afzal Mohammed <afzal@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Igor Grinberg <grinberg@compulab.co.il>
Subject: Re: [PATCH 3/3] omap3 nand : use NAND_BUSWIDTH_AUTO
Date: Thu, 22 Nov 2012 18:48:33 +0100 [thread overview]
Message-ID: <50AE6571.5030100@parrot.com> (raw)
In-Reply-To: <1353054136.3618.2.camel@sauron.fi.intel.com>
Artem Bityutskiy a écrit :
> On Tue, 2012-11-06 at 10:40 -0800, Tony Lindgren wrote:
>>> Where such tree could be found ?
>> You should be able to use omap-for-v3.8/cleanup-headers-gpmc
>> branch as a base for your patches [1].
>
> Is this a stable branch which I may pull into l2-mtd.git? Then I could
> merge Matthieu's patches.
>
patch 1 and 2 are not controller dependent.
I added the support for the omap controller because I can easily test on it (and
beagleboard got a x16 onfi flash).
What a shame that omap workflow is so complex :
- I think Artem want support for at least one controller before merging generic code
- I can rebase on omap-for-v3.8/cleanup-headers-gpmc, but this is weird to add
generic code for nand that is not specific to omap on it ?
Matthieu
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2012-11-22 17:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 10:51 [PATCH 1/3] mtd nand : onfi need to be probed in 8 bits mode Matthieu CASTET
2012-11-06 10:51 ` Matthieu CASTET
2012-11-06 10:51 ` [PATCH 2/3] mtd nand : add NAND_BUSWIDTH_AUTO to autodetect bus width Matthieu CASTET
2012-11-06 10:51 ` Matthieu CASTET
2012-11-30 13:21 ` Artem Bityutskiy
2012-11-30 13:21 ` Artem Bityutskiy
2012-11-06 10:51 ` [PATCH 3/3] omap3 nand : use NAND_BUSWIDTH_AUTO Matthieu CASTET
2012-11-06 10:51 ` Matthieu CASTET
2012-11-06 12:37 ` Igor Grinberg
2012-11-06 12:37 ` Igor Grinberg
2012-11-06 16:47 ` Matthieu CASTET
2012-11-06 16:47 ` Matthieu CASTET
2012-11-06 18:40 ` Tony Lindgren
2012-11-06 18:40 ` Tony Lindgren
2012-11-16 8:22 ` Artem Bityutskiy
2012-11-16 8:22 ` Artem Bityutskiy
2012-11-22 17:48 ` Matthieu CASTET [this message]
2012-11-22 17:48 ` Matthieu CASTET
2012-12-03 10:20 ` [PATCH 1/3] mtd nand : onfi need to be probed in 8 bits mode Artem Bityutskiy
2012-12-03 10:20 ` Artem Bityutskiy
2012-12-24 0:29 ` Paul Walmsley
2012-12-24 0:29 ` Paul Walmsley
2013-01-02 9:51 ` Matthieu CASTET
2013-01-02 9:51 ` Matthieu CASTET
2013-01-03 17:10 ` Paul Walmsley
2013-01-03 17:10 ` Paul Walmsley
2013-01-16 14:28 ` Matthieu CASTET
2013-01-16 14:28 ` Matthieu CASTET
2013-01-16 17:15 ` Paul Walmsley
2013-01-16 17:15 ` Paul Walmsley
2013-01-22 2:27 ` Paul Walmsley
2013-01-22 2:27 ` Paul Walmsley
2013-02-06 23:21 ` Paul Walmsley
2013-02-06 23:21 ` Paul Walmsley
2013-02-07 9:47 ` Matthieu CASTET
2013-02-07 9:47 ` Matthieu CASTET
2013-03-01 14:02 ` Matthieu CASTET
2013-03-01 14:02 ` Matthieu CASTET
2013-04-02 18:28 ` Paul Walmsley
2013-04-02 18:28 ` Paul Walmsley
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=50AE6571.5030100@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=afzal@ti.com \
--cc=dedekind1@gmail.com \
--cc=grinberg@compulab.co.il \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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.