From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] dmaengine: add new dma API for max_segment_number
Date: Wed, 8 Jun 2011 21:41:27 +0100 [thread overview]
Message-ID: <20110608204127.GC13151@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTikFKr+3Qph+CR40SUV-DCir1v=KBg@mail.gmail.com>
On Wed, Jun 08, 2011 at 01:05:57PM -0700, Dan Williams wrote:
> Even if that were the case it would be same situation that the scsi device
> driver reports maximum parameters, but the subsystem opts for
> something tighter. Whether the maximal parameters come from the scsi
> device or the dma channel is moot.
Except for the small issue that many DMA-engine using devices do not
have _any_ DMA capabilities of their own, which means they don't have
anything to put in their own struct device's DMA parameters. We can't
go around making up random insane parameters in the hope that they'll
exceed whatever DMA-engine is being used with the device - that's a
hack not a solution.
next prev parent reply other threads:[~2011-06-08 20:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 7:30 [PATCH v2 1/3] dmaengine: add new dma API for max_segment_number Shawn Guo
2011-06-06 7:30 ` [PATCH v2 2/3] dmaengine: mxs-dma: set up max_segment_number Shawn Guo
2011-06-06 7:30 ` [PATCH v2 3/3] mmc: mxs-mmc: call dmaengine API to set mmc->max_segs Shawn Guo
2011-06-06 8:06 ` [PATCH v2 1/3] dmaengine: add new dma API for max_segment_number FUJITA Tomonori
2011-06-06 9:14 ` Russell King - ARM Linux
2011-06-06 9:41 ` FUJITA Tomonori
2011-06-06 9:47 ` Russell King - ARM Linux
2011-06-06 10:12 ` FUJITA Tomonori
2011-06-06 10:15 ` Russell King - ARM Linux
2011-06-06 18:48 ` Dan Williams
2011-06-08 5:23 ` FUJITA Tomonori
2011-06-08 6:56 ` Dan Williams
2011-06-08 7:10 ` FUJITA Tomonori
2011-06-08 20:05 ` Dan Williams
2011-06-08 20:41 ` Russell King - ARM Linux [this message]
2011-06-08 21:52 ` Dan Williams
2011-06-09 0:07 ` FUJITA Tomonori
2011-06-07 22:35 ` Dan Williams
2011-06-12 15:28 ` Shawn Guo
2011-06-15 12:08 ` [PATCH v3] " Shawn Guo
2011-06-15 16:25 ` FUJITA Tomonori
2011-06-16 9:54 ` Per Forlin
2011-06-16 12:30 ` [PATCH v3 RESEND] dma-mapping: add new " Shawn Guo
2011-06-17 12:40 ` Matthew Wilcox
2011-06-17 18:09 ` Per Forlin
2011-06-21 17:44 ` FUJITA Tomonori
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=20110608204127.GC13151@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).