Re: [PATCH 1/2] PPC32: New OCP core support
From: Matt Porter
Date: Tue May 11 2004 - 20:50:36 EST
On Tue, May 11, 2004 at 08:39:17PM -0400, Valdis.Kletnieks@xxxxxx wrote:
> On Tue, 11 May 2004 17:01:50 PDT, Matt Porter said:
> > New OCP infrastructure ported from 2.4 along with several
> > enhancements. Please apply.
> Big honking patch. Wholesale removal of old code. Wholesale addition of new code.
> And this is the closest to a hint of what an OCP in the old code:
> I'm *guessing* that this is some all-in-one integrated north/south/PCI/east bridge
> with an APIC or similar and some I/O controllers.... Or maybe it's a board-level
> designator like 'ebony' seems to be.. or something..
> It's a UART... or a Bus-level board.. or both.. ;)
Actually, OCP stands for On-Chip Peripheral and is the basic system
we've used in ppc32 for some time now to abstract dumb peripherals
behind a standard API. BenH did yet another rewrite of OCP in 2.4
sometime ago and I picked up that work to port to 2.6 and the new
device model. It is a software abstraction, and easily allows us to
plug in SoC descriptors when new chips come out and use standard
apis to modify device entries on a per-board basis during
"setup_arch() time". It used to be PPC4xx-specific, but now is being
used by PPC85xx, MV64xxx, and MPC52xx based PPC systems. "Now", meaning
that the respective developers for those parts are using the OCP
working tree to base their 2.6 ports off of.
> (Actually, other than the apparent lack of any comment that says what an OCP
> in fact is, I didn't see any really big style problems while scrolling through it..)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/