* i.MX6S/GPMI-NAND issue on 3.5.4
@ 2012-09-21 18:29 Vikram Narayanan
2012-10-08 2:51 ` Huang Shijie
2012-10-08 4:02 ` Fabio Estevam
0 siblings, 2 replies; 4+ messages in thread
From: Vikram Narayanan @ 2012-09-21 18:29 UTC (permalink / raw)
To: Huang Shijie, linux-mtd; +Cc: dedekind1
Hello,
I'm facing some issue with GPMI-NAND driver on i.MX6 solo.
I've a TOSHIBA 4KiB page NAND connected to the GPMI.
(4KiB + 128 bytes OOB)
I tested it using the following,
1) U-boot v2012.04
2) Freescale's U-boot for i.MX6
3) Freescale's Kernel 3.0.15
Result: 0x98 0xAC 0x90 0x26 (Correct)
4) Linux v3.5.4 stable
Result: 0x98 0xA8 0x90 0x20 (Incorrect)
When I issue a READID command, 1, 2 & 3 gives me correct results,
whereas the 3.5.4 version gives me some different result.
Any help would be very much appreciated.
Regards,
Vikram
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: i.MX6S/GPMI-NAND issue on 3.5.4
2012-09-21 18:29 i.MX6S/GPMI-NAND issue on 3.5.4 Vikram Narayanan
@ 2012-10-08 2:51 ` Huang Shijie
2012-10-08 16:44 ` Vikram Narayanan
2012-10-08 4:02 ` Fabio Estevam
1 sibling, 1 reply; 4+ messages in thread
From: Huang Shijie @ 2012-10-08 2:51 UTC (permalink / raw)
To: Vikram Narayanan; +Cc: linux-mtd, dedekind1
于 2012年09月22日 02:29, Vikram Narayanan 写道:
> Hello,
>
> I'm facing some issue with GPMI-NAND driver on i.MX6 solo.
Does the MX6Q solo support the NAND?
I have the solo board in my hand. But it can not support the NAND.
You make the board yourself?
If so, please check the pinmux for solo.
thanks
Huang Shijie
> I've a TOSHIBA 4KiB page NAND connected to the GPMI.
> (4KiB + 128 bytes OOB)
>
> I tested it using the following,
>
> 1) U-boot v2012.04
> 2) Freescale's U-boot for i.MX6
> 3) Freescale's Kernel 3.0.15
> Result: 0x98 0xAC 0x90 0x26 (Correct)
>
> 4) Linux v3.5.4 stable
> Result: 0x98 0xA8 0x90 0x20 (Incorrect)
>
> When I issue a READID command, 1, 2 & 3 gives me correct results,
> whereas the 3.5.4 version gives me some different result.
>
> Any help would be very much appreciated.
>
> Regards,
> Vikram
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: i.MX6S/GPMI-NAND issue on 3.5.4
2012-10-08 2:51 ` Huang Shijie
@ 2012-10-08 16:44 ` Vikram Narayanan
0 siblings, 0 replies; 4+ messages in thread
From: Vikram Narayanan @ 2012-10-08 16:44 UTC (permalink / raw)
To: Huang Shijie; +Cc: linux-mtd, dedekind1
On 10/8/2012 8:21 AM, Huang Shijie wrote:
> 于 2012年09月22日 02:29, Vikram Narayanan 写道:
>> Hello,
>>
>> I'm facing some issue with GPMI-NAND driver on i.MX6 solo.
> Does the MX6Q solo support the NAND?
Yes. i.Mx6Solo supports NAND.
> I have the solo board in my hand. But it can not support the NAND.
>
> You make the board yourself?
> If so, please check the pinmux for solo.
Yeah I figured out that pinctrl driver was the problem.Anyway thanks for
the pointing it out.
Regards,
Vikram
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: i.MX6S/GPMI-NAND issue on 3.5.4
2012-09-21 18:29 i.MX6S/GPMI-NAND issue on 3.5.4 Vikram Narayanan
2012-10-08 2:51 ` Huang Shijie
@ 2012-10-08 4:02 ` Fabio Estevam
1 sibling, 0 replies; 4+ messages in thread
From: Fabio Estevam @ 2012-10-08 4:02 UTC (permalink / raw)
To: Vikram Narayanan; +Cc: Huang Shijie, linux-mtd, dedekind1
Hi Vikram,
On Fri, Sep 21, 2012 at 3:29 PM, Vikram Narayanan <vikram186@gmail.com> wrote:
> Hello,
>
> I'm facing some issue with GPMI-NAND driver on i.MX6 solo.
> I've a TOSHIBA 4KiB page NAND connected to the GPMI.
> (4KiB + 128 bytes OOB)
Can you please post your mx6sl dts patches? This would help us to
identify the problem.
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-10-08 16:44 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-21 18:29 i.MX6S/GPMI-NAND issue on 3.5.4 Vikram Narayanan
2012-10-08 2:51 ` Huang Shijie
2012-10-08 16:44 ` Vikram Narayanan
2012-10-08 4:02 ` Fabio Estevam
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox