From: leilk.liu@mediatek.com (leilk liu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173
Date: Fri, 15 May 2015 15:38:42 +0800 [thread overview]
Message-ID: <1431675522.2128.13.camel@mhfsdcap03> (raw)
In-Reply-To: <20150512160540.GB3066@sirena.org.uk>
Dear Mark,
Thanks for your reply.
On Tue, 2015-05-12 at 17:05 +0100, Mark Brown wrote:
> On Tue, May 12, 2015 at 08:39:16PM +0800, leilk liu wrote:
> > On Fri, 2015-05-08 at 18:53 +0100, Mark Brown wrote:
> > > On Fri, May 08, 2015 at 04:55:42PM +0800, leilk.liu at mediatek.com wrote:
>
> > Could you tell me more details about "You should also be using the core
> > helpers for DMA mapping"?
>
> Implement can_dma() - look for drivers providing that for examples.
>
MTK spi hardware uses the dmaengine in spi controller. According to
datasheet, spi driver just need to enable dma register bit and write a
physical address to relevant dma address register, so I think it may be
complex while the driver supports can_dma.
> > > > +static const struct of_device_id mtk_spi_of_match[] = {
> > > > + { .compatible = "mediatek,mt6589-spi", .data = (void *)COMPAT_MT6589},
> > > > + { .compatible = "mediatek,mt8173-spi", .data = (void *)COMPAT_MT8173},
> > > > + {}
> > > > +};
> > > > +MODULE_DEVICE_TABLE(of, mtk_spi_of_match);
>
> > > There were three compatible strings listed in the DT binding but only
> > > two here.
>
> > MT6589 and MT8135 is compatible;
> > For MT8135 IC, it can use the follow way in dts to probe:
> > compatible = "mediatek,mt8135-spi",
> > "mediatek,mt6589-spi";
>
> > And I test it's ok on MT8135 platform. So I add struct of_device_id
> > mtk_spi_of_match like this in spi driver code.
>
> You should list all the compatibles documented in the binding here, if
> some of them are the same just have them map to a single constant.
next prev parent reply other threads:[~2015-05-15 7:38 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 [this message]
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
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=1431675522.2128.13.camel@mhfsdcap03 \
--to=leilk.liu@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).