From: Huang Shijie <b32955@freescale.com>
To: Kamal Dasu <kdasu.kdev@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2] mtd: nand: Add support to use nand_base poi databuf as bounce buffer
Date: Mon, 28 Apr 2014 17:08:24 +0800 [thread overview]
Message-ID: <20140428090822.GA21064@localhost> (raw)
In-Reply-To: <CAC=U0a3_O2AHX8Y_gCxftkZjrH97U32=8ksLbaBTgTBPX7oWmg@mail.gmail.com>
On Fri, Apr 25, 2014 at 12:10:43PM -0400, Kamal Dasu wrote:
> Huang,
>
> "In the gpmi driver, i do a memcpy for the highmem buffer passed from
> upper layer."
>
> In other l2-mtd driver examples when the mapping fails those drivers
> are reverting to bouce buffering using kmall'd dma buffer and memcpy
> to highmem buffer. So the solutions have been implemented in the
> l2-mtd (lowest level nand controller) driver.
>
> In contrast this in change in nand_base uses the generic mm api
> virt_addr_valid() to check if the passed address is in highmem, and if
> it is I am not trying to convert(map) it, rather using the kmalloc'd
> databuf in nand_base and memcpy to/from the highmem buffer. Also
I think your idea is good. :)
If your patch can be merged to kernel, it mean the driver can always do the
DMA mapping sucessfully(Am i right?). And it makes the gpmi driver more simple.
See my comment in the orginal patch.
thanks
Huang Shijie
next prev parent reply other threads:[~2014-04-28 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 21:40 [PATCH v2] mtd: nand: Add support to use nand_base poi databuf as bounce buffer Kamal Dasu
2014-04-25 2:07 ` Huang Shijie
2014-04-25 3:52 ` Kamal Dasu
2014-04-25 7:43 ` Huang Shijie
2014-04-25 7:59 ` Huang Shijie
2014-04-25 16:10 ` Kamal Dasu
2014-04-28 9:08 ` Huang Shijie [this message]
2014-04-28 9:16 ` Huang Shijie
2014-04-28 15:42 ` Huang Shijie
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=20140428090822.GA21064@localhost \
--to=b32955@freescale.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-mtd@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