The Linux Kernel Mailing List
 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>,
	"Sascha Hauer" <kernel@pengutronix.de>
Subject: Re: [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173
Date: Tue, 9 Jun 2015 11:39:51 +0100	[thread overview]
Message-ID: <20150609103951.GA14071@sirena.org.uk> (raw)
In-Reply-To: <1433844321.16178.6.camel@mtksdaap41>

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

On Tue, Jun 09, 2015 at 06:05:21PM +0800, Eddie Huang wrote:

> --- 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.

Not quite what I'd been thinking of - we can't just pick the device in
the core safely, the device might be a MFD or have some other
restriction that needs us to use a separate struct device.  However most
of those cases are likely to point towards implementing a dmaengine
device so probably the above will work for most cases and is fine.  Can
you send a proper patch please?

Please don't use the ternery operator, though.

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

  reply	other threads:[~2015-06-09 10:40 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
2015-05-08  8:55 ` [PATCH 1/3] dt-bindings: ARM: Mediatek: Document devicetree bindings for spi bus leilk.liu
2015-05-08  8:55 ` [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173 leilk.liu
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 [this message]
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

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=20150609103951.GA14071@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=kernel@pengutronix.de \
    --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