From: Benjamin Krill <ben@codiert.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, arnd@arndb.de
Subject: Re: [PATCH 2/3] powerpc: setup archdata for {of_}platform via a single platform_notify
Date: Thu, 19 Feb 2009 23:08:20 +0100 [thread overview]
Message-ID: <20090219220820.GH12204@codiert.org> (raw)
In-Reply-To: <1235076557-24464-2-git-send-email-galak@kernel.crashing.org>
* Kumar Gala | 2009-02-19 14:49:16 [-0600]:
>Since a number of powerpc chips are SoCs we end up having dma-able
>devices that are registered as platform or of_platform devices. We need
>to hook the archdata to setup proper dma_ops for these devices.
>
>In the short term the majority of these devices only need the
>direct_dma_ops as the platforms don't have any IOMMUs.
>
>In the future to enable >4G DMA support on ppc32 we can hook swiotlb ops.
>
>Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Benjamin Krill <ben@codiert.org>
next prev parent reply other threads:[~2009-02-19 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 20:49 [PATCH 1/3] powerpc/pci: Default to dma_direct_ops for pci dma_ops Kumar Gala
2009-02-19 20:49 ` [PATCH 2/3] powerpc: setup archdata for {of_}platform via a single platform_notify Kumar Gala
2009-02-19 20:49 ` [PATCH 3/3] powerpc: expect all devices calling dma ops to have archdata set Kumar Gala
2009-02-19 22:08 ` Benjamin Krill
2009-02-20 20:45 ` Becky Bruce
2009-02-19 22:08 ` Benjamin Krill [this message]
2009-02-20 20:44 ` [PATCH 2/3] powerpc: setup archdata for {of_}platform via a single platform_notify Becky Bruce
2009-03-04 4:56 ` Benjamin Herrenschmidt
2009-02-19 20:58 ` [PATCH 1/3] powerpc/pci: Default to dma_direct_ops for pci dma_ops Kumar Gala
2009-02-19 22:08 ` Benjamin Krill
2009-02-20 20:44 ` Becky Bruce
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=20090219220820.GH12204@codiert.org \
--to=ben@codiert.org \
--cc=arnd@arndb.de \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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.