Return-path: Received: from mail-ob0-f176.google.com ([209.85.214.176]:59297 "EHLO mail-ob0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935477AbaH0S3g (ORCPT ); Wed, 27 Aug 2014 14:29:36 -0400 Message-ID: <53FE217B.7000401@gmail.com> (sfid-20140827_202939_724255_03248168) Date: Wed, 27 Aug 2014 11:20:43 -0700 From: Florian Fainelli MIME-Version: 1.0 To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Hauke Mehrtens CC: devicetree@vger.kernel.org, "linux-wireless@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-mips@linux-mips.org" Subject: Re: [RFC 2/7] bcm47xx-nvram: add new broadcom nvram driver with dt support References: <1408915485-8078-1-git-send-email-hauke@hauke-m.de> <1408915485-8078-4-git-send-email-hauke@hauke-m.de> In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 08/26/2014 10:54 PM, Rafał Miłecki wrote: > On 24 August 2014 23:24, Hauke Mehrtens wrote: >> +On NorthStar ARM SoCs the NAND flash is available at 0x1c000000 and the >> +NOR flash is at 0x1e000000 >> + >> +Example: >> + >> +nvram0: nvram@0 { >> + compatible = "brcm,bcm47xx-nvram"; >> + reg = <0x1c000000 0x01000000>; >> +}; > > Could we avoid that? Type of flash can easily be checked in the code. > All we need to do is to read BCMA_IOST register of BCMA_CORE_NS_ROM > core. So there is a boot status register you can read to tell what type of flash you booted from, but does that also give you the resource ranges for these type of flashes? Presumably they will be mapped into different addresses (at least bcm63xx is like that), that information needs to be listed somewhere. -- Florian