From: David Brown <davidb@codeaurora.org>
To: Mateusz Krawczuk <willingmagic@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: Onenand support in msm7227
Date: Fri, 23 Dec 2011 19:50:17 -0800 [thread overview]
Message-ID: <20111224035017.GA12653@codeaurora.org> (raw)
In-Reply-To: <CAF6ky88OoMTs4CaxKTnUnpsfFN-q_E94sRTLQwtCJWrpE26WNQ@mail.gmail.com>
On Fri, Dec 23, 2011 at 02:04:10PM +0100, Mateusz Krawczuk wrote:
> I want ask for any help with developing onenand driver.
>
> I tried generic onenand driver, but without success. Kernel module
> was loaded and did nothing or kernel was crashing, and other strange
> things.
I doubt the generic onenand driver will ever work on MSM. The MSM
doesn't allow read/write access to the onenand device, it must go
through the NAND controller.
> I also tried use msm-nand but when I use msm-nand from code-aurora
> kernel crash/panic and get rebooted. When I use msm-nand from htc
> kernel source I'm getting invalid num_resources or this:
>
> [ 22.129249] msm_nand_probe: phys addr 0xa0a00000
> [ 22.129278] msm_nand_probe: dmac 0x7
> [ 22.129339] msm_nand_probe: allocated dma buffer at ffc4c000,
> dma_addr 27294000
>
> with my modification for onenand .
You shouldn't need any modification to the code-aurora msm-nand driver
to support onenand. Have you tried it unmodified?
The MSM NAND controller's support for onenand is very different from
most. The NAND controller tries to make the onenand device look like
a NAND device.
The upstream kernel doesn't have any support yet for the NAND/onenand
controller.
BTW, if you are an MSM customer, I highly recommend using the support
channels, since you will get much better support that way.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-12-24 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF6ky8--joqeeOn+Hn4cgZsgCNuTvgLc2BvGDiiiGW6bcykkcg@mail.gmail.com>
2011-12-23 13:04 ` Onenand support in msm7227 Mateusz Krawczuk
2011-12-24 3:50 ` David Brown [this message]
2012-08-16 18:18 ` Mateusz Krawczuk
2012-08-17 0:00 ` David Brown
2012-08-17 5:29 ` Mateusz Krawczuk
2012-08-17 6:56 ` Pankaj Jangra
[not found] ` <CAF6ky8845Mnsce3Q+vqJG8K_vAU72V+5QO4rBoVwF=jxYWuxxQ@mail.gmail.com>
2012-08-17 11:43 ` Fwd: " Mateusz Krawczuk
2012-08-17 15:29 ` David Brown
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=20111224035017.GA12653@codeaurora.org \
--to=davidb@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=willingmagic@gmail.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 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).