From: Jon Hunter <jonathanh@nvidia.com>
To: Akhil R <akhilrajeev@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Dmitry Osipenko <digetx@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Kartik Rajput <kkartik@nvidia.com>, Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] i2c: tegra: Improve DMA mapping, latency, and power management
Date: Thu, 4 Jun 2026 09:51:56 +0100 [thread overview]
Message-ID: <f2e926e1-9cfb-4d59-b525-2d9590745fc5@nvidia.com> (raw)
In-Reply-To: <20260518114013.62065-1-akhilrajeev@nvidia.com>
Hi Wolfram, Andi,
On 18/05/2026 12:40, Akhil R wrote:
> This series addresses several aspects of the Tegra I2C driver:
>
> - DMA mapping: Use the proper DMA device for buffer allocation to
> ensure correct DMA address translation.
> - Transfer latency: Disable fair arbitration on non-MCTP buses to
> reduce transfer latency.
> - Timing parameters: Update I2C timing values for Tegra410.
> - Power management: Keep the controller available during noirq
> suspend/resume phases for system dependencies.
>
> v1->v2:
> * Add description for is_mctp in the struct
>
> Akhil R (4):
> i2c: tegra: use dmaengine_get_dma_device() for DMA buffer allocation
> i2c: tegra: Disable fair arbitration for non-MCTP buses
> i2c: tegra: Update Tegra410 I2C timing parameters
> i2c: tegra: Fix NOIRQ suspend/resume
>
> drivers/i2c/busses/i2c-tegra.c | 87 +++++++++++++++++++++++-----------
> 1 file changed, 59 insertions(+), 28 deletions(-)
>
Are you OK with these changes? If so we would like to get these into -next.
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2026-06-04 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 11:40 Akhil R
2026-05-18 11:40 ` [PATCH v2 1/4] i2c: tegra: use dmaengine_get_dma_device() for DMA buffer allocation Akhil R
2026-05-18 11:40 ` [PATCH v2 2/4] i2c: tegra: Disable fair arbitration for non-MCTP buses Akhil R
2026-05-18 11:40 ` [PATCH v2 3/4] i2c: tegra: Update Tegra410 I2C timing parameters Akhil R
2026-05-18 11:40 ` [PATCH v2 4/4] i2c: tegra: Fix NOIRQ suspend/resume Akhil R
2026-06-04 8:51 ` Jon Hunter [this message]
2026-06-08 19:30 ` [PATCH v2 0/4] i2c: tegra: Improve DMA mapping, latency, and power management Andi Shyti
2026-06-09 5:18 ` 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=f2e926e1-9cfb-4d59-b525-2d9590745fc5@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.com \
--cc=kkartik@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=thierry.reding@kernel.org \
--cc=wsa@kernel.org \
/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
Powered by JetHome