From: Allen Curtis <acurtis@onz•com>
To: Kumar Gala <kumar.gala@freescale•com>
Cc: Ppc Embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: RFC cpm2_devices DPRAM resource
Date: Thu, 16 Jun 2005 11:08:55 -0700 [thread overview]
Message-ID: <b7db6a3e19a7cb5aa613c6fc25510e1c@onz.com> (raw)
In-Reply-To: <1278c2c53202b80080519cca60bb438f@freescale.com>
>> 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.
>
> Well, we already have an allocator for general dpram memory. I'm not
> really sure how this would help beyond reducing the fact that we may
> ioremap() regions more than once. I think the better solution there
> is to look at the patches that have been made to ioremap() to return
> the same virtual addresses if you are remapping a region of physical
> memory that already has a mapping.
>
I guess my thought regarding the dpalloc() statement is that those
functions could query the platform_device structure to find the region
they are managing. Make them a little more general.
next prev parent reply other threads:[~2005-06-16 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 17:45 RFC cpm2_devices DPRAM resource Allen Curtis
2005-06-16 17:58 ` Kumar Gala
2005-06-16 18:08 ` Allen Curtis [this message]
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=b7db6a3e19a7cb5aa613c6fc25510e1c@onz.com \
--to=acurtis@onz$(echo .)com \
--cc=kumar.gala@freescale$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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