linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4] MXS: Implement DMA support into mxs-i2c
Date: Sun, 16 Sep 2012 13:12:23 +0200	[thread overview]
Message-ID: <20120916111223.GD933@pengutronix.de> (raw)
In-Reply-To: <201209161251.41895.marex@denx.de>


> > Unsurprisingly, I also couldn't get the mode switching between DMA and
> > PIOQUEUE to work :(
> 
> I'd say more work should be invested into this.

I ran out of ideas. Next thing I'd do is to ask FSL if this is possible
at all. Yet, I'd like to have some solution for 3.7.

> Besides, what about rather > trying PIO + DMA instead of PIOQ + DMA?

That could also be a solution.

> > However, I did come up with an idea how to select DMA or PIOQUEUE per
> > bus via devicetree. If we change the view from "I want PIOQUEUE" to "I
> > don't want DMA", we could simply override the default DMA configuration
> > in the devicetree with, e.g.:
> > 
> > 			i2c0: i2c at 80058000 {
> > 				...
> > 				fsl,i2c-dma-channel = <>;
> > 			};
> > 
> > So, no DMA channel set up will fall back to PIOQUEUE. This is more
> > generic than a custom binding, because if one doesn't want DMA, don't
> > configure it. That should also work with other devices which can fall
> > back to something. I think this is worth trying, another advantage is
> > that it doesn't expose something new to the user. So, there is no legacy
> > support needed in case there will be a better way of configuration.
> 
> Ewww ... that's such an ad-hoc hack.

Please give reasons.

> Besides, someone might simply forget to add the binding, you'd need to
> print a warning.

? It is "on" by default because of the entry in the dtsi. And the status
of DMA will be printed.

> > +	dev_info(dev, "registered. DMA: %s\n", i2c->dma_mode ? "on" : "off");
> 
> dev_debug() ?

Yup.

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120916/992906f8/attachment-0001.sig>

  reply	other threads:[~2012-09-16 11:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24  3:44 [PATCH V4] MXS: Implement DMA support into mxs-i2c Marek Vasut
2012-08-27 18:54 ` Fabio Estevam
2012-09-16 10:44   ` Wolfram Sang
2012-09-16 14:44     ` Fabio Estevam
2012-09-16 10:23 ` Wolfram Sang
2012-09-16 10:51   ` Marek Vasut
2012-09-16 11:12     ` Wolfram Sang [this message]
2012-09-16 11:14       ` Marek Vasut
2012-09-27  0:03       ` Marek Vasut
2012-10-08  9:25 ` Wolfram Sang
2012-10-08 13:15   ` Marek Vasut

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=20120916111223.GD933@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --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).