[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SJ1PR12MB6339D6C3D3C489068C40FE94C04DA@SJ1PR12MB6339.namprd12.prod.outlook.com>
Date: Mon, 5 Jun 2023 09:24:24 +0000
From: Akhil R <akhilrajeev@...dia.com>
To: Wolfram Sang <wsa@...nel.org>
CC: "christian.koenig@....com" <christian.koenig@....com>,
"digetx@...il.com" <digetx@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Laxman Dewangan <ldewangan@...dia.com>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"sumit.semwal@...aro.org" <sumit.semwal@...aro.org>,
"thierry.reding@...il.com" <thierry.reding@...il.com>
Subject: RE: [PATCH v6 RESEND 2/2] i2c: tegra: Share same DMA channel for RX
and TX
> 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@...dia.com>
> > Acked-by: Thierry Reding <treding@...dia.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.
Thank you :)
Powered by blists - more mailing lists