Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752730AbaLDH2f (ORCPT ); Thu, 4 Dec 2014 02:28:35 -0500 Received: from mail-ie0-f175.google.com ([209.85.223.175]:59635 "EHLO mail-ie0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750992AbaLDH2e convert rfc822-to-8bit (ORCPT ); Thu, 4 Dec 2014 02:28:34 -0500 MIME-Version: 1.0 In-Reply-To: References: <1416736241-12723-1-git-send-email-zajec5@gmail.com> <1416778509-31502-1-git-send-email-zajec5@gmail.com> Date: Thu, 4 Dec 2014 08:28:33 +0100 Message-ID: Subject: Re: [PATCH V3] MIPS: BCM47XX: Move NVRAM driver to the drivers/soc/ From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: Paul Walmsley Cc: Hauke Mehrtens , "linux-mips@linux-mips.org" , Ralf Baechle , Greg Kroah-Hartman , Kumar Gala , Olof Johansson , Arnd Bergmann , Sandeep Nair , linux-soc@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4 December 2014 at 07:43, Paul Walmsley wrote: > Hello Rafał, > > On Fri, 28 Nov 2014, Paul Walmsley wrote: > >> On Thu, 27 Nov 2014, Rafał Miłecki wrote: >> >> > I'm pretty sure you look at some old version of arch/bcm47xx/nvram.c. >> > I wouldn't dare to move such a MIPS-focused driver to some common >> > place ;) >> > >> > Please check for the version of nvram.c in Ralf's upstream-sfr tree. I >> > think you'll like it much more. Hopefully you will even consider it >> > ready for moving to the drivers/firmware/ or whatever :) >> >> OK I will take a look at this, and will either send comments, or will >> send a Reviewed-By:. > > I had the chance to take a brief look at this file, and you are right: I > like your newer version better than the older one :-) > > It is too bad that it seems this flash area has to be accessed very early > in boot. That certainly makes it more difficult to write something > particularly elegant. It is also a pity that it is unknown how to verify > that the flash MMIO window has been configured before reading from these > areas of the address space. But under the circumstances, calling > bcm47xx_nvram_init_from_mem() with the appropriate addresses from the bus > code during early init, as you did, seems rather reasonable. I also like > the code that you added to read the flash data from MTD later in boot. > > Here are a few very minor comments that you are welcome to take or leave > as you wish. Thanks for your comments! I'll address them before (trying) moving driver to the drivers/firmware/. Appreciate your review. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/