linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
	mkarthik@nvidia.com, smohammed@nvidia.com, talho@nvidia.com,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH V5 3/5] i2c: tegra: Add DMA Support
Date: Wed, 30 Jan 2019 04:42:14 +0300	[thread overview]
Message-ID: <20190130044214.65991195@dimatab> (raw)
In-Reply-To: <1548803771-13424-3-git-send-email-skomatineni@nvidia.com>

В Tue, 29 Jan 2019 15:16:09 -0800
Sowjanya Komatineni <skomatineni@nvidia.com> пишет:

> This patch adds DMA support for Tegra I2C.
> 
> Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
> transfer size of the max FIFO depth and DMA mode is used for
> transfer size higher than max FIFO depth to save CPU overhead.
> 
> PIO mode needs full intervention of CPU to fill or empty FIFO's
> and also need to service multiple data requests interrupt for the
> same transaction. This adds delay between data bytes of the same
> transfer when CPU is fully loaded and some slave devices has
> internal timeout for no bus activity and stops transaction to
> avoid bus hang. DMA mode is helpful in such cases.
> 
> DMA mode is also helpful for Large transfers during downloading or
> uploading FW over I2C to some external devices.
> 
> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
> ---
>  [V5] : Same as V4
>  [V4] : Updated to allocate DMA buffer only when DMA mode.
> 	Updated to fall back to PIO mode when DMA channel request or
> 	buffer allocation fails.
>  [V3] : Updated without additional buffer allocation.
>  [V2] : Updated based on V1 review feedback along with code cleanup
> for proper implementation of DMA.

Could you please tell whether you missed my comments to V3 [0] or chose
to ignore them? If the former, then I'd want to get answers to those
questions and comments. I'll stop here for now.

[0] https://patchwork.ozlabs.org/patch/1031379/

  reply	other threads:[~2019-01-30  1:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 23:16 [PATCH V5 1/5] i2c: tegra: Sort all the include headers alphabetically Sowjanya Komatineni
2019-01-29 23:16 ` [PATCH V5 2/5] i2c: tegra: Add Bus Clear Master Support Sowjanya Komatineni
2019-01-29 23:16 ` [PATCH V5 3/5] i2c: tegra: Add DMA Support Sowjanya Komatineni
2019-01-30  1:42   ` Dmitry Osipenko [this message]
2019-01-30  1:50     ` Sowjanya Komatineni
2019-01-30  4:15       ` Sowjanya Komatineni
2019-01-30  4:22         ` Sowjanya Komatineni
2019-01-30  4:49           ` Dmitry Osipenko
2019-01-30  5:04             ` Sowjanya Komatineni
2019-01-29 23:16 ` [PATCH V5 4/5] i2c: tegra: Update transfer timeout Sowjanya Komatineni
2019-01-29 23:16 ` [PATCH V5 5/5] i2c: tegra: Add I2C interface timing support Sowjanya Komatineni

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=20190130044214.65991195@dimatab \
    --to=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkarthik@nvidia.com \
    --cc=skomatineni@nvidia.com \
    --cc=smohammed@nvidia.com \
    --cc=talho@nvidia.com \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).