From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: OMAP2+: gpmc: handle additional timings
Date: Thu, 14 Jun 2012 05:30:16 -0700 [thread overview]
Message-ID: <20120614123016.GN12766@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E999B34@DBDE01.ent.ti.com>
* Mohammed, Afzal <afzal@ti.com> [120614 05:25]:
> Hi Tony,
>
> On Thu, Jun 14, 2012 at 17:39:41, Mohammed, Afzal wrote:
> > On Thu, Jun 14, 2012 at 17:19:06, Tony Lindgren wrote:
>
> > > For onenand I'm getting the following error:
> > >
> > > omap2-onenand omap2-onenand: Cannot request GPMC CS
> >
> > I am a bit confused with this message, for onenand, we only have,
> >
> > pr_err("%s: Cannot request GPMC CS\n", __func__);
> >
> > dev_err is used only for nand
>
> This error can happen if my patches are not present,
>
> dev_err for onenand driver was removed by,
>
> [mtd: onenand: omap2: obtain memory from resource],
>
> seems, mtd patches are not in your present branch
OK, I'll try with those.
Tony
next prev parent reply other threads:[~2012-06-14 12:30 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 14:01 [PATCH 0/3] Prepare for GPMC driver conversion Afzal Mohammed
2012-06-11 14:01 ` [PATCH 1/3] ARM: OMAP2+: nand: unify init functions Afzal Mohammed
2012-06-11 15:43 ` Jon Hunter
2012-06-12 5:50 ` Mohammed, Afzal
2012-06-11 14:01 ` [PATCH 2/3] ARM: OMAP2+: onenand: cleanup for gpmc driver conversion Afzal Mohammed
2012-06-11 18:36 ` Jon Hunter
2012-06-12 6:16 ` Mohammed, Afzal
2012-06-12 17:30 ` Jon Hunter
2012-06-13 5:03 ` Mohammed, Afzal
2012-06-13 16:38 ` Jon Hunter
2012-06-14 5:40 ` Mohammed, Afzal
2012-06-14 17:53 ` Jon Hunter
2012-06-15 6:52 ` Mohammed, Afzal
2012-06-11 14:02 ` [PATCH 3/3] ARM: OMAP2+: gpmc: handle additional timings Afzal Mohammed
2012-06-11 18:49 ` Jon Hunter
2012-06-12 6:37 ` Mohammed, Afzal
2012-06-12 17:36 ` Jon Hunter
2012-06-13 4:56 ` Mohammed, Afzal
2012-06-13 11:32 ` Tony Lindgren
2012-06-13 11:54 ` Tony Lindgren
2012-06-13 11:58 ` Mohammed, Afzal
2012-06-14 10:10 ` Mohammed, Afzal
2012-06-14 10:19 ` Tony Lindgren
2012-06-14 10:39 ` Mohammed, Afzal
2012-06-14 11:49 ` Tony Lindgren
2012-06-14 11:59 ` Mohammed, Afzal
2012-06-14 12:09 ` Mohammed, Afzal
2012-06-14 12:21 ` Mohammed, Afzal
2012-06-14 12:30 ` Tony Lindgren [this message]
2012-06-14 11:52 ` Tony Lindgren
2012-06-14 11:56 ` Mohammed, Afzal
2012-06-14 12:29 ` Tony Lindgren
2012-06-14 12:53 ` Mohammed, Afzal
2012-06-14 16:53 ` Tony Lindgren
2012-06-15 5:42 ` Mohammed, Afzal
2012-06-15 6:16 ` Mohammed, Afzal
2012-06-15 10:45 ` Tony Lindgren
2012-06-15 10:49 ` Mohammed, Afzal
2012-06-13 12:34 ` Mohammed, Afzal
2012-06-13 12:42 ` Tony Lindgren
2012-06-13 14:04 ` Mohammed, Afzal
2012-06-14 6:32 ` Tony Lindgren
2012-06-14 9:29 ` Tony Lindgren
2012-06-14 9:41 ` Mohammed, Afzal
2012-06-14 11:23 ` Tony Lindgren
2012-06-12 10:27 ` [PATCH 0/3] Prepare for GPMC driver conversion Mohammed, Afzal
2012-06-13 11:33 ` Tony Lindgren
2012-06-13 12:40 ` Mohammed, Afzal
2012-06-13 16:46 ` Jon Hunter
2012-06-14 5:58 ` Mohammed, Afzal
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=20120614123016.GN12766@atomide.com \
--to=tony@atomide.com \
--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).