From: Michael Buesch <mb@bu3sch.de>
To: sbrown@cortland.com
Cc: linux-mips@linux-mips.org
Subject: Re: Correct way to set coherent_dma_mask on a non-pci device?
Date: Tue, 8 Jul 2008 19:55:47 +0200 [thread overview]
Message-ID: <200807081955.47594.mb@bu3sch.de> (raw)
In-Reply-To: <4873A676.8050906@cortland.com>
On Tuesday 08 July 2008 19:40:06 Steve Brown wrote:
> There appears to be no function like pci_set_consistent_dma_mask to set
> the coherent mask for a non-pci device.
>
> What is the "proper" way to set it?
>
> The context for the question is a recent change to ssb_dma_set_mask() in
> drivers/ssb/main.c that removed the somewhat fragile, direct
> manipulation of dma_mask and coherent_dma_mask in favor of a call to
> dma_set_mask().
Note that SSB devices use the dma_*** API for doing DMA remappings.
So it uses dma_set_mask() for setting the mask.
--
Greetings Michael.
next prev parent reply other threads:[~2008-07-08 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 17:40 Correct way to set coherent_dma_mask on a non-pci device? Steve Brown
2008-07-08 17:55 ` Michael Buesch [this message]
2008-07-10 17:38 ` Steve 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=200807081955.47594.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-mips@linux-mips.org \
--cc=sbrown@cortland.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