Fwd: MPC7410 Linux Kernel

Fwd: MPC7410 Linux Kernel

[Vineeth]

[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]

Hi,

We are trying to port  linux 2.6.38 on MPC7410 based board (This is a
preparatory design by our customer)

System architecture is as follows,

MPC7410 <=> MPC107 <=> PCI_to_LOCAL(plx9052) <=> UART

Previously we were using ppc architecture and we had some issues with
page_init() functions; which may be because of our configuration.As we didnt
get much support on ppc architecture we moved to powerpc.

Now we moved to powerpc architecture. We have some doubts on writing the dts
file. Please find the dts file attached.

when we checked the legacy_serial.c file, we found that
legacy_serial_parents not expecting a pci-local or a pci bridge as parent.
is our understanding correct ? should we introduce a new pci parent in that
structure ?

 We are confused about writing the ranges property of PCI node.we were
referring booting_without_of doc but didnt get much info. Is there any file
which gives better idea about the ranges property ?

Thanks
 Vineeth

[-- Attachment #1.2: Type: text/html, Size: 3089 bytes --]

[-- Attachment #2: obc7410.dts --]
[-- Type: application/octet-stream, Size: 2999 bytes --]

/*
 * Device Tree Souce for OBC7410-CoreEl
 *
 * Choose CONFIG_MPC7410 to build a kernel for OBC7410, or use
 * the default configuration mpc7410_defconfig.
 *
 * Based on kuroboxHG.dts
 *
 * 2011 (c) Vineeth/Sumesh
 * Copyright 2011 CoreEl technologies
 *
 * This file is licensed under
 * the terms of the GNU General Public License version 2.  This program
 * is licensed "as is" without any warranty of any kind, whether express
 * or implied.


 */
/dts-v1/;
/ {
	model = "obc7410";
	compatible = "mpc7410";
	#address-cells = <1>;
	#size-cells = <1>;

	aliases {
		serial0 = &serial0;
		pci0 = &pci0;
	};


	cpus {
		#address-cells = <1>;
		#size-cells = <0>;
		PowerPC,603e { /* Really 7410 */
			device_type = "cpu";
			reg = <0x0>;
			clock-frequency = <266000000>;	/* Fixed by bootloader */
			timebase-frequency = <32522240>; /* Fixed by bootloader */
			bus-frequency = <0>;		/* Fixed by bootloader */
			/* Following required by dtc but not used */
			i-cache-size = <0x4000>;
			d-cache-size = <0x4000>;
		};
	};

	memory {
		device_type = "memory";
		reg = <0x0 0x4000000>;
	};

	soc10x { /* AFAICT i got it from KUROBOXHG :) */
		#address-cells = <1>;
		#size-cells = <1>;
		device_type = "soc";
		compatible = "mpc10x";
		store-gathering = <0>; /* 0 == off, !0 == on */
		reg = <0x80000000 0x100000>;
		ranges = <0x80000000 0x80000000 0x70000000	/* pci mem space */
			      0xfc000000 0xfc000000 0x100000	/* EUMB */
                  0xfe000000 0xfe000000 0xc00000	/* pci i/o space */
                  0xfec00000 0xfec00000 0x300000	/* pci cfg regs */
                  0xfef00000 0xfef00000 0x100000>;	/* pci iack */

			mpic: interrupt-controller@80040000 {
			#interrupt-cells = <2>;
			#address-cells = <0>;
			device_type = "open-pic";
			compatible = "chrp,open-pic";
			interrupt-controller;
			reg = <0x80040000 0x40000>;
    		};

		pci0: pci@fec00000 {
			#address-cells = <3>;
			#size-cells = <2>;
			#interrupt-cells = <1>;
			device_type = "pci";
			compatible = "mpc10x-pci";
			reg = <0xfec00000 0x400000>;
			ranges = <0x1000000 0x0 0x0 0xfe000000 0x0 0xc00000
                      0x2000000 0x0 0x80000000 0x80000000 0x0 0x70000000>;
			bus-range = <0 255>;
			clock-frequency = <133333333>;
			interrupt-parent = <&mpic>;
			interrupt-map-mask = <0xf800 0x0 0x0 0x7>;
       
       			pci2local: pciLocal@0xdb000000 {
				#address-cells = <2>;
				#size-cells = <2>;
				#interrupt-cells = <1>;
				device-type = "pci-local"; 
				compatible = "simple-bus";
                reg = <0xdb000100 0x1000>;
    
                   serial0: serial@0x100 {
                     cell-index = <1>;
                     device_type = "serial";
                     compatible = "ns16550";
                     reg = <0x100 0x1000>;
                     clock-frequency = <130041000>;
                     current-speed = <57600>;
                     interrupts = <10 0>;
                     interrupt-parent = <&mpic>;
                 };
            }; 


		};
	};
};

Re: Fwd: MPC7410 Linux Kernel

[tiejun.chen]

Vineeth wrote:
> Hi,
> 
> We are trying to port  linux 2.6.38 on MPC7410 based board (This is a
> preparatory design by our customer)
> 
> System architecture is as follows,
> 
> MPC7410 <=> MPC107 <=> PCI_to_LOCAL(plx9052) <=> UART

MPCXXX should be compatible with TSIXXX. So you can refer to mpc7448_hpc2.

> 
> Previously we were using ppc architecture and we had some issues with
> page_init() functions; which may be because of our configuration.As we didnt
> get much support on ppc architecture we moved to powerpc.
> 
> Now we moved to powerpc architecture. We have some doubts on writing the dts
> file. Please find the dts file attached.
> 
> when we checked the legacy_serial.c file, we found that
> legacy_serial_parents not expecting a pci-local or a pci bridge as parent.
> is our understanding correct ? should we introduce a new pci parent in that
> structure ?

So you can understand this after refer to the file,
arch/powerpc/boot/dts/mpc7448hpc2.dts.

Tiejun

> 
>  We are confused about writing the ranges property of PCI node.we were
> referring booting_without_of doc but didnt get much info. Is there any file
> which gives better idea about the ranges property ?
> 
> Thanks
>  Vineeth

Re: Fwd: MPC7410 Linux Kernel

[Vineeth]

[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]

Thanks for the reply.

We were referring kuroboxHG.dts which uses Sandpoint architecture; which is
almost same as ours.

1. one doubt in kuroboxHG is the ranges property in SOC node says EUMB is at
0xFC00_0000; and as per the datasheet of mpc107, the open pic address will
be EUMB_BASE + 0x40000; but in kurobox its given as 0x80040000;

2. We know that our UART is mapped at address 0xDB00_0100; which is
connected in a PCI-LOCAL bridge whose base is at 0xDB00_0000
How can i represent these things in dts ? Can the RANGES property of PCI
node can mention this ?







On Tue, Aug 2, 2011 at 1:15 PM, tiejun.chen <tiejun.chen@windriver.com>wrote:

> Vineeth wrote:
> > Hi,
> >
> > We are trying to port  linux 2.6.38 on MPC7410 based board (This is a
> > preparatory design by our customer)
> >
> > System architecture is as follows,
> >
> > MPC7410 <=> MPC107 <=> PCI_to_LOCAL(plx9052) <=> UART
>
> MPCXXX should be compatible with TSIXXX. So you can refer to mpc7448_hpc2.
>
> >
> > Previously we were using ppc architecture and we had some issues with
> > page_init() functions; which may be because of our configuration.As we
> didnt
> > get much support on ppc architecture we moved to powerpc.
> >
> > Now we moved to powerpc architecture. We have some doubts on writing the
> dts
> > file. Please find the dts file attached.
> >
> > when we checked the legacy_serial.c file, we found that
> > legacy_serial_parents not expecting a pci-local or a pci bridge as
> parent.
> > is our understanding correct ? should we introduce a new pci parent in
> that
> > structure ?
>
> So you can understand this after refer to the file,
> arch/powerpc/boot/dts/mpc7448hpc2.dts.
>
> Tiejun
>
> >
> >  We are confused about writing the ranges property of PCI node.we were
> > referring booting_without_of doc but didnt get much info. Is there any
> file
> > which gives better idea about the ranges property ?
> >
> > Thanks
> >  Vineeth
>
>

[-- Attachment #2: Type: text/html, Size: 2551 bytes --]

Re: Fwd: MPC7410 Linux Kernel

[tiejun.chen]

Vineeth wrote:
> Thanks for the reply.
> 
> We were referring kuroboxHG.dts which uses Sandpoint architecture; which is
> almost same as ours.
> 
> 1. one doubt in kuroboxHG is the ranges property in SOC node says EUMB is at
> 0xFC00_0000; and as per the datasheet of mpc107, the open pic address will
	
And for powerpc looks u-boot should initialize MPC107 and EUMB_ADDR should be
configured as well. And kernel doesn't reconfigure EUMB again. This is different
from original ppc implementation.

So I think you should check how u-boot did. Note not all targets use 0xfc000000
as EUMB_ADDR. At least for linkstation 0x8000000 is set as EUMB_ADDR. And so
maybe this value, 0xFC000000, should be one typo since kernel don't use this
node property as I previously said.

> be EUMB_BASE + 0x40000; but in kurobox its given as 0x80040000;
> 
> 2. We know that our UART is mapped at address 0xDB00_0100; which is
> connected in a PCI-LOCAL bridge whose base is at 0xDB00_0000
> How can i represent these things in dts ? Can the RANGES property of PCI
> node can mention this ?

How do u-boot resided on your target set EUMB_ADDR? Then you can migrate
kuroboxHG.dts with this base address.

Tiejun

> 
> 
> 
> 
> 
> 
> 
> On Tue, Aug 2, 2011 at 1:15 PM, tiejun.chen <tiejun.chen@windriver.com>wrote:
> 
>> Vineeth wrote:
>>> Hi,
>>>
>>> We are trying to port  linux 2.6.38 on MPC7410 based board (This is a
>>> preparatory design by our customer)
>>>
>>> System architecture is as follows,
>>>
>>> MPC7410 <=> MPC107 <=> PCI_to_LOCAL(plx9052) <=> UART
>> MPCXXX should be compatible with TSIXXX. So you can refer to mpc7448_hpc2.
>>
>>> Previously we were using ppc architecture and we had some issues with
>>> page_init() functions; which may be because of our configuration.As we
>> didnt
>>> get much support on ppc architecture we moved to powerpc.
>>>
>>> Now we moved to powerpc architecture. We have some doubts on writing the
>> dts
>>> file. Please find the dts file attached.
>>>
>>> when we checked the legacy_serial.c file, we found that
>>> legacy_serial_parents not expecting a pci-local or a pci bridge as
>> parent.
>>> is our understanding correct ? should we introduce a new pci parent in
>> that
>>> structure ?
>> So you can understand this after refer to the file,
>> arch/powerpc/boot/dts/mpc7448hpc2.dts.
>>
>> Tiejun
>>
>>>  We are confused about writing the ranges property of PCI node.we were
>>> referring booting_without_of doc but didnt get much info. Is there any
>> file
>>> which gives better idea about the ranges property ?
>>>
>>> Thanks
>>>  Vineeth
>>
>