From: Feng Tang <feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Cc: alek.du-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: [PATCH v2 0/4] patch serie for dw_spi driver
Date: Wed, 30 Mar 2011 23:09:51 +0800 [thread overview]
Message-ID: <1301497795-6924-1-git-send-email-feng.tang@intel.com> (raw)
Hi all,
Alek Du made some optimization for the dw_spi driver, the original driver
will wait for non-busy state after every work of read/write. With these
patches, driver will read/write as much as possible data from/to the HW
FIFO. The DMA mode transfer is not affected at all. There is also some
minor code cleanup.
Pls help to review, thanks!
v2 change:
* fix a typo about bits_per_word checking
* re-generate the patches against v2.6.39-rc1
Thanks,
Feng
-------------------------
Alek Du (3):
spi/dw_spi: remove the un-necessary flush()
spi/dw_spi: change poll mode transfer from byte ops to batch ops
spi/dw_spi: improve the interrupt mode with the batch ops
Feng Tang (1):
spi/dw_spi: unify the low level read/write routines
drivers/spi/dw_spi.c | 202 ++++++++++++++++---------------------------------
drivers/spi/dw_spi.h | 2 -
2 files changed, 66 insertions(+), 138 deletions(-)
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
next reply other threads:[~2011-03-30 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 15:09 Feng Tang [this message]
[not found] ` <1301497795-6924-1-git-send-email-feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2011-03-30 15:09 ` [PATCH v2 1/4] spi/dw_spi: unify the low level read/write routines Feng Tang
[not found] ` <1301497795-6924-2-git-send-email-feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2011-03-31 3:32 ` Grant Likely
2011-03-30 15:09 ` [PATCH v2 2/4] spi/dw_spi: remove the un-necessary flush() Feng Tang
[not found] ` <1301497795-6924-3-git-send-email-feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2011-03-31 3:32 ` Grant Likely
2011-03-30 15:09 ` [PATCH v2 3/4] spi/dw_spi: change poll mode transfer from byte ops to batch ops Feng Tang
[not found] ` <1301497795-6924-4-git-send-email-feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2011-03-31 3:32 ` Grant Likely
2011-03-31 9:54 ` Alan Cox
[not found] ` <20110331105448.0f6d0bd4-Z/y2cZnRghHXmaaqVzeoHQ@public.gmane.org>
2011-03-31 12:54 ` Du, Alek
2011-03-31 13:13 ` Grant Likely
2011-04-25 7:46 ` Feng Tang
2011-04-25 8:54 ` Du, Alek
2011-03-30 15:09 ` [PATCH v2 4/4] spi/dw_spi: improve the interrupt mode with the " Feng Tang
[not found] ` <1301497795-6924-5-git-send-email-feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2011-03-31 3:32 ` Grant Likely
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=1301497795-6924-1-git-send-email-feng.tang@intel.com \
--to=feng.tang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=alek.du-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).