public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>,
	linux-input@atrey.karlin.mff.cuni.cz,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Paul Mackerras <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>, Greg KH <greg@kroah.com>
Subject: Re: DMA APIs gumble grumble
Date: Thu, 09 Nov 2006 10:41:21 +1100	[thread overview]
Message-ID: <1163029281.28571.767.camel@localhost.localdomain> (raw)
In-Reply-To: <20061108225612.GA12345@flint.arm.linux.org.uk>

On Wed, 2006-11-08 at 22:56 +0000, Russell King wrote:
> On Wed, Nov 08, 2006 at 07:47:33PM +1100, Benjamin Herrenschmidt wrote:
> > Yes, I need multiple dma_ops for powerpc too
> 
> Ditto for ARM.

Ok, so there is some interest in having the dma_ops in struct device
beyond powerpc.

I'll put together today a patch doing:

 - add #include <asm/device.h> to linux/device.h
 - add a device.h file in asm/* that does:

	struct dev_sysdata {
	};

 - add a struct dev_sysdata sysdata; field to struct device

That patch alone is 0 overhead and allows archs to start adding things.
I'll then modify my pending patches for 2.6.20 to use that instead of my
current device_ext thing.

Is that ok with everybody for 2.6.20 ?

Then, we can do, in no special order:

  - on x86, put the acpi data in there and remove firmware_data from
struct device

  - on x86, m32, frv, put the dma_coherent_mem pointer in there too and
remove it from struct device

  - you can use it on ARM to put your dma_operations pointer as I'm
doing in for powerpc

  - x86 can do the same 

etc...

Cheers,
Ben.



  reply	other threads:[~2006-11-08 23:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08  1:54 DMA APIs gumble grumble Benjamin Herrenschmidt
2006-11-08  4:46 ` David Miller
2006-11-08  5:23   ` Benjamin Herrenschmidt
2006-11-08  5:29     ` David Miller
2006-11-08  5:44       ` Benjamin Herrenschmidt
2006-11-10  1:02   ` Benjamin Herrenschmidt
2006-11-10  2:50     ` David Miller
2006-11-10  2:55       ` Benjamin Herrenschmidt
2006-11-10  3:01         ` David Miller
2006-11-10  4:07           ` Benjamin Herrenschmidt
2006-11-08  8:25 ` Muli Ben-Yehuda
2006-11-08  8:47   ` Benjamin Herrenschmidt
2006-11-08  9:21     ` Muli Ben-Yehuda
2006-11-08 10:00       ` Benjamin Herrenschmidt
2006-11-08 22:56     ` Russell King
2006-11-08 23:41       ` Benjamin Herrenschmidt [this message]
2006-11-09  0:43       ` Benjamin Herrenschmidt

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=1163029281.28571.767.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=anton@samba.org \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=paulus@samba.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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