From: James Bottomley <James.Bottomley@steeleye.com>
To: Jeremy Higdon <jeremy@sgi.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Proposal for new generic device API: dma_get_required_mask()
Date: 18 Jun 2004 09:19:00 -0500 [thread overview]
Message-ID: <1087568345.2135.10.camel@mulgrave> (raw)
In-Reply-To: <20040618055909.GA13007@sgi.com>
On Fri, 2004-06-18 at 00:59, Jeremy Higdon wrote:
> Sounds good. But I'm curious why you make the driver call dma_set_mask()
> twice.
Basically so that dma_get_required_mask() returns a value that may be
related to the current mask. If the device has a wierd mask setting
(say it has bits missing or something), the platform may want to return
something different to tune the required mask to be optimal.
James
next prev parent reply other threads:[~2004-06-18 14:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 14:08 Proposal for new generic device API: dma_get_required_mask() James Bottomley
2004-06-17 14:51 ` Meelis Roos
2004-06-17 15:28 ` Matthew Wilcox
2004-06-17 20:12 ` James Bottomley
2004-06-18 0:46 ` Krzysztof Halasa
2004-06-18 1:45 ` James Bottomley
2004-06-18 23:07 ` Krzysztof Halasa
2004-06-19 15:00 ` James Bottomley
2004-06-19 23:39 ` Krzysztof Halasa
2004-06-20 16:56 ` James Bottomley
2004-06-18 9:21 ` Russell King
2004-06-18 23:10 ` Krzysztof Halasa
2004-06-19 20:22 ` Russell King
2004-06-20 0:00 ` Krzysztof Halasa
2004-06-20 19:47 ` Russell King
2004-06-23 19:32 ` Krzysztof Halasa
2004-06-18 5:59 ` Jeremy Higdon
2004-06-18 14:19 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 14:52 Salyzyn, Mark
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=1087568345.2135.10.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=jeremy@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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