All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: How to add platform specific data to a of_device
Date: Mon, 16 Jul 2007 08:51:44 +0200	[thread overview]
Message-ID: <20070716065144.GH1678@pengutronix.de> (raw)
In-Reply-To: <1184446133.6059.284.camel@localhost.localdomain>

On Sun, Jul 15, 2007 at 06:48:53AM +1000, Benjamin Herrenschmidt wrote:
> Your approach would work I suppose.... though it's a bit ugly.

Speaking of uggly, I'm still wondering why this oftree stuff for powerpc
must be soooo complicated. If you come from the ARM-linux world like we
do, the whole powerpc BSP stuff looks like a completely overengineered
piece of code, introducing complexity where it isn't necessary. But it
may be that it's just me not knowing powerpc kernel requirements deeply
enough :)

For most of the devices on for example the MPC5200B and MPC8260 I would
just model them as platform devices; there could be a simple

	oftree -> oftree-interpreter -> bunch of platform devices

mapping. Is there a reason why there is sooo much interaction of the
platform code with the oftree? We usually have the situation that, if
something goes wrong, you have to change

	- the driver
	- the platform code
	- the oftree

and they often contain redundant information (like names of oftree
nodes, which change more often than some people's panties).

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

  parent reply	other threads:[~2007-07-16  7:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-14 16:31 How to add platform specific data to a of_device Juergen Beisert
2007-07-14 20:48 ` Benjamin Herrenschmidt
2007-07-15  8:33   ` Juergen Beisert
2007-07-15  8:57     ` Benjamin Herrenschmidt
2007-07-16 16:13       ` Segher Boessenkool
2007-07-16  6:51   ` Robert Schwebel [this message]
2007-07-16  7:09     ` Benjamin Herrenschmidt
2007-07-16  7:19       ` Robert Schwebel
2007-07-16  7:29         ` Benjamin Herrenschmidt
2007-07-16 16:47         ` Segher Boessenkool
2007-07-16 16:28       ` Segher Boessenkool
2007-07-16  7:40     ` Michael Ellerman
2007-07-16 16:16     ` Segher Boessenkool

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=20070716065144.GH1678@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.