From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-gw2-out.broadcom.com ([216.31.210.63]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1YwvkB-0008SH-TE for linux-mtd@lists.infradead.org; Mon, 25 May 2015 17:00:56 +0000 Message-ID: <55635511.30602@broadcom.com> Date: Mon, 25 May 2015 10:00:01 -0700 From: Ray Jui MIME-Version: 1.0 To: Hauke Mehrtens , Brian Norris , , , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Subject: Re: iProc nand iproc-idm register References: <5562078A.6030909@hauke-m.de> In-Reply-To: <5562078A.6030909@hauke-m.de> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Hauke, On 5/24/2015 10:16 AM, Hauke Mehrtens wrote: > Hi Ray, > > in the iproc_nand driver your are using this register range: > reg = <0x18046000 0x600>, <0xf8105408 0x600>, <0x18046f00 0x20>; > reg-names = "nand", "iproc-idm", "iproc-ext"; > > I think the iproc-idm register range is the wrap address part on bcma > bus. On the bcma bus it is 0x1000 in size and 0x0408 is the offset of > the IO control register in it. Are the new iProc devices different here > or is this register not always at this offset but varies? It's different. Based on the Cygnus RDB, there's nothing between 0xf8105000 and 0xf8105404. > > Wouldn't it be better to specify the complete range like this: > reg = <0x18046000 0x600>, <0xf8105000 0x1000>, <0x18046f00 0x20>; > Then you can read the register at offset 0x408 in that range. > > Hauke >