From: David Brownell <david-b@pacbell.net>
To: Feng Tang <feng.tang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>,
"spi-devel-list" <spi-devel-general@lists.sourceforge.net>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH v5] serial: spi: add spi-uart driver for Maxim 3110
Date: Tue, 2 Mar 2010 23:25:52 -0800 [thread overview]
Message-ID: <201003022325.52315.david-b@pacbell.net> (raw)
In-Reply-To: <20100303143731.0c009c64@feng-i7>
On Tuesday 02 March 2010, Feng Tang wrote:
> > > Here comes another idea, can we add a capability flag in struct
> > > spi_master indicating the master supporting poll or dma or both.
> > > Also we add similar bits in struct spi_transfer indicating the this
> > > transfer wants to be handled in poll or dma mode.
> >
> > Let's not do either of those. There's no need to introduce such
> > complexity, or to enable the associated new failure modes and bugs.
>
> This idea has nothing to do with the dma-safe problem you pointed out,
Your comment has nothing to do with my response. Are you implying that
your suggestions do *NOT* introduce complexity, including new failure
modes and thus the possibility of new confusing types of bugs?
> I will
> make the buffer dma safe anyway.
Good ...
> What I proposed just wants to provide some flexibility for protocol device
> drivers, it will use dma-safe buffer always, but it prefer not to use DMA
> for its one-word transfers,
That kind of heuristic is something the SPI controller driver could
already apply if it's a good tradeoff on that hardware. (Considering
also the extra added complexity, failure modes, and potential for new
flavors of bug...)
Of course, drivers like the max3110 are high enough in the driver
stack that they can only guess about such tradeoffs. (And thus
most drivers will likely guess wrong...)
> and hope to have a choice to do that. For current
> existing controller and device drivers, they can simply ignore the new
> working mode setting in struct spi_master and spi_transfer and leave them
> as 0.
If someone decided to update a SPI controller driver to avoid DMA in
some cases, in favor of PIO, they could already code such heuristics
without needing your proposed hinting from upper layers.
The result in the low-level driver would be just to use a different
test (maybe "is this a one-word transfer?" instead of checking your
per-transfer "use PIO?" hint) before kicking in whatever logic you
think would improve performance (by eliminating DMA setup and teardown
costs, including cache cleaning).
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-03 7:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091229222006.1ddb28a4@feng-desktop>
2009-12-29 14:59 ` [spi-devel-general] [RFC][PATCH] serial: spi: add spi-uart driver for Maxim 3110 Baruch Siach
2009-12-29 16:05 ` Tang, Feng
2009-12-29 18:43 ` Erwin Authried
2009-12-30 1:54 ` Feng Tang
2010-02-25 4:47 ` David Brownell
2010-02-25 7:49 ` Feng Tang
2009-12-29 15:02 ` Alan Cox
2010-02-08 8:59 ` [RFC][PATCH v2] " Feng Tang
[not found] ` <20100208165946.0e4dde83@feng-i7>
2010-02-09 0:20 ` Andrew Morton
2010-02-09 0:26 ` Grant Likely
2010-02-09 1:36 ` Feng Tang
2010-02-17 22:58 ` Greg KH
2010-02-24 5:11 ` [RFC][PATCH v3] " Feng Tang
2010-02-24 10:44 ` Alan Cox
2010-02-24 14:25 ` Grant Likely
2010-02-24 23:18 ` Andrew Morton
2010-02-25 6:39 ` Feng Tang
2010-02-25 4:43 ` David Brownell
2010-02-25 7:44 ` Feng Tang
2010-02-25 8:11 ` David Brownell
2010-02-26 3:47 ` [PATCH v4] " Feng Tang
[not found] ` <20100226114729.679bb933@feng-i7>
2010-02-26 9:59 ` Masakazu Mokuno
2010-02-26 19:41 ` David Brownell
2010-03-01 2:30 ` Feng Tang
2010-03-02 3:38 ` Feng Tang
2010-02-09 9:25 ` [RFC][PATCH v2] " Alan Cox
2010-03-03 2:57 ` [PATCH v5] " Feng Tang
2010-03-03 3:59 ` Grant Likely
2010-03-03 4:51 ` David Brownell
2010-03-03 5:52 ` Feng Tang
2010-03-03 6:16 ` David Brownell
2010-03-03 6:37 ` Feng Tang
2010-03-03 7:25 ` David Brownell [this message]
2010-03-03 7:42 ` Feng Tang
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=201003022325.52315.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=feng.tang@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=linux-serial@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).