From: "Du, Alek" <alek.du@intel.com>
To: "Tang, Feng" <feng.tang@intel.com>
Cc: "dirk.brandewie@gmail.com" <dirk.brandewie@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"alan@linux.intel.com" <alan@linux.intel.com>
Subject: Re: [PATCH 3/5] dw_spi: rework message processing
Date: Fri, 17 Jun 2011 09:34:26 +0800 [thread overview]
Message-ID: <20110617093426.40f0be34@dxy2> (raw)
In-Reply-To: <20110616220003.7ac89d56@feng-i7>
On Thu, 16 Jun 2011 22:00:03 +0800
"Tang, Feng" <feng.tang@intel.com> wrote:
> Hi Dirk,
>
> On Thu, 16 Jun 2011 01:23:06 +0800
> "dirk.brandewie@gmail.com" <dirk.brandewie@gmail.com> wrote:
>
> > From: Dirk Brandewie <dirk.brandewie@gmail.com>
> >
> > NOTE: patch created git format-patch --break-rewrites=/50%
> >
> > This patch reworks the message pump worker thread function to run
> > until all messages queued to the driver have been handled. The
> > function to handle individual spi_transfers is now a synchronus
> > function the tasklet to handle spi_transfers has been removed. Work
> > for the worker thread is only queued in host controller transfer
> > function.
> >
> > Psuedo code for new thread function:
> > message = get_message()
> > while (message){
> > for_each_transfer_in_msg(message){
> > transfer_setup(transfer)
> > do_transfer()
> > }
> > complete_message()
> > message = get_message()
> > }
> >
> > Changes that fell out of the message thread changes:
> > Non-DMA transfers that are larger than the size of the controller FIFO
> > are handled as interrupt driven transfers.
> >
> > Common FIFO handling functions shared PIO and interrupt transfers.
> >
> > Simplified queue stop/start funcitons.
> >
> > Cleanup fixes:
> > Changed exported all exported function names to have dw_spi_ prefix
> >
> > Removed support for registering chip select control function. Setting
> > the slave chip select is handled by setting the SER (Slave enable
> > register)
> >
Removing this, you already break the TI spi BT module which requires that it
controls the chip select instead of controller.
When TX FIFO empty (means TX draining fast) the CS pin will de-assert.
In order to support those spi slaves that cannot stand this, the chip
select control function callback was added to this driver. Please don't
break previous contribution please.
And again, it is meaningless to enable both TX and RX fifo threshold interrupts,
since they are connected in hardware.
Thanks,
Alek
next prev parent reply other threads:[~2011-06-17 1:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 17:23 [PATCH 0/5] Designware SPI driver update dirk.brandewie
2011-06-15 17:23 ` [PATCH 1/5] spi/makefile: Fix typo from reorganize drivers patch dirk.brandewie
2011-06-16 12:31 ` Grant Likely
2011-06-15 17:23 ` [PATCH 2/5] spi/dw_spi: expose dw_spi platform data stucture dirk.brandewie
2011-06-15 17:23 ` [PATCH 3/5] dw_spi: rework message processing dirk.brandewie
2011-06-16 13:14 ` Grant Likely
2011-06-16 16:03 ` Dirk Brandewie
2011-06-16 16:40 ` Grant Likely
2011-06-16 14:00 ` Feng Tang
2011-06-16 17:28 ` Dirk Brandewie
2011-06-16 17:38 ` Grant Likely
2011-06-16 19:52 ` Dirk Brandewie
2011-06-17 1:22 ` Feng Tang
2011-06-17 1:34 ` Du, Alek [this message]
2011-06-15 17:23 ` [PATCH 4/5] spi/spi-dw: update function naming convention dirk.brandewie
2011-06-16 13:15 ` Grant Likely
2011-06-15 17:23 ` [PATCH 5/5] spi_dw_pci: Add runtime power management dirk.brandewie
2011-06-16 13:16 ` 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=20110617093426.40f0be34@dxy2 \
--to=alek.du@intel.com \
--cc=alan@linux.intel.com \
--cc=dirk.brandewie@gmail.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@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