From: Becky Bruce <beckyb@kernel.crashing.org>
To: Benjamin Krill <ben@codiert.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: Fri, 20 Feb 2009 14:44:51 -0600 [thread overview]
Message-ID: <6F644D32-0FEF-4D42-9735-4ECF5371009F@kernel.crashing.org> (raw)
In-Reply-To: <20090219220820.GH12204@codiert.org>
On Feb 19, 2009, at 4:08 PM, Benjamin Krill wrote:
> * 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>
Tested on ppc 86xx, looks good.
Acked-by: Becky Bruce <beckyb@kernel.crashing.org>
-B
next prev parent reply other threads:[~2009-02-20 20:45 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 ` [PATCH 2/3] powerpc: setup archdata for {of_}platform via a single platform_notify Benjamin Krill
2009-02-20 20:44 ` Becky Bruce [this message]
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=6F644D32-0FEF-4D42-9735-4ECF5371009F@kernel.crashing.org \
--to=beckyb@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=ben@codiert.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).