LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Allen Curtis <acurtis@onz.com>
To: Ppc Embedded <linuxppc-embedded@ozlabs.org>
Subject: RFC cpm2_devices DPRAM resource
Date: Thu, 16 Jun 2005 10:45:28 -0700	[thread overview]
Message-ID: <ecc06b51023e6ebd23d075aa3948749e@onz.com> (raw)

Slightly different question than the current thread:

Should the DPRAM appear as it's own platform_device?
Option 1) Specify the portion of the DPRAM used by each device with 
that platform_device definition. (current)

Option 2) Define the whole DPRAM region as its own platform_device 
entry. Move the device DPRAM information to the device specific 
platform structure.

Would this help with a general dpalloc() implementation? It would 
reduce the number of ioremap() regions.

Another thought.

             reply	other threads:[~2005-06-16 17:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 17:45 Allen Curtis [this message]
2005-06-16 17:58 ` RFC cpm2_devices DPRAM resource Kumar Gala
2005-06-16 18:08   ` Allen Curtis
2005-06-16 19:36   ` Dan Malek
2005-06-16 19:41 ` Dan Malek
2005-06-16 20:07   ` Allen Curtis
2005-06-17  6:48     ` 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=ecc06b51023e6ebd23d075aa3948749e@onz.com \
    --to=acurtis@onz.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