From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] GPMI-NAND: Define ecc.strength
Date: Mon, 21 May 2012 05:43:45 +0200 [thread overview]
Message-ID: <201205210543.45682.marex@denx.de> (raw)
In-Reply-To: <4FB9AC27.2050207@freescale.com>
Dear Huang Shijie,
> Hi Marek:
> > On Mon, May 21, 2012 at 03:36:41AM +0200, Marek Vasut wrote:
> >> Dear Shawn Guo,
> >>
> >>> So non-DT probe has the same issue? Or this is a DT probe only issue?
> >>
> >> I started using DT, so I'm now fixing everything to work like it used
> >> to. Damn this DT conversion broke about everything.
> >
> > So you are saying the issue is introduced by gpmi-nand DT conversion?
>
> thanks for your work. :)
> But the gpmi nand driver should not work right now.
Why not? I tested, I could at least read stuff from it.
> The DT for gpmi-nand is in Artem's l2-mtd tree.
> And the device node item in DTS for gpmi is not added now.( I ever
> submitted, but not accepted.)
Well I crafted one myself, I need different pinmux settings anyway so I added my
own pinmux configuration.
> Also the pinctrl item for gpmi is also not added not.
>
> So I suggest you test it again when the next merge window opens, and all
> the code is merged to kernel.
Please ... Shawn explained that this bug will still be there. So why not get it
in early to fix bug asap. I'll resend to artem now.
> If the bug still exits, please submit a fix patch then.
>
> By the way, I really did not meet your error when I test the DT patches
> for gpmi.
Can you post your snippet?
> thanks
> Huang Shijie
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-05-21 3:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 1:02 [PATCH 1/4] GPMI-NAND: Define ecc.strength Marek Vasut
2012-05-21 1:02 ` [PATCH 2/4] GPMI-NAND: Fixup compile issue Marek Vasut
2012-05-21 1:16 ` Shawn Guo
2012-05-21 1:02 ` [PATCH 3/4] MXS-MMC: Move of_match_table out of CONFIG_PM Marek Vasut
2012-05-21 4:09 ` Shawn Guo
2012-05-21 3:52 ` Chris Ball
2012-05-21 4:33 ` Marek Vasut
2012-05-21 1:02 ` [PATCH 4/4] MXS-MMC: Add wp-inverted property Marek Vasut
2012-05-21 1:39 ` Shawn Guo
2012-05-21 2:38 ` Marek Vasut
2012-05-21 2:48 ` Shawn Guo
2012-05-21 3:22 ` Chris Ball
2012-05-21 3:36 ` Marek Vasut
2012-05-21 7:22 ` Lothar Waßmann
2012-05-21 17:38 ` Marek Vasut
2012-05-21 1:14 ` [PATCH 1/4] GPMI-NAND: Define ecc.strength Shawn Guo
2012-05-21 1:36 ` Marek Vasut
2012-05-21 1:41 ` Shawn Guo
2012-05-21 2:40 ` Marek Vasut
2012-05-21 3:08 ` Huang Shijie
2012-05-21 3:48 ` Marek Vasut
2012-05-21 3:45 ` Shawn Guo
2012-05-21 3:39 ` Marek Vasut
2012-05-21 2:44 ` Huang Shijie
2012-05-21 3:43 ` Marek Vasut [this message]
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=201205210543.45682.marex@denx.de \
--to=marex@denx.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).