From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Kartik Babu <kbabu@automatika.com>
Subject: Re: dma_alloc_coherent
Date: Tue, 04 Apr 2006 17:45:57 -0600 [thread overview]
Message-ID: <44330535.2070803@shaw.ca> (raw)
In-Reply-To: <5XY8B-82x-1@gated-at.bofh.it>
Kartik Babu wrote:
> I'm trying to replace consistent_alloc in a driver that was written for
> the 2.4 kernel with dma_alloc_coherent. My question is that I do not use
> a struct device * pointer at all. Browsing through the source for the
> 2.6.12
> on ARM XScale PXA255, I see that this argument may be NULL.
>
> Still, I'd like to know if passing NULL has any side effects. If so,
> what are they?
>
> I do however have a cdev structure taht I use for device registration,
> but I do not see how that would help.
What kind of a device is it? If it's a PCI device, the struct device can
be accessed with the dev pointer inside the struct pci_dev.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-04-04 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5XY8B-82x-1@gated-at.bofh.it>
2006-04-04 23:45 ` Robert Hancock [this message]
2006-04-05 14:12 ` dma_alloc_coherent Kartik Babu
2016-02-08 4:01 dma_alloc_coherent Vishwas Srivastava
2016-02-08 6:24 ` dma_alloc_coherent Ran Shalit
2016-02-08 6:59 ` dma_alloc_coherent Saumendra Dash
2016-02-08 10:35 ` dma_alloc_coherent sanjeev sharma
-- strict thread matches above, loose matches on Subject: below --
2016-02-05 8:53 dma_alloc_coherent Ran Shalit
2016-02-05 9:15 ` dma_alloc_coherent Denis Kirjanov
2016-02-06 19:22 ` dma_alloc_coherent Ran Shalit
2011-10-12 18:17 dma_alloc_coherent bob jonny
2011-10-13 4:24 ` dma_alloc_coherent rohan puri
2006-04-04 18:07 dma_alloc_coherent Kartik Babu
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=44330535.2070803@shaw.ca \
--to=hancockr@shaw.ca \
--cc=kbabu@automatika.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.