All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoder Stuart-B08248 <B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: question about dma-ranges
Date: Tue, 26 Oct 2010 17:48:47 -0700	[thread overview]
Message-ID: <9696D7A991D0824DBA8DFAC74A9C5FA306911C5F@az33exm25.fsl.freescale.net> (raw)

Mitch,

In the dma-ranges proposal:

http://playground.sun.com/1275/proposals/Closed/Accepted/410-it.txt

...there is the following special case described:

   As a special case, a "dma-ranges" property may be present in the
   root node of the device tree.  In this case, the property value
   describes the ranges of DMA addresses that the system bus can
   accept.  In this case, the length of the parent-address portion
   of each entry in the property value is 0 (because the root node
   has no parent), so the format reduces to...

A few of us in the ePAPR committee were discussing this and
were wondering what the use case for a dma-ranges on the
root is.   Is this special case really needed?

Thanks,
Stuart Yoder

             reply	other threads:[~2010-10-27  0:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27  0:48 Yoder Stuart-B08248 [this message]
     [not found] ` <9696D7A991D0824DBA8DFAC74A9C5FA306911C5F-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2010-10-27  0:51   ` question about dma-ranges Mitch Bradley
     [not found]     ` <4CC77784.2070701-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2010-10-27  1:37       ` Timur Tabi
     [not found]         ` <AANLkTikTu_p0-Uk7=FuUay4mvCEEU0e9V5eY6bjuK5RQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-27  2:42           ` David Gibson
2010-10-27 19:46             ` Scott Wood
     [not found]               ` <20101027144602.2c5ef098-N/eSCTBpGwP7j4BuCOFQISmX4OfbXNuMKnGXBo5VDl8@public.gmane.org>
2010-10-27 19:47                 ` Timur Tabi

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=9696D7A991D0824DBA8DFAC74A9C5FA306911C5F@az33exm25.fsl.freescale.net \
    --to=b08248-kzfg59tc24xl57midrcfdg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.