From: Akhil R <akhilrajeev@nvidia.com>
To: <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>, <wsa@kernel.org>
Cc: <akhilrajeev@nvidia.com>
Subject: [PATCH v6 RESEND 0/2] Tegra I2C DMA and SMBus blockread updates
Date: Thu, 27 Apr 2023 18:09:13 +0530 [thread overview]
Message-ID: <20230427123915.38199-1-akhilrajeev@nvidia.com> (raw)
The patchset contains two independent updates to tegra-i2c driver.
* Update I2C DMA channel usage to use single DMA channel instead of
two different hardware channels.
* Fix PEC byte issue during SMBus block read caused by mismanaged
msg->len property in i2c_msg struct.
v5->v6:
Updated __u16 to unsigned int
v4->v5:
Corrected the comment style
v3->v4:
Combine the two patches to one series to avoid merge conflicts.
Akhil R (2):
i2c: tegra: Fix PEC support for SMBUS block read
i2c: tegra: Share same DMA channel for RX and TX
drivers/i2c/busses/i2c-tegra.c | 109 ++++++++++++++-------------------
1 file changed, 47 insertions(+), 62 deletions(-)
--
2.17.1
next reply other threads:[~2023-04-27 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 12:39 Akhil R [this message]
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
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=20230427123915.38199-1-akhilrajeev@nvidia.com \
--to=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 \
--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