From: Matt Porter <mporter@kernel.crashing.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Brian Waite <brian@waitefamily.us>,
lachwani@pmc-sierra.com, Ralf Baechle <ralf@linux-mips.org>,
mdharm@momenco.com, linuxppc-embedded@ozlabs.org,
sjhill@realitydiluted.com, David Woodhouse <dwmw2@infradead.org>,
rabeeh@galileo.co.il, Russell King <rmk@arm.linux.org.uk>
Subject: Re: OCP vs. platform_device (was Marvell 64360/64340 GigE driver for MIPS and PPC....)
Date: Fri, 8 Oct 2004 13:42:50 -0700 [thread overview]
Message-ID: <20041008134250.A15724@home.com> (raw)
In-Reply-To: <4166D5E7.8080209@mvista.com>; from mgreer@mvista.com on Fri, Oct 08, 2004 at 11:01:11AM -0700
On Fri, Oct 08, 2004 at 11:01:11AM -0700, Mark A. Greer wrote:
> Moving to a wider PPC audience...
>
> Mark
> --
>
> Russell King wrote:
>
> >On Fri, Oct 08, 2004 at 12:16:43PM +0100, David Woodhouse wrote:
> >
> >
> >>On Fri, 2004-10-08 at 13:13 +0200, Ralf Baechle wrote:
> >>
> >>
> >>>I was already considering to implement something like OCP for MIPS also.
> >>>Since it already exists on PPC I instead would suggest to move
> >>>arch/ppc/syslib/ocp.c into generic code, something like drivers/ocp/
> >>>maybe?
> >>>
> >>>
> >>Fine... but if you're doing that instead of extending platform_device to
> >>meet your needs, make sure you remove platform_device while you're at it
> >>and convert its users to OCP.
> >>
> >>
> >
> >There are a lot of users of platform devices, and this now includes
> >virtually everything in the input layer. This would be a very large
> >amount of work to rip out platform devices.
<snip a bunch of valid points>
> >So I think ripping out platform devices and throwing in something
> >which is very different is a backwards step.
As I've mentioned a couple time now on #mklinux, we should be
moving to platform_device on PPC. When I moved OCP forward from
2.4 it was because a bunch of work was done to fix it up there
by BenH and the 4xx stuff had been using it for a long time before
platform_device was around. There's a bunch of "backend" type info
that is PPC subarch specific that is encoded in the .additions field
of the OCP defs that can be moved to the platform_data field. That's
really where most of the important stuff for OCP is at. We really
just need somebody with time to convert all the subarches to add
platform_devices and drivers to gather info from them. I may or
may not have time to accomplish this myself in the near future.
The point here is that I'm 100% behind converting from ocp_device
to platform_device as long as whoever does it preserves the
rest of the functionality (which should mostly can accomplished
by moving the additions info to platform_data. Maybe it's only
4xx that needs this so other PPC subarches can convert possibly
with a little less work.
-Matt
prev parent reply other threads:[~2004-10-08 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CFESm-0002PH-00@real.realitydiluted.com>
[not found] ` <4165E52E.60908@waitefamily.us>
[not found] ` <20041008111345.GA23212@linux-mips.org>
[not found] ` <1097234203.318.89.camel@hades.cambridge.redhat.com>
[not found] ` <20041008122633.C17999@flint.arm.linux.org.uk>
2004-10-08 18:01 ` OCP vs. platform_device (was Marvell 64360/64340 GigE driver for MIPS and PPC....) Mark A. Greer
2004-10-08 18:03 ` Mark A. Greer
2004-10-08 20:42 ` Matt Porter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041008134250.A15724@home.com \
--to=mporter@kernel.crashing.org \
--cc=brian@waitefamily.us \
--cc=dwmw2@infradead.org \
--cc=lachwani@pmc-sierra.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mdharm@momenco.com \
--cc=mgreer@mvista.com \
--cc=rabeeh@galileo.co.il \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
--cc=sjhill@realitydiluted.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).