linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* PCIe switch driver in Linux 2.6.29
@ 2010-02-27 23:59 Hu, Bingquan (NSN - CN/Shanghai)
  0 siblings, 0 replies; only message in thread
From: Hu, Bingquan (NSN - CN/Shanghai) @ 2010-02-27 23:59 UTC (permalink / raw)
  To: linuxppc-dev

Hi,

I am new to this mail list and this is my first post, I apologize if I =
break some rules.

Description of the problem:
We incorporated Freescale MPC8548E CPU, PLX PEX8648 PCIe switch and =
Altera FPGA into our solution.
FPGA has one prefetchable 64-bit BAR 0 and 32-bit non-prefetchable =
Bar2.It was recognized successfully,as well as the PCIe switch.
But there are resources collisions on the upstream bridge and the =
downstream bridge connected to FPGA.
the startup log, as well the device tree, is shown below.

My question is:=20
am I missing something in the device tree that standa for the PCIe =
switch?
Do I need to code in the Linux kernel to fix this problem?

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D startup log =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
pci 0000:01:00.0: device not available because of BAR 0 =
[0xb0000000-0xb001ffff] collisions
pci 0000:01:00.0: device not available because of BAR 8 =
[0xb0000000-0xb00fffff] collisions
pci 0000:01:00.0: device not available because of BAR 9 =
[0xa0000000-0xa0ffffff] collisions
pci 0000:02:08.0: device not available because of BAR 8 =
[0xb0000000-0xb00fffff] collisions
pci 0000:02:08.0: device not available because of BAR 9 =
[0xa0000000-0xa0ffffff] collisions=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D device tree regarding PCIe =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
	pci2: pcie@e000a000 {
		cell-index =3D <2>;
		interrupt-map-mask =3D <0xf800 0x0 0x0 0x7>;
		interrupt-map =3D <

			/* IDSEL 0x0 (PEX) */
			00000 0x0 0x0 0x1 &mpic 0x0 0x1
			00000 0x0 0x0 0x2 &mpic 0x1 0x1
			00000 0x0 0x0 0x3 &mpic 0x2 0x1
			00000 0x0 0x0 0x4 &mpic 0x3 0x1>;

		interrupt-parent =3D <&mpic>;
		interrupts =3D <26 2>;
		bus-range =3D <0 255>;
		ranges =3D <0x2000000 0x0 0x10000000 0xb0000000 0x0 0x10000000
		        0x43000000 0x0 0x0 0xa0000000 0x0 0x10000000
			  0x1000000 0x0 0x0 0xe3000000 0x0 0x100000>;

	      //ranges =3D empty;
		clock-frequency =3D <33333333>;
		#interrupt-cells =3D <1>;
		#size-cells =3D <2>;
		#address-cells =3D <3>;
		reg =3D <0xe000a000 0x1000>;
		compatible =3D "fsl,mpc8548-pcie";
		device_type =3D "pci";
		pcie@0 {
			reg =3D <0x0 0x0 0x0 0x0 0x0>;
			#size-cells =3D <2>;
			#address-cells =3D <3>;
			device_type =3D "pci";
			//ranges =3D empty;
			ranges =3D <0x2000000 0x0 0x10000000
				  0x20000000 0x0 0x0
				  0x0 0x10000000

                            0x43000000 0x0 0xa0000000
				  0x43000000 0x0 0xa0000000
				  0x0 0x10000000

				  0x1000000 0x0 0x0
				  0x1000000 0x0 0x0
				  0x0 0x100000>;
				 =20
		};
	};

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-02-28  0:19 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-02-27 23:59 PCIe switch driver in Linux 2.6.29 Hu, Bingquan (NSN - CN/Shanghai)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).