SATA FSL and upstreaming

Zang Roy-R61911 r61911 at freescale.com
Thu May 16 17:20:00 EST 2013



> -----Original Message-----
> From: tiejun.chen [mailto:tiejun.chen at windriver.com]
> Sent: Thursday, May 16, 2013 2:25 PM
> To: Zang Roy-R61911
> Cc: Benjamin Herrenschmidt; Liu Qiang-B32616; Fleming Andy-AFLEMING;
> linuxppc-dev at lists.ozlabs.org; Xie Shaohui-B21989; Bhushan Bharat-R65777
> Subject: Re: SATA FSL and upstreaming
> 
> On 05/16/2013 02:20 PM, Zang Roy-R61911 wrote:
> >
> >
> >> -----Original Message-----
> >> From: tiejun.chen [mailto:tiejun.chen at windriver.com]
> >> Sent: Thursday, May 16, 2013 2:18 PM
> >> To: Benjamin Herrenschmidt
> >> Cc: Zang Roy-R61911; Liu Qiang-B32616; Fleming Andy-AFLEMING;
> >> linuxppc- dev at lists.ozlabs.org; Xie Shaohui-B21989; Bhushan
> >> Bharat-R65777
> >> Subject: Re: SATA FSL and upstreaming
> >>
> >> On 05/16/2013 02:09 PM, Benjamin Herrenschmidt wrote:
> >>> On Thu, 2013-05-16 at 06:05 +0000, Zang Roy-R61911 wrote:
> >>>> I do not suggest changing the RCW. If the RCW is broken on Ben's
> >>>> side, it is not easy to recover for him.
> >>>> Let's check the U-boot output first.
> >>>
> >>> U-Boot 2013.01-00009-g7bcd7f4 (Mar 14 2013 - 14:23:16)
> >>>
> >>> CPU0:  P5020E, Version: 1.0, (0x82280010)
> >>> Core:  E5500, Version: 1.0, (0x80240010) Clock Configuration:
> >>>          CPU0:2000 MHz, CPU1:2000 MHz,
> >>>          CCB:800  MHz,
> >>>          DDR:666.667 MHz (1333.333 MT/s data rate) (Asynchronous),
> >> LBC:100  MHz
> >>>          FMAN1: 600 MHz
> >>>          QMAN:  400 MHz
> >>>          PME:   400 MHz
> >>> L1:    D-cache 32 kB enabled
> >>>          I-cache 32 kB enabled
> >>> Board: P5020DS, Sys ID: 0x1c, Sys Ver: 0x12, FPGA Ver: 0x05, vBank:
> >>> 0 Reset Configuration Word (RCW):
> >>>          00000000: 0c540000 00000000 1e120000 00000000
> >>>          00000010: d8984a01 03002000 de800000 41000000
> >>>          00000020: 00000000 00000000 00000000 10070000
> >>>          00000030: 00000000 00000000 00000000 00000000
> >>
> >> I think you can use Bharat's RCW, which seems RR_HXAPNSP_0x36, then
> >> please take a look at this:
> > Why?
> 
> I just believe Bharat should pick a proper RCW from SDK.
We may also need to check the original RCW why it does not work!

> 
> > Ben's on board RCW protocol is 0x36, which should work for PCIe1 (slot
> 7) and PCIe3 (slot4).
> 
> Didn't you see I'm also saying to use slot 7 and slot 4?
Which slot depends on Serdes protocol. slot7 is fixed to pcie1.
Roy


More information about the Linuxppc-dev mailing list