[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110718133101.GB26701@crust.elkhashab.com>
Date: Mon, 18 Jul 2011 08:31:01 -0500
From: Ayman El-Khashab <ayman@...hashab.com>
To: Tony Breeds <tony@...eyournoodle.com>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [v2 PATCH 1/1] powerpc/4xx: enable and fix pcie gen1/gen2 on
the 460sx
On Mon, Jul 18, 2011 at 02:01:15PM +1000, Tony Breeds wrote:
> On Fri, Jul 15, 2011 at 11:40:27AM -0500, Ayman Elkhashab wrote:
>
> > @@ -1582,8 +1628,8 @@ static int __init ppc4xx_setup_one_pciex_POM(struct ppc4xx_pciex_port *port,
> > dcr_write(port->dcrs, DCRO_PEGPL_OMR2BAH, lah);
> > dcr_write(port->dcrs, DCRO_PEGPL_OMR2BAL, lal);
> > dcr_write(port->dcrs, DCRO_PEGPL_OMR2MSKH, 0x7fffffff);
> > - /* Note that 3 here means enabled | single region */
> > - dcr_write(port->dcrs, DCRO_PEGPL_OMR2MSKL, sa | 3);
> > + dcr_write(port->dcrs, DCRO_PEGPL_OMR2MSKL,
> > + sa | DCRO_PEGPL_OMRxMSKL_VAL);
>
> Didn't you just change "sa | 3" to "sa | 1" ?
>
Yes, but I think that is correct for it to be "1". The data
sheets for these parts that I checked had bit 1 marked as
reserved. Only OMR1MSKL and OMR3MSKL had extra definitions
such as the _IO and _UOT. The parts I checked which were
the sheets for the EX and SX (which cover another 6 or 7
parts) all had it with just a single bit defined on that
register.
Ayman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists