LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan Masel" <jmasel@arabellasw.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Re: [RFC][PATCH 2.6.12-rc2 3/3] FCC Ethernet PlatformDevice
Date: Thu, 5 May 2005 16:58:10 +0200	[thread overview]
Message-ID: <E1DTgrw-0004Lt-00@gold.webfusion.co.uk> (raw)
In-Reply-To: <mailman.0.1115279646.20825.linuxppc-embedded@ozlabs.org>

Are you interested in looking at our Resource Manager? It works in 2.4 and
2.6 kernels for a wide range of PQ's (virtually all of them).

It seems to take some of these ideas, but further. The basic idea is to
handle at all on-chip resources in an orderly and robust way (not just
modularly, but that too). We allocate parallel port pins, clocks (BRG or
CLK), internal DPRAM and communication channels to "consumers". Board
specific (if/where needed) are all located in a single per-board file.
Allocation is all dynamic and we can check that we're not conflicting with
prior requests. There are quite a few other goodies too (display all
consumers to which certain resources are allocated, etc).

This lets us easily handle dynamic configurations. E.g. configure pins for
I2C during reset or start-up, modify them later on when you need ATM (they
are multiplexed on the same pins on several devices). Or, as you mentioned,
dynamic modules - but even when they have potentially conflicting requests.

And it is one, simple to use mechanism that we use across all devices
(adapted for PQ1, PQ2 and PQ3).

If you're interested, please let me know. We'd be happy to contribute it if
it will help.

Jonathan

       reply	other threads:[~2005-05-05 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1115279646.20825.linuxppc-embedded@ozlabs.org>
2005-05-05 14:58 ` Jonathan Masel [this message]
2005-05-05 14:40   ` [RFC][PATCH 2.6.12-rc2 3/3] FCC Ethernet PlatformDevice Pantelis Antoniou

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=E1DTgrw-0004Lt-00@gold.webfusion.co.uk \
    --to=jmasel@arabellasw.com \
    --cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox