From: eddie.huang@mediatek.com (Eddie Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173
Date: Thu, 18 Jun 2015 16:11:47 +0800 [thread overview]
Message-ID: <1434615107.22739.1.camel@mtksdaap41> (raw)
In-Reply-To: <20150617163531.GU14071@sirena.org.uk>
On Wed, 2015-06-17 at 17:35 +0100, Mark Brown wrote:
> On Wed, Jun 17, 2015 at 10:10:51PM +0800, Eddie Huang wrote:
>
> > Our hardware limitation is: we don't have separate dma tx, rx channel
> > with transfer finish interrupt, only have spi trigger operation.So the
> > mediatek SPI dma full duplex operation steps are:
> > 1. Set TX DMA address.
> > 2. Set RX DMA address.
> > 3. Set length (this step assume TX, RX are the same size).
> > 4. Set TX DMA enable, RX DMA enable bit in spi config register. (not
> > trigger DMA, just told spi use dma)
> > 5. Trigger spi operations.
> > 6. Wait spi operations finish interrupt.
>
> Sure, that's what I understood.
>
> > If tx scatterlist per list data size are 128, 4096, 256. rx scatterlist
> > per list data size are 128, 4096, 256. So we need to go through above
> > steps three times. If tx scatterlists per list data size are 128, 4096,
> > 256. rx scatterlists per list data size are 256, 4096, 128. If we start
> > sending first entry, tx size is 128, rx size is 256, this will cause
> > hardware malfunction because tx, rx data length are not the same.
>
> > The solution I think is copy scatterlist data into one single buffer in
> > mediatek spi transfer function, but I think this is odd because
> > __spi_map_msg() map single buffer into scatterlist, then our driver map
> > scatterlist into single buffer again. I hope this explaination is more
> > clear than before.
>
> To repeat what I said in my last mail: there's no need to use the
> scatterlists as-is, your driver can do whatever set of DMA transfers it
> likes to keep the lengths of each transfer the same. Attempting to
> linearise the transfers in memory isn't going to work unless you
> allocate physically contiguous memory (which could get painful) and will
> add substantial overhead.
>
> For example with your above example you could split the transfers up to
> be 128, 128, 3968, 128, 128.
This is a workable way.
Thanks your suggestion.We will try to implement this,
Eddie
Thanks
next prev parent reply other threads:[~2015-06-18 8:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 8:55 Add Mediatek SPI driver leilk.liu at mediatek.com
2015-05-08 8:55 ` [PATCH 1/3] dt-bindings: ARM: Mediatek: Document devicetree bindings for spi bus leilk.liu at mediatek.com
2015-05-08 8:55 ` [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173 leilk.liu at mediatek.com
2015-05-08 17:53 ` Mark Brown
2015-05-12 12:39 ` leilk liu
2015-05-12 16:05 ` Mark Brown
2015-05-13 9:26 ` Yingjoe Chen
2015-05-13 11:10 ` Mark Brown
2015-05-13 13:58 ` Yingjoe Chen
2015-05-15 7:38 ` leilk liu
2015-05-15 9:25 ` Mark Brown
2015-06-08 10:15 ` Eddie Huang
2015-06-08 17:59 ` Mark Brown
2015-06-09 10:05 ` Eddie Huang
2015-06-09 10:39 ` Mark Brown
2015-06-10 8:06 ` Eddie Huang
2015-06-17 9:08 ` Eddie Huang
2015-06-17 12:47 ` Mark Brown
2015-06-17 14:10 ` Eddie Huang
2015-06-17 16:35 ` Mark Brown
2015-06-18 8:11 ` Eddie Huang [this message]
2015-05-08 8:55 ` [PATCH 3/3] arm64: dts: Add spi bus dts leilk.liu at mediatek.com
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=1434615107.22739.1.camel@mtksdaap41 \
--to=eddie.huang@mediatek.com \
--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