From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2 V3] MXS: Implement DMA support into mxs-i2c
Date: Mon, 16 Jul 2012 15:06:07 +0200 [thread overview]
Message-ID: <201207161506.08147.marex@denx.de> (raw)
In-Reply-To: <20120716102151.GC17435@pengutronix.de>
Dear Wolfram Sang,
> Marek,
>
> > > I am also still interested to check the runtime switching, but it might
> > > take another month until I can really hack on it.
> >
> > Good, there is some bit that probably needs to be flipped to allow this
> > switching. I managed to get this working with SPI, not with i2c though.
> > With
>
> Ah, hearing that it works with SPI is good news.
>
> > i2c, if I restarted the controller inbetween each transaction, it worked
> > ... which is not what I'd like to see there.
>
> Agreed.
>
> > > > No, it doesn't. See above about small transfers. Consider the easy
> > > > situation where you have sensor on one bus (so you do PIO because you
> > > > transfer small data) and you have EEPROM on other bus, where you use
> > > > DMA because you transfer large data. And the mixed mode isn't there
> > > > yet.
> > >
> > > I fully understand what you want to configure. I did before. Yet,
> > > devicetree bindings are not platform_data and shouldn't be used like
> > > them.
> >
> > But then, how would you configure this detail on a per-bus basis? Well
> > all
>
> This is a question for devicetree-discuss.
Did you Cc it?
> > patch actually fixes a real issue, I'd like to have it in ASAP and it's
> > been aboue three months already, which sucks.
>
> I am open to ideas improving the situation (which is: a lot more
> patches, but not a lot more reviewers)
>
> Thanks,
>
> Wolfram
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-16 13:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 16:22 [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-07-09 16:22 ` [PATCH 2/2 V3] MXS: Implement DMA support into mxs-i2c Marek Vasut
2012-07-13 8:22 ` Wolfram Sang
2012-07-13 12:10 ` Marek Vasut
2012-07-14 11:29 ` Wolfram Sang
2012-07-14 12:09 ` Marek Vasut
2012-07-16 10:21 ` Wolfram Sang
2012-07-16 13:06 ` Marek Vasut [this message]
2012-07-16 13:25 ` Wolfram Sang
2012-07-15 8:17 ` Shawn Guo
2012-07-21 12:44 ` Wolfram Sang
2012-07-21 14:11 ` Marek Vasut
2012-07-21 15:41 ` Wolfram Sang
2012-07-21 15:54 ` Marek Vasut
2012-07-22 8:33 ` Wolfram Sang
2012-07-28 8:02 ` Shawn Guo
2012-07-13 8:07 ` [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Wolfram Sang
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=201207161506.08147.marex@denx.de \
--to=marex@denx.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).