From: Wolfram Sang <wsa@kernel.org>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: christian.koenig@amd.com, digetx@gmail.com, jonathanh@nvidia.com,
ldewangan@nvidia.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
sumit.semwal@linaro.org, thierry.reding@gmail.com
Subject: Re: [PATCH v6 RESEND 2/2] i2c: tegra: Share same DMA channel for RX and TX
Date: Mon, 5 Jun 2023 10:21:13 +0200 [thread overview]
Message-ID: <ZH2a+S/1yeV5gN07@shikoro> (raw)
In-Reply-To: <20230427123915.38199-3-akhilrajeev@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On Thu, Apr 27, 2023 at 06:09:15PM +0530, Akhil R wrote:
> Allocate only one DMA channel for I2C and share it for both TX and RX
> instead of using two different DMA hardware channels with the same
> slave ID. Since I2C supports only half duplex, there is no impact on
> perf with this.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> Acked-by: Thierry Reding <treding@nvidia.com>
Applied to for-next, thanks!
No, there wasn't an issue with this patch. I just needed to make sure
patch 1 (which was for-current material) landed upstream to avoid merge
conflicts.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-05 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 12:39 [PATCH v6 RESEND 0/2] Tegra I2C DMA and SMBus blockread updates Akhil R
2023-04-27 12:39 ` [PATCH v6 RESEND 1/2] i2c: tegra: Fix PEC support for SMBUS block read Akhil R
2023-04-30 5:50 ` Wolfram Sang
2023-04-27 12:39 ` [PATCH v6 RESEND 2/2] i2c: tegra: Share same DMA channel for RX and TX Akhil R
2023-05-22 14:57 ` Akhil R
2023-06-05 8:21 ` Wolfram Sang [this message]
2023-06-05 9:24 ` 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=ZH2a+S/1yeV5gN07@shikoro \
--to=wsa@kernel.org \
--cc=akhilrajeev@nvidia.com \
--cc=christian.koenig@amd.com \
--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=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