From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Cousson, Benoit" Subject: Re: [PATCH v4 0/7] Add TI EMIF SDRAM controller driver Date: Thu, 12 Apr 2012 21:24:29 +0200 Message-ID: <4F872BED.7000703@ti.com> References: <1331934707-29487-1-git-send-email-aneesh@ti.com> <20120412030044.GA26236@kroah.com> <4F867A95.9030104@ti.com> <20120412131045.GB31384@kroah.com> <4F87240F.6060902@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Paul Walmsley Cc: "Balbi, Felipe" , "Mohammed, Afzal" , Greg KH , "Shilimkar, Santosh" , "V, Aneesh" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-omap@vger.kernel.org" , "mgreer@animalcreek.com" , "msalter@redhat.com" List-Id: linux-omap@vger.kernel.org On 4/12/2012 9:15 PM, Paul Walmsley wrote: > Hi Beno=EEt, > > On Thu, 12 Apr 2012, Cousson, Benoit wrote: > >> The LPDDR2 spec does consider as well NVM (Non Volatile Memory), so = I think we >> should stick to driver/memory for EMIF. > > Hmm good point! > >>> So perhaps something like drivers/memory/dram/ for the SDRAM contro= llers, >>> and maybe drivers/memory/ for the GPMC? >> >> In fact Felipe was considering something else for that kind of gener= al purpose >> bus driver like GMPC, C2C and LLI... >> >> ... But I do not remember the name :-) > > It would be nice if we could separate IP blocks that can drive an Eth= ernet > controller or modem chip from the DRAM controllers; they are quite > different beasts from a common API standpoint. Yep, fully agree. In fact Felipe's suggestion was something like=20 drivers/ocd for off-chip devices, but maybe something like drivers/gpbu= s=20 will highlight a little bit more the bus controller aspect of such driv= er. Regards, Benoit