linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mnalajal@codeaurora.org (Murali Nalajala)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/2] mtd: msm_nand: Add initial msm nand driver support.
Date: Tue, 26 Apr 2011 18:27:35 +0530	[thread overview]
Message-ID: <4DB6C13F.2020402@codeaurora.org> (raw)
In-Reply-To: <4DABE8FE.5040300@parrot.com>

On 4/18/2011 1:02 PM, Matthieu CASTET wrote:
> Hi,
>
> Murali Nalajala a ?crit :
>> Add initial msm nand driver support for Qualcomm MSM platforms.
>> This driver is capable of handling both 2k and 4k page support
>> nand devices.
>>
>> This driver was originally developed by Arve Hj?nnev?g at google.
>> Its source is available at
>> http://android.git.kernel.org/?p=kernel/msm.git under
>> android-msm-2.6.35 branch.
>>
>> CC: Dima Zavin<dima@android.com>
>> CC: Brian Swetland<swetland@google.com>
>> CC: Arve Hj?nnev?g<arve@android.com>
>> Signed-off-by: Murali Nalajala<mnalajal@codeaurora.org>
>> ---
>> Changes in V2
>> * Turn most of the pr_info() calls into pr_debug().
>>
>>   drivers/mtd/devices/Kconfig    |   11 +
>>   drivers/mtd/devices/Makefile   |    1 +
>>   drivers/mtd/devices/msm_nand.c | 1597 ++++++++++++++++++++++++++++++++++++++++
>>   drivers/mtd/devices/msm_nand.h |   77 ++
>>   4 files changed, 1686 insertions(+), 0 deletions(-)
>>   create mode 100644 drivers/mtd/devices/msm_nand.c
>>   create mode 100644 drivers/mtd/devices/msm_nand.h
>>
>
> For the record, I am not sure it is a great idea to make nand drivers
> independent of the nand layer.
> By doing that you could change the expected behavior, and introduce bug
> difficult to debug.
>
> Why do you need that ? Nand drivers can override callbacks of nand framework.
>
> Maybe because the nand layer call the driver page per page, and  you want to
> work with more than one page. But in this case you can extend nand layer.
>
> Or does your controller don't allow sending raw command ?
> And in that case all the nand logic is in the nand controller ?

Our controller doesn't allow sending RAW commands to the flash. All 
these commands are abstracted by the controller logic. Please refer the 
msm_nand.h file where you will find the commands which are different 
from the actual NAND device commands.

eg: To send read/write data command to the device we configure the 
controller with page address & controller specific command. Then the 
controller itself takes care of generating the internal h/w signals 
required by the flash and it polls for the R/B signal & wait states are 
internally controlled by the h/w.

>
> Matthieu



Thanks,
Murali N

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  parent reply	other threads:[~2011-04-26 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 16:50 [PATCH V2 2/2] mtd: msm_nand: Add initial msm nand driver support Murali Nalajala
2011-04-18  7:32 ` Matthieu CASTET
2011-04-18  7:56   ` Artem Bityutskiy
2011-04-26 12:57   ` Murali Nalajala [this message]
2011-04-27 12:38     ` Matthieu CASTET
2011-04-27 16:04       ` Murali Nalajala
2011-04-27 17:36         ` 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=4DB6C13F.2020402@codeaurora.org \
    --to=mnalajal@codeaurora.org \
    --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).