在 Sep 28, 2012,0:07,"Kumar Gala" <ga...@kernel.crashing.org> 写道:

>>>> Hi Kumar,
>>>> I have already sent the log.
>>>> Do you have any comment on it?
>>>> 
>>>> Thanks.
>>>> - Hongtao.
>>>> 
>>> 
>>> Hongtao,
>>> 
>>> You mentioned:
>>> 
>>>> I tested the re-parsing way by using setup_pci_atmu() when resume.
>>>> And I found out that re-parsing will *change* outbound IO
>>>> translation address regitster.
>>> 
>>> What do the values look like in both ATMU registers and io_resource if you 
>>> reparse?
>> 
>> I think Hongtao mentioned in previous email as follows, the ATMU
>> registers are inline with the io_resource address.
> 
> I was under that the impression that was the normal boot case, not the values 
> from after wakeup.

It is for the normal boot.  But re-parse will use the io resource after pic 
scan to initialize atmu.  Instead, the original atmu is initialized use the io 
resource before the scan.

Leo
> 
> - k
> 
>>>> Since potar is set by out_be32(&pci->pow[j].potar, (hose-
>>>> io_resource.start >> 12);
>>>> I provide the result of hose->io_resource.start >> 12 as follows:
>>>> 
>>>> pcie@ffe09000:
>>>> before pci scan: io_resource.start >> 12: 0
>>>> after pci scan : io_resource.start >> 12: ff7ed
>>>> 
>>>> pcie@ffe0a000:
>>>> before pci scan: io_resource.start >> 12: 0
>>>> after pci scan : io_resource.start >> 12: ff7db
>>>> 
>>>> pcie@ffe0b000:
>>>> before pci scan: io_resource.start >> 12: 0
>>>> after pci scan : io_resource.start >> 12: ff7c9
>>>> 
>>>> Note that I tested on P1022DS.
> 
> 
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to