linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Mantravadi Karthik <mkarthik@nvidia.com>,
	Shardar Mohammed <smohammed@nvidia.com>,
	Timo Alho <talho@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: RE: [PATCH V16 4/6] i2c: tegra: Add DMA support
Date: Fri, 8 Feb 2019 17:02:25 +0000	[thread overview]
Message-ID: <BYAPR12MB33980494FB2E5C439210124FC2690@BYAPR12MB3398.namprd12.prod.outlook.com> (raw)
In-Reply-To: <dd2899ab-1a5f-834c-ab97-1654845c7de2@gmail.com>


> I'm still also suggesting to squash "fix maximum transfer size" into this patch because it is really part of DMA-support enabling.

Max transfer length limits apply to PIO also but for DMA its more needed to prevent crash.
So had this as patch before DMA as its applicable for both DMA & PIO.
We exchanged on this yesterday, so thought the reason you want to squash separate patch and include in this is due to max msg len limit and when moved into hw feature

  reply	other threads:[~2019-02-08 17:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 16:45 [PATCH V16 1/6] i2c: tegra: sort all the include headers alphabetically Sowjanya Komatineni
2019-02-08 16:45 ` [PATCH V16 2/6] i2c: tegra: add bus clear Master Support Sowjanya Komatineni
2019-02-08 16:45 ` [PATCH V16 3/6] i2c: tegra: fix maximum transfer size Sowjanya Komatineni
2019-02-08 16:45 ` [PATCH V16 4/6] i2c: tegra: Add DMA support Sowjanya Komatineni
2019-02-08 16:56   ` Dmitry Osipenko
2019-02-08 17:02     ` Sowjanya Komatineni [this message]
2019-02-08 17:06       ` Sowjanya Komatineni
2019-02-08 17:21         ` Dmitry Osipenko
2019-02-08 17:29           ` Sowjanya Komatineni
2019-02-08 17:34             ` Dmitry Osipenko
2019-02-08 17:36               ` Dmitry Osipenko
2019-02-08 17:53                 ` Sowjanya Komatineni
2019-02-08 18:01                   ` Dmitry Osipenko
2019-02-08 16:45 ` [PATCH V16 5/6] i2c: tegra: update transfer timeout Sowjanya Komatineni
2019-02-08 16:45 ` [PATCH V16 6/6] i2c: tegra: add i2c interface timing support Sowjanya Komatineni
2019-02-08 16:55   ` Dmitry Osipenko

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=BYAPR12MB33980494FB2E5C439210124FC2690@BYAPR12MB3398.namprd12.prod.outlook.com \
    --to=skomatineni@nvidia.com \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkarthik@nvidia.com \
    --cc=smohammed@nvidia.com \
    --cc=talho@nvidia.com \
    --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).