From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: 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 V7 3/5] i2c: tegra: Add DMA Support
Date: Thu, 31 Jan 2019 21:15:15 +0300 [thread overview]
Message-ID: <7ddf46a8-ae98-c567-6d3d-8155989effb5@gmail.com> (raw)
In-Reply-To: <48135b67-eed7-9a9d-de3e-e400e8ef8176@gmail.com>
31.01.2019 21:08, Dmitry Osipenko пишет:
> 31.01.2019 19:55, Dmitry Osipenko пишет:
> +config I2C_TEGRA_DMA_SUPPORT
> + bool "NVIDIA Tegra internal I2C controller DMA support"
> + depends on I2C_TEGRA
> + depends on TEGRA20_APB_DMA && ARCH_TEGRA_2x_SOC
> + depends on TEGRA20_APB_DMA && ARCH_TEGRA_3x_SOC
> + depends on TEGRA20_APB_DMA && ARCH_TEGRA_114_SOC
> + depends on TEGRA20_APB_DMA && ARCH_TEGRA_124_SOC
> + depends on TEGRA20_APB_DMA && ARCH_TEGRA_210_SOC
> + help
> + If you say yes to this option, DMA engine integration support will
> + be included for the I2C controller embedded in NVIDIA Tegra SOCs
> +
Actually, seems should be like that:
config I2C_TEGRA_DMA_SUPPORT
bool "NVIDIA Tegra internal I2C controller DMA support"
depends on I2C_TEGRA
depends on (TEGRA20_APB_DMA && ARCH_TEGRA_2x_SOC) || \
(TEGRA20_APB_DMA && ARCH_TEGRA_3x_SOC) || \
(TEGRA20_APB_DMA && ARCH_TEGRA_114_SOC) || \
(TEGRA20_APB_DMA && ARCH_TEGRA_124_SOC) || \
(TEGRA20_APB_DMA && ARCH_TEGRA_210_SOC)
help
If you say yes to this option, DMA engine integration support will
be included for the I2C controller embedded in NVIDIA Tegra SOCs
But you got the idea.
next prev parent reply other threads:[~2019-01-31 18:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:01 [PATCH V7 1/5] i2c: tegra: Sort all the include headers alphabetically Sowjanya Komatineni
2019-01-30 16:01 ` [PATCH V7 2/5] i2c: tegra: Add Bus Clear Master Support Sowjanya Komatineni
2019-01-31 11:31 ` Thierry Reding
2019-01-30 16:01 ` [PATCH V7 3/5] i2c: tegra: Add DMA Support Sowjanya Komatineni
2019-01-31 0:05 ` Dmitry Osipenko
2019-01-31 1:19 ` Sowjanya Komatineni
2019-01-31 2:13 ` Dmitry Osipenko
2019-01-31 2:24 ` Sowjanya Komatineni
2019-01-31 2:53 ` Dmitry Osipenko
2019-01-31 3:34 ` Sowjanya Komatineni
2019-01-31 4:01 ` Dmitry Osipenko
2019-01-31 12:06 ` Thierry Reding
2019-01-31 14:06 ` Dmitry Osipenko
2019-01-31 14:43 ` Thierry Reding
2019-01-31 15:02 ` Dmitry Osipenko
2019-01-31 16:01 ` Thierry Reding
2019-01-31 16:27 ` Dmitry Osipenko
2019-01-31 16:31 ` Dmitry Osipenko
2019-01-31 19:02 ` Dmitry Osipenko
2019-01-31 16:55 ` Dmitry Osipenko
2019-01-31 18:08 ` Dmitry Osipenko
2019-01-31 18:15 ` Dmitry Osipenko [this message]
2019-01-30 16:01 ` [PATCH V7 4/5] i2c: tegra: Update transfer timeout Sowjanya Komatineni
2019-01-31 1:38 ` Dmitry Osipenko
2019-01-30 16:01 ` [PATCH V7 5/5] i2c: tegra: Add I2C interface timing support Sowjanya Komatineni
2019-01-31 4:30 ` Dmitry Osipenko
2019-01-31 11:28 ` [PATCH V7 1/5] i2c: tegra: Sort all the include headers alphabetically Thierry Reding
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=7ddf46a8-ae98-c567-6d3d-8155989effb5@gmail.com \
--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).