From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Ray Jui" <rjui@broadcom.com>,
"Brian Norris" <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: iProc nand iproc-idm register
Date: Fri, 29 May 2015 18:24:24 +0200 [thread overview]
Message-ID: <556892B8.3020706@hauke-m.de> (raw)
In-Reply-To: <55635511.30602@broadcom.com>
On 05/25/2015 07:00 PM, Ray Jui wrote:
> 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.
Thanks for the info, the space before 408 is not used on the older
chips, just some addresses ontop of that.
Still this is a strange address to start a register map.
>
>>
>> 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
>>
prev parent reply other threads:[~2015-05-29 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 17:16 iProc nand iproc-idm register Hauke Mehrtens
2015-05-25 17:00 ` Ray Jui
2015-05-29 16:24 ` Hauke Mehrtens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=556892B8.3020706@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox