From: Wolfram Sang <wsa@kernel.org>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: christian.koenig@amd.com, devicetree@vger.kernel.org,
digetx@gmail.com, jonathanh@nvidia.com, ldewangan@nvidia.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, robh+dt@kernel.org,
sumit.semwal@linaro.org, thierry.reding@gmail.com
Subject: Re: [PATCH v2 1/3] i2c: tegra: Add GPCDMA support
Date: Fri, 16 Sep 2022 20:47:56 +0100 [thread overview]
Message-ID: <YyTS7MWbaIS4gAMj@shikoro> (raw)
In-Reply-To: <20220906144716.16274-2-akhilrajeev@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
On Tue, Sep 06, 2022 at 08:17:14PM +0530, Akhil R wrote:
> Enable support for GPCDMA, which is used in I2C controllers
> in Tegra 186 and above. The chips before that used APB DMA.
> This change works under the presumption that all chips apart from
> those supporting APB DMA is using GPCDMA.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-16 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 14:47 [PATCH v2 0/3] Add GPCDMA support to Tegra I2C Akhil R
2022-09-06 14:47 ` [PATCH v2 1/3] i2c: tegra: Add GPCDMA support Akhil R
2022-09-10 9:03 ` Dmitry Osipenko
2022-09-16 19:47 ` Wolfram Sang [this message]
2022-09-06 14:47 ` [PATCH v2 2/3] arm64: tegra: Add GPCDMA support for Tegra I2C Akhil R
2022-10-07 13:20 ` Thierry Reding
2022-10-07 14:34 ` Thierry Reding
2022-10-07 14:53 ` Robin Murphy
2022-10-07 15:17 ` Thierry Reding
2022-10-07 17:40 ` Robin Murphy
2022-09-06 14:47 ` [PATCH v2 3/3] arm64: defconfig: Make TEGRA186_GPC_DMA built-in Akhil R
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=YyTS7MWbaIS4gAMj@shikoro \
--to=wsa@kernel.org \
--cc=akhilrajeev@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sumit.semwal@linaro.org \
--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).