From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754333AbeDBHBN (ORCPT ); Mon, 2 Apr 2018 03:01:13 -0400 Received: from mail.bootlin.com ([62.4.15.54]:43432 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752583AbeDBHBM (ORCPT ); Mon, 2 Apr 2018 03:01:12 -0400 Date: Mon, 2 Apr 2018 09:01:00 +0200 From: Boris Brezillon To: Sekhar Nori Cc: David Lechner , Bartosz Golaszewski , Richard Weinberger , linux-kernel@vger.kernel.org, Marek Vasut , linux-mtd@lists.infradead.org, Cyrille Pitchen , Brian Norris , David Woodhouse , Linux ARM Mailing List Subject: Re: [PATCH] mtd: nand: davinci: don't acquire and enable clock Message-ID: <20180402090100.28961677@bbrezillon> In-Reply-To: <20180330143051.26423-1-nsekhar@ti.com> References: <20180330143051.26423-1-nsekhar@ti.com> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 30 Mar 2018 20:00:51 +0530 Sekhar Nori wrote: > NAND itself is an asynchronous interface, it does not have any > clock input. DaVinci NAND driver acquires clock for AEMIF > (asynchronous external memory interface) which is an on-chip > IP to which NAND is connected. > > The same clock is also enabled in AEMIF driver (either present > drivers/memory or from machine code for some older platforms). > AEMIF timing must be initialized before NAND can be accessed. > This ensures that AEMIF clock is enabled too. > > Remove the superfluous clock acquisition and enable in DaVinci > NAND driver. > > Tested on K2L, K2HK, K2E, DA850 EVM, DA850 LCDK in device-tree > boot and DM644x EVM in legacy boot. > > Signed-off-by: Sekhar Nori > --- > Hi Boris, > > If/when this patch gets accepted, I'll probably queue it just after v4.17-rc1 is out if nobody complains about the change. > it will nice to put this on > an immutable branch others can merge. There is potential cleanup > in drivers/clock and in DaVinci machine code that will depend > on this. Sure, I can do that. -- Boris Brezillon, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com