From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 1/3] mtd nand : onfi need to be probed in 8 bits mode
Date: Wed, 16 Jan 2013 15:28:20 +0100 [thread overview]
Message-ID: <50F6B904.5000600@parrot.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301031704460.8721@utopia.booyaka.com>
Hi,
Paul Walmsley a écrit :
> Hi
>
> On Wed, 2 Jan 2013, Matthieu CASTET wrote:
> .... which did not get merged because Tony requested that it should be
> based on top of his cleanup work (which takes priority over adding new
> features):
>
> http://thread.gmane.org/gmane.linux.ports.arm.omap/88550/focus=88549
>
> Could you please update this "omap3 nand : use NAND_BUSWIDTH_AUTO" patch
> on v3.8-rc2 and repost?
Do you know when this patchset will be submited to mtd ?
I think I will wait it is merged in mtd and redo my patch after that.
>
>> For drivers that can't support ONFI, I don't know what to do.
>> May we should be replace the WARN_ON by a printk and early return.
>
> That sounds like a good idea to me. The traceback seems excessive, since
> the NAND was usable before this series.
>
I submited a patch for doing that.
Matthieu
WARNING: multiple messages have this Message-ID (diff)
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/3] mtd nand : onfi need to be probed in 8 bits mode
Date: Wed, 16 Jan 2013 15:28:20 +0100 [thread overview]
Message-ID: <50F6B904.5000600@parrot.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301031704460.8721@utopia.booyaka.com>
Hi,
Paul Walmsley a écrit :
> Hi
>
> On Wed, 2 Jan 2013, Matthieu CASTET wrote:
> .... which did not get merged because Tony requested that it should be
> based on top of his cleanup work (which takes priority over adding new
> features):
>
> http://thread.gmane.org/gmane.linux.ports.arm.omap/88550/focus=88549
>
> Could you please update this "omap3 nand : use NAND_BUSWIDTH_AUTO" patch
> on v3.8-rc2 and repost?
Do you know when this patchset will be submited to mtd ?
I think I will wait it is merged in mtd and redo my patch after that.
>
>> For drivers that can't support ONFI, I don't know what to do.
>> May we should be replace the WARN_ON by a printk and early return.
>
> That sounds like a good idea to me. The traceback seems excessive, since
> the NAND was usable before this series.
>
I submited a patch for doing that.
Matthieu
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-01-16 14:28 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
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 [this message]
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=50F6B904.5000600@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.