From: Wolfram Sang <wsa@the-dreams.de>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
mkarthik@nvidia.com, smohammed@nvidia.com, talho@nvidia.com,
peda@axentia.se, digetx@gmail.com, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH V19 5/7] i2c: tegra: Add DMA support
Date: Thu, 14 Feb 2019 17:53:15 +0100 [thread overview]
Message-ID: <20190214165314.dczoxwkayras5cdr@ninjato> (raw)
In-Reply-To: <1549998408-9137-5-git-send-email-skomatineni@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]
On Tue, Feb 12, 2019 at 11:06:46AM -0800, Sowjanya Komatineni wrote:
> 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.
>
> Tegra210 and prior Tegra chips use APBDMA driver which is replaced
> with GPCDMA on Tegra186 and Tegra194.
> This patch uses has_apb_dma flag in hw_feature to differentiate
> DMA driver change between Tegra chipset.
>
> APBDMA driver is registered from module-init level and this patch
> also has a change to register I2C driver at module-init level
> rather than subsys-init to avoid deferring I2C probe till APBDMA
> driver is registered.
>
> Acked-by: Thierry Reding <treding@nvidia.com>
> Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
> Tested-by: Dmitry Osipenko <digetx@gmail.com>
> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
Not directly related to your code, but maybe someone is interested in
fixing this rightful checkpatch comment somewhen later:
WARNING: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#332: FILE: drivers/i2c/busses/i2c-tegra.c:791:
+ BUG();
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-14 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 19:06 [PATCH V19 1/7] i2c: tegra: sort all the include headers alphabetically Sowjanya Komatineni
2019-02-12 19:06 ` [PATCH V19 2/7] i2c: tegra: add bus clear Master Support Sowjanya Komatineni
2019-02-12 19:06 ` [PATCH V19 3/7] i2c: tegra: fix maximum transfer size Sowjanya Komatineni
2019-02-12 19:06 ` [PATCH V19 4/7] i2c: tegra: update " Sowjanya Komatineni
2019-02-12 19:06 ` [PATCH V19 5/7] i2c: tegra: Add DMA support Sowjanya Komatineni
2019-02-14 16:53 ` Wolfram Sang [this message]
2019-02-20 18:02 ` Jon Hunter
2019-02-20 18:05 ` Dmitry Osipenko
2019-02-12 19:06 ` [PATCH V19 6/7] i2c: tegra: update transfer timeout Sowjanya Komatineni
2019-02-12 19:06 ` [PATCH V19 7/7] i2c: tegra: add i2c interface timing support Sowjanya Komatineni
2019-02-12 21:00 ` [PATCH V19 1/7] i2c: tegra: sort all the include headers alphabetically Peter Rosin
2019-02-12 21:15 ` Dmitry Osipenko
2019-02-13 8:35 ` Wolfram Sang
2019-02-13 13:13 ` Dmitry Osipenko
2019-02-13 14:55 ` Wolfram Sang
2019-02-13 23:45 ` Sowjanya Komatineni
2019-02-14 16:51 ` Wolfram Sang
2019-02-14 16:51 ` 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=20190214165314.dczoxwkayras5cdr@ninjato \
--to=wsa@the-dreams.de \
--cc=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=peda@axentia.se \
--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