From: Akhil R <akhilrajeev@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
Dmitry Osipenko <digetx@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
"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>
Cc: <mochs@nvidia.com>, Akhil R <akhilrajeev@nvidia.com>
Subject: [PATCH 0/4] i2c: tegra: Improve DMA mapping, latency, and power management
Date: Tue, 5 May 2026 16:29:24 +0530 [thread overview]
Message-ID: <20260505105928.38457-1-akhilrajeev@nvidia.com> (raw)
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.
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 | 86 +++++++++++++++++++++++-----------
1 file changed, 58 insertions(+), 28 deletions(-)
--
2.50.1
next reply other threads:[~2026-05-05 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 10:59 Akhil R [this message]
2026-05-05 10:59 ` [PATCH 1/4] i2c: tegra: use dmaengine_get_dma_device() for DMA buffer allocation Akhil R
2026-05-05 10:59 ` [PATCH 2/4] i2c: tegra: Disable fair arbitration for non-MCTP buses Akhil R
2026-05-05 10:59 ` [PATCH 3/4] i2c: tegra: Update Tegra410 I2C timing parameters Akhil R
2026-05-05 10:59 ` [PATCH 4/4] i2c: tegra: Fix NOIRQ suspend/resume 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=20260505105928.38457-1-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.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=mochs@nvidia.com \
--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