linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] base board consolidation
Date: Mon, 4 Jul 2011 11:38:20 +0100	[thread overview]
Message-ID: <20110704103820.GC8286@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACTFLAPsaiF8KEXeDGOX72dcAvzegHDUQcPEPNxywwYewrHsUw@mail.gmail.com>

On Mon, Jul 04, 2011 at 12:20:08PM +0200, Daniel Mack wrote:
> Yes, I would also much more like to see these boards being supported
> by DT, and eventually, we can probably provide static tree definitions
> for these boards and get rid of the whole code entirely.

While some of that can be done, I think the idea of getting rid of all
the code is a pipedream - things like detecting the LCD panel is
something which has to be in code.

Having separate DT blobs because you happen to have connected a different
LCD display is not sane when you can detect the LCD type at run time -
from either the support perspective or the maintainence perspective.

There's also a similar issue where the ethernet controller may be of
two different types, which can only be detected at runtime - and again
having different DT blobs would be a nightmare.

With that alone, you're talking about 10 different DT blobs (5 different
CLCD panel configs + 2 ethernet configs) for just one Realview board.

There's also the matter of the platform specific registers setting the
clock speed for the SP804 timers.

So no, I don't think that we'll ever get rid of all the code for ARMs
development platforms without losing functionality/utility, but we should
be able to get rid of quite an amount like I've already done by
consolidating across the entire set with plat-versatile.

  reply	other threads:[~2011-07-04 10:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  9:44 [RFC PATCH 0/3] base board consolidation Uwe Kleine-König
2011-07-01  9:46 ` [RFC PATCH 1/3] ARM: common abstraction for specifying a baseboard Uwe Kleine-König
2011-07-01  9:46   ` [RFC PATCH 2/3] ARM: imx/mx31moboard: convert to new baseboard handling Uwe Kleine-König
2011-07-01  9:46   ` [RFC PATCH 3/3] ARM: imx/mx31moboard: remove obsolete " Uwe Kleine-König
2011-07-04  8:19 ` [RFC PATCH 0/3] base board consolidation Philippe Rétornaz
2011-07-04  8:27 ` Russell King - ARM Linux
2011-07-04 10:20   ` Daniel Mack
2011-07-04 10:38     ` Russell King - ARM Linux [this message]
2011-07-04 11:55       ` Marek Vasut
2011-07-04 12:33         ` Russell King - ARM Linux

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=20110704103820.GC8286@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 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).