Searched hist:"287 df01e6aef0464c5e5bcbd7e87aa4ff1f24f5a" (Results 1 – 4 of 4) sorted by relevance
| /rk3399_rockchip-uboot/arch/powerpc/include/asm/ |
| H A D | fsl_pci.h | 287df01e6aef0464c5e5bcbd7e87aa4ff1f24f5a Sat Oct 12 05:46:33 UTC 2013 Zhao Qiang <B45475@freescale.com> PCIe:change the method to get the address of a requested capability in configuration space.
Previously, the address of a requested capability is define like that
"#define PCI_DCR 0x78"
But, the addresses of capabilities is different with regard to PCIe revs.
So this method is not flexible.
Now a function to get the address of a requested capability is added and used.
It can get the address dynamically by capability ID.
The step of this function:
1. Read Status register in PCIe configuration space to confirm that
Capabilities List is valid.
2. Find the address of Capabilities Pointer Register.
3. Find the address of requested capability from the first capability.
Signed-off-by: Zhao Qiang <B45475@freescale.com>
|
| /rk3399_rockchip-uboot/drivers/pci/ |
| H A D | pci.c | 287df01e6aef0464c5e5bcbd7e87aa4ff1f24f5a Sat Oct 12 05:46:33 UTC 2013 Zhao Qiang <B45475@freescale.com> PCIe:change the method to get the address of a requested capability in configuration space.
Previously, the address of a requested capability is define like that
"#define PCI_DCR 0x78"
But, the addresses of capabilities is different with regard to PCIe revs.
So this method is not flexible.
Now a function to get the address of a requested capability is added and used.
It can get the address dynamically by capability ID.
The step of this function:
1. Read Status register in PCIe configuration space to confirm that
Capabilities List is valid.
2. Find the address of Capabilities Pointer Register.
3. Find the address of requested capability from the first capability.
Signed-off-by: Zhao Qiang <B45475@freescale.com>
|
| H A D | fsl_pci_init.c | 287df01e6aef0464c5e5bcbd7e87aa4ff1f24f5a Sat Oct 12 05:46:33 UTC 2013 Zhao Qiang <B45475@freescale.com> PCIe:change the method to get the address of a requested capability in configuration space.
Previously, the address of a requested capability is define like that
"#define PCI_DCR 0x78"
But, the addresses of capabilities is different with regard to PCIe revs.
So this method is not flexible.
Now a function to get the address of a requested capability is added and used.
It can get the address dynamically by capability ID.
The step of this function:
1. Read Status register in PCIe configuration space to confirm that
Capabilities List is valid.
2. Find the address of Capabilities Pointer Register.
3. Find the address of requested capability from the first capability.
Signed-off-by: Zhao Qiang <B45475@freescale.com>
|
| /rk3399_rockchip-uboot/include/ |
| H A D | pci.h | 287df01e6aef0464c5e5bcbd7e87aa4ff1f24f5a Sat Oct 12 05:46:33 UTC 2013 Zhao Qiang <B45475@freescale.com> PCIe:change the method to get the address of a requested capability in configuration space.
Previously, the address of a requested capability is define like that
"#define PCI_DCR 0x78"
But, the addresses of capabilities is different with regard to PCIe revs.
So this method is not flexible.
Now a function to get the address of a requested capability is added and used.
It can get the address dynamically by capability ID.
The step of this function:
1. Read Status register in PCIe configuration space to confirm that
Capabilities List is valid.
2. Find the address of Capabilities Pointer Register.
3. Find the address of requested capability from the first capability.
Signed-off-by: Zhao Qiang <B45475@freescale.com>
|