From: "David S. Miller" <davem@redhat.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: hch@infradead.org, Marc Zyngier <mzyngier@freesurf.fr>,
rth@twiddle.net, linux-kernel@vger.kernel.org
Subject: Re: [Patch] DMA mapping API for Alpha
Date: 01 May 2003 03:56:01 -0700 [thread overview]
Message-ID: <1051786561.8772.4.camel@rth.ninka.net> (raw)
In-Reply-To: <20030430000807.A731@localhost.park.msu.ru>
On Tue, 2003-04-29 at 13:08, Ivan Kokshaysky wrote:
> Ok, for clean dma_* implementation on alpha (and others, I guess) we need
> to move root level IO controller data from struct pci_dev (pdev->sysdata)
> to struct dev. Actually, the latter already has such field (platform_data)
> but right now it's kind of parisc specific. ;-)
> I'll look into it after short vacation (4-5 days).
I don't know if this will really be all that nice Ivan.
The data is different for me on PCI vs. SBUS vs. whatever.
This knowledge of what the dev->platform_data type is has to come from
somewhere.
This means device->ops->dma_*(), a level of indirection I wish terribly
that we could avoid. If a driver is PCI or SBUS only it should not eat
this overhead, I should just call call sbus_*() or pci_*() and this
vectors directly to the proper DMA routines.
Doing all of this generic crap is nice for writing generic drivers,
but terrible for what the generated code will look like. This kind of
stuff tends to silently accumulate, and it's really hard to delete once
it's there.
--
David S. Miller <davem@redhat.com>
next prev parent reply other threads:[~2003-05-02 0:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 18:38 [Patch] DMA mapping API for Alpha Marc Zyngier
2003-04-28 18:49 ` Jeff Garzik
2003-04-28 18:52 ` Marc Zyngier
2003-04-28 22:20 ` Alan Cox
2003-04-29 6:59 ` Christoph Hellwig
2003-04-29 11:05 ` Ivan Kokshaysky
2003-04-29 11:20 ` Christoph Hellwig
2003-04-29 12:08 ` Ivan Kokshaysky
2003-04-29 12:32 ` Christoph Hellwig
2003-04-29 12:59 ` Ivan Kokshaysky
2003-04-29 11:58 ` Marc Zyngier
2003-04-29 12:23 ` Ivan Kokshaysky
2003-04-29 12:37 ` Marc Zyngier
2003-04-29 12:41 ` Christoph Hellwig
2003-04-29 20:08 ` Ivan Kokshaysky
2003-05-01 10:56 ` David S. Miller [this message]
2003-04-30 12:07 ` Maciej W. Rozycki
2003-04-30 14:12 ` Jeff Garzik
2003-04-30 14:18 ` Marc Zyngier
2003-04-30 19:25 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2003-04-29 20:22 James Bottomley
2003-04-29 20:46 ` Ivan Kokshaysky
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=1051786561.8772.4.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=hch@infradead.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mzyngier@freesurf.fr \
--cc=rth@twiddle.net \
/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