From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752660AbbLJDBH (ORCPT ); Wed, 9 Dec 2015 22:01:07 -0500 Received: from mga02.intel.com ([134.134.136.20]:3002 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751713AbbLJDBF (ORCPT ); Wed, 9 Dec 2015 22:01:05 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,406,1444719600"; d="scan'208";a="857758695" Date: Thu, 10 Dec 2015 08:34:10 +0530 From: Vinod Koul To: Tony Lindgren Cc: Peter Ujfalusi , arnd@arndb.de, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, balbi@ti.com, linux-kernel@vger.kernel.org, nsekhar@ti.com Subject: Re: [PATCH for 4.4 0/2] DT/dmaengine: edma: Convert 16bit arrays to 32bit Message-ID: <20151210030410.GG1854@localhost> References: <1449649091-9848-1-git-send-email-peter.ujfalusi@ti.com> <20151209201226.GB23396@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151209201226.GB23396@atomide.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 09, 2015 at 12:12:27PM -0800, Tony Lindgren wrote: > * Peter Ujfalusi [151209 00:19]: > > Hi, > > > > Based on the discussion regarding to (convert am33xx to use the new eDMA > > bindings): > > https://www.mail-archive.com/linux-omap@vger.kernel.org/msg122117.html > > > > This two patch will convert the new eDMA binding to not use 16bit arrays for > > memcpy channel selection and for marking slots reserved. > > The '/bits/ 16' seams to be causing confusion so it is probably better to just > > use standard type for the arrays. > > > > The new bindings for the eDMA is introduced for 4.4 and we do not have users of > > it, which means that we can still change it w/o the risk of breaking anything > > and we do not need to maintain the compatibility with 16bit arrays. > > > > The changes in the eDMA driver is local to the DT parsing and should not > > conflict with other changes (like the filter function mapping support). Hrm, > > there might be trivial conflict in the include/linux/platform_data/edma.h with > > the "dmaengine 'universal' API". > > > > Tony, Arnd, Vinod: Can you agree on the practicalities on how these patches are > > going to be handled? I would like to send the updated am33xx/am437x conversion > > for 4.5 based on these changes. > > Yes this should go into v4.4 as discussed, otherwise it will be a mess. > For both, please feel free to add: > > Acked-by: Tony Lindgren > > I suggest Vinod sets up an immutable branch against v4.4-rc1 with just these > two patches. Then it can get merged into whichever branch needs it, I > certainly will need it as most of my v4.5 branches are v4.4-rc1 or -rc2 > based. > > Then the immutable branch can be merged into v4.4 by Vinod or Arnd. Applied to fix/edma. This is based on -rc1 and will not rebase. I am merging this to my fixes and will send to Linus in couple of days Thanks -- ~Vinod