public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Robert Love" <rml@ximian.com>
Cc: <mochel@digitalimplant.org>, "Greg KH" <greg@kroah.com>,
	<ambx1@neo.rr.com>, <len.brown@intel.com>, <shaohua.li@intel.com>,
	"Bjorn Helgaas" <bjorn.helgaas@hp.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Device Resource Management
Date: Thu, 16 Dec 2004 09:21:44 -0600	[thread overview]
Message-ID: <31B0C50E-4F76-11D9-8900-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1103173505.6052.282.camel@localhost>

Two issues that we have discussed for embedded usage would be making 
resources 64-bit always.  We are starting to see more and more systems 
with greater than 32-bits of physical address space while still having 
32-bit effective.  The second is sharing resources.  On several devices 
the IO memory region for one device may reside inside another.  One 
example of this is the registers used to control ethernet MII PHYs 
exist inside of an ethernet controllers register block.

Also, I liked having a name in resource.  It allows us to find the 
specific resource we need if we have multiple resources of a given type 
without assuming order.  And thus adding a device_find_iores_bynames().

- kumar


  reply	other threads:[~2004-12-16 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11  5:45 [RFC] Device Resource Management Adam Belay
2004-12-16  4:14 ` Greg KH
2004-12-16  4:57   ` Adam Belay
2004-12-17 19:21     ` Greg KH
2004-12-16  5:05   ` Robert Love
2004-12-16 15:21     ` Kumar Gala [this message]
2004-12-17 19:18     ` Greg KH

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=31B0C50E-4F76-11D9-8900-000393DBC2E8@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=rml@ximian.com \
    --cc=shaohua.li@intel.com \
    /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