* iProc nand iproc-idm register
@ 2015-05-24 17:16 Hauke Mehrtens
2015-05-25 17:00 ` Ray Jui
0 siblings, 1 reply; 3+ messages in thread
From: Hauke Mehrtens @ 2015-05-24 17:16 UTC (permalink / raw)
To: Ray Jui, Brian Norris, linux-mtd, bcm-kernel-feedback-list,
Rafał Miłecki
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?
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: iProc nand iproc-idm register
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
0 siblings, 1 reply; 3+ messages in thread
From: Ray Jui @ 2015-05-25 17:00 UTC (permalink / raw)
To: Hauke Mehrtens, Brian Norris, linux-mtd, bcm-kernel-feedback-list,
Rafał Miłecki
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: iProc nand iproc-idm register
2015-05-25 17:00 ` Ray Jui
@ 2015-05-29 16:24 ` Hauke Mehrtens
0 siblings, 0 replies; 3+ messages in thread
From: Hauke Mehrtens @ 2015-05-29 16:24 UTC (permalink / raw)
To: Ray Jui, Brian Norris, linux-mtd, bcm-kernel-feedback-list,
Rafał Miłecki
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
>>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-05-29 16:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox