public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] DMA mapping API for Alpha
Date: 29 Apr 2003 15:22:12 -0500	[thread overview]
Message-ID: <1051647735.2501.45.camel@mulgrave> (raw)



> 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).

Well, it (platform_data) predates the parisc conversion to the dma_
API.  I just assumed that was what it was there fore.  I had to do it
this way because parisc has a rather nasty set up in that there are
usually two PCI (and several other busses) which connect to two
different IO-MMUs.  I use the platform_data field to cache the
particular IO-MMU the device is connected to.  I assume this is the same
in alpha?

Previously parisc was using the sysdata field of the pci_dev (and
constructing fake pci_devs for other busses).  The conversion wasn't
actually that complex (although it was made easier on parisc because the
IO-MMU lives above the PCI busses, so in the generic device model we can
simply now traverse parents to find it).

James



             reply	other threads:[~2003-04-29 20:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 20:22 James Bottomley [this message]
2003-04-29 20:46 ` [Patch] DMA mapping API for Alpha Ivan Kokshaysky
  -- strict thread matches above, loose matches on Subject: below --
2003-04-28 18:38 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
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

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=1051647735.2501.45.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.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