mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Does pci_map_single magicly work on > 32 bit address for 32bit capable device?
Date: Fri, 11 Dec 2009 23:39:42 +0200	[thread overview]
Message-ID: <1260567582.5983.23.camel@maxim-laptop> (raw)

Hi,

I am writing a driver, and I am faced with following problem:

I receive a kernel pointer, and I want device to dma into that memory.
However, device is only capable of 32 bit dma.

I can create a 'consistent' mapping and use memcpy from/to it, but it
feels like waste of performance.


According to Documentation/DMA-mapping.txt, I can tell that hw supports
32 bit dma using pci_set_dma_mask, however, what will happen if I pass
arbitrary kernel address into pci_map_single.
What will happen if the address is above 32 bit?

I tried to follow source of pci_map_single, but it is quite strongly
buried.
Also note that I don't need any scatter gather lists, because buffer
will always be 512 bytes long.


Note that I don't write the block driver itself, but a small driver that
plugs into that driver.
I am writing a driver for mtd subsystem and more precisely a nand
driver.

Unfortunately mtd system can call the driver with arbitrary kernel
pointer, although I am sure its not vmalloc'ed.
Usually it passes the pointer that is received from block subsystem.



Thanks in advance,
Maxim Levitsky


             reply	other threads:[~2009-12-11 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 21:39 Maxim Levitsky [this message]
2009-12-12  0:07 ` Robert Hancock
2009-12-12  0:18   ` Maxim Levitsky
2009-12-12  0:38     ` Robert Hancock
2009-12-21 19:48       ` Maxim Levitsky

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=1260567582.5983.23.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®