From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH v5 3/3] ARM: OMAP2+: onenand: prepare for gpmc driver migration Date: Thu, 5 Jul 2012 07:49:37 -0700 Message-ID: <20120705144936.GF1122@atomide.com> References: <20120628123207.GG19842@atomide.com> <4FEC89B9.3090404@ti.com> <20120702063651.GO4202@atomide.com> <4FF1D980.4040100@ti.com> <20120703081746.GJ1122@atomide.com> <20120704075158.GQ1122@atomide.com> <20120705105535.GB1122@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:25788 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932602Ab2GEOtk (ORCPT ); Thu, 5 Jul 2012 10:49:40 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Mohammed, Afzal" Cc: "Hunter, Jon" , "paul@pwsan.com" , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" * Mohammed, Afzal [120705 05:03]: > Hi Tony, > > On Thu, Jul 05, 2012 at 16:25:35, Tony Lindgren wrote: > > * Mohammed, Afzal [120705 03:29]: > > > > Initially I thought you were suggesting that all peripheral drivers > > > connected to gpmc should register their retime function (where > > > Yes that's what I was suggesting. > > To understand you better, peripheral drivers above refers to > driver created out of present gpmc platform init code like > gpmc-smsc911x.c. You were not referring to > drivers/net/ethernet/smsc/smsc911x.c, right ? Yes arch/arm/mach-omap2/gpmc-smsc911x.c for now, but eventually that too should probably be just a regular driver. Just how it will work together with drivers/net/ethernet/smsc/smsc911x.c is still a bit open though :) Tony