All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
To: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Cc: Yoder Stuart-B08248
	<b08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	devicetree-discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: standard property to convey device dma address width?
Date: Mon, 16 Aug 2010 10:17:10 -1000	[thread overview]
Message-ID: <4C699CC6.1060507@firmworks.com> (raw)
In-Reply-To: <5A878376-AFCC-4CB0-A0E9-F2F497066FD5-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>

Kumar Gala wrote:
> Do we or should we have a standard property to convey that address width a device is capable of?
>   

What is the context?  When Open Firmware was first developed, the only 
bus with partial addresses was ISA.  The ISA bus binding has a "dma" 
property that describes some of the legacy DMA characteristics, but 
address width isn't one of them, for reasons that I don't remember.

I thought at the time (perhaps wishfully) that partial addresses would 
not be consideration for future buses, because

a) The transition to large-scale integration had already made logic 
gates nearly "free", so there was no motivation to skimp on address 
register bits.

b) Although packages were - and still are - pin-limited, partial address 
bus connections were not feasible because of uneven bus loading problems.

c) Address and data buses were usually multiplexed onto the same pins, 
further reducing the motivation for partial addresses.

Obviously, since you are asking the question, there is some case where 
address width could be variable.  I'd be interested to learn the details.

If I had to describe a partial address, I'd consider a property name 
like "dma-address-mask", whose value is a bitmap of implemented bits, 
corresponding to the bits in a unit address for the parent bus.  
Low-order bits might be zero if the DMA addressing hardware had 
alignment restrictions.

> - k
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
>   

  parent reply	other threads:[~2010-08-16 20:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16 16:01 standard property to convey device dma address width? Kumar Gala
     [not found] ` <5A878376-AFCC-4CB0-A0E9-F2F497066FD5-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2010-08-16 20:17   ` Mitch Bradley [this message]
     [not found]     ` <4C699CC6.1060507-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2010-08-17 20:55       ` Kumar Gala
     [not found]         ` <366D8D84-D210-4BC1-8FC1-4E0A9E06C433-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2010-08-17 21:03           ` Scott Wood
     [not found]             ` <20100817160317.458ea513-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2010-08-18  3:57               ` Kumar Gala
2010-08-17 21:22           ` Mitch Bradley
2010-08-17 20:50   ` Yoder Stuart-B08248
     [not found]     ` <9696D7A991D0824DBA8DFAC74A9C5FA3065BD776-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2010-08-17 20:54       ` Kumar Gala

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=4C699CC6.1060507@firmworks.com \
    --to=wmb-d5eqfidgl7eakbo8gow8eq@public.gmane.org \
    --cc=b08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@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.