Devicetree
 help / color / mirror / Atom feed
From: Timur Tabi <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Yoder Stuart-B08248
	<B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: question about dma-ranges
Date: Wed, 27 Oct 2010 14:47:37 -0500	[thread overview]
Message-ID: <4CC881D9.6020808@freescale.com> (raw)
In-Reply-To: <20101027144602.2c5ef098-N/eSCTBpGwP7j4BuCOFQISmX4OfbXNuMKnGXBo5VDl8@public.gmane.org>

Scott Wood wrote:
> Or can the QE code just know about that because it only has 32-bit
> registers/descriptor fields for DMA addresses?  I.e. it is a limitation
> of all instances of QE, not just as integrated in this system.

It's a limitation of the QE registers -- they're only 32-bit.  If we ever
produce a new QE that has bigger registers, we can use the compatible property
to distinguish between them.

-- 
Timur Tabi
Linux kernel developer at Freescale

      parent reply	other threads:[~2010-10-27 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27  0:48 question about dma-ranges Yoder Stuart-B08248
     [not found] ` <9696D7A991D0824DBA8DFAC74A9C5FA306911C5F-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2010-10-27  0:51   ` 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 [this message]

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=4CC881D9.6020808@freescale.com \
    --to=timur-kzfg59tc24xl57midrcfdg@public.gmane.org \
    --cc=B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=scottwood-KZfg59tc24xl57MIdRCFDg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox