Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Eddie Huang <eddie.huang@mediatek.com>
Cc: "Leilk Liu (刘磊)" <Leilk.Liu@mediatek.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will.deacon@arm.com>,
	"HongZhou Yang" <hongzhou.yang@mediatek.com>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	srv_heupstream <srv_heupstream@mediatek.com>
Subject: Re: [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173
Date: Wed, 17 Jun 2015 17:35:31 +0100	[thread overview]
Message-ID: <20150617163531.GU14071@sirena.org.uk> (raw)
In-Reply-To: <1434550251.23617.38.camel@mtksdaap41>

[-- Attachment #1: Type: text/plain, Size: 1800 bytes --]

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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-06-17 16:35 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-NuS5LvNUpcJWk0Htik3J/w
     [not found] ` <1431075343-7887-1-git-send-email-leilk.liu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-05-08  8:55   ` [PATCH 1/3] dt-bindings: ARM: Mediatek: Document devicetree bindings for spi bus leilk.liu-NuS5LvNUpcJWk0Htik3J/w
2015-05-08  8:55   ` [PATCH 3/3] arm64: dts: Add spi bus dts leilk.liu-NuS5LvNUpcJWk0Htik3J/w
2015-05-08  8:55 ` [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173 leilk.liu
     [not found]   ` <1431075343-7887-3-git-send-email-leilk.liu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-05-08 17:53     ` Mark Brown
2015-05-12 12:39       ` leilk liu
2015-05-12 16:05         ` Mark Brown
     [not found]           ` <20150512160540.GB3066-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
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
     [not found]                 ` <20150515092543.GY2761-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-08 10:15                   ` Eddie Huang
2015-06-08 17:59                     ` Mark Brown
     [not found]                       ` <20150608175927.GO14071-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-09 10:05                         ` Eddie Huang
2015-06-09 10:39                           ` Mark Brown
     [not found]                             ` <20150609103951.GA14071-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-10  8:06                               ` Eddie Huang
2015-06-17  9:08                                 ` Eddie Huang
2015-06-17 12:47                                   ` Mark Brown
     [not found]                                     ` <20150617124758.GE3214-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-17 14:10                                       ` Eddie Huang
2015-06-17 16:35                                         ` Mark Brown [this message]
     [not found]                                           ` <20150617163531.GU14071-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-18  8:11                                             ` Eddie Huang

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=20150617163531.GU14071@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Leilk.Liu@mediatek.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eddie.huang@mediatek.com \
    --cc=galak@codeaurora.org \
    --cc=hongzhou.yang@mediatek.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=srv_heupstream@mediatek.com \
    --cc=will.deacon@arm.com \
    /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