linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: GPMI-NAND Status?
Date: Tue, 9 Aug 2011 22:42:23 +0200	[thread overview]
Message-ID: <20110809204223.GA5858@pengutronix.de> (raw)
In-Reply-To: <4E4111F3.5070409@freescale.com>


> >>>Always reproducible by me when trying to format mtd0. Sometimes(always?) seen
> >>>by Koen during boot (on read?). Never seen by Huang? It is currently unclear if
> >>After I used a different .config, it never appears in my side.
> >So, you have a config which triggers this? That should be useful for
> >debugging. What do you need to enable to see this?
> >
> My old config is made by myself. I think it was a wrong config,

Let's see what the bug is in the end, but I don't think a config could be
"wrong" in a way to trigger such a bug. Even misconfiguration can be handled
gracefully with code.

> it's not a DMA bug, I discuss with Koen, and make sure that the bug is
> caused by the GPMI or BCH.

Did you get any further during this day?

> it's a different bug from  Aisheng Dong's bug.

Okay, I had a look at this one today.

> >>>* custom kernel command line parameters
> >>The kernel command line 'gpmi_nand' is to avoid the conflict with
> >>other modules such as
> >>SD.
> >>
> >>If it's be removed, I have to use different config to resolve the
> >>issue which is not better either. :(
> >This is a board-specific issue, so you should handle this at
> >board-level, not at driver level.
> >
> I wish to handle it at the board level.
> 
> But I have no idea how to solve the conflict between GPMI and SD.  :(
> 
> Could you give me some hint?

For starters, you could move some kerel-parameter to the board-file and create the
devices as needed depending on that:

if (gpmi_nand)
	mx28_add_gpmi_nand(&mx28evk_gpmi_nand_data);
else
	mx28_add_mxs_mmc(1, &mx28evk_mmc_pdata[1]);

or something alike unless I miss something. This is probably not the best
solution as well, but at least it keeps the driver free from the
board-configuration.

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110809/5fc77cd0/attachment.sig>

  reply	other threads:[~2011-08-09 20:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 13:51 GPMI-NAND Status? Wolfram Sang
2011-08-08  6:21 ` Huang Shijie
2011-08-08  9:19   ` Koen Beel
2011-08-08 10:37     ` Huang Shijie
2011-08-08 12:42       ` Koen Beel
2011-08-09  6:36         ` Huang Shijie
2011-08-09  7:58           ` Koen Beel
2011-08-09  8:18             ` Huang Shijie
2011-08-09  8:25               ` Koen Beel
2011-08-09  5:11     ` Huang Shijie
2011-08-09  6:25       ` Koen Beel
2011-08-09  6:40         ` Huang Shijie
2011-08-09  9:45     ` Wolfram Sang
2011-08-09  9:35   ` Wolfram Sang
2011-08-09 10:54     ` Huang Shijie
2011-08-09 20:42       ` Wolfram Sang [this message]
2011-08-08  9:12 ` Huang Shijie
2011-08-09  9:19   ` Wolfram Sang
2011-08-09 10:41     ` Huang Shijie
2011-08-09 11:36       ` Lothar Waßmann
2011-08-14  8:11 ` Ivan Djelic
2011-08-14 18:31   ` Wolfram Sang
2011-08-15  5:41   ` Lothar Waßmann
2011-08-15  6:30     ` Lin Tony-B19295
2011-08-15  8:41       ` Ivan Djelic
2011-08-15  8:29     ` Ivan Djelic
2011-08-15  9:31       ` Lothar Waßmann
2011-08-15 12:54         ` Ivan Djelic
2011-08-15 13:37           ` Lothar Waßmann
2011-08-15 16:34         ` Artem Bityutskiy
2011-08-15 16:18     ` Artem Bityutskiy
2011-08-15 16:22   ` Artem Bityutskiy
2011-08-15 16:57     ` Ivan Djelic

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=20110809204223.GA5858@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --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).