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: Tue, 9 Jun 2015 18:05:21 +0800 [thread overview]
Message-ID: <1433844321.16178.6.camel@mtksdaap41> (raw)
In-Reply-To: <20150608175927.GO14071@sirena.org.uk>
Hi Mark,
On Mon, 2015-06-08 at 18:59 +0100, Mark Brown wrote:
> On Mon, Jun 08, 2015 at 06:15:46PM +0800, Eddie Huang wrote:
> > On Fri, 2015-05-15 at 17:25 +0800, Mark Brown wrote:
>
> > > That's how a very large proportion of devices that work with DMA are
> > > done - why would this be complicated? All can_dma() does is report if
> > > DMA is possible.
>
> > In include/linux/spi/spi.h, it describes if can_dma() exists and returns
> > true, dma_tx and dma_rx must be set.But Medaitek SPI controller has its
> > own dma hardware, which means this dma resides in the same base address
> > range with SPI controller, and only used by SPI, so we don't implement
> > generic DMA driver, such that can't provide dma channel and assign to
> > dmx_tx, dmx_rx parameter. We think it's strange to implement generic dma
> > driver for dma that only used by specific hardware.Can we just provide
> > can_dma() function and return false ? But I think it's a little odd that
> > there actually has dma. So can we just skip can_dma() function let it be
> > NULL ?
>
> If it's simply the unavailbility of a struct dma_chan we must be able to
> get a better solution than just open coding all the DMA mapping and
> unmapping in the driver. The only thing we actually use the channel for
> is to get the device we need to use to do the mapping and unmapping,
> either we need a way for devices to provide their own channels easily or
> a way for SPI drivers to specify a device here instead of a channel.
> The latter seems easier if a bit clunky (with having to work with both).
I list two ways you mention.
Pesudo code of your first suggestion:
static int mtk_spi_probe(struct platform_device *pdev) {
struct dma_chan *tx_chan;
struct dma_device *tx_dma;
tx_chan = devm_kzalloc(&pdev->dev, sizeof(*tx_chan), GFP_KERNEL);
tx_dma = devm_kzalloc(&pdev->dev, sizeof(*tx_dma), GFP_KERNEL);
tx_dma->dev = &pdev->dev;
tx_chan->device = tx_dma;
master->dma_tx = tx_chan;
...
}
Modification of your second suggestion:
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
@@ -539,8 +539,8 @@ static int __spi_map_msg(struct spi_master *master,
struct spi_message *msg)
if (!master->can_dma)
return 0;
- tx_dev = master->dma_tx->device->dev;
- rx_dev = master->dma_rx->device->dev;
+ tx_dev = master->dma_tx ? master->dma_tx->device->dev :
master->dev;
+ rx_dev = master->dma_rx ? master->dma_rx->device->dev : master-
Is this what you want ? Actually, I don't like first one at all.
Eddie
Thanks
next prev parent reply other threads:[~2015-06-09 10:05 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 [this message]
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
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=1433844321.16178.6.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;
as well as URLs for NNTP newsgroup(s).