From: Marek Vasut <marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Cc: "Shawn Guo" <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Detlev Zundel" <dzu-ynQEQJNshbs@public.gmane.org>,
"Dong Aisheng" <b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
"Fabio Estevam"
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
"Linux ARM kernel"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"Sascha Hauer" <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Stefano Babic" <sbabic-ynQEQJNshbs@public.gmane.org>,
"Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Wolfgang Denk" <wd-ynQEQJNshbs@public.gmane.org>,
"Wolfram Sang" <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: MXS i2c PIOQ/DMA mode selection via DT
Date: Wed, 18 Jul 2012 14:38:54 +0200 [thread overview]
Message-ID: <201207181438.54721.marek.vasut@gmail.com> (raw)
In-Reply-To: <201207161605.44379.marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Hello,
>
> There's been this patch going on, which adds DMA mode into MXS i2c driver:
> https://patchwork.kernel.org/patch/1174051/
>
> Recent nitpick was about toggling the PIOQUEUE (almost like PIO, only
> transfer mode in current implementation) vs. DMA mode (newly added) on a
> per-bus basis.
>
> Current implementation in the patch adds a DT property, "fsl,use-pio"
> (shall be changed to "fsl,use-pioqueue", but that's irrelevant) to select
> between the PIOQUEUE and DMA mode on per-bus basis.
>
> There was now a suggestion to dump this property and use kernel module
> parameter instead. This obviously disallows to configure this behavior on
> per-bus basis. Consider a scenario where small transfers happens on one
> bus (possibly from a sensor) and large transfers on the other bus (eg. i2c
> EEPROM). In such scenario, it's beneficial to enable PIOQUEUE mode for the
> sensor and DMA mode for the EEPROM to minimize the overall overhead.
>
> The mixed mode (PIOQ for small data and DMA for large data transfers) isn't
> supported yet.
>
> Please advise.
>
> Best regards,
> Marek Vasut
BUMP?
prev parent reply other threads:[~2012-07-18 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 14:05 MXS i2c PIOQ/DMA mode selection via DT Marek Vasut
[not found] ` <201207161605.44379.marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-18 12:38 ` Marek Vasut [this message]
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=201207181438.54721.marek.vasut@gmail.com \
--to=marek.vasut-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dzu-ynQEQJNshbs@public.gmane.org \
--cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=sbabic-ynQEQJNshbs@public.gmane.org \
--cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=wd-ynQEQJNshbs@public.gmane.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).